Skip to main content

AI content

Test prompts on real products Nothing saves until you apply.

Load a real product, generate a field, and read the generated text next to the value that is stored today.

  • 7 prompt modes
  • Current and generated side by side
  • Your recent results stay switchable

Key features

  • Seven fields to work on

    Description, short description, title, SEO meta, product attributes, image alt text and web research, each with its own settings.

  • Tone, industry and length

    Set the voice, say what you sell, and cap the length. The character count and the field's limit sit under the output.

  • Nothing is applied by accident

    Generating writes nothing. Apply is a separate button and it only touches the product you loaded.

Why test first

Why the first prompt rarely works

Wording that produced a good description for one product often collapses on the next one, and a catalog is where you find that out the expensive way.

  • The first draft is always too generic

    A prompt written in the abstract produces copy that would fit any product in the category. Reading it next to a real record is what makes that obvious.

    Result: you fix the prompt instead of four hundred descriptions.

  • Length rules break quietly

    A meta description that runs past the limit gets cut by the search engine rather than by you, and nothing in the catalog flags it.

    Result: the character count and the limit are visible while you tune.

  • Nobody wants to test on live data

    Trying a prompt on real products usually means writing to them and undoing it afterwards.

    Result: generating and applying are two separate actions.

How it works

Load a product, choose a field, compare

Three steps, and the third is where you decide whether the prompt was any good.

  1. 01

    Load a product

    Step 1

    Pick a real product from your catalog. Its current values fill the left panel, so every comparison is against what is actually stored.

    The lab is working on your data instead of an example.

  2. 02

    Choose a field and configure it

    Step 2

    Pick the field to work on, set tone, industry and target length, and start from a saved prompt or one of your presets.

    A configuration you can save as a preset for next time.

  3. 03

    Generate and compare

    Step 3

    The generated text appears next to the current value with its character count. Quick refinements nudge the result without rewriting the prompt.

    You apply the version you picked, or change the prompt and run it again.

What you can work on

Seven fields, seven sets of settings

Each mode knows what its field is for, so the controls and the limits change with it.

  • Description

    The long product description, with tone, industry and a target length you set before generating.

  • Short description

    The teaser that has to work inside a listing, held to the length the channel expects.

  • Titles

    Product titles built from the attributes the record already carries, in the order your category reads best.

  • SEO meta

    Meta title and description with the character count and the limit visible while you tune.

  • Product attributes

    Structured attribute values instead of prose, derived from what the product already holds.

  • Image alt text

    Alt text per image, written from the product it belongs to rather than from the file name.

  • Web research

    Look the product up on the web from inside the lab and see what comes back before you merge it.

Compare

Compare before you apply

Generated text lands beside the value it would replace, never on top of it, so the decision is a comparison instead of an undo.

  • Current and generated, side by side

    Both panels carry a character count, and the generated one warns when it runs past the field's limit.

  • Refine without rewriting

    Quick refinements adjust the result, so a small correction does not mean editing the prompt again.

  • Your recent results stay

    The last few results per field stay switchable, so you can go back to the one that read best.

The two panels never merge: your stored title and description stay on the left, and anything the AI writes appears on the right, where you read it before it is saved.

FAQs

Prompt Lab questions, answered

What you can generate, what testing does to your data, and how a prompt you tuned here reaches the rest of the catalog.

Still have questions?

Can't find the answer you're looking for? Please get in touch with our team.

Contact Support

Seven things: the long description, the short description, product titles, SEO meta, product attributes, image alt text, and web research on the loaded product. Each one is its own mode with its own settings, because a title and a meta description do not need the same controls. It does not generate images, only the text about them.

No. Generating produces output in the lab and writes nothing to the product. Apply is a separate button and it only touches the single product you loaded. Running a prompt across a selection is a different action, in the enrichment modal on the product grid.

Yes. Save it to your Prompt Library and it is available to the whole workspace, and to the bulk enrichment run. The per-mode settings can also be kept as a preset, so the tone, industry and length you settled on come back the next time you open that mode.

Two ways. Tone and industry are controls you set per run, which is enough for a quick test. Anything more specific comes from the Knowledge Library, which the lab reads along with your prompt: the phrases you use, the ones you avoid, who you are writing for.

It keeps your recent results per field so you can switch back to an earlier one while you are working. That is a working history for the session, not a permanent audit log of everything the AI has ever written. Anything you want to keep goes into the Prompt Library or gets applied to the product.

Name the audience in the prompt rather than describing the product, set the industry so the vocabulary matches your sector, and lower the target length: short copy forces the model to pick something specific. If it still reads like anyone's catalog, the Knowledge Library is usually the missing piece.

Next step

Test a prompt on your own product

Load one product, generate the field, compare it with what is there. Nothing is saved until you apply it.