ULD Demurrage: The Hidden Cost Most Handlers Are Not Tracking
Airline demurrage charges for overdue ULDs can quietly erode margins. Automated overdue alerts and a clear holding ledger are the first step to getting them under control.
A single LD3 container sitting unused in your warehouse for three extra days might not feel like a financial crisis. Multiply that by 15 containers, across 4 airlines, over 12 months, and you are looking at a demurrage bill that can reach five figures before anyone has noticed.
ULD demurrage — the charge airlines levy when handlers hold their equipment beyond an agreed grace period — is one of the most consistently underestimated cost lines in cargo ground handling. Not because handlers are careless, but because the tracking infrastructure to catch it does not exist in most operations.
How ULD demurrage charges accumulate
Each airline has its own demurrage schedule, but the structure is broadly consistent. A ULD arriving at your facility starts a clock. You have a grace period — typically 24 to 72 hours depending on the airline and ULD type — to use the container and make it available for collection or return. Every day beyond that grace period incurs a daily charge, which escalates if the container is held significantly longer than expected.
The charges are not enormous per unit per day. That is exactly why they go unnoticed. At £8–£25 per container per day for a typical narrow-body LD3, the individual invoice line looks manageable. Aggregated across a quarter, it is a different story.
Why most handlers do not track it
The fundamental problem is visibility. ULDs arrive on multiple flights, from multiple airlines, and are received by different shift teams. Without a centralised holding register, there is no single view of which containers are on-site, how long they have been there, and when the clock started for each airline's grace period calculation.
Paper logs and spreadsheets break down quickly under this complexity. A container registered on the day shift's sheet that is still present three days later may not appear on anyone's radar until the airline sends an invoice.
By that point, the damage is done. The charge is payable. The conversation with the airline is difficult because there is no counter-record to dispute with.
The overstock problem compounds it
Beyond pure demurrage, many airlines place a cap on the number of their ULDs a handler should hold at any one time. Exceed that cap — because loads are heavy or because returns are backing up — and you may be in breach of the handling agreement before any grace period even expires.
Knowing you are approaching an overstock threshold requires the same centralised visibility as demurrage tracking. If you cannot see the total count per airline on demand, you cannot act before the threshold is crossed.
Automated alerts change the economics
The intervention point for demurrage control is not the invoice — it is the moment a container crosses into its overdue window. At that point, there is still time to prioritise that ULD for outbound loading, arrange collection, or at minimum document the circumstances in case a dispute is needed later.
Automated overdue alerts — fired when a holding record exceeds the per-airline, per-ULD-type grace period — turn what was a passive accumulation into an active queue. The team sees which containers need action today, not which invoices need paying next month.
What a holding ledger gives you
A structured ULD holding register — with arrival time, airline, ULD prefix, current location, and movement history — does more than enable alerts. It gives you the data to negotiate. When an airline raises a demurrage invoice, you can produce an exact record of when the container arrived, where it was staged, and when it was handed back. Disputes become evidence-based conversations rather than arguments from memory.
RRMS maintains a per-record movement log for every ULD in the holding module. Arrivals, location changes, overstock flags, and closures are all timestamped and attributed. The overdue alert fires automatically based on the rule set configured for each airline — no manual calculation required.
Demurrage will never be zero for a busy handler. But it can be managed, challenged, and reduced — as long as you have the records to do it.