Templates
A template is a saved set of settings for one task, so you do not have to rebuild the same job by hand every time.
Your shop Configuration holds one set of settings per task. That is enough as long as you always want the same thing. As soon as you want two — a short punchy description for accessories and a long technical one for machines, say — you save each of them as a template and pick the right one when you start a job.
Owners, Managers and Editors can create, edit, duplicate and delete templates. Auditors cannot. See Team & roles.
What a template is — and is not
- A template belongs to exactly one task. A product-description template cannot be used for meta texts. You choose the task when you create the template and it cannot be changed afterwards — if you picked the wrong one, create a new template.
- A template is only settings. It contains no products, no categories, no languages and no model choice. You still pick those every time you start a job.
- A template does not run anything by itself. It is a preset you load.
Jobs copy the settings — they do not follow them
This is the single most important thing to understand about templates, and the page says it at the top: “Jobs copy the settings when they start — editing or deleting a template never changes existing jobs.”
When you create a job with a template, the app takes a copy of the template’s settings and stores that copy with the job. From that moment the job is on its own.
- Edit the template afterwards → running and finished jobs are untouched. Only the next job you create picks up the change.
- Delete the template → existing jobs keep working, and keep showing the template’s name for reference. The delete confirmation says so: “Existing jobs are not affected.”
You can tidy up your templates whenever you like without wondering whether you are about to change what a job that is halfway through is doing. And a finished job stays a faithful record of the settings it actually ran with.
The Templates page
- Open your shop.
- In the left sidebar, click Templates.
You get a table with Name, Module (the task it belongs to) and Updated, plus the buttons View, Duplicate and Delete on every row. If you have none yet, the page says No templates yet and offers New template.
Creating a template
- On the Templates page, click New template.
- If your shop has more than one task, a row of task buttons appears above the form — Product description, Meta content, Category description and so on. Click the one you want. The form reloads with that task’s settings.
- Give it a Template name. Use a name you will recognise in a dropdown six months from now: “Accessories – short” beats “Template 3”.
- Fill in the settings. These are the same fields as the matching card in Settings › Configuration, with the same explanations underneath them.
- Press Create template.
The line under the heading reminds you which task you are editing: “Module: …”.
A Multi-field text template carries the shared settings — the system prompt, temperature, token budget, keyword research. Which fields are written, and the instruction for each one, is composed in the job wizard itself and belongs to that one job. See Multi-field text.
Prompt boxes in the template form always show their available placeholders as small clickable chips underneath, labelled Insert variable:. Clicking one drops it into the text at the cursor. (In the job wizard these chips are hidden unless you have expert mode on — in the template form they are always visible, because building prompts is what this screen is for.)
Write result to
Templates for product and category descriptions carry a Write result to block:
- Description — the normal description field in your shop. The default.
- Custom field — then a second dropdown, Target custom field, appears with the list of text custom fields that actually exist in your shop. Pick one.
This is the only place in the app where you can pick a specific custom field, because the list has to be fetched from your connected shop live.
If the custom field you pick is not translatable, the form warns you straight away: a value generated for one language would be overwritten by the next one. Only the text in your shop’s default language is written; the other languages are skipped.
Product context
At the bottom of the form, text templates have a Product context block: “Pick which product properties and custom fields are added to the prompt for extra accuracy. Options come live from the connected shop.”
- Property groups — the property groups your shop uses (colour, material, size, …). Leave everything unticked to include every group; the label then carries an all badge. Tick a few to narrow it down.
- Custom fields — your own product fields. Here it works the other way round: only ticked fields are added. Nothing ticked means nothing extra is sent.
The point of this block is accuracy. The more real facts about a product the AI is handed, the less it has to guess — and the app instructs the AI not to invent anything that was not in the input. If your descriptions come out vague, this is the first place to look.
Both lists are read from your Shopware shop at the moment you open the form, so they always show what is really there.
When your shop cannot be reached
If the app cannot talk to your shop while you are editing a template, an amber box appears at the top: “We cannot reach your shop right now” — the lists below are empty because we could not ask your shop which fields it has, not because it has none.
In that state saving is blocked. That is deliberate: saving would store an empty selection over your real one and silently drop settings you had carefully chosen. Your saved settings are untouched. Fix the connection (see Connect your shop), then come back.
Looking at a template
Click a template name, or View on its row. The detail page lists every setting with its saved value, marks the ones still at their factory value with a default badge, and shows the two context lists: Property groups (All property groups when nothing was narrowed down) and Custom fields (None when nothing was picked).
From here you also get Edit, Duplicate, Delete and Use in new job.
Duplicating and deleting
Duplicate makes a copy immediately, named like the original with (Copy) appended. This is the right way to build a variant: duplicate the template that already works, rename it, change the one setting you wanted different. It is also a cheap safety net before a risky edit.
Delete asks first: “Delete template …? Existing jobs are not affected.” Confirm and it is gone. Jobs that used it keep running and keep their settings; only the preset disappears.
Using a template in a job
Two ways in, and they end up in the same place:
- From the template. Open it and press Use in new job. The job wizard for the right task opens with this template already selected. (The button is hidden if that task is not enabled for your shop, and if you do not have permission to create jobs.)
- From the wizard. Start a job the normal way and use the Template dropdown in the What gets generated card at the top. Its first entry is Shop configuration — that is the “no template” option, and it means the settings from Settings › Configuration. Below it, your templates for this task.
Choosing a template reloads the options shown further down the page so you can see exactly what you are about to run — and you can still adjust anything for this one run without touching the template.
If a job also generates a second task in the same run (the Also generate … checkbox), that second task gets its own Template dropdown, so you can combine, for example, a specific description template with a specific meta-text template.
The job page later shows which templates a run used, as small badges under the heading labelled Templates:.
Where to go next
- Generating content — the job wizard from start to finish.
- The generation modules — what each task produces and which settings it offers.
- Configuration — the shop-wide defaults a template starts from.