LOGISTICS / CARGOWISE
CargoWise integration for freight document automation
Mirage reads the documents your operators key into CargoWise today, checks them against each other and your codes, and sends the approved data to your instance through eAdaptor. A person reviews what does not reconcile. Your CargoWise configuration stays as it is.
THE REALITY
CargoWise holds the shipment, but most of what fills it still arrives as a PDF, a scan or an email that an operator opens, reads and keys field by field, then checks against the other documents of the same shipment by eye.
WHAT MIRAGE DOES
From the document to the shipment in CargoWise
Reads every format
PDF, scans and email bodies, in the layouts your shippers, carriers and agents actually send, without a template per document type.
Checks before it writes
Documents of the same shipment are checked against each other, parties against your organization codes, and anything that does not reconcile goes to a person with the reason.
Writes through eAdaptor
Approved data goes to your instance through the interface CargoWise provides, with its own credentials, logged message by message.
FIRST, WHAT CARGOWISE ALREADY DOES
Check CargoWise's own document capture before adding anything
WiseTech describes a document portal embedded in CargoWise that captures documents uploaded through eDocs and posts them straight through when its accuracy thresholds are met. Commercial invoices are listed as available; bills of lading, packing lists and transport bookings as coming. An invoice processing portal extracts supplier, amounts and job references from invoices forwarded by email. WiseTech also bought Shipamax, a data entry automation business, in November 2022, to embed it in the CargoWise document engine.
If most of what your team keys is commercial invoices in common layouts, test that capability first: it lives inside the system and needs no integration. An outside workflow earns its place when the documents, layouts or checks are not covered, when a document has to be checked against others before anything is written, or when the same data must also reach another system.
THE CONNECTION
How the workflow talks to CargoWise
CargoWise exchanges data with outside systems through eAdaptor, its XML messaging interface. WiseTech describes eAdaptor Next as using OAuth 2.0 in both directions and REST over HTTP with XML for inbound messages, with separate credentials for each external system. The CargoWise Connector handles the transport side, from HTTPS and SFTP to email and web services.
- eAdaptor's developer documentation is not public. WiseTech shares it with CargoWise customers and with partners, who sign a confidentiality agreement before reaching restricted resources. The field-level design is therefore done with your administrator, against your instance.
- Your CargoWise administrator confirms that eAdaptor is available on your instance and sets up the connection for the workflow. Mirage does not reach CargoWise through a shared user login.
- WiseTech runs partner programmes; Mirage is not part of one and holds no CargoWise certification. The integration is built for your instance with the interface it provides.
DOCUMENTS
What is read, where it lands, when a person checks
A design example for a forwarder's import desk. The exact message types and fields are agreed against your eAdaptor configuration before the build.
| Document | What is read | Where it lands in CargoWise | Goes to a person when |
|---|---|---|---|
| Commercial invoice | Seller, buyer, invoice lines, quantities, values, currency, origin | Shipment and customs declaration data | Totals that do not reconcile with the packing list |
| Bill of lading (house or master) | Parties, containers and seals, ports, vessel, dates | Shipment and container data | A container number that fails its check digit, or a party with no match |
| Packing list | Packages, gross and net weights, volumes | Shipment packing and weight data | Weights or package counts that differ from the bill of lading |
| Arrival notice | Vessel, ETA, charges, free time | Shipment dates and expected charges | No shipment found for the references on the notice |
| Carrier or agent invoice | Charge lines, amounts, job references | Costs against the job | A cost that differs from what was expected on the job |
ACCESS, MAPPING, DUPLICATES, ERRORS
What to set up, and what to refuse
| Area | Do | Avoid |
|---|---|---|
| Access | An eAdaptor connection with its own credentials for the Mirage workflow, set up by your CargoWise administrator | Shared user logins, or a connection that can send message types the workflow does not need |
| Environment | A test or training instance first, if your licence includes one | Building and testing against production |
| Organizations | Parties matched to the organization codes already in CargoWise | Creating new organizations from a document |
| Codes | Ports, charge codes and units mapped to the lists your instance uses | Free text where CargoWise expects a code |
| Duplicates | Each document and each message keyed on its references and a file hash, so a resend changes nothing | Sending again on a timeout without checking what CargoWise received |
| Errors | A message CargoWise rejects is logged and the document goes to review with the reason | A failed send that leaves nothing in CargoWise and nothing in a queue |
THE PILOT
Read only first, then a test instance, then production
Set the pass marks before the pilot starts, per field and per document type, and decide who signs the result. Nothing is written to production until a document type has passed.
| Phase | What happens | Condition to move on |
|---|---|---|
| Read only | The workflow reads the documents and produces its proposed data in a review list; your operators key as usual | Proposals match what the operators keyed, field by field, at the thresholds you set |
| Write to test | Approved proposals are sent through eAdaptor to a test or training instance | Every message accepted, no duplicates, nothing lost |
| Write to production | Document types that passed are sent to production; a person approves what the rules flag | The same criteria hold for two weeks in a row |
SOURCES
Where the CargoWise facts on this page come from
WiseTech Global's own pages and product flyers, read on October 5, 2026. CargoWise changes; check with WiseTech and your administrator before you build.
- WiseTech Global, partners: integration scopes and onboarding: integration covers CargoWise interface development, eAdaptor and EDI scopes; partner access to restricted resources after a confidentiality agreement
- CargoWise, eAdaptor Next (flyer): OAuth 2.0 inbound and outbound, REST (HTTP and XML) replacing SOAP for inbound asynchronous messages, separate credentials per external system
- CargoWise Connector (flyer): transports supported: HTTP(S), FTP, SFTP, FTPS, email, file system, SQL/ODBC, REST web services
- CargoWise, Document Management Portal (flyer): document capture embedded in CargoWise; commercial invoices available, bills of lading, packing lists and transport bookings announced
- CargoWise, Invoice Processing Portal (flyer): invoices forwarded by email or uploaded, supplier, amounts and job references extracted
- WiseTech Global, acquisition of Shipamax (November 2, 2022): Shipamax acquired by WiseTech Global, to be embedded in the CargoWise document engine
- CargoWise, become a partner: the partner programmes WiseTech runs
PROOF
Freight document automation in production, on other TMS
Mirage has not published a CargoWise deployment. These two run on the TMS each client already used.
OFRET Groupe
Connected to its TMS, Logitude World, through the Logitude World API
90%+ of standard RFQs handled automatically
Transwin
70% less manual entry on freight documents
Wired into the TMS Transwin already ran
Send us a document your team keys into CargoWise
Attach one bill of lading, invoice or arrival notice, and tell us which CargoWise screens it feeds. We come back with what can be read, what needs review and what the connection involves on your instance. We answer within two business hours.
How a deployment runs: Observe, Map, Build, Run, Expand. See the method
Prefer to talk it through first? Book a call
FAQ