A shipper wrote in last week: "We booked FCL on the **shipping route from Xiamen to Dubai**, filed our SI two days before cut-off, sent VGM on time — and the container still did not sail. The carrier just says 'rolled' and gives no reason. How is that possible?" It is possible, and it is more common on this lane than most exporters realise.

![Freight image](https://zhongdong123.cn/image/A015.jpg)

### Cut-off is a deadline, not a guarantee

Three separate deadlines sit between your booking and the vessel: the cargo/booking cut-off, the **SI cut-off**, and the VGM cut-off. Clear all three and the terminal will accept your container.

Whether it actually sails depends on a fourth factor nobody publishes — the carrier's **allocation and roll list**. When a vessel is over-committed, bookings are ranked by revenue, contract type, DG status and onward connection. Yours can be fully compliant and still rank last.

### Pitfall 1: Overbooking, and where your rate sits

Carriers routinely accept more bookings than the vessel can carry, because a percentage of shippers always cancel. When everyone shows up, the excess is rolled.

The bookings cut first are usually those priced below the current market, short-term NVOCC rates, and cargo with no long-term contract behind it. That is why a **Persian Gulf rate** quoted three weeks ago plus a new **Red Sea surcharge** can push you off the list: space goes to the cargo paying today's number.

### Pitfall 2: Equipment, weight and VGM

A confirmed booking is not a confirmed container. Xiamen equipment pools tighten during peak export weeks, and 40HQ boxes run short first. Heavy **machinery** and **building materials** add a second problem: stack weight and road limits.

If VGM arrives late, or the terminal's weight plan rejects a heavy box, the container can be offloaded at the quay even after gate-in.

### Pitfall 3: Documentation triggers that quietly re-rank you

An **amendment** after SI submission is one of the most overlooked causes of a roll. The carrier has already filed the manifest; changing shipper, consignee, HS code or final destination forces a re-filing and a re-check of the booking.

Special cargo is stricter. **Lithium batteries** and other **dangerous goods** need DG approval, MSDS and UN38.3 test summaries, plus a slot against the vessel's DG capacity — and that approval can be withdrawn when capacity is reallocated.

For **Saudi**-bound cargo moving via Jebel Ali toward Dammam or Jeddah, **SABER** and **SASO** readiness is reviewed before loading. A missing certificate or a mismatched consignee on a **DDP** booking is enough to hold the box at origin.

### Pitfall 4: The vessel changed, not you

Blank sailings, vessel phase-outs and service reconfigurations are routine on Middle East services. A rotation change can pull your cut-off forward with less than a day's notice. The terminal keeps the container; the booking rolls to the next sailing.

### Pitfall 5: The roll happens at the relay port

Not every container on the **shipping route from Xiamen to Dubai** is loaded direct. Many routings connect through Jebel Ali, Khor Fakkan, Colombo or Singapore before reaching Dammam, Jeddah or **Hamad Port**.

Your container can leave Xiamen on schedule and still miss the connection at the relay port because of feeder delays or yard congestion. From the shipper's side it looks identical to an origin roll — the cargo simply arrives two weeks late.

| Symptom | Most likely cause | Check this first |
| --- | --- | --- |
| Gate-in confirmed, container not loaded | Overbooking, low-priority allocation | Ask for the roll notice and reason code in writing |
| Equipment released late, VGM missed | 40HQ shortage at Xiamen | Confirm container release before filing SI |
| SI accepted, then amended | Re-manifest risk | Freeze the SI — submit once, correctly |
| Sailed from Xiamen, stuck en route | Missed connection or feeder delay | Track the relay port, not just the origin |
| DG or battery booking cancelled | DG capacity reallocated | Get DG approval in writing before trucking |
| Saudi-bound cargo held at origin | SABER/SASO or consignee data | Verify certificate validity and consignee details |

### What to do in the first 24 hours after a roll

1. Request the roll in writing, with the carrier's reason code — not a verbal "no space".
2. Ask for the next available vessel and its estimated arrival, and confirm whether the roll is at origin or at the relay port.
3. Confirm who carries storage and demurrage, and from which date.
4. Ask whether the quoted rate and surcharges still apply to the new sailing, or whether a fresh **Persian Gulf rate** will be used.
5. For **DDP** and Saudi-bound cargo, notify the consignee and check that certificates will still be valid on the new arrival date.
6. For **lithium batteries** and other **dangerous goods**, re-confirm DG acceptance for the new vessel before the container is re-nominated.

### How to lower the risk on your next booking

- Book **confirmed allocation**, not a soft space request, and ask how many slots the carrier holds on that service.
- Compare a direct call at **Jebel Ali** against a transhipment routing to Dammam, Jeddah or Hamad Port — one connection is one more roll point.
- Submit the SI once and correctly. Every amendment is a flag on your booking.
- Pre-clear DG, battery and certification paperwork days before cut-off, not hours.
- Keep a buffer between cargo readiness and cut-off; late gate-in is the easiest roll to avoid.

None of this makes a roll impossible — overbooking is a commercial decision, not an operational mistake. But understanding where the risk sits turns a mystery into a manageable variable.

Before booking your next **shipping route from Xiamen to Dubai**, ask your forwarder for three things in writing: the carrier's confirmed allocation and roll policy, the latest freight rate plus applicable surcharges, and destination charge confirmation for the port that will actually clear your cargo.
