Supply chain insight
Where it came from, not where it was invoiced from
Procurement data tells you who you paid. EPCIS events tell you which facility the material actually passed through — which is a different answer, and the one a due diligence obligation asks for.
- Source
- EPCIS 2.0 events
- Unit
- Facility, not entity
- Not
- Spend-based estimate
Definition
What can supply chain analytics show that procurement data cannot?
Procurement data records who you contracted with. Event data records which facility material physically passed through, when, and in what business step. That distinction surfaces shared upstream dependencies, real tier depth, and the origin evidence a due diligence obligation asks for — none of which contract records contain.
The analysis runs on GS1 EPCIS 2.0 events, so it improves as suppliers participate rather than as a survey cycle completes.
Two sources
The same supply chain, two records of it
| Question | Procurement records | Event data |
|---|---|---|
| Who supplies this product? | The contracting entity | Every facility the material passed through |
| How deep does the chain go? | Tier one, and whatever was declared | As deep as participation reaches, with dates |
| Where is the concentration risk? | By spend, per legal entity | By facility, across nominally separate suppliers |
| Can we prove origin? | A supplier declaration | A dated event, signed by the party that recorded it |
| How current is it? | As of the last survey cycle | As of the last event written |
Capabilities
What the event record supports
Origin analysis
Where material entered the chain, down to plot coordinates where EUDR requires them.
Tier depth
How far visibility actually reaches per product line, and where it stops.
Concentration risk
Shared upstream facilities behind suppliers that look independent on paper.
Transformation tracking
Follow inputs through processing steps into the finished product they became.
Recall scoping
Trace forward from an affected batch to every downstream object it reached.
Cycle timing
Dwell time between business steps, measured from events rather than estimated.
Answers
Frequently asked questions
Where does supply chain analytics data come from?
From the EPCIS 2.0 events already recorded against your products, plus the credentials suppliers issue. Nothing is inferred from spend, and nothing is collected through a separate survey — which is the point, because survey-derived supply chain data is out of date the moment it is submitted.
How deep into the supply chain can we actually see?
As deep as your suppliers participate. Tier one is straightforward, tier two follows once direct suppliers onboard theirs, and beyond that visibility is usually driven by a specific regulatory need — EUDR plot geolocation or battery cell origin — rather than pursued for its own sake.
Can this identify concentration risk?
Yes, and it is often the first thing a supply chain lead looks at. Because events name facilities rather than legal entities, the analysis surfaces the case where four nominally different suppliers all route through one dyeing house or one cell producer — a dependency that contract data alone hides.
Does it predict disruptions?
No. We do not claim prediction. What the platform provides is a complete, dated record of what actually happened at product level, which is the input forecasting has always lacked in this domain. Modelling on top of it belongs in your own tools, with your own assumptions.
Next step
Find the dependency your contract data hides
Bring one product line's supplier list. We will show you what the event record would reveal that the contracts do not.