For every field, Elbuz gives the model a ready-made instruction; you can replace it with your own — with the warranty, manufacturer, delivery city or category-specific requirements.
When you need this:
- Default descriptions work for you — auto mode fills every empty field from a default prompt; nothing to write.
- The description needs the price or manufacturer — your own prompt inserts any catalog column.
- A category needs its own requirements — a category template overrides the universal one.
- Don't want to risk a thousand descriptions — “Test” shows the answer for one product and saves nothing.
Where to start: “Text generator” → “Generation templates” tab → “Universal template”.
What generator prompts can do
- Write from ready-made default prompts — the name, attributes and store data are filled in automatically.
- Use your instruction instead of the default — with any catalog columns.
- Keep separate prompts for a category — they override the universal template.
- Show the result on one product — before a bulk run.
How to create a template for a category
The “Generation templates” tab is split in two: the template list on the left, the editor for the selected one on the right. At the top are four counters: “Templates”, “Active”, “Auto mode”, “Own prompts”. The last one shows how many fields you've filled with your own instructions; while it's zero, only the default prompts are used.
Until you select a template, the right half shows the three-step cheat sheet “How to get texts for the whole catalog”: fill in “Store data”, open the universal template, click “Start generation”. Clicking any template in the list replaces the cheat sheet with the editor.
The “New template” button asks for a category name — start typing and Elbuz suggests matching ones. You can't create a second template for the same category: Elbuz returns the existing one.
Changes in the editor are saved automatically, just like on the “Store data” tab. Click the “Active” toggle to switch it: a disabled template doesn't take part in a run. You can delete a category template with the trash button — its prompts are deleted with it.
A category template only applies in a run started for that specific category (why).
1
Own prompts tile2
New template3
Universal template4
Scope chip5
Start generation- Own prompts tile — while it shows zero, only the built-in presets work.
- New template — creates a separate prompt set for one category.
- Universal template — works for the whole catalog.
- Scope chip — shows what the template applies to.
- Start generation — opens the launch window.
What automatic prompts write
1
Automatic prompts2
Own-prompt counter3
Macro chip4
Prompt field5
Test- Automatic prompts — when on, empty fields use the built-in preset.
- Counter next to the sub-tab — how many prompts you wrote yourself for this entity.
- Macro chip — click copies the code to insert into the task text.
- Prompt field — your own text overrides the preset.
- Test link — checks the prompt on a single item (not clicked).
The “Automatic prompts” switch in the “Field prompts” card is on by default. In this mode, fields you haven't filled in get a ready-made default prompt from the library — you can open it with the “AI Templates” button in the top bar.
The default prompt for the full product description, for example, asks the model to write with H2-H3-H4 subheadings and lists, use the product's attributes, and explain what it is, how it's used, who it suits and what the benefit is. The instruction includes the product name, its attributes on one line as “name: value”, and the store data.
What auto mode does not include: price, SKU, manufacturer, stock and the product's category name. If you need these in the description, you'll have to write your own prompt.
Another limit of auto mode: there are no default prompts for “Extra field #1…#7”. If you select these fields in auto mode, no instruction for the model is built. These fields only make sense with your own prompt.
How to write your own prompt
Text you enter in a field overrides the default prompt. An empty field with auto mode on means the default prompt; an empty field with auto mode off means “don't generate anything”.
- Action or result
- Decision: the path depends on the answer
Three kinds of placeholders work in a prompt:
[name]— the name of the item itself: product, category or manufacturer;[store_name],[store_city],[store_country]and the other codes from the “Store data” tab, plus[language]— the name of the language the text is written in;{Product: Price}— any base catalog column by its name in the product grid. Name, Old price, Model, SKU (internal), Quantity, Warranty, Manufacturer and Short description are available the same way.
Example of your own instruction for the short description: Write a short selling description of the product [name] by {Product: Manufacturer}, up to 400 characters. Mention the warranty {Product: Warranty} and delivery to [store_city].
How many questions and reviews to ask the model for is set in the run window, in the FAQ and RV fields; leaving them empty means “take the number from the template”.
In that case, the number to the right of the “FAQ” and “Reviews” labels here in the editor applies: first from the category template if the run was started for that category, then from the universal one, and if it isn't set anywhere — three.
How to check a prompt with the “Test” button
Next to every field there's a “Test” link. It opens the small “Prompt test” window, where you enter the of an item — a product, category or manufacturer, depending on which tab you're on — and click “Generate”. The model's answer appears in the field below.
The test doesn't save the result to the card: it only shows what came out. But the request to the model is real and is billed just like a normal generation. Testing a prompt on one product is still cheaper than running a thousand and finding out the wording doesn't work.
Scenarios
Add the warranty and delivery city to the short description
What to do. In the template, on the “Products” subtab, enter your instruction in the “Short description” field with the placeholders {Product: Warranty} and [store_city] — as in the example above. Click “Test” and check the answer on one product.
What you get. For this field, generation uses your prompt instead of the default one, and the warranty from the product card goes into the text. The other fields are written from default prompts while “Automatic prompts” is on.
Have the model fill in “Extra field #1”
What to do. Expand “Additional fields” on the “Products” subtab and enter a prompt for “Extra field #1”.
What you get. The field is generated from your instruction. Without a prompt it would stay empty: there are no default prompts for extra fields.
Check the default prompt on your products before a run
What to do. Next to “Full description”, click “Test” for two or three products from different categories, one at a time.
What you get. You see what the model will write for each, and nothing goes into the cards. Don't like it? Enter your own prompt and test again. Each test is billed as one request.
What to do when a prompt doesn't work
| What you see | Why | What to do |
|---|---|---|
| You wrote a prompt in a category template, but the texts came out from the general one | The run was started for the whole catalog — then only the universal template is used | Start generation from that category's card or from its template with the “Start generation” button (one category) |
| You selected “Extra field #1”, the run finished, but the field is still empty | There's no default prompt for extra fields, and you didn't write your own | Write a prompt for this field in the template (your own prompt) |
FAQ
Do the product's price and manufacturer get into the default prompt?
No. Price, SKU, manufacturer, stock and category name aren't included in auto mode — only through your own prompt (how to write one).
Can I create two templates for one category?
No. If you try to create a second one, Elbuz returns the category's existing template.
Is “Test” billed?
Yes: the request to the model is real and costs the same as a normal generation of one field. The test doesn't write anything to the card.
What language should I write the prompt in?
In the catalog's main language — the one the generator writes the text in (which language the text will be in).
What happens if I turn off “Automatic prompts”?
Fields without your own prompt stop being generated: with auto mode off, an empty field means “don't generate” (your own prompt).
Where to find it and who has access
- Menu
- Directories → Base product catalog → text generator → “Generation templates” tab
- Access right
- access to the “Text generator” window: whoever can open it can edit the templates
- Prepare
- “Store data” — it's inserted into the default prompts
Related topics
- If you need the big picture of the generator — SEO text generator.
- If your prompts are ready and it's time to run — how to start generation.
- If a formula without a model is enough for the Title — fixed text without AI.
- If descriptions lack product properties — fill in the attributes: default prompts include them in the instruction.
