Product onboarding form
How the product onboarding form for your suppliers is built: the steps, the settings and where each piece of data comes from.
Video transcript
In this video, your supplier adds a product step by step, and you validate it.
The form builds itself from what you already set up: your attribute groups, your tree and your channels.
General data, categorization and review always go; variants, content and images can be turned off.
Each group the supplier fills in is a step, and here you write its subtitle.
And you decide how a new family's SKU is built and which content texts they send.
Your supplier goes to “Send products” and picks “One product”.
What they enter saves itself, and waits for your review before it goes into your catalog.
The first step carries your subtitle. The brand is set by their access, and they enter the name.
They say whether it has variants, enter its code and fill in their group's attributes.
On the right, the live review tells them what's missing before they can send it.
The category comes from your tree: they pick it level by level.
If it came in shades or sizes, they'd enter each variant here; this is a single product.
They write the texts for your store, like the name and a short description…
…and upload the main photo, which is saved to your image library.
In the review they see everything together: what they entered and what you complete.
They send it for validation, and the product lands in your queue.
In Validation you see how it will look: its brand, its category and what your store asks for.
If everything checks out, approve it.
And it goes into your catalog with its category, photo and material, ready for you to generate its description.
That wraps up the “Suppliers” series. Next up: “Connections”.
What it is
The form a supplier uses to submit a product isn't something someone designs: it builds itself from what you already configure in Bruxel. The steps are your attribute groups, the fields are their attributes, the category comes from your tree and the requirements from the channels you mark.
In Settings → Product onboarding form you see it all together and adjust the little that doesn't live anywhere else. An administrator changes it; the rest of the team reads it and your suppliers don't see it.
The steps
The form starts with the product's identity (brand, name, structure and barcode) and categorization, and ends with the review: those three blocks always go. Variants, content and images can be turned off. Without variants, the form only takes single products; without content or images, that data isn't asked for and doesn't travel on approval.
Each attribute group you mark «Filled in by the supplier» is a step: its name is the title and you write the subtitle here. Move them up or down to change the order; it's the same order as the sections of the product page.
The settings
Families and variants: whether a family varies by a single axis (color or size) or by several, which attributes are offered as axes and what is asked for each variant, such as the hex color or the initial stock.
Parent SKU: the template used to build the code of a new family. Each piece comes from the brand, from a code of the category the supplier picks, or the supplier types it: the supplier code and the sequence number. The preview shows how it would look with a category from your tree.
Also the content texts that are asked for, which root of the tree belongs to your system and which to the site (the site's decides the attribute family), what «How it will look» shows and the fields prefilled with the brand's codes.
What's configured elsewhere
Which channels count for the supplier requirements is chosen in Channels, and the capture rules (when a field is asked for, when it's hidden and where its value comes from) on each attribute's page. This screen links to both.