Expedient Integration

Documents in. Expedient updated.

StarShipper reads your shipping documents, extracts every field, and sends a structured forwarding manifest directly to Expedient's intake system. References, containers, line items, parties. No manual data entry into the TMS.

The bottleneck isn't Expedient, it's the data entry to get there

Expedient (e2open) handles customs declarations and freight forwarding. But every shipment that arrives needs someone to key references, container numbers, line items, weights, and party details into the system. For a team processing 20 or 30 shipments a day, that's most of the morning gone on data entry.

StarShipper reads those documents during extraction and builds a 58-column forwarding manifest CSV. References, transport details, port codes, dates, cargo summary, container data, line items with HS codes, and full party details including ABN. The CSV is sent directly to Expedient's email intake address. Your team reviews exceptions, not every field.

Your team still handles the exceptions. They just stop typing what a machine already read.

Documents Arrive

Commercial invoices by email or upload

StarShipper Extracts

AI reads references, containers, line items, and parties

Expedient Updated

58-column CSV manifest sent to intake email

Built for Expedient

Not a generic webhook. This is a structured forwarding manifest in the exact format Expedient's intake system expects.

Zero-config delivery

Point StarShipper at your Expedient intake email address. No API keys, no VPN, no IT tickets.

58-column forwarding manifest

Full shipment detail: references, transport, ports, dates, cargo, containers, line items, parties. Everything Expedient needs.

One row per container and line item

Denormalised CSV that Expedient's parser expects. Multi-container shipments expand into the right number of rows.

Injection-safe CSV

Formula prefix detection and RFC 4180 escaping on every value. No spreadsheet injection vectors in the output.

Auto-dispatch

Configure once, every shipment flows to Expedient automatically after extraction. Or trigger manually from the shipment page.

ABN included

Australian Business Number in the export for customs declarations and compliance.

What the integration covers

58-column forwarding manifest CSVFull shipment data including references, transport, ports, containers, line items, and parties.
All shipment references (HBL, MBL, booking, invoice)Every reference extracted from your documents, mapped to the right CSV columns.
Full container and line item detailContainer numbers, seal numbers, weights, descriptions, quantities, HS codes, country of origin.
Party data with ABNShipper, consignee, and notify party with addresses. ABN included for Australian customs.
Formula injection protectionRFC 4180 escaping and formula prefix detection on every value in the CSV output.
Auto-dispatch or manual sendConfigure per-integration: send automatically after extraction, or trigger manually.

Send a document. See what Expedient would receive.

Forward a B/L or invoice to the address below. StarShipper will extract the data and show you the structured result, the same data that would be sent to Expedient as a CSV manifest. No signup required.

or

View all solutions →