TradeWindow Integration

Documents extracted. TradeWindow updated.

StarShipper reads your trade documents and formats the data into the exact CSV structure TradeWindow expects. SpeEDI Cargo for ABF reporting with 40 columns, or Freight Manifest for job creation with 16. Port codes resolved, dates formatted, parties mapped.

The bottleneck isn't TradeWindow, it's preparing the data

TradeWindow handles cargo reporting and freight management for Australian importers and customs brokers. But building SpeEDI Cargo submissions means pulling manifest references, vessel details, port codes, party addresses, and container data from bills of lading, invoices, and packing lists. Each field has to be in the right format: UN/LOCODE for ports, DD/MM/YYYY for dates, Lloyd's number for vessels.

StarShipper extracts every field during document processing and formats it into the CSV structure TradeWindow expects. The SpeEDI Cargo format covers 40 columns including manifest references, vessel, voyage, IMO number, origin and destination ports, full party details, and per-container cargo lines with tariff codes. The Freight Manifest format covers 16 columns for job creation. Both formats handle multi-container shipments by expanding one row per container or line item.

Your team still reviews the submission. They just stop copying fields from PDFs into spreadsheets.

Documents Arrive

Bills of lading, invoices, and packing lists

StarShipper Extracts

AI reads vessel, ports, parties, containers, and cargo details

TradeWindow Updated

SpeEDI Cargo or Freight Manifest CSV ready for import

Built for TradeWindow

Not a generic CSV. Two purpose-built formats matching exactly what TradeWindow's import system expects: SpeEDI Cargo for ABF reporting and Freight Manifest for job creation.

SpeEDI Cargo format

40-column ABF cargo reporting CSV. Manifest references, vessel, voyage, IMO (Lloyd's number), ports, parties, container lines, tariff codes.

Freight Manifest format

16-column job creation CSV for TradeWindow Freight module. Product codes, descriptions, weights, packaging, seal numbers.

Australian port codes

UN/LOCODE port resolution from your documents. Port alias handling built in for common variations.

Date formatting

ISO dates from extraction converted to DD/MM/YYYY for TradeWindow import. No manual reformatting.

Multi-line cargo rows

One CSV row per container or line item. Multi-container shipments expand into the right number of rows automatically.

Full party mapping

Shipper, consignee, notify party with name, address, city, and country extracted and mapped to the right columns.

What the integration covers

SpeEDI Cargo format (40 columns) for ABF reportingFull cargo reporting CSV with manifest references, vessel, voyage, IMO, ports, parties, and tariff codes.
Freight Manifest format (16 columns) for job creationCompact CSV for TradeWindow Freight module with product codes, weights, packaging, and seal numbers.
Australian port code resolution with alias handlingUN/LOCODE ports resolved from document text. Common port alias variations handled automatically.
Vessel IMO (Lloyd's number) includedVessel identification number extracted and mapped to the LloydsNumber column in SpeEDI Cargo.
Full party mapping (shipper, consignee, notify)Name, address, city, and country for all three party roles extracted and mapped.
DD/MM/YYYY date formatting for Australian systemsDates converted from ISO format to the DD/MM/YYYY format TradeWindow expects.

Send a document. See what TradeWindow 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 formatted for TradeWindow import. No signup required.

or

View all solutions →