Supply Chain

Why ‘We Have an ERP’ No Longer Counts as Traceability

Mithileshkumar R NaikAug 15, 20263 min read

Every brand that got asked “can you prove where this came from” in the last two years said yes, and pointed to their ERP. Most of them were telling the truth about the wrong thing.

Oritain’s 2026 Global Supply Chain Intelligence Report puts a number on the gap. Ninety-four percent of UK companies and 87% of US companies now trace their cotton supply chains through exactly this kind of documentation. And yet 90% of the brands Oritain analysed in 2025 recorded at least one prohibited-cotton result anyway. The paperwork was in order. The product wasn’t.

Why the ERP can’t catch what it was never built to catch

The report’s own explanation is the uncomfortable part: digital systems like blockchains and ERPs depend entirely on data entry. If a supplier mislabels conventional cotton as organic, or a distributor logs a counterfeit batch under a genuine SKU, the system doesn’t flag the lie. It immutably records it as fact. A blockchain doesn’t make bad data honest, it just makes bad data permanent and harder to quietly walk back.

This is the structural limit of document-based traceability. It answers “was a record created for this shipment,” not “was the thing in the shipment actually what the record says it is.” Those are different questions, and for years, compliance teams have been allowed to treat the first as a stand-in for the second, because checking the second used to mean expensive lab testing at a scale nobody could sustain across an entire supply chain.

See Origin in action

See how Origin validates the physical unit, not just the paperwork trail.

Explore Origin

What “event-based” traceability actually means

The alternative the report points to is validating the physical asset itself, at the point an event happens, rather than trusting whatever got typed into a system afterward. In practice, that means:

• A unit gets a verifiable marker (QR code, serialised ID, or forensic signature) tied to a real production event, not a retroactive database entry.
• Verification happens at the point someone actually questions the product, a retailer, a distributor, a regulator, a customs inspector, not months later during an internal audit of paperwork.
• The check is on the physical unit or its packaging, not on whether a form was filled out correctly somewhere upstream.

This is a meaningfully different model from “we have an ERP that logs our supply chain.” An ERP records what someone told it. Event-based, unit-level verification checks what’s actually true about the specific unit in front of you, which is the exact gap Oritain’s report says regulators, customers, and auditors are starting to notice.

What this means before it becomes a regulatory requirement

Global manufacturing capacity is expanding faster than internal controls and traditional compliance models can adapt, per Oritain’s own framing, and sourcing patterns are shifting fast under trade and tariff pressure. That combination is exactly the setup for a document-compliance system that looks complete and isn’t, the same 94%-trace-but-90%-fail dynamic the report already found in cotton.

For brands relying on Origin’s supply chain traceability model, this is the difference the platform was already built around, unit-level, event-based verification that a counterfeiter or a mislabelling supplier can’t simply type past. The same logic underlies real anti-counterfeiting infrastructure generally, verification has to happen at the level of the physical unit, not the paperwork describing it.

Sources: Oritain Launches Landmark 2026 Global Supply Chain Intelligence Report (PR Newswire); 2026 Oritain Supply Chain Intelligence Report Reveals Growing Trust Gap & Risk in Supply Chains (Oritain); Oritain Warns ‘Verification Gap’ is Exposing Global Supply Chains to Rising Regulatory and Reputational Risk (EME Outlook Magazine).

Trace claims, not just records

Book a free demo and see how Origin gives you event-based, unit-level traceability.

Book a Free Demo