Bruxel modules

Review before publishing and AI-powered quality control

Decide what gets published and catch in time the description that doesn't match the product.

What it solves

With thousands of generated product pages, reviewing them one by one isn't realistic, and publishing without review is risky. Bruxel separates who produces from who approves, and checks every description before it reaches your channels.

  • Optional editorial workflow: new content waits in «Waiting for approval» and an administrator approves it or rejects it with a reason, without touching what was already published.
  • Free checks on every description: empty or cut-off fields, filler text, the wrong language or broken HTML, plus a flag on claims of cures, clinical studies or guarantees.
  • Detected issues: an AI check that looks for descriptions about another type of product, confirmed by a second reviewer that keeps the evidence.

What it looks like

Queue of descriptions waiting for approval in Bruxel, with demo products, their language and notices such as «First publication».
The approval queue, in Content → To publish. · Demo data

Who it is for

  • Organizations where one person generates and another decides what gets published.
  • Catalog quality leads who need to find errors without reading everything.
  • Teams that want to approve every text before it reaches their store or a marketplace.

What it needs

  • An administrator turns the workflow on in Content → Brand voice; sending to review takes Editor or above, and approving, an administrator.
  • The Detected issues check costs 2 credits per description, up to 2,000 per run, and is launched by an Operator or above.
  • The automatic checks on each description cost no credits.

Its guides

Read more: Review and quality in Bruxel: approve before you publish

Try it with your own catalog.

Review before publishing and AI-powered quality control · Bruxel