Email to Shipment Automation: Shipments That Create Themselves

The Booking Email Already Contains the Shipment

Look at any booking confirmation in a forwarder's inbox and you will find the entire shipment written out in prose: shipper, consignee, FOB Shanghai to Jebel Ali, one forty-foot container, commodity, cargo ready date, the works. Then watch what happens next — an operator opens a TMS and re-types every field the email already contained.

That re-typing is the most expensive ritual in forwarding operations. It burns operator hours that should go to exceptions and customers. It introduces errors — a transposed container number, a wrong consignee — that surface later as detention bills and angry calls. And it means the shipment only exists once someone gets around to it, which on a busy day can be tomorrow.

Zavin removes the ritual. When a booking confirmation arrives, the shipment is created from the email with zero manual data entry: job file opened, parties resolved against your records, references captured, routing set, milestone plan attached. The email becomes operational data at the moment it lands.

What Gets Created — Without a Keystroke

“Creating a shipment” in Zavin means the whole working file, not a stub record someone still has to finish:

• •Job file — a complete shipment record with shipper, consignee, notify party, routing, mode, equipment, Incoterm, and commodity, matched against your existing customer and partner data.
• •References — booking numbers, container numbers, HBL/MBL or HAWB/MAWB references, and customer PO numbers captured and linked as they appear across the thread.
• •Documents — attachments filed against the shipment automatically, each one recognized for what it is rather than dumped in a folder.
• •Milestone plan — the expected chain of events for that mode and routing, from cargo pickup through departure, arrival, and delivery.
• •Pre-alerts and updates — outbound notifications to the customer and destination partner, generated and sent as the file progresses.

Document Filing That Knows an HBL From an Invoice

Freight documents arrive as attachments on a dozen different threads, and filing them is its own quiet time sink. Zavin reads each attachment and recognizes the document type — House B/L, Master B/L, commercial invoice, packing list, certificate of origin, arrival notice, delivery order — then files it against the right shipment using the references inside the document itself.

That last part matters. The MBL that arrives in a carrier's email three days after booking does not mention your job number; it mentions the container and booking reference. Zavin matches on what the document actually contains, so the file ends up on the right shipment even when the email subject line is “RE: RE: FW: docs”.

The result is a job file that is complete by default. When a customer or customs broker asks for the commercial invoice, it is on the shipment — not in someone's inbox, not in a shared drive, not attached to a thread nobody can find.

Pre-Alerts and Milestones on Autopilot

The communication around a shipment is as much work as the shipment itself. Destination offices need pre-alerts with documents attached. Customers want to know the vessel departed, the container arrived, the delivery is booked. In most operations, every one of those messages is typed by hand — or skipped when things get busy, which is exactly when customers worry most.

Zavin generates and sends this traffic automatically. Pre-alerts go to the destination partner with the HBL, MBL, and invoice attached the moment the file is ready. Milestone updates go to the customer as events happen — departure, transshipment, arrival, delivery — in your branding and tone. And when a customer emails “where's my container?”, the answer comes back instantly, at any hour, because the tracking module already knows.

The cadence is yours to shape. Some customers want every event narrated; others only want exceptions like a rolled sailing or a customs hold. Zavin applies the notification profile per customer, so a high-touch account gets the full commentary while a self-serve account gets a clean summary — without an operator remembering who prefers what.

What Stays Under Human Control

Operators do not lose the file — they supervise it. You decide which parts of the workflow run automatically and which wait for a human: many teams start by letting the AI create shipments as drafts for review, then move to full auto-creation for trusted customers and standard lanes once they have watched it work.

Approval rules are granular. Auto-send pre-alerts to your own branches, but hold customer-facing milestone messages for review. Let documents file automatically, but flag any shipment where the extracted details conflict across emails. Every action the AI takes — every field it filled, every document it filed, every message it sent — is written to a full audit trail, and field-level access control across every object, branch, and country governs who sees what.

Exceptions always go to people. Ambiguous bookings, mismatched references, or anything the AI is not confident about is escalated with its reasoning attached, so operators spend their day on the files that need judgment.

Connected to Email, Quoting, and Tracking

Shipment Management works because it sits inside a connected operating system. AI Email Automation is the front door: it reads every inbound message, recognizes booking confirmations, and hands them here — which is why shipments can create themselves. Upstream of that, Pricing & Quote Automation means many shipments begin life as a quote the platform already sent, so the shipment inherits the quoted rates, parties, and terms with nothing re-entered.

Downstream, Schedules & Tracking keeps every live shipment's status current from carrier data and answers customer tracking questions around the clock. Reports & Analytics sees every shipment the moment it is created, so volume, lane, and margin reporting reflects reality in real time rather than whatever got typed in last week.

Why Legacy TMS Data Entry Never Ends

A legacy TMS assumes a human bridge between the inbox and the system. The email arrives, a person reads it, interprets it, and re-types it — and the TMS's job starts only after all of that unpaid translation is done. Adding more TMS features never fixes this, because the bottleneck is in front of the system, not inside it.

That is why forwarders with capable TMS platforms still drown in data entry, and why job files are perpetually behind the inbox. Zavin is built the other way around: reading and acting on freight email is the platform's core competency, and the shipment record is an output of that reading. 80% of freight forwarding runs on email — a system that cannot read email was always going to need an army of typists.

Works Alongside CargoWise and Magaya — Live in Under 14 Days

Zavin does not ask you to abandon your system of record. It works alongside CargoWise, Magaya, and other TMS platforms, taking over the email-to-shipment workflow while your existing stack stays where it is. There is no migration and no IT project: connect your mailboxes, configure your milestone plans and approval rules, and run live bookings with your team reviewing the AI's work.

Most teams are live in under 14 days. The change your operators feel is immediate and simple: bookings stop being typing work. The shipment is just there — file open, documents attached, pre-alert sent — and their day starts at the part that actually needs them.