Sea export, from booking to stuffed container.

The Sea Export module covers the full outbound sea-cargo lifecycle.

• Allotments — pre-purchased space from carriers; pool of TEUs.
• Customer Booking — confirms space for a specific shipper.
• Carrier Booking — your booking against the shipping line.
• Shipping Instructions — sent to the carrier after CY cutoff.

Allotment Dashboard is the cockpit view of every allotment in the system. Shows at a glance:

• How much capacity is allocated, used, available
• Utilization % with color coding (🟢 <60% / 🟡 60–85% / 🔴 >85%)
• Days remaining in the period
• MQC penalty exposure (if MQC tracking is enabled on that allotment)

Two opposite kinds of risk visible on one screen:

• Operational risk (🔴 red): allotment nearly exhausted, no space for new customers
• Commercial risk (⚠ warn-low): allotment underused, MQC penalty looming if not consumed

Filter by Mode (Sea/Air/Road), Carrier, Date range. Click any row to drill into the per-equipment capacity breakdown.

An Allotment is the commercial commitment between you and a shipping line: e.g. "Maersk gives me 100 TEU on the AE7 service Karachi → Jebel Ali for the month of June at $1,450 per 40HC". You commit to the volume; in return you get guaranteed space + locked rates.

Industry terminology — same idea, different names:

• Sea: Service Contract, MQC (Minimum Quantity Commitment), BSA (Block Space Agreement)
• Air: Allotment, Hard/Soft Allotment
• Road: Lane Commitment

Key features in LogiSoft:

• Capacities tab — break the total into per-equipment lines (e.g. 100×40HC + 50×20DV)
• MQC (optional) — track penalty exposure if you don't meet the commitment
• Roll-over policy — bookings stay on the original allotment period when a vessel rolls (industry default)
• Equipment-first dashboard view — see at a glance: "Maersk Karachi→Jebel Ali, 40HC: 28/100 available"

Allotments are optional. Customer bookings can run "spot" without one — you just won't get rate/capacity benefits.

A Carrier Booking is what you submit to the shipping line (e.g. Maersk, MSC) to reserve actual space. It carries the cost rate and the carrier's confirmation reference.

How it relates to Customer Bookings:

• One Carrier Booking can serve multiple Customer Bookings (consolidation)
• One Customer Booking can be split across multiple Carrier Bookings (rolling)
• Optionally pulls from a pre-purchased Sea Allotment for guaranteed space + locked rate

Status updates flow the same way as Customer Bookings — locked status field on header, all changes via the Tracking tab.

A Customer Booking captures the demand — your customer wants to ship cargo and asks you to arrange it. This booking is the source-of-truth record for that shipment until the BL is issued.

Two bookings to keep separate:

• Customer Booking (this screen) = your customer → you. Sell rate captured here.
• Carrier Booking = you → shipping line. Cost rate captured there.

How it links:

• Optionally pull from a pre-purchased [Sea Allotment](/SeaAllotments/Index) — this auto-suggests when you click the magic-wand button
• The system can require an Allotment link or a Carrier Booking link via Module Settings → Sea.RequireAllotmentLink / Sea.RequireCarrierBookingLink (off by default — see Configuration-driven enforcement)

CBM auto-fill: when you pick a container size on a line (20 / 40 / 40HC / 45), the CBM column fills with the size's standard capacity (33 / 67 / 76 / 86). Override per line if cargo doesn't fill the container. Header Total Volume is auto-summed from the lines.

Booking Templates save the standard fields of a booking (customer, route, equipment, charges, incoterm, freight term, commodity, description) so the next booking for the same recurring shipper takes 5 seconds instead of 5 minutes.

Cross-mode: one template per (Mode, BookingType, Name) — a Sea Customer Booking template is separate from an Air Customer Booking template even if for the same customer.

SI Inbound tracking answers a single question: which of my customers still owe me a Shipping Instruction for this voyage?

Each row represents one Customer Booking. Status colors:

• 🟢 Received — customer sent the SI
• 🟡 Pending — within the cut-off window
• 🔴 Late — past the SI cut-off

Mark received: click the upload button, attach the customer's SI document (PDF/image), add notes, save. The document is stored linked to the booking. Bulk-select rows to send email reminders via the existing Email Templates engine.

SI Outbound tracking is the second half of the SI workflow. After receiving SI from a customer, you forward it to the carrier (typically by email with PDF attachment, sometimes via EDI).

Status colors:

• 🟢 Sent — SI submitted to carrier
• ⚠ Awaiting Customer — can't send because customer hasn't given us the SI yet
• 🟡 Pending — have customer SI; not yet sent
• 🔴 Overdue — past carrier cut-off; risk of missed sailing

The bulk-send action consolidates multiple bookings on the same vessel/voyage into one PDF attachment to the carrier — much faster than per-booking emails.

Shows Sea bookings that are still missing a customer SI. Click Send Request on a row to email the configured recipient (Customer for Export; configurable Shipper/Consignee/OriginAgent for Import). The booking's SI Request Sent checkbox auto-ticks once the email goes out.

Lists Sea bookings of any direction (Import + Export). Each row has quick-action milestone buttons; clicking one logs that milestone with the current timestamp and updates the booking's status badge. Branch-scoped to your allowed branches.

Settings that apply across the entire Sea Export module. Each setting is grouped under a Category tab — pick the tab, change the value, click Save Settings.