In Q3 2023, Veridian completed its first large-scale cold-chain deployment with an APAC vaccine distributor. The route ran Singapore to Jakarta, covered three SKUs and roughly 2.8M units, and crossed four customs checkpoints. This is not the sales deck. These are the five things we learned over 11 weeks that ended up in our internal retro doc.
Week 1: logistics doesn't run "to plan"
The customer's brief looked simple: a VeriTag on every case, distributor scans for chain-of-custody. Our pitch deck had a clean six-box "end-to-end" diagram.
The first week on the ground in Jakarta turned six boxes into twenty-three: bonded warehouse holds, customs spot inspections, driver shift changes mid-route, cases consolidated and split. Our first ops playbook was rewritten more or less from scratch.
Week 3: the temperature logger is not on our team
The customer already used a mature temperature logger vendor (active IoT devices at $14 each). The original plan was to ingest temperature data directly into the VeriTrace event stream.
We discovered the vendor's API was read-only with a 4–6 hour data latency — fine for regulator filings, useless for real-time anomaly detection. Our fix was a "latency-tolerant" mode in VeriShield that treats temperature data as a delayed correlate, not a join key. That mode is now the default for every cold-chain customer we onboard.
Week 5: the scan isn't free
We assumed handlers would scan every time they touched a case. Reality: on a 35°C warehouse floor in Jakarta, handlers averaged one scan per six handovers. Coverage fell from the expected 95% to 18%.
The fix wasn't "training" — it was a structural change. We embedded NFC reads into the firmware of the PDA devices they were already using, making the scan automatic rather than manual. Coverage went back up to 92%. Never assume last-mile humans will change behavior. Change the device, not the human.
Week 8: customs stopped the whole route
A routine customs inspection in week eight flagged our NFC tags as "looking like electronics" — possibly subject to import licensing as electronic components. The route held for 36 hours.
Lesson: pre-classify with customs before launch. VeriTag belongs in "packaging auxiliary labels," not "wireless communication devices." We now run a pre-classification filing for every new market.
Week 11: the two numbers from go-live
First 30 days of production traffic:
- 2.1M signed scan events written to VeriTrace.
- 4 confirmed suspect events, all on the cross-border segment: 3 legitimate-but-unauthorized parallel importers, 1 genuine clone attempt — geolocated and seized by customs within 9 hours of the alert.
Every supply chain scheme that looks "perfect on a whiteboard" discovers something not on the whiteboard by week three. Plan with 30% slack.
Five takeaways for peers
- Fly out. The diagram cannot replace the warehouse floor.
- Treat temperature as a delayed correlate. Don't block auth on it.
- Don't let manual scans be a single point of failure. Embed reads into existing devices.
- Customs classification will stop your route faster than any cryptographic protocol can.
- Customers ask for "end-to-end control." The honest goal is end-to-end visibility.