On this page
Before you start
Both options live on the same screen of the "PIM tabs" wizard, and they do two different things.
AI enrichment writes values for marketplace fields, using your own product data as its input. It is what fills a field the marketplace asks for and you never had, such as a short description or a bullet.
Translation takes values you already have and puts them in the language of the marketplace. Translate your products walks through that flow.
You switch them on with "Would you like to enrich with AI?" and "Would you like to translate?". Answer Yes to either and the checkbox "I waive any error claims against e-tailize." appears, which you have to tick before "Next" turns on.
What happens next
The next screen, "Confirm fields", is where you decide per field. If you answered Yes to "Would you like to translate?" and picked a language, every row carries a translate toggle, green when the field is translated. The fields the AI can write also carry a "Generate with AI (beta)" button, green when it is on.
The two exclude each other on one field. Switch the AI on and that field's translate toggle greys out, and the value box locks, because the AI is going to write it. Switch the AI off again and the box unlocks, translation comes back and the field's default mapping returns, so you can map it yourself after all. The toggles start on. With a translation language every field that can be translated already has its translate toggle on, and after Yes to AI every field with a prompt already has its AI button on and its mapping cleared. Switch a toggle off and that field is used exactly as you mapped it. The product's own name and description are always translated on a run with a translation language, whether or not their translate toggle is on. Translation writes the new text into the field itself, so the tab's own previous value is overwritten with no backup. The source language text is still on the "Main product" tab, because translation only runs on the fields of the marketplace tab.
After "Create tab" the work runs in the background. Tabs stay pending while it runs and the app tells you when the batch is done.
You do not have to decide everything up front. On a tab that already exists, the fields the AI can write carry the same button, so you can have one field generated later even though you created the tab without AI. On a bol tab there are also "Ai optimize title" and "Ai optimize description", which rewrite the text that is already in the field. Those two appear only when that access is switched on for your account.
Common problems
A field has no AI button. Not every field is set up for AI: that depends on the marketplace and the category, so the button only shows on the fields where it is available. Ask support if a field really should have one.
A tab comes back as failed. Enrichment does not retry a field on its own, and the failed tab stays where it is. Use the AI button on the field itself to generate that field again on the existing tab, or fill it by hand. Want the whole run again, then remove the tab first with the cross on the tab, because a second tab for the same marketplace is refused with "The product version already exists for this marketplace." The message "Too many requests at the moment. Please try after an hour" means exactly that: wait, do not resubmit in a loop.
FAQ
Does the AI touch my images?
No. Both features work on text. Images are never generated, edited or translated, and image fields are left out of the data the AI reads.
Do I have to check the result?
Yes. The content is machine made and that is what the waiver is about, so read the generated and translated fields before you list them.
Why are my dropdown fields untouched?
Because their values have to match the list the marketplace allows. Fields with a fixed list of values are never translated, and neither are fields that follow a reference to your own data.
Was this useful?