Documents in. CargoWise updated.

Forward the pre-alert and StarShipper does the keying. It reads the B/L, invoice and packing list, builds the shipment, and sends it into CargoWise One with your organisation codes on the parties and the documents filed on eDocs. Your team opens the job and it's already filled in.

Send to CargoWise
HBL SZ2604118 · Forwarding shipment + customs declaration
Organisations: 4 of 4 matched
ShipperHartwell Pumps Ltd
HARPUMLGP
Name and address
ConsigneeCoastline Civil Pty Ltd
COACIVSYD
ABN
NotifyCoastline Civil Pty Ltd
COACIVSYD
ABN
CarrierMSC
MEDSHI_AU
Name
Documents for eDocs
HBLHouse bill of ladingCIVCommercial invoicePKLPacking list
eAdaptor Next · OAuth certificateSend

From the pre-alert to a CargoWise job

A shipment usually arrives as a pre-alert with five or six PDFs attached. Someone opens each one and keys the vessel, voyage, ports, dates, containers, parties and invoice lines into CargoWise, then saves the PDFs to eDocs by hand. For a desk handling 30 shipments a day, that's most of the morning.

StarShipper reads those documents and puts them together as one shipment, checking the B/L against the invoice and packing list as it goes. When it's ready, it sends a Universal XML message to your CargoWise instance. CargoWise finds the job by its house bill and references and updates it, or creates it if it's new. The shipper, consignee and carrier carry the organisation codes from your own list, and the source documents are filed on the job under your eDoc types. When an amended invoice turns up, the same job is updated.

Vessel, voyage, ports, dates, containers, parties, invoice lines and documents are all in the job before anyone opens it. Your people spend their time on the shipments that need a decision.

Documents arrive

B/Ls, invoices and packing lists by email or upload

StarShipper builds the shipment

Fields extracted, checked across documents, parties matched to org codes

CargoWise updated

Job created or updated, parties coded, documents on eDocs

Built for CargoWise

Built on CargoWise's Universal XML and eAdaptor, set up around the way your business already runs CargoWise: your modules, your organisation codes, your eDoc types.

Ready for WiseCloud

Connects through eAdaptor Next with the OAuth certificate login WiseCloud requires, and still talks to self-hosted instances on the classic eAdaptor. Setup is a one-off: create an EDI Client, add the details, test the connection.

Your organisation codes on the parties

Upload your CargoWise organisation list once. Shippers, consignees, notify parties and carriers are matched to your codes by ABN, name and address within your branch, so jobs arrive linked to the organisations you already have.

Forwarding, customs and agency

Forwarders get the forwarding shipment, the consol with its main-leg routing, and the customs declaration, kept in step with each other. Shipping agencies send straight to the Bill of Lading module.

Documents filed on eDocs

The B/L, commercial invoice, packing list and certificates are attached to the job and labelled with your own eDoc types. Nobody has to save a PDF by hand.

Updates the job you already have

CargoWise matches the shipment on its references and updates it in place. Send again after a change and the same job, consol and declaration are updated. Each send is tracked, with CargoWise's own response recorded and retries handled for you.

Clean data from the start

Ports arrive as UN/LOCODE, container numbers are checked against ISO 6346, transport modes use CargoWise's codes, and invoice lines carry their HS codes.

Getting connected

An EDI Client in CargoWiseYour CargoWise admin creates one for StarShipper. We provide the certificate.
Your eAdaptor endpointeAdaptor Next for WiseCloud, or the classic eAdaptor for self-hosted instances.
Your eDoc typesSo documents are filed under the labels your people already use.
Your organisation listExported from CargoWise and uploaded once, so parties arrive with your codes.

Step-by-step instructions are in the CargoWise setup guide.

Common questions

Does it work with CargoWise on WiseCloud?

Yes. StarShipper connects through eAdaptor Next with OAuth 2.0 certificate authentication, which is what WiseCloud requires. Self-hosted instances on the classic eAdaptor are supported as well.

Do I need to give StarShipper our CargoWise job numbers?

No. CargoWise matches the shipment on its house bill and references, updating the job if it exists and creating it if it doesn't. StarShipper remembers the job CargoWise created, so later sends update the same one.

How are parties matched to our organisation codes?

You upload your organisation list from CargoWise as a spreadsheet. StarShipper matches the shipper, consignee, notify party and carrier against it by ABN, then name and address, within your controlling branch. The Send screen shows the codes before anything goes.

Can shipments go to CargoWise automatically?

Yes. Turn on auto-send and shipments go to CargoWise as soon as their documents pass extraction and cross-document checks. Anything that needs a look waits for review. You can also send any shipment yourself in one click.

Which documents end up in CargoWise?

The source documents behind the shipment: bills of lading, commercial invoices, packing lists, certificates of origin and more. They're attached to the job on the eDocs tab under your own document types.

Send a document. See what CargoWise would receive.

Forward a B/L or invoice to the address below. StarShipper will extract it and show you the structured result, the same data that goes into the CargoWise message. No signup required.

or

View all solutions →