- Bruxel.AI Blog
- AI in your product catalog: where it helps and where you need human review
AI in your product catalog: where it helps and where you need human review
By Manuel Mattar3 min read
In short
AI pays off in the catalog when it works on real product data: writing descriptions, filling attributes, proposing categories, translating and describing images. It fails when information is missing and it fills the gap with something plausible but untrue. That is why it works with a simple rule: AI proposes and a person reviews before publishing.
Where it really helps
A catalog has a lot of repetitive work that needs judgment but not creativity: thousands of descriptions with the same structure, attributes sitting in a spec sheet, categories that can be inferred from the name. That is where AI pays off:
- Descriptions from the product data, in the brand's voice.
- Attributes that can be read from the description or the source data.
- Categories proposed from the name and attributes.
- Translations of approved product records.
- Alt text for images.
- Photos of the product in a scene or with a model, from real photos.
In every case, the work shifts from writing from scratch to reviewing a proposal, which is much faster.
Where it gets things wrong
AI is very good at producing text that sounds right, and that is exactly the risk. It gets things wrong when:
- A fact is missing and it fills the gap with something plausible: a dimension, a material, a compatibility.
- It exaggerates. It turns “water resistant” into “waterproof”.
- It mixes up similar products when the data is ambiguous.
- It copies the wrong tone if nobody told it how the brand sounds.
None of these mistakes shows on a dashboard; they show in a return or a review.
The process that works
The rule is simple: AI proposes, a person approves. For that rule to scale:
- Start from real data. AI works with what is in the product record; the more complete it is, the better the result.
- Define the voice and the limits in writing: formality, tone and banned words.
- Review a sample at first and adjust the rules before generating the whole catalog.
- Approve before publishing, with a clear step and an owner.
- Keep the history, to know what AI generated, what a person changed, and to be able to go back.
What Google says
Google does not penalize content for being made with AI. Its position is that appropriate use of AI is not against its guidelines, and that what matters is that the content is helpful and reliable. What it does consider spam is mass-producing content, with or without AI, with the primary purpose of manipulating rankings. A reviewed product page, based on real data and useful to the buyer, is on the right side.
How to know whether AI is helping
Measure before and after with the same numbers:
- Time per published product record, from import to approval.
- Share of proposals approved without changes. If it is low, source data or voice rules are missing.
- Errors that reach the buyer: returns or questions caused by wrong data.
- Complete records per channel every week.
If time goes down and errors don't go up, AI is doing its job; if errors go up, check the source data before blaming the tool.
Questions for your AI vendor
- Is my data used to train your models?
- Can I see what the AI generated and what a person changed?
- How much does each thing I generate cost, before I generate it?
- Are generated images disclosed as such?
How Bruxel handles it
In Bruxel AI works on each product's data and in your brand voice: it writes descriptions for search engines and AI assistants, fills attributes, proposes categories, translates, describes images and generates photos from real photos. Nothing is published without review, every product record keeps its history and generated images are disclosed as such. A customer's catalog and descriptions are not used to train AI models, with the disclosed exception of the 3D object, which is optional. The guide to generating descriptions shows the process and the PIM page the rest of the product.
The video tutorial
Chapters
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.
Frequently asked questions
Does Google penalize AI-written content?
Not for being AI-written. Google says appropriate use of AI is not against its guidelines; what is against them is mass-producing content with the primary purpose of manipulating rankings.
Can AI make up data about my products?
It can, if information is missing. That is why it should start from the product's real data, be told not to state what is not in it and be reviewed by someone before publishing.
Is my data used to train AI models?
It depends on the vendor; always ask. In Bruxel, a customer's catalog and descriptions are not used to train AI models; the only exception is the 3D object, which is optional and disclosed.
Sources
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 MattarTry it with your catalog
Create your free account and try Bruxel with your own products using the welcome credits.
Keep reading
· 3 min read
Product attributes: the guide to a complete catalog
Attributes turn a product record into data you can filter, compare and send to every channel. What they are, how to group them and how to complete them.
· 4 min read
How to choose a PIM: ten questions to ask before you sign
A neutral guide to choosing a PIM: what to ask about data, channels, team, suppliers, integrations, AI, price and exit, and how to test it with your catalog.
· 3 min read
PIM alternatives: how to compare the options on the market
The kinds of PIM on the market and what each vendor publishes about its editions and pricing on its own site, with date and source, so you can compare them.