Use case: when the ERP, the store and the datasheet disagree

By Manuel Mattar3 min read

In short

In this example, the manufacturer connects its ERP, its engineering system and its store to Bruxel, each with its own key. Each system reports what it says about an attribute without overwriting the master value, the team sees where they disagree in a queue and decides which one goes to the master, with history.

This is an example scenario, not a customer. The systems, products and figures are hypothetical.

The situation

A water pump manufacturer has about 2,000 products and three places where its information lives:

  • The ERP, with the shipping weight and dimensions logistics uses.
  • The engineering system, where the PDF datasheets come from, with power, flow and voltage.
  • The online store, where someone fixed some data by hand over the years.

A customer complains that the pump weighs something different from what the store says. On review, the ERP says 12.5 kg, the datasheet 12.8 kg and the store 12 kg. Nobody knows which one is right, and each system overwrites the other when it syncs.

What the team does in Bruxel, step by step

1. One key per system

In Channels → Connected systems, the team registers the three systems, and in Channels → API keys it issues a key for each one, with permission to write attributes. Each system uses its own: that way Bruxel knows who said what.

2. Each system reports its own, without overwriting anyone

Each integration sends through the public API what its system says about an attribute. Bruxel validates the value like the master's (a measurement is converted to the attribute's unit) and stores it as that system's version. The master value —the one that goes out in downloads and channels— does not change.

3. See the differences on the product page

Under each reported attribute, the product page says how many sources there are and whether they match the master, for example “3 sources · don't match”, with each system's value and when it was seen. If engineering confirms the real weight is the one on its datasheet, someone clicks “Use this one” and that value goes to the master. The history records it as “Reconciliation”.

4. Resolve in bulk

With 2,000 products, reviewing one page at a time does not scale. In Catalog → Source reconciliation are all the products whose systems disagree, with filters by family, attribute and source. In the example, the team decides the ERP wins for weight and engineering wins for power: it filters by attribute, selects the rows, picks “Use the value from” the right system and clicks “Send to master”. What could not be done, Bruxel explains: that source did not report the attribute, the attribute is protected or a rule sets it.

5. The PDFs, next to the product

Datasheets are uploaded on the product page, Files tab, with the “Datasheet” type. They are private, downloaded with a link that lasts 5 minutes and only after passing the virus check. For certificates, in Media → File types the team creates a type with an expiry date, and the tab says whether it is “Valid”, “Expiring” or “Expired”.

6. Notify the systems when the master changes

In Channels → Webhooks, the team registers its ERP's and its store's addresses and listens for the product updated notice. Every time the master changes, the notice says what changed (fields and codes, never values) and the system re-reads the product. Notices are signed, and “See deliveries” shows each attempt and what the system answered.

7. Know how much is left

In Reports, “Source discrepancies” downloads the full list, and the PDF quality report says how many are left to resolve.

What gets solved

  • No system overwrites another: each one says its own and the master is a decision, not the last sync.
  • Each difference is shown with its source and date, and each resolution stays in the history.
  • The systems learn about the change without anyone having to tell them.

What does not get solved

  • Bruxel does not read the PDFs. What the datasheet says enters reconciliation only if a system reports it through the API.
  • Bruxel does not write to your ERP or your store. It notifies them; updating is each integration's job.
  • It does not apply to multi-select attributes, and the comparison is exact: 12.5 and 12.8 do not match, even if the difference is small.
  • Deciding which system is right is still the team's job. Bruxel shows the difference; it does not know which scale is properly calibrated.
  • The integrations are built by your team or your integrator, with the developer portal documentation.

To go deeper, read the guides on source reconciliation, technical documents and webhooks, or the Reconciliation, Integrations and Files pages.

Frequently asked questions

Does what a system reports change the product's value?

No. What a system reports is stored separately and does not change the master, the history or the completeness. The master changes when someone with the Editor role or above picks Use this one or resolves in bulk from the queue.

Does Bruxel read the values in my PDF datasheets?

No. The PDFs are stored with the product, private and virus-checked, but Bruxel does not extract their values. What the datasheet says enters reconciliation when a system reports it through the API.

Why do 285 and 285.4 show up as a discrepancy?

Because the comparison is exact, after converting units. Bruxel does not round on its own: if two systems give different figures, it shows you so you can decide which one is right.

Sources

  1. Master data management (Wikipedia)
  2. Enterprise resource planning (Wikipedia)
  3. 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

Use case: when the ERP, the store and the datasheet disagree