- Bruxel.AI Blog
- The Bruxel supplier portal: onboarding, bulk upload and validation
The Bruxel supplier portal: onboarding, bulk upload and validation
By Manuel Mattar4 min read
In short
The Bruxel supplier portal lets each supplier join your organization limited to their brands, maintain their product pages and send new products through a step-by-step form or a template of up to 5,000 rows. Nothing enters the catalog until your team approves it in the validation queue.
The problem: the supplier knows, but enters data elsewhere
The supplier is the one who knows the product best, and yet their data arrives by email, in a template everyone fills in their own way. The article on onboarding products with suppliers explains why it pays for the supplier to enter data directly in your system. Here we describe how Bruxel does it with the Suppliers module.
How it works in Bruxel, step by step
1. Invite the supplier, limited to their brands
In Account → Team you type their email, choose "Editor" (or "Viewer" if they should only look), tick "Limit to their brands" and pick their brands. They join already limited: there is no moment when they see the full catalog. The portal is not a separate product: it is the same organization, with a shorter menu and, if you have one, your logo in the header.
The scopes guide explains how brands, categories, families and attribute groups add up.
2. What they see and what they write
The supplier sees a home page with counts for their brands, their products, "Send products" and "My uploads". They edit the base data of their products —name, category, family and images— and, among attributes, only those in the groups an administrator marks "Filled in by the supplier". Everything else shows with a lock. Their edits to existing product pages go in directly, with their name in the history.
On the product page they comment in the "With the supplier" thread; they do not see your notes in the "Internal" one. And under requirements they see what their products are missing for the channels you mark, without the channel's name or its columns. The supplier portal guide has the full list.
3. Send new products
A supplier does not create products directly: they send them for validation from "Send products", in two ways.
- One product: a step-by-step form that builds itself from what you already configure —general data, categorization, variants, one step per group the supplier fills in, content and images, and the review—. It saves itself, and on the right a preview tells what your system will receive, while a live review says what blocks the submission.
- Several products: they download their department's template in Excel or CSV, fill it in and upload it, up to 5,000 rows. "Review" applies the same rules as the single-product form and says what goes in, what goes in with a warning and what does not, with its row and column. They can send only the valid rows, or a pilot first.
The order of the steps, variants, the parent SKU template and the requested texts are adjusted in "Sign-up form". The sign-up form guide explains each setting.
4. Validate
Submissions wait in Suppliers → Validation. Approving is for operators and above and runs the usual import; a form submission also shows the preview and, channel by channel, whether the product comes out ready. Sending back asks for a reason, which reaches the supplier in the bell and by email. A file of more than 500 rows is approved in the background, and if something fails, nothing goes in.
5. Follow every upload
In "My uploads" the supplier sees each submission with its status —awaiting review, approving, approved, sent back or withdrawn— and resumes their drafts. "View journey" says where each submission stands, and the skipped-rows download gives back the rows that did not go in, with their reason.
Who it is for
A hypothetical example: a supermarket chain with 40 suppliers that send new products every month. Each supplier signs in limited to their brands; those who add a few products use the step-by-step form, and those who send hundreds use the template. The commercial team reviews everything in a single queue.
It serves retailers, distributors and brands that receive products from third parties.
What you need to get started
- Your attributes split into groups, and a decision on which ones the supplier fills in. If you mark none, suppliers do not write attributes.
- Your category tree and, if it applies, your families and variants.
- A brand on every product: a product without a brand is not in any brand scope.
- The channels that count for supplier requirements, marked in Channels.
Honest limits
- A supplier's scope depends on the brand text. If an import changes a product's brand, it leaves the scope of whoever had the first one.
- Only viewers and editors can be limited. If you raise a supplier to operator or above, they are no longer limited and see the full menu.
- Nobody who is limited can change a product's brand.
- A submission cannot be sent back or withdrawn while it is being approved in the background.
- Whatever the supplier sends for an attribute that is not theirs is skipped on approval.
To see the whole module, open the Suppliers page.
Frequently asked questions
Does the supplier spend my credits?
No. A supplier does not spend credits, does not import or download, and does not see credits, team, settings, channels, batches or metrics.
Can a supplier see other suppliers?
No. They only see their brands' products. If a brand has more than one supplier, those suppliers do share the comment thread with your team.
What if the supplier closes the tab halfway through onboarding?
The form saves itself while they type and when they change steps. They pick it up from My uploads, with Continue, at the step where they left off.
What happens to the rows with errors in a file?
Review says what goes in, what goes in with a warning and what does not, with its row and column. The rows that do not go in are downloaded with their reason, fixed and uploaded again.
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
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.
· 5 min read
Flows in Bruxel: each product's journey, step by step
How flows work in Bruxel: lanes, rules that mark a step done, the board, alerts and tasks on arrival. And what they don't do yet.
· 4 min read
Review and quality in Bruxel: approve before you publish
How Bruxel controls what gets published: editorial workflow, approval queue, automatic checks, detected issues and scheduled publishing, step by step.