All courses

Source reconciliation

When your ERP, your PLM or your datasheet say different things about the same data: what each system reported, where they disagree and how to decide which one wins.

What it is

Besides the value of each product attribute (the master value, the one that goes out in your downloads and channels), Bruxel keeps what each of your connected systems says. That way you see where they disagree and decide which one wins, without one system overwriting another.

  • What a system reports doesn't change the master value, the history or completeness.
  • The comparison is exact, after converting units: 285 and 285.4 don't match.
  • It applies to text, number, measure, date, yes/no and select attributes; not to multi-select ones.

How a system reports

Through the public API, with `PUT /v1/products/:id/attributes/:code/source` and a key with the `attributes:write` permission. Each system uses its own key: the source is the system the key is linked to in «Connected systems» or, if it has none, the key's name.

The value is validated like the master value (a measure is converted to the attribute's unit), and sending it empty deletes what that system said. The details are in the developer portal.

On the product page

Under each attribute some system reported, the page says how many sources there are and whether they match the master value («2 sources · don’t match»), with each system's value and when it saw it. «Use this one» moves that value to the master value and goes into the history as «Reconciliation».

Using it takes Editor or higher and respects the same locks as editing by hand: protected attributes, access limited by group, and whatever a rule sets.

The discrepancy queue

In Catalog → «Source reconciliation» are all the products whose systems disagree, with filters by family, attribute and source. To settle them in bulk, tick the rows («Select all» ticks the ones on the page), choose «Use the value from» a system and click «Send to master». Whatever couldn't be done says why: that source didn't report the attribute, the attribute is protected, it's outside your access or a rule sets it.

People without access limited to part of the catalog see the queue; settling takes Editor or higher.

Let one system win

With priority rules on, picking an attribute in the filter shows «Source priority»: the systems, from the one that wins most to the one that wins least. Once you save it with «Save order», every time a system reports, the highest one on the list that has reported writes the master value by itself (in the history: «Priority rule»). «Apply to existing» does the same with what was already reported.

  • Saving the order doesn't change anything by itself.
  • It never writes a protected attribute or one that another rule sets.
  • With no order, everything stays a discrepancy.
An administrator changes the order.

In reports

In Reports, «Source discrepancies» downloads the full list, and the PDF quality report says how many are left to settle.