Generate descriptions
What generating costs, how a batch differs, what web search adds, and what happens when something goes wrong.
Video transcript
In this video, you'll generate your first product descriptions with AI.
With your catalog imported, Bruxel suggests starting with three products.
Three are enough to hear how the content sounds before you generate the whole catalog.
The button shows the cost before charging: three products, 21 credits.
A batch costs less than generating one by one.
The batch runs in the background, so you can keep working in the meantime.
It's finished: all three products are ready.
And you're only charged for the products that came out right.
Back in the catalog, those three now say “Published” and they are more complete: they have their descriptions.
The record has what the customer reads: a product title, a short and a long description, the benefits and the features.
Set apart, the technical side: the meta title, the meta description, the keywords and the URL.
Plus the text for social media and, for AI assistants, a context block and the product's structured data.
If something's off, correct it with an instruction or edit it by hand.
In the next video, you'll export your records to your store.
What it costs
Everything is measured in credits. One description costs 10 credits.
| Action | Credits | Note |
|---|---|---|
| Generate one product | 10 | Immediate result. |
| Generate as a batch | 7 | Per product. Cheaper, but slower. |
| With web search | +5 | Added per product. |
Multiple languages
The cost multiplies by each output language you have configured: two languages are two generations. Your balance is checked against the total before starting, so you do not end up halfway.
The batch
A batch sends many products together and costs less. In exchange it is not immediate:
- Up to 500 products per batch.
- Credits are reserved on launch and whatever is not processed is refunded to you.
- If you cancel, whatever was still pending is refunded.
Web search
When you enable it, the AI looks up public information about the product before writing. It helps when your feed brings little more than the name; if you already have complete attributes and context, it adds less and costs more.
Descriptions rejected for quality
Before accepting one, Bruxel checks that the description has no filler text, no broken HTML, and is not in the wrong language. If something fails, it is flagged and not published. You can generate it again, or mark it as valid if it looks fine to you on review.
Correcting a wrong fact
If a description came out with a wrong fact —the product type, a material, a use— don't fix it field by field: on the product page, hover over any generated field and use “Correct”. Write what's wrong as you would tell a copywriter (for example, “this is not a drill, it's a hammer drill”) and the whole product is regenerated incorporating the correction. It costs the same as regenerating.
- The correction stays with the product: it applies to every future generation —batches included— and in all your languages, until you remove it from “Active corrections” on the product page.
- You can have up to 10 active corrections per product. If you hit the limit, remove one that no longer applies to add another.
- Correct or edit by hand? If the fact is wrong, correct: the AI rewrites all the content coherently and remembers it for next time. If you just want to touch up a sentence, “Edit by hand” is free and doesn't regenerate anything.