One shipment: booking to manifest/VGM
Example project PRJ (e.g. TXHSZYUK251217).
Roles
| Role | Description |
|---|---|
| Customer | Sends booking pack; receives pre-booking forward + manifest/VGM |
| Booking office | Receives booking request; sends pre-booking |
| Fleet / customer | May send container seal list |
| System mailbox | Your monitored mailbox: sends booking, forwards pre-booking, sends manifest |
Timeline (logical order)
A — Booking
- Customer → system mailbox: ORDER mail + attachments → project created/updated; if gates allow, booking request to booking office.
- System → booking office: subject like
[Booking] PRJ; body from LLM/template; may attach booking pack. If approval on → queue first, send frozen content after approve.
B — Pre-booking
- Booking office → system: PREBOOKING.
- System → customer: forward pre-booking; subject like
PRJ pre-booking info; attachments from PREBOOKING docs. Approval path same as above.
C — Customs + seal list (order flexible)
- Customer → DECLARATION attachments.
- Fleet/customer → CONTAINER_LIST.
Both declaration docs and seal list must exist before manifest/VGM generation.
D — Manifest & VGM
- System → customer: subject like
PRJ manifest and VGM; attachments generated files. If approval: files generated before queue; after approve, send frozen content only.
Outbound mail summary
| # | To | Example subject |
|---|---|---|
| 1 | Booking office | [Booking] PRJ |
| 2 | Customer | PRJ pre-booking info |
| 3 | Customer | PRJ manifest and VGM |