The Operations
Brief

Most operators can trace product reasonably well inside their own four walls. The trouble starts at the handoff, when a supplier’s records have to make sense inside someone else’s ERP, WMS, and quality system.

This issue is about that handoff: why it’s becoming part of the supplier relationship, what it looks like at a real receiving dock, and a practical way to find where your own evidence chain breaks.

Bill

The Traceability Handshake Is Becoming a Supplier Requirement

Traceability evidence now has to survive the boundary between companies.

A shipment can reach the dock before its usable traceability record does. The product is physically there. The lot references, certificates, event records, and receiving data that would let the next operator accept it are not, or they arrive in a form the receiving system can’t use. So the team rebuilds the trail by hand from inboxes, portals, and disconnected systems before it can decide whether to accept, hold, investigate, or escalate.

Most companies can trace at least part of a product inside their own environment. The harder problem starts when that history has to cross into another company’s ERP, WMS, QMS, MES, or receiving process. Item identifiers differ. Lot and serial references don’t match. Certificates travel separately from the shipment. Event records use different structures.

NIST gave this problem a current technical foundation on September 9. NIST IR 8536 lays out a manufacturing traceability meta-framework for building a continuous, time-ordered provenance chain across separate supply chain ecosystems. It relies on common data patterns, interoperable interfaces, cryptographically verifiable links, and selective disclosure, so companies can share the evidence traceability requires without exposing proprietary operating data or depending on a central repository.

The framework matters less than what it signals for operators. The shift is from visibility to usability. A supplier can hold the right information and still fail the handoff if the receiver can’t connect it to the product, lot, shipment, event, or decision inside its own workflow. Traceability is becoming part of the supplier handshake, judged alongside the product, the ASN, and the delivery date.

For Cencora, this isn’t a future architecture problem. A truck can reach the dock before the data required to receive its product.

The Truck Is at the Dock. The Data Isn’t.

Gregg Gorniak of Cencora on receiving product that arrives before its evidence.

Gregg Gorniak is Vice President of Manufacturer Operations and Data Services and Secure Supply Chain Lead at Cencora, which receives pharmaceutical shipments from manufacturer partners. Under the Drug Supply Chain Security Act, Cencora needs the matching serialized data before it can receive covered product and take ownership of it. In a Q&A with Pharmaceutical Commerce, Gorniak described how his team compares purchase orders, ASNs, and expected delivery windows against incoming EPCIS data.

His fix is an early warning. A red, amber, and green view flags suppliers whose EPCIS data hasn’t arrived 12 to 24 hours before the truck is due. That window gives Cencora and the manufacturer time to repair the data handoff, whether the cause was a system glitch or a file nobody pushed, before the shipment reaches receiving. Without it, the truck is physically present and the product is operationally unavailable.

Gorniak also draws a line between compliance and a usable handoff. A portal, PDF, or spreadsheet can satisfy a minimum access requirement and still leave the receiver stuck, because a PDF can’t be ingested into the system that validates the product. In his framing, a portal makes a supplier compliant. It doesn’t make it a good partner.

The Supplier Traceability Reconciliation Agent

One place to rebuild the supplier-to-production evidence chain, with humans reviewing only the exceptions.

Supplier evidence arrives through ASNs, certificates, packing documents, emails, portals, and shared event records. Internal evidence sits across the PO, the ERP receipt, the WMS scan, the QMS inspection, inventory movements, and BOM or production consumption. Today the buyer or quality lead spends most of the effort matching identifiers and putting events in order before investigating the actual discrepancy.

This agent does the assembly work and hands a person only the missing or conflicting links. It’s a practical system pattern, not a named product you can buy off the shelf.

Two paths to build it