Review and quality in Bruxel: approve before you publish

By Manuel Mattar4 min read

In short

Bruxel checks every description as it is generated and rejects any with filler, broken HTML or the wrong language. If you turn on the editorial workflow, nothing new is published until an administrator approves it. And the detected issues check looks for pages that describe another product type, with evidence.

The problem it solves

Generating with AI moves the bottleneck: it is no longer writing, it is knowing what can be published. Without a control, a page with a wrong fact reaches the store just like a good one. The note on approval workflows explains the pieces of a workflow in general. Here we describe the three layers Bruxel uses, from the Content area: To publish and Detected issues.

How it works in Bruxel

Layer 1: the checks on each description

When it is generated, each description goes through checks with no AI and no cost: empty or cut-off required fields, filler text, a language other than the one you asked for, unclosed HTML or fields that are too long. If something serious turns up, the description is marked "Failed quality check", is not published and is not charged. You can regenerate it or mark it as valid if it looks fine on review.

These checks also flag claims of cures, medical use, clinical studies, guarantees or prices, so someone sees them before approving.

Layer 2: the editorial workflow

Publishing a description is what sends it to your downloads, your channels and the API. Normally what you generate publishes on its own. With the "Editorial workflow" switch on (in Content → Brand voice, changed by an administrator), nothing new is published without approval. Everything goes by product and language: approving English does not touch Spanish.

The path is this:

  1. You generate or translate: the new version waits, unpublished.
  2. Someone with the Editor role or higher clicks "Send for review" on the product page.
  3. The description appears in the To publish queue, longest-waiting first.
  4. An administrator clicks "Approve and publish" or "Reject".

Each row in the queue carries signals to help decide: whether it replaces what is live or is the first publication, whether the quality check found problems and how many claims there are to review. If the check flagged something, approving requires ticking "Publish anyway". When rejecting you can write the reason: it stays in the product page comments and whoever generated the version is notified.

An administrator also has three tools: "Unpublish" takes the description out of your outputs in that language; "Go back to this version" publishes an earlier one and pins it; and scheduled publishing publishes a chosen version at the time you set, without going through the queue. If by then a newer version is published or the description is pinned, it is not published and you get a notice. The review and approval guide explains it step by step.

Layer 3: detected issues

Content → Detected issues launches an AI check that looks for descriptions that talk about another product type according to your source data. It works in two steps: first it flags candidates, and then a second reviewer, stricter and with web search, confirms or dismisses each one and keeps the evidence.

It costs 2 credits per description checked, up to 2,000 per run; what was already checked is not charged again. Each finding is resolved with "Fix category" (no cost), "Re-generate" (regenerates in all your languages, at its normal cost) or "Dismiss". The detected issues guide covers it.

An example

As a hypothetical scenario: a beauty store generates 2,000 pages in a batch. The automatic checks reject a few for cut-off fields, which are regenerated. With the editorial workflow on, the team sends them for review by family and an administrator approves starting with the ones that carry claims. Before a relaunch, it runs a detected issues check and finds a couple of pages that describe the product as something else; it fixes their category and regenerates them.

Who it is for

For organizations where someone answers for what gets published: a legal, brand or quality team. Also for anyone who just wants peace of mind: the automatic checks always run, even with the workflow off.

What you need to start

An administrator to turn on the workflow and decide who sends for review. For the detected issues check, credits and the Operator role or higher. Tracking is in Reports: "Pending approval" and "Publications and rejections". The module summary is on Review and quality; for the data errors worth watching, see the note on product data quality.

Honest limits

  • The detected issues check only reviews the product type, not spelling, style or SEO.
  • Only the first 50 candidates of each check go to the second reviewer; the rest stay to be reviewed.
  • One check runs at a time per organization, and if nobody opens it in 48 hours it closes itself and refunds the credits for what was not checked.
  • Turning the workflow off does not empty the queue: what is pending can still be approved.

Frequently asked questions

Does a new version remove what was already published?

No. What is published keeps going out to your downloads, channels and API while the new version waits for approval. If it is rejected, it goes back to draft and the published one stays the same.

Does the detected issues check review spelling or SEO?

No. It checks one thing only: whether the description talks about the right product type according to your source data. It does not review style, spelling or SEO.

Who can approve?

Sending for review takes Editor or higher; approving and publishing or rejecting, an administrator. A supplier or someone with access limited to part of the catalog does not see the queue.

Sources

  1. Quality control (Wikipedia)
  2. Workflow (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

Review and quality in Bruxel: approve before you publish