Back to Blog
Supply Chain

Product Provenance in B2B Supply Chains: A Practical Anti-Counterfeiting Playbook

September 28, 20268 min read

Counterfeiting is usually discussed as a consumer problem โ€” fake handbags, fake sneakers. For manufacturers selling to other businesses, it looks different: a copied spare part, a relabelled component, a consumable refilled and sold as new. The buyer is a professional, the product often ends up inside someone else's machine, and when it fails, the question "was this really yours?" lands on your desk.

This article is a practical playbook for building provenance into a B2B supply chain: what the standards recommend, what a digital record can and can't do, and a step-by-step rollout.

How Big Is the Problem?

The most-cited figures come from the OECD and the EU Intellectual Property Office. Their Mapping Global Trade in Fakes 2025 report estimates global trade in counterfeit goods at USD 467 billion in 2021, or 2.3% of world trade, and imports of fakes into the EU at EUR 99 billion, or 4.7% of EU imports. On the enforcement side, the EUIPO reports that about 112 million counterfeit items were detained in the EU in 2024, worth over EUR 3.8 billion.

Those numbers are dominated by consumer goods, but the mechanism is the same for industrial ones โ€” and the consequences of a failed counterfeit bearing, filter or electronic component are usually worse than a failed phone case. Some sectors have their own standards for this, such as SAE AS5553 for avoiding and detecting counterfeit electronic parts in aerospace supply chains.

Why B2B Supply Chains Are Exposed

  • Many hands between you and the user. Distributors, sub-distributors, service companies and online resellers each handle the product. Every handoff is a place where a substitute can enter.
  • Grey-market and aftermarket channels. Parts bought outside your authorised network are hard to trace back, and genuine and fake stock can be mixed.
  • The person checking isn't your customer. An installer or maintenance technician has no account with you and no way to check a serial number against your systems.
  • Identical-looking products. Industrial parts rarely have visible brand cues; a good copy of a gasket or a cartridge is indistinguishable by eye.

What the Standards Say

The reference standard is ISO 22383:2020, guidelines for selecting and evaluating authentication solutions for material goods (it replaced ISO 12931). Three ideas from it are worth borrowing even if you never get certified:

  • Start with a risk assessment. Performance criteria are set against the actual threat โ€” who copies your products, where they enter the chain, and who needs to check them.
  • Layer overt, covert and forensic features. Overt features (a visible label or QR code) can be checked by anyone; covert ones by trained staff with a tool; forensic ones in a lab. No single layer is enough.
  • Security by design. Build authentication into the product and the process, rather than bolting a sticker on later.

Its companion, ISO 22384:2020, covers how to set up a brand-level product fraud protection plan.

Provenance Starts With Unit-Level Identity

You can't prove where a product has been if you can't tell one unit from another. Regulation is pushing in the same direction: the General Product Safety Regulation already requires consumer products to carry a type, batch or serial number, the new Machinery Regulation (EU) 2023/1230 requires machinery to carry its series or type and any batch or serial number, and the EU Digital Product Passport will add persistent unique identifiers for more product groups.

A serial number on its own, though, is just a string. It becomes provenance when it is linked to a record that says who made the unit, when, and what happened to it since โ€” and when that record is reachable by the people who need to check it.

What a Digital Record Can โ€” and Can't โ€” Do

A blockchain-anchored record makes one thing very hard: changing history after the fact. Once an event is anchored, anyone can check that it hasn't been altered since, without trusting the manufacturer's database. We compare this with simple code-lookup systems in Code Lookup vs. Blockchain Verification.

But it is not magic. The EU Blockchain Observatory puts the limit plainly in its report on supply chain transparency: "'garbage in, garbage out' โ€“ if inaccurate data is entered into the blockchain platform, it will be maintained and propagated in the system." In practice this means:

  • The link between the physical item and its record is the weak point. A QR code can be photocopied. A digital record doesn't stop that; what it does is let a checker see that the code they scanned belongs to a unit with a known history โ€” for example one already delivered to, or claimed by, someone else.
  • Who records an event matters. The record proves what was entered and when, not that it was true. Keep recording rights with parties you trust.
  • Physical security features still count. For high-risk parts, pair the digital record with covert or forensic features, as ISO 22383 suggests.

A Step-by-Step Rollout

  1. Pick the SKUs that hurt. Start with the products you know are copied, the ones with safety or warranty exposure, or the ones sold through channels you don't control.
  2. Serialise at unit level. Give each unit its own identifier at production. For numbered runs, create them as a series so every unit gets its sequence number automatically.
  3. Put a data carrier on the item. A QR code on the part, its packaging or its documentation that resolves to a public page โ€” no app and no login, so an installer on site can scan it.
  4. Record the handoffs that matter. Shipped to distributor, received, installed, inspected, returned. Connect your ERP or warehouse system through an API rather than asking people to type events in.
  5. Anchor the record. Periodically commit the events to a public blockchain so no one โ€” including you โ€” can quietly rewrite them later.
  6. Tell the chain to check. Print "scan to verify" on the label, put verification into distributor agreements and service documentation, and embed a verification widget on your own site.
  7. Review what you see. Unexpected scans, disputed histories and warranty claims on units you can't find are your early warning system.

How This Maps to Our Platform

Our platform covers steps 2 to 6: unit-level digital twins with unique IDs, numbered series, QR codes that resolve to a public verification page showing the product's chain of custody, custom custody events via the dashboard or the REST API, Merkle-batched anchoring on Solana, and an embeddable verification widget. See the technology overview for how the anchoring works, or the manufacturers use case for how teams put it together.

Give every unit a verifiable record with RivetChain.

Register products and their events via the dashboard or the API, anchor them to the blockchain, and let anyone check them with a QR scan.