Every serialization team knows the feeling. A single unhandled exception. A syntax error buried in a partner message queue. A shipment stuck at the 3PL dock — and an automated reply promising a response in 48 to 72 hours.
That’s not a hypothetical. It’s a conversation Alex Roth had with a pharma supply chain VP at the last HDA conference, and it’s exactly the scenario that pushed one manufacturer to walk away from TraceLink and onto OPTEL’s VerifyBrand platform. In a recent webinar, Alex sat down with Scott Pugh to break down why that switch happened — and what changed once it did.
Webinar replay
The Real Cost of Opening a Support Ticket
According to Scott, the industry needs to raise its own bar: opening a vendor support ticket shouldn’t be routine, it should be the exception. Once DSCSA enforcement kicked in, the calculus changed. A stalled exception isn’t just an inconvenience anymore — it’s lost revenue, carrier penalties, and returned product.
For this manufacturer, three factors converged:
- Support that wasn’t sustainable. Ticket volume climbed, resolution times didn’t improve, and the team leaned harder on costly professional services just to keep operations running.
- A vendor dictating the roadmap. When the manufacturer wanted to pair a new L5 provider (Trust.Med) with their existing L4 system, TraceLink simply refused to support the integration — a hard stop that made the vendor relationship feel backwards.
- A market that had moved on. Once the team started taking demos, they saw what they’d been missing: better usability, more features, and — despite assumptions to the contrary — a lower total cost.
Migration Without the Mythology
The biggest myth Scott hears? That switching serialization systems means months of running two systems in parallel and crossing your fingers. That’s where Exodus, OPTEL’s structured L4/L5 migration platform, changes the math.
Exodus automates migration across four stages — export, convert, import, reconcile — down to the individual serial number and parent-child hierarchy. Every batch is reconciled at each stage, and by the time a production cutover happens, the full historical data set has already been tested twice. It’s not an easy button — this is still pharma — but it replaces guesswork with a validated, repeatable process.
The proof is in the numbers from this migration:
- 18+ million serial numbers moved, spanning more than seven years of history
- Under 48 hours for the entire cutover — no parallel systems, no overlap
- Zero outbound shipments impacted
- The majority of the manufacturer’s 75+ downstream customers never even knew a migration happened, thanks to Trust.Med managing those connections independently of the L4 switch
Life After the Switch
Three months in, the results speak for themselves:
- Zero support tickets opened. Exceptions still happen — they always will — but the team resolves them directly in VerifyBrand.
- No manual XML edits. No more hand-correcting T2 files that fall out of sync with source data.
- A fully standards-based data set — the manufacturer’s first, ever, with historical data now converted to EPCIS alongside everything new.
- Reduced reliance on external consultants, with the manufacturer already planning to cut outside resource spend next year.
- No forced upgrade cycles. No more biweekly release notes and change-control scrambles — the validated configuration stays stable unless the client decides otherwise.
Starting Is Never Too Early
One of the clearest takeaways: companies don’t need to wait for a contract to expire to start exploring. OPTEL offers an export-and-convert assessment — a low-commitment way to see exactly what a company’s data quality looks like and what a migration would actually require, long before anyone has to pull the trigger.
As Scott put it: nothing about a legacy vendor relationship magically improves on its own. If the pain is already there, the smartest move is to start the conversation now.
Built for Compliance. Engineered for Reliability.