Flows in Bruxel: each product's journey, step by step

By Manuel Mattar5 min read

In short

In Bruxel, a flow is the map of a product's path between your supplier, your teams and your systems. Each step has a rule that marks it done as soon as it is met, the board counts the products in each step and the bell alerts you to errors and delays. Bruxel observes and coordinates; it does not execute.

The problem it solves

When a product page goes through several hands —the supplier, Purchasing, Master data, Content, your ERP, your store— the everyday question is “where is this product at?”. In the article on approval workflows we explained the pieces of a flow in general. Here we cover how Bruxel does it: what you configure, what each person sees and what is left out.

The underlying idea is simple: instead of someone keeping track in a spreadsheet, the status of each step comes from what is already on the product page, in its supplier's submission or in what your systems report to Bruxel.

How it works in Bruxel, step by step

1. An admin designs the flow

In Catalog → Flows, “New flow” starts from a template (onboarding that arrives through the supplier portal, or a content update) or from scratch. The flow has lanes —the supplier portal, a team with its attribute group or one of your systems— and steps that depend on each other. For each step you choose what it depends on, when it is done, when it applies, its deadline and how the supplier sees it. While you edit, Bruxel checks for circular dependencies, lanes without steps and attributes, channels or groups that don't exist. “Test with a SKU” tells you where a real product would land without writing anything, and each “Save” creates a version you can compare with the previous one.

2. Products enter on their own

A flow can have an entry rule, for example that the supplier's submission is approved; with no rule, every product in the catalog enters. Before activating, Bruxel counts how many products would enter and what state each step would be in. The same product can be in more than one flow at a time.

3. Each step is marked done by a rule

Nobody ticks boxes somewhere else: the rule looks at the product page. A step is met when a Yes/No flag is set to Yes (“Ready for review”), when a field has a value (the code your ERP assigned), when the description is published in every output language, when the product has everything a channel requires or when the supplier submitted it. A step can also apply only to some products, by category or by the value of a field; the rest show “Not applicable” and that does not hold up the following steps.

A system step moves with what happens outside: an event the system reports through the public API, the response to a webhook notification or a read or write made with its key. If the last thing that happened went wrong, the step is marked “with error” and the journey stops until a good one arrives.

4. You follow progress on the board and on the product page

Each 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 7 days, with the typical end-to-end time. On the map, each step shows how many products are there today, and a click opens the list with the longest-waiting ones first. On the product page, the “Journey” tab shows that product's map, a log of what changed and who caused it, and a control to replay the journey event by event.

5. Alerts, tasks and webhooks

Bruxel checks deadlines every minute and alerts you in the bell when a product stops because of an error or passes a step's deadline. A step can assign a task to someone on the team when a product reaches it, and your systems find out by webhook when there are new products in a step, when a journey stops and when it finishes.

Tasks and comments: the work next to the product

Flows tell you where each product is; tasks and comments tell you who is working on it and what is missing. A task is a person, an optional note of up to 500 characters and an optional date. A product has at most one open task, and the “My queue” chip sorts yours by due date, overdue first.

Comments are one thread per product page, in plain text, with @ mentions that notify in the bell. A comment stays open until someone marks it resolved. If you work with suppliers, the page has two threads: “Internal”, which only your team sees, and “With the supplier”. None of this appears in your downloads, your feeds or your store.

Who it is for

For teams where a product goes through at least two areas or systems before it can be sold. A hypothetical example: a tools brand with 3,000 products receives supplier submissions, Purchasing validates the cost, Master data waits for the ERP code and Content writes the page. With a four-lane flow, on Monday someone opens the board and sees which products have been waiting for the ERP code longer than their deadline, instead of asking by email. If a single person works your catalog, tasks and comments are probably enough.

What you need to get started

  • An admin to design and activate the flow; the rest of the team only consults it.
  • The data the rules will look at: Yes/No flags (the designer can create a step's flag), attributes and channels.
  • For your systems' steps, register each one in Channels → Connected systems, with its key and its endpoint.

The flows and journeys guide explains each screen, and the flows module page summarizes what it includes.

Honest limits

  • Bruxel does not create anything in SAP or any other system, and it does not query them either: if a system doesn't report, receive notifications or call with its key, its steps only move with rules on the product page.
  • The board counts what the engine left on its last pass, which is usually one or two minutes behind; the screen says so.
  • A journey's log shows up to the 300 most recent events.
  • You can't assign a task manually from the journey: that is done in the catalog or on the product page.
  • The supplier doesn't see the “Journey” tab, only “Your progress”.

Frequently asked questions

Who can create a flow in Bruxel?

Designing, saving and activating a flow is for admins. Every other role, viewers included, sees each flow's board and each product's journey on its product page.

Does Bruxel create the product in my ERP when that step comes up?

No. Bruxel observes and coordinates, but it does not execute in your systems. A system step moves forward with what that system reports through the public API, with the response to a webhook or with a call made with its key.

Does the supplier see which step their product is in?

They see “Your progress”: only the steps you gave a name for them, with their status in words. They don't see your lanes, your systems, errors or the flow's name.

Do flow alerts arrive by email?

No. Error and overdue alerts arrive in the app's bell, grouped by step, and each one opens the board on that step's list.

Sources

  1. Workflow (Wikipedia)
  2. Webhook (Wikipedia)

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 Mattar

Try it with your catalog

Create your free account and try Bruxel with your own products using the welcome credits.

Keep reading

Flows in Bruxel: each product's journey, step by step