When the sailing leaves without your container

The booking is confirmed, the container is stuffed and the cut-off is met. Then the vessel sails and the shipment status shows the container stayed on the quay. A short shipment is the sharpest version of a failed booking, but the same recovery question follows any confirmed booking that does not result in a loaded container: a cancelled booking, cargo that missed the cut-off or space that never materialised. Your customer still expects a departure date, your inland transport may already have run, and the original booking is no longer a plan you can work with.

Most of the work in our cargo-ready rescheduling playbook happens before gate-in, while the booking is still alive and an amendment can fix it. This playbook starts where that one ends: the booking has failed, and the job is to close it cleanly and get the cargo onto the next sailing without losing the record.

Scope and exclusions

This playbook covers a failed ocean booking on a forwarder file: the container was short shipped, the booking was cancelled, or cargo missed the sailing. It does not cover hazmat rejections, customs holds or equipment defects found at gate-in, which usually need terminal or customs involvement before any rebooking decision. It also does not set carrier fees or deadlines: those come from the booking terms and the carrier’s current guidance for your trade, not from this page.

Step 1: Establish what actually happened

Before anyone emails the customer, confirm the booking state from the carrier’s own record. Read the latest status for the booking and the container — loaded, rolled, short shipped or cancelled, and on which vessel and voyage. Capture the evidence as issued, a portal status page or the notification message, and store it against the booking file.

If the container was short shipped, raise it formally rather than in passing. Maersk’s guidance, for example, directs customers to report a short-shipped container through its Case Management system, selecting Cargo/Container, then Container Status, then Container has been Short Shipped, linking the shipment and attaching supporting documents; the carrier states an aim to resolve cases within 4 working hours. Whatever your carrier’s route is, the formal channel gives you a case reference — the anchor for everything that follows.

Done when: you have a recorded booking state, the vessel and voyage it failed on, and a carrier case or reference if one exists.

Exception: if the status is ambiguous — the booking shows confirmed but the container shows not loaded — treat it as short shipped until the carrier confirms otherwise, and say so in the file note rather than waiting.

Step 2: Decide what happens to the existing booking

A failed booking has two possible endings with different consequences.

  • The carrier closed it. The booking is cancelled at the carrier’s side, possibly with fees or a new quotation for the next sailing. Confirm in writing whether any cancellation or rebooking charge applies before you commit the customer to a new price.
  • The booking survives but the cargo does not. Some failures leave the booking standing while the container misses the vessel. Then decide deliberately: rebook the same booking onto the next sailing, or cancel it formally and start fresh. Leaving it in limbo guarantees a second failure. If you close it yourself, use the carrier’s formal route — Maersk’s cancellation guidance, for example, runs from the shipment summary: select Cancel, give a reason from the dropdown, add comments and complete the cancellation.

Done when: the file records one clear decision — rebook on the existing booking, or cancel and rebook — with who made it and the cost basis if any charge was quoted.

Exception: if the customer may prefer a different carrier or mode entirely, cancel nothing yet. Pause, present the confirmed options and prices, and resume once they choose.

Step 3: Rebook against facts

Rebooking is an amendment-shaped task: pick the next sailing, confirm equipment, check cut-offs against the container’s actual position, and get the revised confirmation. The discipline is the same as any other change — one clear instruction, an approval attached to it, and a returned confirmation checked field by field. It is the same sequence our ocean booking rescheduling workflow is designed to support.

  • Next sailing and closing dates, checked against the container’s real location and any outstanding inland legs.
  • Equipment: does the released container carry over to the new booking, or is a new release needed?
  • Costs: any rebooking charge or freight difference, approved by whoever approved the original quote before you confirm to the customer.
  • Documents: the shipping instructions and draft B/L must follow the new booking. If documents were already in progress, our SI and draft B/L correction playbook covers keeping the approval attached to the right revision.

Done when: a revised booking confirmation is returned and checked against the approval — use our amended booking confirmation checklist for that comparison.

Exception: if the next sailing is full or the quote changes materially, that is a new decision, not a correction. Go back to the customer with options before submitting.

Step 4: Tell the customer once, with the recovery attached

The customer call goes better after Steps 1–3 than during them. One message: what happened to the original booking, the new sailing and cut-offs, the cost impact and who approved it, and the new expected departure. Avoid a sequence of updates that each revise the last; assemble the recovery first, then communicate it.

Done when: the customer has the new booking details and the cost position in writing, and the file shows who sent it.

Step 5: Close the record

A failed booking produces more paperwork than a smooth one, and it is the file most likely to be queried later — by the customer over charges, or by a colleague picking up the destination leg. Assemble the same four artefacts we describe in booking amendment tracking: the evidence of what happened to the original booking, the cancel-or-rebook decision with its approval, the new booking confirmation, and the field check against it. Add the carrier case reference from Step 1.

Done when: a colleague could reconstruct the failure and the recovery from the file alone, without reading anyone’s inbox.

Example

For example, a forwarder’s 40HC on a north Europe to Asia service is short shipped at the load port. The operator confirms the status on the carrier portal, raises a case through the carrier’s formal short-shipment route and receives a case reference. The customer, whose consignee needs the goods within three weeks, approves rebooking onto the next sailing at a quoted difference of USD 180. The operator submits the rebooking, checks the revised confirmation — new vessel, same 40HC, new cut-off three days out — against that approval, and sends the customer one message with the new departure, the cost and its approval. The file holds the short-shipment evidence, the case reference, the approval, the revised confirmation and the check result, so the later query about the USD 180 is answered from the record.

Where a workflow review earns its keep

Short shipments and failed bookings arrive without warning, and each one costs a burst of unstructured work: status checking, case raising, re-approval, re-documentation and customer communication. Unhurdled builds AI-assisted workflows that keep that burst under control — assembling the status evidence and case reference, drafting the rebooking instruction for human approval, and checking the returned confirmation against it, so the recovery is a guided sequence rather than a scramble. If failed bookings and short shipments are a recurring cost in your operation, Let’s talk about reviewing one of them with us.