- Bruxel.AI Blog
- Use case: 500 supplier products a month without the spreadsheet ping-pong
Use case: 500 supplier products a month without the spreadsheet ping-pong
By Manuel Mattar4 min read
In short
In this example, the retailer stops receiving spreadsheets by email: each supplier signs in to Bruxel limited to their brands, enters data in a form that follows the catalog rules or uploads the template with validation up front, and the team approves or sends back with a reason from a single Validation queue.
This is an example scenario, not a customer. The numbers belong to the example and help size the problem; they are not measured results.
The situation
A hardware and home retailer works with about 40 suppliers and onboards around 500 new products a month. Today the process is the usual one: the buyer sends an Excel template, the supplier fills it in their own way, someone on the catalog team fixes it, asks for what is missing and waits for the answer. Column names change from one supplier to the next, dimensions arrive in different units and colors are written three different ways.
The problem is not the volume: each product goes through several rounds of email before it enters the catalog, and nobody knows which round each product is in.
What the team does in Bruxel, step by step
1. Organize the product record before opening the door
In Catalog → Attributes, the team splits attributes into groups and marks as “Filled in by the supplier” the ones that really belong to the supplier: dimensions, material, package contents. Everything else (for example, attributes decided by the commercial team) stays out: the supplier sees it with a lock saying the retailer completes it.
In Channels → Channels & templates, the team marks its main channel as “Counts toward supplier requirements”. On their products, the supplier then sees what is missing for that channel, without seeing the channel name or its columns.
2. Review the form the supplier will see
In Suppliers → Sign-up form the team sees the full onboarding flow, built from what it already configured: identity, categorization, variants, one step per group the supplier fills in, content and images, and the review. There it adjusts what lives nowhere else: whether families vary by one or several axes, the parent SKU template and the content texts it asks for. On save, Bruxel checks that everything exists in the organization.
3. Invite each supplier limited to their brands
In Account → Team, for each supplier: their email, the “Editor” role, “Limit to their brands” and their brands. They are limited from the very first moment, with a short menu and the “Supplier portal” label. They do not spend credits, do not import or download and do not see other suppliers.
4. The supplier sends: one at a time or by file
From Send products, the supplier picks a route:
- One product: the step-by-step onboarding. It saves on its own; if they close the tab, they pick it up from My uploads with “Continue”. On the right, “How it will look” and “Live review” tell them what blocks the submission before they send it.
- Several products: they download their department template in Excel or CSV and upload it, up to 5,000 rows. “Review” applies the same rules as the single onboarding and says what goes in, what goes in with a warning and what does not. What does not go in is downloaded with “Download rows with errors”, with the reason, to fix and upload again. They can send only the valid rows, or a pilot first.
In the example, the small suppliers use the form and the five largest use the template.
5. The team validates in a single queue
Submissions wait in Suppliers → Validation. Approving runs the same import as always. Sending back requires a reason, which reaches the supplier in the bell and by email and which they read in full in My uploads. A file of more than 500 rows is approved in the background, with its progress in view; if something fails, nothing goes in and the submission returns to the queue with the reason.
6. Track each upload
In My uploads, “View journey” shows where each submission is: sent, reviewed, imported and, once in, its product records, its publication and its delivery.
What gets solved
- The spreadsheet stops going back and forth: the supplier enters data with the catalog rules and knows right away what is missing.
- Values arrive normalized because the form uses the attributes and lists the retailer already has.
- There is a single queue, with history: who sent, who approved and why something was sent back.
- Each supplier sees and edits only their own products.
What does not get solved
- The initial setup is the retailer's work. If attributes are not split into groups, the supplier writes no attributes: the onboarding only asks for identity, category, content and images.
- Review is still human. Bruxel validates rules; deciding whether a product is worth listing is the team's call.
- Products without a brand fall outside any brand scope, and if an import changes a product's brand, that product moves into another supplier's scope.
- Large suppliers still fill in a file. What changes is that the file is validated before it is sent, not after several rounds of email.
- AI descriptions are not generated by the supplier: generating spends credits and belongs to the retailer's team.
To go deeper, read the guides on the supplier portal, the sign-up form and scopes, or the Suppliers, Import and Catalog pages.
Frequently asked questions
Can the supplier create products directly in the catalog?
No. What they send, by form or by file, waits in Validation and does not exist in the catalog until someone on the team approves it. Edits to existing products of their brands do go in directly, with their name in the history.
Does the supplier spend credits or see my channels?
No. A supplier does not spend credits, does not import or download, and does not see channels, team, settings or other suppliers. On the product page they see what their products are missing for the channels you mark, without the channel name.
What about a supplier who sends hundreds of products at once?
They use Several products: download their department template, fill it in and upload it, up to 5,000 rows. Before sending, Review tells them which row goes in, which goes in with a warning and which does not, with the reason.
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
· 4 min read
Use case: ecommerce, merchandising and master data in a staged workflow
A step-by-step example: three teams and an ERP hand off each product through a staged flow in Bruxel, with tasks, comments, approval and a board.
· 4 min read
Use case: a tender with datasheets, certificates and artwork in one package
A step-by-step example: a manufacturer gathers datasheets, certificates with expiry dates and approved artwork for hundreds of products in one ZIP for a tender.
· 4 min read
Catalog reports in Bruxel: from data to decision without building sheets
How Reports and Analytics work in Bruxel: periods, filters, favorites, scheduled sends, catalog health and the PDF quality report.