WHAT IS A ROLLOVER? WHY CAN A CONTAINER BE GATED IN BUT NOT LOADED ON THE VESSEL?
A full container gated into the nominated terminal is not automatically guaranteed to be loaded on the vessel shown in the Booking Confirmation. Before the crane operation, the carrier and terminal still have to close Shipping Instructions, VGM, customs status, special-cargo approvals, the load list and the vessel stowage plan. If capacity is exhausted, the vessel schedule or port rotation changes, data is late, the unit is on hold, or the container does not meet operating limits, it may be rolled to a later voyage while remaining inside the terminal. For industrial components, spare parts and production materials tied to a factory schedule, one missed sailing may trigger delivery delays, document amendments and storage exposure. This article explains the rollover mechanism, its causes, the evidence to review and the response workflow after a rollover notice.
QUICK FACTS
Cargo or a container is not carried on the intended voyage and is transferred to a later voyage, routing or transport option.
Gate-in confirms terminal receipt; Loaded on Board confirms the container was physically lifted onto the vessel.
The cause may involve the carrier, terminal, weather, schedule, documents, VGM, customs, DG/OOG or shipper data.
After rollover, confirm the new vessel/voyage, ETD/ETA, cut-offs, documents, free time, charges and ownership.
SCOPE OF APPLICATION
This article mainly applies to dry-container FCL exports, especially industrial components, spare parts, production materials and trading goods in 20DC, 40DC or 40HC containers. The same control logic is useful for reefer, DG, OOG and transshipment cargo, subject to additional approvals, cut-offs and tariffs. The article does not determine fault or compensation for a specific shipment. The final position depends on the Booking Confirmation, pricing terms, contract of carriage, carrier notice, terminal events and the reason confirmed in writing.
TERM DEFINITIONS
| Term | Meaning | Operational role |
|---|---|---|
| Rollover / Rolled cargo | Cargo or a container is moved from the intended voyage to another voyage or routing. | It may occur at the port of loading or a transshipment port; analyse carrier-side, merchant-side and outside-control events. These are operational categories, not a universal reason-code set. |
| Gate-in | The event recording that the container entered the terminal or CY. | It proves terminal receipt, not inclusion in the final load list or physical loading. |
| Load list | The list of containers planned for loading after data and operating conditions are checked. | A gated-in unit may still be omitted from the final loading plan or assigned to another voyage; displayed status labels vary by carrier and terminal. |
| Stowage plan | The vessel loading plan based on discharge port, weight, cargo type, safety and stability. | Weight, DG, OOG or vessel-balance restrictions may displace a container. |
| Vessel omission | The vessel skips a port that was previously scheduled. | Containers at that port need another vessel, feeder or transfer plan. |
| Blank sailing | A voyage or service loop is cancelled or not operated. | Bookings may be shifted even after equipment pickup or gate-in. |
| Cut-off | The deadline for CY, SI, VGM, customs or special-cargo data. | Meeting the CY cut-off does not cure a missed SI, VGM, DG or customs cut-off. |
| Loaded on Board | The status confirming that the container was physically loaded on the vessel. | It is different from booking confirmed, empty pickup, gate-in and planned loading. |
OPERATING MECHANISM
Rollover happens in the gap between “the terminal has accepted the container” and “the unit is included in the final loading plan and physically lifted onto the vessel.” A Booking Confirmation identifies an intended voyage and booking conditions; a gate-in event records the container inside the terminal. However, the master, carrier and terminal still use VGM, cargo type, discharge port, customs status, DG/OOG/reefer approvals, the load list and the stowage plan to decide what can be loaded. When vessel capacity, port rotation, safety, schedule recovery or shipment data changes, a unit may remain in the yard but lose eligibility or space on that voyage. “In terminal” or “Full gate-in” therefore cannot replace “Loaded on Board.”
STATUS MILESTONES: GATE-IN IS NOT LOADED ON BOARD
| Milestone | Meaning | What it does not prove |
|---|---|---|
| Booking Confirmed | The carrier accepts the booking under the displayed terms. | It does not prove terminal entry or guaranteed loading unless the product/terms expressly provide a commitment. |
| Empty Pick-up / Released | Empty equipment is released or collected. | It does not prove stuffing, sealing, customs completion or gate-in. |
| Full Gate-in | The packed container enters the terminal and has a gate event/EIR. | SI, VGM, customs, special-cargo approval and load-list status may still be outstanding. |
| Planned / Load list (where displayed) | The unit is planned for a voyage; the status label varies by carrier and terminal. | The plan may still change due to stowage, weather, omission, inspection or safety constraints. |
| Loaded on Board | The unit is physically lifted onto the vessel and recorded as loaded. | This is the primary operational proof of loading. |
| Vessel Departed | The vessel leaves the port with the loaded unit. | Used to lock the actual schedule, track ETA and close documents as applicable. |
WHY A GATED-IN CONTAINER MAY NOT BE LOADED
| Cause | Related party | Mechanism | Signal/evidence | Control |
|---|---|---|---|---|
| Capacity exhausted or allocation exceeded | Carrier/vessel operator | The vessel is full, bookings exceed allocation or priority changes. | Rolled-cargo notice, revised voyage, container absent from load list. | Request a written reason and alternative voyage; check whether a loading guarantee applies. |
| Vessel change, port omission, blank sailing or schedule recovery | Carrier/alliance/port | Rotation changes, a port is skipped, the voyage is cancelled or the service is adjusted. | Service advisory, revised booking, changed vessel/voyage. | Re-lock routing, transshipment, ETD/ETA and document deadlines. |
| Late or rejected SI, VGM or customs data | Shipper/forwarder/docs | Data is missing, late, incorrect or not accepted by the system. | Portal shows pending/rejected; carrier asks for correction. | Track acceptance status, not only the email submission time. |
| DG/OOG/reefer or restricted-cargo approval outstanding | Shipper/carrier specialist | DGD, SDS, packing certificate, OOG details, temperature or commodity approval is incomplete. | Booking hold or special-cargo approval pending. | Complete approval before empty pickup/gate-in and retain the approval reference. |
| Customs hold, inspection or export not released | Shipper/customs broker/authority | Declaration, manifest, seal, permit or inspection is incomplete. | Customs/terminal hold or inspection notice. | Confirm release/no-hold status before the terminal or carrier operational deadline and review voyage-data amendments. |
| Wrong container, seal or mass; operating limit exceeded | Warehouse/shipper/trucker | Container/seal mismatch, abnormal VGM, overweight or operating incompatibility. | Terminal exception, weight discrepancy or rework request. | Reconcile container–seal–VGM–booking and route limits before gate-in. |
| Container damage, leakage or safety rework | Warehouse/terminal/carrier | Equipment or cargo appears unsafe and needs survey, repair, rework or replacement. | Damage hold, survey report or terminal incident. | Record condition, obtain written instructions and control any new seal/container. |
| Weather, port closure, congestion or terminal incident | Port/terminal/carrier | High winds, storms, berth/crane limits, yard congestion or system failure. | Port notice, operational advisory or delayed berthing. | Monitor advisories and request confirmation of free-time/storage treatment. |
EVIDENCE FOR CONFIRMING CONTAINER STATUS
| Status | Meaning | Evidence | Conclusion limit |
|---|---|---|---|
| Full gate-in | The container entered the terminal. | EIR/gate event with timestamp. | Insufficient to prove loading. |
| VGM accepted | Carrier/terminal accepted the verified mass. | Portal/email acceptance. | Customs, documents and load plan still apply. |
| Customs released / no hold | No relevant customs hold remains. | Customs/terminal/portal evidence. | Not a loading confirmation. |
| Planned loading | The unit is scheduled for the voyage. | Tracking or load-list status. | May change before crane operation. |
| Loaded / Loaded on Board | The unit was physically loaded. | Carrier/terminal event or onboard confirmation. | Primary operational loading milestone. |
| Vessel sailed | The vessel departed the POL. | Actual departure/AIS/carrier event. | Check that the unit sailed on the same voyage. |
| Rolled / Rebooked | The unit was assigned to another voyage. | Rollover notice/revised booking. | Re-lock schedule, documents and costs. |
DOCUMENTS AND DATA TO REVIEW
| Document/data | Issuer/source | Fields to review | Use |
|---|---|---|---|
| Booking Confirmation and revisions | Carrier/NVOCC/forwarder | Booking, vessel/voyage, POL/POD, ETD, cut-offs, equipment, commodity, loading guarantee/rollable terms. | Defines the intended voyage and original commercial conditions. |
| EIR and terminal event history | Terminal/depot/trucker | Container, seal, full gate-in time, yard location, hold/exception. | Evidence of terminal receipt and the start of terminal exposure. |
| SI acceptance and draft B/L | Shipper/forwarder/carrier | SI submitted/accepted, voyage, packages, weight, parties, DG/OOG data. | Shows whether transport data was accepted or remains pending. |
| VGM submission/acceptance | Shipper/carrier/terminal | Container, VGM, method, signatory, timestamp, accepted status. | Required for using the packed container in the SOLAS stowage process. |
| Customs/terminal release status | Broker/customs/terminal | Declaration, customs hold, inspection, seal and release timestamp. | Identifies procedural or inspection blocks. |
| Rollover notice / revised booking | Carrier/NVOCC/forwarder | Reason, new voyage, ETD/ETA, routing, new cut-offs and charge treatment. | Basis for replanning and cause allocation. |
| Tariff, free time and invoice evidence | Carrier/terminal/contract | Export demurrage/storage, amendment, shifting, rework, reefer power and special-cargo tariffs. | Budgeting and invoice-dispute evidence during the waiting period. |
| Customer delivery commitment | Sales/customer/factory | Delivery date, production plan, penalty, buffer and emergency option. | Measures commercial impact and supports split/air/alternative-sailing decisions. |
ROLLOVER RESPONSE WORKFLOW
| Step | Action | Output |
|---|---|---|
| 1. Identify affected units | Match booking, container, seal, POL, voyage and terminal events. | List of rolled, loaded and unresolved containers. |
| 2. Obtain the written reason | Require the carrier/NVOCC to state the actual cause, supporting evidence and control scope. Internal analysis may group the event as carrier-controlled, merchant-caused, operational hold, omission or force majeure, but these are not universal standard reason codes. | Evidence for ownership, charges and escalation. |
| 3. Lock the replacement voyage | Confirm vessel/voyage, direct/transshipment routing, ETD/ETA, port rotation and further-roll risk. | A clear revised booking. |
| 4. Recheck cut-offs and acceptance | SI, VGM, customs, DG/OOG/reefer approval, manifest data and terminal holds. | All statuses accepted/released for the new voyage. |
| 5. Review documents and declarations | Check the draft B/L, C/O, payment documents, permits and transport data for required amendments. | Amendment list, owners and deadlines. |
| 6. Control the container in the terminal | Check location, seal, condition, free time, storage, shifting, reefer power and rework requirements. | Plan to keep, move, withdraw or rework the unit. |
| 7. Update the customer and supply plan | Assess the new ETA, safety stock, production-stop risk, split shipment or emergency mode. | Impact notice, mitigation option and next update milestone. |
| 8. Close the file after sailing | Retain loaded-on-board event, revised booking, reason emails, invoices and response timeline. | Audit trail for carrier KPI, claim and booking improvement. |
RISKS AND COMMON ERRORS
| Risk/error | Cause | Impact | Control |
|---|---|---|---|
| Relying on “container is in port” | Gate-in is treated as onboard confirmation. | ETA commitments are wrong and rollover is detected late. | Make Loaded on Board/Vessel Sailed mandatory milestones. |
| No separation of carrier and customer causes | No reason code or acceptance evidence. | Weak charge, compensation and KPI disputes. | Request the written cause on the day of notice. |
| Assuming SI/VGM automatically transfers | The team assumes every data set moves to the new voyage. | The revised booking remains pending or documents show the wrong voyage. | Verify acceptance for every data element after rebooking. |
| Ignoring export demurrage/storage | Tariff exposure while the unit waits is not tracked. | Unbudgeted cost, especially for reefer/DG/OOG. | Lock free time, charge-start event and any waiver request. |
| Seal/container change not controlled after rework | Equipment is changed or resealed without document updates. | SI, VGM, manifest, B/L or customs mismatch. | Use formal change control with new EIR/seal evidence. |
| Repeated rollovers | “Next available vessel” is accepted without priority control. | Factory delay and escalating cost. | Escalate, obtain guarantee/priority or change carrier/routing where feasible. |
| Only part of a multi-container booking is loaded | Container-level status is not monitored. | Split B/L, documents, origin papers and delivery become misaligned. | Manage each container and approve controlled booking splits. |
REFERENCES AND OFFICIAL SOURCES
| Source | What it supports | Use condition |
|---|---|---|
| Maersk – Rolled cargo | Defines rolled cargo as cargo not loaded on the intended vessel because capacity ran out. | Operational definition; use the shipment notice for the actual reason. |
| Maersk – Rollable cargo / next available vessel | States that most rolled cargo is moved to the next available calling vessel, without an absolute guarantee. | Explains rebooking logic, not a confirmed new ETD. |
| Maersk Spot Terms | Sets booking, load-promise, rollable-option and exclusion rules for the product. | Read the version incorporated into the specific booking. |
| Hapag-Lloyd – Shipping Guarantee | Describes protected loading and compensation mechanics subject to product terms and exceptions. | Do not extend it to standard bookings or other carriers. |
| Hapag-Lloyd – Quick Quotes Spot Terms | Sets the Quick Quotes Spot loading commitment, the booking party’s cut-off and operational obligations, and exceptions for causes outside carrier control. | Apply only to bookings under the stated product and current terms; do not generalise it to standard bookings. |
| IMO – SOLAS Verified Gross Mass | VGM must be available to the terminal and master early enough for the stowage plan. It is a loading condition, not an entitlement to load; the master retains ultimate discretion to accept a packed container. | International safety requirement for packed containers within SOLAS scope. |
FAQ
1. Does gate-in before the CY cut-off guarantee loading?
No. SI, VGM, customs, special-cargo approval, load-list status and operating conditions still apply. Loaded on Board is the loading confirmation.
2. Is every rollover caused by carrier overbooking?
No. Causes include capacity, omission, terminal conditions, weather, VGM, SI, customs holds, DG/OOG approvals, mass/seal errors and container condition.
3. Will a rolled container automatically sail on the next vessel?
A replacement is often proposed, but never assume it. Obtain a revised booking with the vessel/voyage, ETD/ETA, routing and new cut-offs.
4. Who pays storage while the container waits?
It depends on cause, tariff, contract and booking terms. The invoiced party and the party ultimately bearing the cost may differ; obtain written treatment immediately.
5. Why can a container with accepted VGM still be rolled?
VGM is only one condition and not a loading guarantee. Capacity, stowage, omission, customs, DG/OOG, damage and operational changes can still prevent loading.
6. Is a transshipment rollover different?
The mechanism is similar, but the cargo is already within the carrier network. Check the connecting vessel, connection time, congestion, transit documents and revised ETA.
7. Can the shipper claim compensation?
Only where the booking product or contract provides a commitment and claim conditions are met. A standard booking by itself does not establish an automatic compensation right; check the applicable carriage terms, exclusions and claim time bar.
Tiếng Việt
中文 (中国)
NEED TO REVIEW IMPORT PROCEDURES OR A SHIPPING PLAN?
Send us the product name, shipping route, current dossier, or implementation request in advance so we can suggest a suitable approach that is practical, focused, and aligned with your shipment.
Import procedure for cream-filled wafers: HS code, tax, food safety, C/O and E2E workflow
Gate Valve Export Guide: Markets, HS, Origin, Documents and Process
Industrial Router Export Guide: Markets, HS, Licensing, Origin and E2E Workflow
Exporting Butterfly Valves from Vietnam: Markets, HS 8481, Origin, Pressure Compliance and Transport
Laser Cutting Machine Export Procedure: HS, Dual-Use Screening, Origin and Shipping
Blade server export procedure: markets, HS, origin, dual-use screening and logistics
Exporting Gateways from Vietnam: Markets, HS 8517.62.21, Origin and Compliance
Mini PC export procedure: markets, HS, origin, dual-use, FCC/IMDA/OFCA and logistics
Exporting Industrial PCs from Vietnam: Markets, HS, Origin, Compliance and Transport
SERVER RACK EXPORT GUIDE: MARKETS, HS, ORIGIN, COMPLIANCE AND SHIPPING
Exporting Tower Servers from Vietnam: Markets, HS, Origin and E2E Workflow
Exporting PoE Switches from Vietnam: Markets, HS, Origin, Compliance and Transport
Desktop PC export guide: markets, HS code, origin and shipping
Exporting Edge Servers from Vietnam: Markets, HS, Origin and E2E Workflow
Exporting Load Balancers from Vietnam: Markets, HS, Origin, Compliance and E2E Workflow