A temperature-controlled pallet of biologics leaves a plant in Poland, bound for a distributor two borders away. The ERP marks it shipped. The TMS tracks it as far as the first carrier's network, then loses the thread at a cross-dock where the load changes hands. At the second border it catches a six-hour customs hold. The reefer holds temperature for a while, then drifts toward the top of the allowed range. No one watching the shipment knows any of this in real time, because the moment it crossed the first handoff it dropped out of every system that was supposed to be tracking it. The excursion only surfaces when the data logger is downloaded at delivery — long after the window to save the product, or prove it stayed in range, has closed.
This is the pharma supply chain's structural blind spot. The systems are in place and each one works. What fails is continuity: visibility resets at every border, every carrier change, every 3PL handoff — and cold chain leaves no margin for the hours it takes to notice.
Why ERP and TMS aren't enough at the seams
The pharmaceutical industry loses billions of dollars a year to temperature excursions and cold-chain failures, and a single ruined batch of biologics can be worth more than an entire truckload of ordinary freight. That's the stakes. The reason the loss keeps happening isn't a lack of systems — most pharma operations already run capable ERP and TMS. It's that those systems were built to manage transactions and transport within a defined scope, not to maintain an unbroken line of sight across organizations. An ERP knows an order shipped. A TMS knows what it tendered to a carrier. Neither was designed to follow a shipment after it changes carriers, hand off cleanly to a 3PL's tracking, reconcile a customs hold against a temperature limit, and raise an alarm while there's still time to act.
In Central and Eastern Europe that gap is wider, not narrower. Operations span multiple countries, so a single shipment routinely crosses two or three borders and moves through several carriers and 3PLs before it reaches the patient-facing end. Each crossing is a customs process that can stall a load, and the causes are usually knowable in advance (see how to reduce customs clearance delays). Each carrier change is a point where tracking data stops conforming to the same format. The more borders and partners a shipment touches, the more seams there are for it to disappear into — and the more manual the tracking becomes. Here's how to close those seams.
1. Map exactly where you go blind
You can't watch what you haven't located. Start by tracing your highest-risk lanes end to end and marking every point where visibility actually resets: the border crossings, the carrier-to-carrier handoffs, the 3PL transfers, the mode changes from air to road. For most pharma operations the blind spots aren't random — they cluster at a handful of predictable handoffs. Naming them turns a vague sense that "we lose shipments sometimes" into a specific list of seams you can instrument, prioritized by what's moving through them and what an excursion on that lane would cost.
2. Normalize the data so a handoff doesn't reset tracking
The reason a shipment goes dark at a carrier change is rarely that no data exists — it's that the new carrier reports in a different format, on a different schedule, against a different reference number, and nothing reconciles the two into one continuous record. The fix is to normalize tracking data across every carrier and 3PL to a common shape, keyed to the order and the batch rather than to any one carrier's tracking ID. When the data speaks one language, a handoff becomes one more event in a continuous timeline instead of the end of the timeline. Continuity across carriers is the whole game.
3. Watch the shipment, not the system of record
An ERP status of "shipped" tells you what happened at dispatch, not what's happening now. The same is true of a clean TMS record — it can look healthy while the physical shipment sits stalled at a border. The discipline that separates teams who catch exceptions early is watching the shipment's real-world movement against its plan, not trusting the system of record to surface a problem it was never built to detect. A reefer that hasn't reported in four hours, a load that hasn't cleared customs on schedule, a carrier gone silent across a border — these are knowable in real time if you're watching the right layer.
4. Treat a cold-chain exception as time-critical from the first signal
In cold chain, the difference between a save and a write-off is measured in hours. A customs hold, a delayed handoff, a temperature trending toward its limit — each is an early signal that the window is closing. Waiting for the data logger at delivery to confirm an excursion means learning about it when nothing can be done except quarantine the product and file the claim. Acting on the first signal — re-icing at a transfer point, expediting through customs, diverting to a closer cold-storage site — is what keeps product releasable and patients supplied. The earlier the signal reaches someone who can act, the more of the shipment you save.
5. Give every cross-border exception an owner and a clock
A shipment stalled at a border most often sits because no single person owns moving it. It's "with the broker," or "with the 3PL," or "someone's checking." Across a multi-country operation, that ambiguity compounds — the people who could act are in different countries, time zones, and companies. Assign ownership the moment a high-risk exception is raised, attach a deadline tied to the product's stability window or the customer's need-by date, and escalate automatically when that deadline is at risk. The goal is that a cold-chain exception two borders away reaches a named, accountable person in minutes — not that it waits in an inbox for someone to notice.
6. Build the coordination layer for multi-country reality
A pharma shipment crossing CEE is a relay between organizations — the manufacturer, two or three carriers, one or more 3PLs, a customs broker, the receiving distributor. When each runs its own tracking and its own email threads, every handoff is a delay and every status check is a round of phone calls. The operations that hold visibility end to end run the shipment on shared rails: one record of the order, the batch, the temperature history, the customs status, and the current location, visible to everyone with a stake at once. Coordination stops being a sequence of relays and becomes a single, observable line.
What to do Monday morning
Pick one high-value, multi-border lane and trace a single recent shipment across it. Mark every point where your systems lost sight of it and how long the gap lasted. You'll likely find the product was fine, the carriers were competent, and the risk lived entirely in the hours of darkness between handoffs that no one owned. That darkness is the opportunity. You don't need to replace your ERP or TMS to remove it — you need the seams between them, and between your carriers and partners, to carry one continuous, accountable line of sight instead of resetting at every border.
How Orkestra fits
Holding that line of sight across carriers and borders is exactly what real-time visibility is built to do — and it's where Orkestra starts. Rather than replacing the ERP and TMS you already run, Orkestra connects above them and across your carriers and 3PLs: normalizing tracking into one continuous record per shipment, detecting an exception the moment a load stalls or goes silent, and routing it to an owner before the data logger ever comes off the truck. Seeing the shipment the whole way is the difference between saving a batch and explaining one.
It's the pattern that helped Levitt Safety deliver 1.75 million masks and shields on time during COVID — coordinating multiple 3PLs across China and Canada with real-time carrier and flight tracking when getting it wrong meant front-line workers went without.
Get full visibility — Book a demo.
