In week 44 a planner on the Shanghai to Rotterdam lane books fifteen containers against a contract that promises twenty a week. Twelve load. Two roll to the next sailing. For the remaining six the carrier never offered space at all, because the service was blanked. The planner does what planners do: splits the load, pays spot for the pallets that cannot wait, and moves on to Tuesday. Nothing in any system records that the week closed eight boxes short of what was bought.
Multiply that by thirteen weeks and you have a quarter where the contract and the reality drifted apart, and no number that says by how much.
Why the gap is wider this quarter
Carriers cut capacity ahead of soft weeks and congestion eats the rest. Drewry's cancellation tracker counted 39 blanked sailings between week 41 and week 45 across the transpacific, Asia to Europe and transatlantic trades, roughly 5% of the 710 voyages scheduled in that window, with about half of the cuts landing on the transpacific alone. Congestion absorbs more: roughly 12% of the global container fleet has been tied up waiting at anchor or alongside this autumn, the highest share in four years.
Capacity that is cancelled or stuck is capacity that is not available to you, whatever the rate sheet says. When space is loose, a contract enforces itself because the carrier wants the volume. When space is tight, the contract only works if someone is counting.
Most teams are not counting. They are handling. A rolled container gets re-booked, a blanked sailing gets re-planned, and each incident closes as its own small fire. The pattern across the quarter never assembles, so the next negotiation opens with the carrier's service story and no counter-evidence.
What allocation compliance actually measures
Allocation compliance is one ratio: the space you actually loaded with a carrier, divided by the space that carrier committed to you, measured per lane and per week.
It is not on-time performance. A carrier can hit 95% on-time on the containers it carried and still have left a quarter of your committed volume on the quay. The two numbers answer different questions. On-time performance tells you how well the carrier moved what it took. Allocation compliance tells you whether it took what it promised.
It is also not your booking acceptance rate. Acceptance measures the bookings the carrier confirmed. The number you need sits one step earlier and one step later: earlier because the demand your team suppressed (the week nobody bothered requesting the full twenty because the last three weeks came back short) never becomes a booking at all, and later because a confirmed booking that rolls twice is not loaded space.
Three figures per lane, per week, per carrier:
- Committed: what the contract or the weekly allocation call put on the table.
- Requested: what your team asked for, including the requests that were refused.
- Loaded: what physically sailed on that carrier in that week.
Compliance is loaded over committed. Requested sits between them and tells you whether a low score is the carrier's shortfall or your own forecast.
Why nobody has the number
The three figures live in three places and none of them talk. The commitment is in a procurement spreadsheet or a contract PDF. The request and the booking are in the TMS or, more often, in a mailbox. The loaded reality arrives as carrier EDI, a portal export, or a container list somebody pastes into Excel on Friday. The reason a box did not load is in a chat message.
Producing the quarterly number from that spread is a reconstruction project, which is why it gets done once a year, badly, two weeks before the tender. This is exactly the gap a supply chain command center closes. Orkestra normalises booking and carrier data across more than 200 pre-built connectors, so the committed allocation, the request, the confirmation and the loaded container sit on one record for each shipment instead of four systems that each hold a quarter of the story. Once they do, compliance is a query rather than an archaeology exercise.
How to build the measurement
1. Write the denominator down. Most allocations are verbal, agreed on a weekly call and never recorded in a system. Put the committed figure for each lane and carrier into the same place you keep rates, dated, so it can change mid-quarter without erasing history. A commitment nobody wrote down cannot be missed.
2. Log the request, not just the booking. Capture what your team asked for before the carrier answered. This is the figure teams skip, and it is the one that exposes suppressed demand. If requested drops below committed for three weeks running, the carrier has already trained your planners to stop asking.
3. Put a reason code on every shortfall. Four codes carry most of it: no space offered, rolled, blanked service, and own volume shortfall. That last one matters as much as the others. A carrier who sees you miss your own minimum quantity commitment has an argument, and you need to know before they make it.
4. Measure weekly, judge quarterly. A single bad week is weather. A lane where the same carrier delivers 70% of committed space in nine weeks out of thirteen is a structural position, and that is what you take into a conversation.
Keep the granularity at lane and carrier. Rolled up to the network, allocation compliance averages out to a comfortable number that hides the two lanes doing the damage. The same trap catches most carrier performance monitoring: aggregate scorecards look healthy right up until the lane that matters fails.
What the pattern tells you
Once you have thirteen weeks of it, a few things fall out quickly.
You can see who rolls you first. Carriers do not cut everyone equally when a vessel is oversubscribed, and the shipper whose volumes are smallest or whose rates were sharpest usually goes first. That is useful to know before you chase the sharpest rate again.
You can see whether your shortfalls track the spot market. If compliance drops in the weeks the spot rate moved above your contract rate, you are not looking at an operations problem. You are looking at a commercial one, and it needs a commercial answer rather than another escalation email.
You can see which lanes are single-carrier by accident. Many are. Nobody decided it, the allocation just concentrated over two tenders, and now one blanked service takes out a week.
None of this works on memory, which is where the timing matters. Shortfalls get recorded properly when they are recorded as they happen, not reconstructed in January. Orkestra flags a short load or a rollover as the carrier message lands, so the reason code gets captured while the planner still knows why. Bridgestone used that combination of normalised data and customisable alerts to surface $11.6K in weekly savings across 22 shipments, which is the kind of figure that only shows up once the underlying events stop being anecdotes.
Take it into the negotiation
A compliance number changes the shape of the tender conversation. Instead of asking for a better rate and hoping service follows, you can price the risk: this carrier delivered 78% of committed space on this lane last quarter, so either the commitment comes down to something real, or the rate reflects the 22% you had to cover at spot.
It also gives you a reason to split allocation deliberately rather than by habit, and a defensible basis for shifting volume mid-contract. Teams running ocean freight rate procurement on rate alone tend to rediscover the same lesson every year: the cheapest contract that delivers 70% of its space is more expensive than the contract priced 8% higher that delivers 95%.
Start with your two highest-volume lanes. Write down the commitment, log requests for four weeks, code every shortfall, and see what the ratio says. That is a month of light discipline, and it produces the one number most ocean programmes cannot currently produce.
The record is what makes it real. Orkestra's analytics turn shipment-level history into lane-by-lane carrier performance you can put in front of a carrier without anyone arguing about where the data came from. See how the analytics work, or book a demo and bring one lane to look at.
