AI content in Bruxel: brand voice, generating and translating

By Manuel Mattar4 min read

In short

In Bruxel you set your brand voice once —languages, form of address, tone, context and forbidden words— and the AI writes every product page with it from your data. You generate one by one or in batches, fix a wrong fact without rewriting by hand and translate from the primary language.

The problem it solves

Writing thousands of product pages by hand does not scale, and asking a generic AI to write them produces texts that do not sound like your brand, repeat claims your legal team does not approve or make up data. The note on brand voice explains what a voice is and why it gets lost. Here we describe how Bruxel does it, from the Content area of the menu: Generate, Batches, Activity and Brand voice.

How it works in Bruxel

Step 1: brand voice

The voice is set once and applies to the whole catalog. In Content → Brand voice you define:

  • the output languages and which one is primary;
  • the form of address: formal, informal or neutral;
  • the tone your brand should have;
  • the brand name and context, what one of your copywriters would know and the AI does not;
  • forbidden words: competitors, terms your legal team does not approve.

You also pick a curated template, which decides which fields are generated: SEO name, short and long description, bullets, meta title, structured data and more. The method behind each field is maintained by us and runs on the server; you control the voice and your catalog's attributes. By default, Bruxel writes without efficacy, health or guaranteed-results claims. The brand voice guide explains each setting.

Step 2: generate

The AI writes from what you already know about the product: its attributes and the source data you kept when importing. There are three ways:

  • One product, with an immediate result: 10 credits.
  • In a batch, up to 500 products: 7 credits per product. Credits are reserved at launch and whatever is not processed is refunded; you follow it in "Batches".
  • Everything in a filter: with a filter set —a family, a brand, the incomplete ones— the panel tells you how many are missing and what it costs before charging. It only sends products without any generated description.

Web search adds 5 credits per product and helps when your file carries little more than the name. The cost is multiplied by each output language, and Bruxel checks your balance covers the total before starting. You are only charged if the generation succeeds. The generating descriptions guide has the full table.

Step 3: fix a wrong fact

If a page came out with a wrong fact —the product type, a material—, use "Correct" on the product page and write what is wrong as you would tell a copywriter. The product is regenerated with the correction, which stays with it for future generations and in all your languages (up to 10 active per product). It costs the same as regenerating. If you only want to touch up a sentence, "Edit by hand" is free.

Step 4: translate

With the page published in the primary language, "Translate to…" carries it into another language instead of writing it again: it costs less and says the same thing. Codes, the INCI list, JSON-LD, the friendly URL, the hex color and proper names are copied as they are; they are not even sent to the model. If the translation comes back practically identical to the original, it is not published or charged. The translating a product page guide has the details, and the note on translating your catalog covers the market side.

An example

As a hypothetical example: a personal care brand with 800 products in Spanish wants to sell them in English too. It sets the voice to an informal form of address, adds two terms its legal team vetoed as forbidden words and keeps the health-claims block on. It first generates 20 products one by one to check the tone, adjusts the brand context and launches the rest by filter, in a batch. With the Spanish pages published, it translates into English.

Who it is for

For ecommerce and content teams that need consistent product pages at volume, and for whoever answers for what gets published. Generating everything in a filter takes an operator or higher.

What you need to start

Your catalog loaded with whatever data you have, the brand voice set up and credits. Credits do not expire and the price per description drops with volume; see pricing. You can set a weekly or monthly spending cap in Account → Credits. The module summary is on AI content.

Honest limits

  • Quality depends on your data: with little more than the name, the page will be generic or need web search.
  • A batch is cheaper, but descriptions arrive in a few hours, not instantly.
  • A description with filler text, broken HTML or in another language fails the quality check and is not published.
  • The translation does not update itself when you change the original.

Frequently asked questions

How much does generating a description cost?

10 credits per product on the spot, 7 per product in a batch and 5 more if you turn on web search. The cost is multiplied by each output language, and you are only charged if the generation succeeds.

Can the AI write health or results claims?

Not by default: Bruxel writes without efficacy, health or guaranteed-results claims. You can turn that off, and then what you publish is your responsibility.

Does the translation update itself if I change the original?

No. It tells you it came from an earlier version and offers to translate again. Redoing it costs credits, so the decision is yours.

Sources

  1. Natural language generation (Wikipedia)
  2. Machine translation (Wikipedia)

About the author

Manuel Mattar

Founder of Bruxel.AI

In 2014 he founded Wolf Sellers, an e-commerce agency in Mexico City, and later Bruxel.AI, the AI-powered PIM.

See all posts by Manuel Mattar

Try it with your catalog

Create your free account and try Bruxel with your own products using the welcome credits.

Keep reading

AI content in Bruxel: brand voice, generating and translating