Supply Chain Terminology Every Haulier Should Know
A practical glossary of supply chain terminology for hauliers and container operators, with plain definitions, abbreviations, and operational examples.
You can have three screens open, a driver already at the gate, and finance asking whether the POD is clean enough to invoice. That's a normal morning on a haulage desk, and it's exactly why supply chain terminology matters before the first call is even answered. The words on the booking, the run sheet, and the POD decide who moves, who waits, and who pays.
A dispatcher who knows the difference between free time, demurrage, and detention doesn't just sound informed. They protect margin, avoid pointless argument, and keep the job moving. The same goes for terms like FCL, LCL, gate-in, terminal release, and proof of delivery, because each one is a trigger in the daily workflow, not a glossary entry sitting in a binder.
Table of Contents
Why This Glossary Matters on a Busy Haulage Day
At 07:30, the desk is already noisy. A driver is parked near the terminal waiting for a release note, a planner is checking a vessel ETA against a customer's delivery slot, and finance is chasing an unsigned POD that's blocking invoicing. In that moment, language isn't decoration, it's the operating system of the day.
If one person says “drop and pick” and another hears “drop only,” the mistake ripples across the whole job. The truck may arrive without the right chassis plan, the container may sit too long in the terminal, and a charge that should've been avoided gets argued later as if it came from nowhere. Shared vocabulary stops that drift before it starts.
The working rule on a live desk
Practical rule: if a term can change who pays, it must be understood the same way by dispatch, planning, and finance.
That's why a working glossary has to go beyond dictionary definitions. On a haulage desk, the question is not “what does the word mean,” but “what action does it trigger?” A last free day changes when you pull the box, delivery order changes whether you can move it at all, and POD changes whether the job is billable.
The best teams build their language around those triggers. They don't let dispatch, customer service, and accounts each use a slightly different version of the same word. They use one operational meaning, then apply it consistently from booking to billing.
How Supply Chain Terminology Evolved into Today's TMS Language
The modern use of supply chain management is widely traced to 1982, when Keith Oliver of Booz Allen Hamilton introduced the term in a Financial Times interview, and the phrase then moved into wider public and professional use during the 1990s (history of supply chain management). That matters on a transport desk because older logistics ideas were gradually pulled into one framework, instead of being treated as separate silos for procurement, storage, and transport.
From siloed functions to one workflow
Containerisation pushed that change into the world. A 2024 ITIF discussion on supply chain origins notes that the rise of containers in the 1950s helped turn mostly regional supply networks into global systems, and it explains why container handling became central to modern logistics and freight planning (ITIF on supply chain origins and innovations). The same source also notes that loading a ship in a container costs less than one twentieth of loading bulk, which is one reason container vocabulary became such a practical part of day-to-day operations.
That shift didn't stop at the dock. As ERP and later TMS systems came in, old shorthand had to live beside event-based language like booking, gate-in, dispatch, POD, and invoice ready. New dispatchers often stumble because the screen is mixing warehouse habits, port terminology, and customer-facing status codes in one place.
Why the digital layer changed the language
SCOR DS, the Supply Chain Operations Reference Digital Standard, gives teams a shared process framework for business activities from opportunity to payment (SCOR DS). For transport teams, the benefit is straightforward: the same term means the same thing in planning, dispatch, proof of delivery, and invoicing. This is how handoffs get cleaner, KPI definitions stop drifting, and exception reporting becomes usable rather than argumentative.
The words didn't become less physical just because they became digital. They still describe the same truck, container, and document, they just need more precision now.
Foundational Supply Chain Terms Every Operator Uses
The terms below show up in almost every job file, even if nobody notices them until something goes wrong. A good desk keeps them grouped by lifecycle, because that's how they appear in the work, before shipment, while it's moving, and after delivery.
Pre-shipment terms
Shipper is the party sending the goods, consignee is the receiver, and notify party is the person or company that needs updates when the cargo lands. Booking is the reservation of space or equipment, while ETD and ETA tell the planner when a movement should leave and arrive.
Cut-off is the deadline that matters when a container must be at a terminal or document must be submitted before the vessel closes. Free time is the allowed period before storage or equipment charges start. In practice, that's the number finance checks first when a job looks marginal.
In-transit and arrival terms
ATA and ATD are the actual arrival and departure times, and they matter because they expose delay patterns that planned times hide. Haulage is the road movement itself, which may be arranged directly or through a third party. On a live desk, these terms tell you whether a job is still on plan or whether the clock is already working against you.
Post-arrival and billing terms
POD is proof of delivery, and it's the record finance needs before they can invoice with confidence. Demurrage and detention are the two terms that cause the most confusion and the most avoided margin loss, because they apply to different clocks and different custody points. One is tied to the container sitting inside the terminal, the other to the box being held outside the terminal beyond the agreed time.
| Lifecycle Stage |
Term |
Where It Shows Up |
Operational Note |
| Pre-shipment |
Booking |
Booking confirmation email |
Confirms space, equipment, and route details |
| Pre-shipment |
ETD |
Vessel schedule |
Helps the planner judge readiness |
| Pre-shipment |
Cut-off |
Terminal notice |
Miss it, and the job slips to the next move |
| In-transit |
ETA |
Customer update or TMS screen |
Drives planning and bay scheduling |
| In-transit |
ATA |
TMS event log |
Shows whether the vehicle or vessel arrived late |
| Post-arrival |
POD |
Driver paperwork or ePOD |
Unlocks invoicing when complete and clean |
| Post-arrival |
Demurrage |
Port or line charge advice |
Starts after free time inside the terminal |
| Post-arrival |
Detention |
Equipment charge note |
Starts when the container stays out too long |
Container and Intermodal Vocabulary from Port to Gate
Once the booking is live, container language starts doing real work. FCL means Full Container Load, where one shipper uses the box. LCL means Less than Container Load, where freight is consolidated with other cargo. The difference affects how you plan, how long the container takes to turn, and how many people need to touch the job.
The equipment terms matter just as much. TEU and FEU tell you the size of the unit, while high-cube, reefer, and tank container tell you what tractor, chassis, and handling rules you'll need. If the box is refrigerated, the driver and planner need to know more than the destination. They need temperature, power, and timing discipline.
Port-side terms that decide whether the truck moves
Terminal release tells you the box can be collected. Interchange is the handover record that shows responsibility changed hands. Gate-in, gate-out, and yard slot are the practical checkpoints that decide whether the move is on time or already drifting.
A simple rule saves endless arguments, if the box isn't released, the truck isn't moving.
That's also where demurrage and detention must stay distinct. Demurrage belongs to the terminal side of the clock. Detention belongs to the container-outside-the-terminal side of the clock. When those two are mixed up, the invoice dispute usually starts before the job is even closed.
For a useful plain-English reference on drayage, see what drayage means in trucking. It's the kind of term that sounds simple until a port move stalls and everyone uses it differently.
A Container Move in Practice and the Terms That Drive It
A normal container job has a lot more language in it than a new starter expects. It begins with booking and equipment release, which tell the planner the box exists and can be collected. From there, the job moves into pre-pull or yard pull, where the container is positioned ahead of the delivery appointment.
The move from port to receiver
The driver then takes the chassis pick-up, heads to the terminal appointment, and completes gate-in before the stack move and crane lift. When the vessel works the box, the same move appears in the system as discharge, gate-out, drayage, and delivery to the consignee. The final handover is where the paperwork matters most, because POD capture confirms who received the cargo and when.
The clocks that change who pays
Free time and last free day tell you when the charge window starts. EIR, the equipment interchange receipt, marks custody of the box. If the container stays too long in or out of the terminal, demurrage, detention, or per-diem charges can kick in depending on where the clock is running.
Practical rule: the handover document is never just paperwork, it is the point where liability changes.
That's why dispatch, planning, and finance all need the same language. If dispatch says the job is “done” but the POD lacks the right timestamps, finance still has a problem. If the driver has moved the container but the EIR or release note is missing, the job may be physically complete and commercially unusable at the same time.
Common Abbreviations and Acronyms on Run Sheets and Screens
Dispatchers don't read one abbreviation at a time, they read clusters. BOL, AWB, SCN, and CRO belong to shipment identity and release. Those are the references that tell you which cargo, which mode, and which container you're handling.
The operational layer
ETA, ATA, ETD, and ATD are the timing codes that tell the desk whether the movement is on track. CUT can mean different things depending on the context, so nobody should guess. CY is the Container Yard, the place where the box sits before or after line haul work.
Customs and compliance
HS code tells customs what the goods are classified as. EORI is the registration that identifies the trader for customs purposes. T1, T2, and ENS belong in the compliance trail, and they matter because a missing document can stop the job as effectively as a missing truck.
Internal run sheet shorthand
DO, PU, DLV, TRP, and POD all point to workflow stages rather than standing alone. A smart desk treats them as verbs or status markers, not as random labels on a screen.
| Function |
Abbreviation |
Meaning |
| Shipment Identity |
BOL |
Bill of Lading, the contract and cargo record |
| Shipment Identity |
AWB |
Air Waybill, used for air freight moves |
| Shipment Identity |
SCN |
Shipping Container Number |
| Operational Timing |
ETA |
Estimated Time of Arrival |
| Operational Timing |
ATA |
Actual Time of Arrival |
| Customs |
HS |
Harmonised System code |
| Customs |
EORI |
Economic Operators Registration and Identification |
| Workflow |
POD |
Proof of Delivery |
Route, Load, and Vehicle Terms That Shape Margin
A lot of margin disappears in route language before it shows up in the accounts. Back haul is a paid return load on the way back from a destination. Deadhead is the empty repositioning move, and it's usually where fuel, time, and driver hours get burned without matching revenue.
The decisions that come from the load plan
Drop and hook means the trailer or container is left and another unit is taken, which helps turn time if the depot or chassis pool is working properly. Live load keeps the driver on site while the cargo is loaded or unloaded, which can be fine when the consignee is organised and expensive when they're not. Drop trailer arrangements can improve flexibility, but they also demand better equipment control and clearer responsibility for detention.
Cube-out happens when the vehicle fills by volume before weight. Weight-out happens when the legal weight limit is reached first. Payload and GVM are the numbers the planner needs to know before the truck is dispatched, because the wrong load decision turns into rework, delays, or a failed collection.
Margin usually leaks in the small stuff, the waiting, the repositioning, the missed reuse of equipment, and the charge that never got raised because nobody named it correctly.
| Term |
Operational Trigger |
Planning or Invoice Impact |
| Back haul |
Return leg has freight |
Creates revenue on the way back |
| Deadhead |
Empty return or repositioning |
Reduces margin if not controlled |
| Drop and hook |
Trailer or box can be swapped |
Improves vehicle utilisation |
| Live load |
Driver waits during loading |
Triggers waiting time or detention discussion |
| Accessorials |
Extra service or delay |
Adds a separate charge line |
| Detention |
Vehicle or container waits beyond agreed time |
Must be standardised for invoicing |
Dispatch, POD, and Invoicing Vocabulary in a Connected Workflow
A job only becomes cash when the workflow terms line up. Order, dispatch, ETA, ATA, loaded, delivered, POD, ePOD, query, WIP, accrual, AR, and dispute are all status words that determine what happens next. If the words aren't consistent, finance ends up reconciling the same move twice.
What a clean workflow looks like
A dispatcher reads a board differently once each status has a clear meaning. On-site means the vehicle has arrived, loaded means the cargo is on board, and delivered means custody has passed. If the POD is still missing signatures, timestamps, or supporting images, finance may still treat the job as incomplete.
A strong ePOD usually captures the timestamp, signature, GPS position, and photos where needed. That's not bureaucracy, it's the audit trail that proves the delivery happened in the state claimed. For a plain-English explanation of POD handling, see POD meaning in shipping and transport.
Why status codes matter to billing
Practical rule: a delivered status without a clean POD is not a billable finish.
If waiting time was incurred on site, the accessorial should be coded while the job is still fresh. Otherwise the note gets lost, the invoice goes out light, and the query lands back on the desk weeks later. That's why shared status codes are not just for the dispatcher, they're the handoff into invoicing.
One useful option for teams trying to tie planning, POD capture, and invoicing into one flow is Logivo, which links job planning, driver briefing, POD capture, and invoicing in a single transport workflow.
Emerging 2026 Terms Around AI, Visibility, and Sustainability
A late vessel update, a missed geofence alert, or an ETA that drifts without warning changes the whole day on a haulage desk. That is why control tower, orchestration, and real-time visibility keep appearing in customer briefs. They are not just software labels. They are the language shippers use when they want exceptions spotted before they become missed slots, late collections, or a messy invoicing query.
Which terms are becoming operational, and which are still marketing
API-first TMS is already useful where job data, tracking, and POD details need to move without manual rekeying. Digital twin of the network sounds abstract, but the useful version is a planning model that reflects real routes, loads, and delay patterns. Autonomous freight still sits more in concept than in daily haulage work, while ETA prediction and geofencing are part of live screens and dispatch calls now.
Sustainability terms are following the same path. CO2e per TEU-km, well-to-wheel, biofuel mandate, green corridor, and Scope 3 reporting come up when shippers ask for emissions data as part of procurement or ESG reporting. If you want a wider view of how visibility is changing these conversations, Logivo's supply chain visibility overview is a useful companion read.
Before you accept a new customer or a new lane, check whether the visibility requirement is operational or just sales language. For carrier selection and chain-of-custody discipline, keep how to prevent double brokering close, because identity gaps and visibility gaps often show up in the same workflow.
Quick Decision Guide for Commonly Confused Term Pairs
| Term Pair |
Trigger Event |
Decision Rule |
| Demurrage vs Detention |
Box sits in terminal or stays out too long |
Demurrage is the port-side clock, detention is the container-outside-port clock |
| FCL vs LCL |
Booking is made for one shipper or shared freight |
FCL is one container for one shipper, LCL is consolidated cargo |
| POD vs BOL |
Delivery completes or goods are carried |
POD proves delivery, BOL documents the carriage |
| Back haul vs Deadhead |
Return leg is available or empty |
Back haul earns revenue, deadhead is an empty reposition |
| Free Time vs Demurrage |
Allowed period ends |
Free time is the allowance, demurrage is the charge after it |
One-Page Abbreviation Lookup
| Abbreviation |
Full Form |
Where It Appears |
| ETD |
Estimated Time of Departure |
Run sheets, vessel schedules |
| ETA |
Estimated Time of Arrival |
Job board, customer updates |
| ATA |
Actual Time of Arrival |
TMS status logs |
| ATD |
Actual Time of Departure |
TMS status logs |
| CUT |
Cargo Available or Container Unit Train |
Booking notes, operational screens |
| EOR |
End of Receipt |
Internal process notes |
| NOR |
Notice of Readiness |
Shipping documents |
| FCL |
Full Container Load |
Booking and port paperwork |
| LCL |
Less than Container Load |
Freight booking documents |
| TEU |
Twenty-foot Equivalent Unit |
Port and capacity planning |
| FEU |
Forty-foot Equivalent Unit |
Port and capacity planning |
| BOL |
Bill of Lading |
Cargo documents, customs files |
| POD |
Proof of Delivery |
Driver paperwork, invoicing |
| PSS |
Peak Season Surcharge |
Freight invoices |
| GVW |
Gross Vehicle Weight |
Vehicle and compliance records |
| HGV |
Heavy Goods Vehicle |
Vehicle and route documentation |
| RTW |
Return to Warehouse |
Internal transport notes |
| TIR |
Transports Internationaux Routiers |
Cross-border transport docs |
| ADR |
European Agreement concerning the International Carriage of Dangerous Goods by Road |
Dangerous goods paperwork |
| IMO |
International Maritime Organization |
Container and shipping compliance |
| COD |
Cash on Delivery |
Commercial and billing records |
| C&F |
Cost and Freight |
Commercial contracts |
| CIF |
Cost, Insurance, and Freight |
Trade terms |
| FOB |
Free on Board |
Trade terms |
| EXW |
Ex Works |
Trade terms |
| HS |
Harmonised System |
Customs forms |
| HBL |
House Bill of Lading |
Forwarder documentation |
| MBL |
Master Bill of Lading |
Carrier documentation |
| AWB |
Air Waybill |
Air freight paperwork |
| CMR |
International Carriage of Goods by Road consignment note |
Road freight documents |
Related Standards, Glossaries, and Logivo Resources
A serious haulier keeps a small library of standards close at hand. FIATA freight vocabulary, the ICC Incoterms 2020 rules, IMO and UN dangerous goods conventions, and the CSC plate register all give structure to the terms people throw around casually. For UK-specific depth, BIFA guidance, Department for Transport codes, and European Commission customs glossaries help keep local usage aligned with the bigger trade framework.
The useful internal habit is to keep one living reference for the desk. For related reading, Logivo's supply chain visibility article sits well beside this guide because visibility and terminology are tightly linked in daily transport work. The point isn't to memorise every term, it's to stop language drift between dispatch, drivers, and finance.
If your desk still loses time to vague status updates, missing PODs, or invoice queries that started as terminology mistakes, Logivo is built for that workflow. It connects job planning, driver briefing, proof of delivery, and invoicing in one transport system, so the language stays consistent from first booking to payment. Visit Logivo if you want to see how that looks on a live haulage desk.