- Bruxel.AI Blog
- Use case: ecommerce, merchandising and master data in a staged workflow
Use case: ecommerce, merchandising and master data in a staged workflow
By Manuel Mattar4 min read
In short
This is an example scenario. A company splits the product page into groups per team, and an administrator designs a flow with a lane for master data, one for merchandising, one for ecommerce and one for its ERP. Each step is marked done by a rule, assigns tasks on arrival and the board shows where each product gets stuck.
This case is an example, not a customer: an imaginary company, with made-up teams and deadlines, to show how Bruxel's flows, tasks, comments and approval are used together.
The situation
A home appliance distributor onboards about 60 new products a month. Each one goes through three teams and one system:
- Master data captures dimensions, weight, warranty and supplier code.
- The company's ERP assigns its material code.
- Merchandising decides category, commercial attributes and family.
- Ecommerce generates the description, reviews it and publishes it to the store.
Today coordination lives in a shared spreadsheet and in messages: "is the code there yet?", "who has the new fridge?". When someone asks about a SKU, nobody can answer without asking three people.
Step 1: split the product page by team
In Catalog → Attributes, the administrator creates three groups —Master data, Merch and Ecomm— and puts each attribute in its own. The product page and the grid are ordered by group, so each team finds its part without scrolling through the whole page.
Step 2: design the flow
In Catalog → Flows → New flow, the administrator starts from a template and adjusts it. The flow has one lane per participant: the three teams, each with its attribute group, and the ERP as a system. For each step they choose which steps it depends on, when it is done, which products it applies to and its deadline:
- Master data ready: done when the group's "Ready for review" flag is set to Yes. The "Create this step's flag" button adds it to the team's group.
- ERP code: done when the code attribute has a value.
- Merchandising: depends on the two previous steps, with its own flag and a three-day deadline.
- Ecommerce: done when the description is published in every output language.
Before activating, "Try with a SKU" says where a real product would land with what is on screen, without writing anything. "Activate…" counts how many products would enter and what state each step would be in. Every save creates a version, with who saved it and what changed.
Step 3: the ERP reports, Bruxel does not execute
Bruxel creates nothing in the ERP. For the ERP step to move with what happens outside, the systems team registers it in Channels → Connected systems with its key name, its API key and its endpoint. From then on, the ERP can report an event through the public API, answer the notification Bruxel sends it or write the code to the product with its key. If the last thing that happened went wrong, the step is marked with an error and the journey stops until something good arrives.
Step 4: tasks and comments
Each team step assigns a task on arrival: "On arrival, assign a task to". The person gets a notification in the bell, the product shows up in their "My tasks" queue and, if the step has a deadline, the task is due with it.
Questions stay on the product page, not in chat: the Comments tab is one thread per product, with @email mentions that notify in the bell. A comment is pending until someone marks it as resolved.
Step 5: nothing is published without approval
In Content → Brand voice, the administrator turns on the Editorial workflow. From then on, what ecommerce generates is not published by itself: someone with the editor role or above uses "Send to review" and the description appears in Content → To publish. An administrator approves and publishes it, or rejects it with a reason that stays in the product's comments and reaches whoever generated it. Once published in every language, the ecommerce step is done on its own.
Step 6: the board shows where things get stuck
In Catalog → Flows, the flow's board shows how many products are in progress, how many are stopped by an error, how many are late and how many finished in the last seven days, with the typical end-to-end time. "How long each step takes" highlights the slowest one, and "Where is my SKU?" opens a product's journey. On each product page, the "Journey" tab replays the path event by event.
In Reports, the Team and operations family includes "Time per step" and "Stopped products" for the weekly meeting.
What gets solved and what does not
Solved: each team knows what is theirs and by when, the question "where is this SKU?" is answered in one click and the slowest step is visible in data, not impressions.
Not everything is solved:
- If the ERP does not report, its steps only move with rules on the product page.
- Tasks are not assigned by hand from the journey; that is done in the catalog or on the product page.
- Alerts do not arrive by email, only in the bell.
- Designing the flow is an administrator's job, and it is worth agreeing on it with the teams before activating it.
The flows, tasks and review and approval guides have the details. The flows, review and quality and team and security pages show the rest.
Frequently asked questions
Who can design and activate a flow?
An administrator of the organization. Designing, saving and activating a flow is an administrator task; the other roles see the board and each product's journey.
Does Bruxel create the material in the ERP?
No. Bruxel observes and coordinates, but does not execute. The ERP step moves forward when the system reports an event through the public API, answers a notification or writes to the product with its key.
Do late-step alerts arrive by email?
No. They arrive in the app's bell, grouped by step, and each one opens the board on that step's list.
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: 500 supplier products a month without the spreadsheet ping-pong
An example scenario: a retailer receives 500 new products a month from 40 suppliers. How it handles them in Bruxel, step by step, and what is still open.
· 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.