Booking a container

This walks the trader’s side of the booking flow. (The forwarder’s side is symmetric: requests appear in your inbox; confirming triggers the same events from the other direction.)

1. Pick a schedule from /shipping-schedules and click Request booking.

2. Pick cars to assign. The picker shows only cars with containerId IS NULL (a car can’t be in two containers). For a RORO trip, similar — cars with roroShipId IS NULL.

3. Pick equipment type (container only) and loading method + days. The pricing matrix cell-matches your choices; total cost appears in the forwarder’s service currency.

4. Pick destination location (optional). When the container is marked arrived later, every car’s locationId will be set to this value automatically.

5. Submit. Forwarder receives the request in their booking inbox.

6. Forwarder confirms. This:

   • Creates the container or RORO trip in your namespace.
   • Sets each car’s containerId (or roroShipId).
   • Auto-advances each car’s status purchased → shipped.
   • Issues a confirmation packet.

7. Pay the forwarder. Open the forwarder’s invoice (it lands in your invoicing list as a received_invoice), record payment from a vault. GL posts to AP and a freight cost row goes onto each car’s landed cost.

Capacity guard

Each container has a capacity (cars-per-box). The booking form rejects assignments that exceed it. Cancelled cars keep their containerId for audit but don’t count toward capacity, so you can re-book the slot.

Modifying after confirmation

You can:

• Add cars to a confirmed booking (subject to capacity).
• Remove cars via Unmap from container — the car’s status reverts to purchased if it has no other shipping assignment.

You can’t change the destination terminal or ETD/ETA — those belong to the forwarder.

Related

• Schedules
• Container vs RORO
• Document checklist
• Tracking