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.

See Shipamax alternatives

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.

Documents read and the data sent to CargoWise, with the review rule for each
DocumentWhat is readWhere it lands in CargoWiseGoes to a person when
Commercial invoiceSeller, buyer, invoice lines, quantities, values, currency, originShipment and customs declaration dataTotals that do not reconcile with the packing list
Bill of lading (house or master)Parties, containers and seals, ports, vessel, datesShipment and container dataA container number that fails its check digit, or a party with no match
Packing listPackages, gross and net weights, volumesShipment packing and weight dataWeights or package counts that differ from the bill of lading
Arrival noticeVessel, ETA, charges, free timeShipment dates and expected chargesNo shipment found for the references on the notice
Carrier or agent invoiceCharge lines, amounts, job referencesCosts against the jobA cost that differs from what was expected on the job

ACCESS, MAPPING, DUPLICATES, ERRORS

What to set up, and what to refuse

Setup choices for a CargoWise document workflow: what to do and what to avoid
AreaDoAvoid
AccessAn eAdaptor connection with its own credentials for the Mirage workflow, set up by your CargoWise administratorShared user logins, or a connection that can send message types the workflow does not need
EnvironmentA test or training instance first, if your licence includes oneBuilding and testing against production
OrganizationsParties matched to the organization codes already in CargoWiseCreating new organizations from a document
CodesPorts, charge codes and units mapped to the lists your instance usesFree text where CargoWise expects a code
DuplicatesEach document and each message keyed on its references and a file hash, so a resend changes nothingSending again on a timeout without checking what CargoWise received
ErrorsA message CargoWise rejects is logged and the document goes to review with the reasonA failed send that leaves nothing in CargoWise and nothing in a queue

Each of these choices, worked through step by step: how to automate CargoWise data entry: mapping, checks, duplicates and failed writes.

CHOOSING A VENDOR

How do you choose a document automation vendor for CargoWise?

Eight questions to put to any vendor, Mirage included, and the answer a forwarder should expect. The honest answers are the ones that name a mechanism, a queue or a client rather than an adjective.

Questions to ask a CargoWise document automation vendor, and the answer to expect
QuestionThe answer to expect
Do you write into CargoWise through eAdaptor, with our own credentials, or through a shared login or screen automation?eAdaptor, with credentials your administrator issues for the workflow and can revoke
Which document types and layouts can we test on our own files before signing?A proof of concept on your documents, dated; for Mirage, one week after the first meeting
What is checked before a message is sent: organisations, codes, cross-document totals?Parties matched to your organisation codes, ports and charges to your lists, documents of one shipment checked against each other
Where does a document that fails a check go, and who sees it?A review queue with the reason and the page, not a silent drop or a guessed value
How do you avoid duplicates and recover from a failed send?Each document and message keyed on references and a file hash; a CargoWise rejection logged and the document sent to review
Do you claim a WiseTech partnership, certification or marketplace listing?A plain answer; Mirage claims none
What results can you show, from which TMS, with definitions?Named deployments: Mirage's are on Logitude World (OFRET Groupe) and Transwin's TMS, not on CargoWise, and the page says so
Who changes the workflow when a shipper changes its invoice layout or CargoWise is upgraded?The engineers who built it, under the subscription

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.

Pilot phases for a CargoWise document workflow and the condition to move on
PhaseWhat happensCondition to move on
Read onlyThe workflow reads the documents and produces its proposed data in a review list; your operators key as usualProposals match what the operators keyed, field by field, at the thresholds you set
Write to testApproved proposals are sent through eAdaptor to a test or training instanceEvery message accepted, no duplicates, nothing lost
Write to productionDocument types that passed are sent to production; a person approves what the rules flagThe 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.

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

See the case study

Transwin

70% less manual entry on freight documents

Wired into the TMS Transwin already ran

See the case study

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.

Attach a document you key into CargoWise (recommended)

We use your email to reply to you and, now and then, to tell you about Mirage. You can opt out at any time. Privacy policy

How a deployment runs: Observe, Map, Build, Run, Expand. See the method

FAQ

Frequently asked questions

  • Yes. Mirage connects to the CargoWise instance a client already runs, through eAdaptor, the interface WiseTech provides for exchanging data with outside systems, set up by the client's CargoWise administrator. Mirage holds no WiseTech partnership, certification or listing, and has not published a CargoWise case study.

  • It is CargoWise's interface for exchanging XML messages with external systems. WiseTech describes its newer version, eAdaptor Next, as using OAuth 2.0 and REST over HTTP with XML, with separate credentials for each external system. Its developer documentation is not public: it is shared with CargoWise customers and partners.

  • Check CargoWise's own capability first. WiseTech describes a document portal embedded in CargoWise that captures commercial invoices, with bills of lading, packing lists and transport bookings announced. An outside workflow is worth it when your documents, layouts or checks are not covered, when the same document must be checked against others, or when the result feeds more than one system.

  • The documents your operators key into shipments today: commercial invoices, bills of lading, packing lists, arrival notices and carrier or agent invoices are the usual first candidates. Each one is mapped to your instance's own codes and organizations, and anything that does not reconcile goes to a person.

  • For writing data into CargoWise, eAdaptor is the route WiseTech documents for outside systems. Your CargoWise administrator confirms what your instance includes. Where it is not available, other exchange methods CargoWise supports, such as file transfer, can be looked at with your administrator.

  • Ask how the vendor writes into CargoWise (eAdaptor with your own credentials, or something less controlled), what it checks before sending, where a failed document goes, how duplicates are avoided, what it claims about WiseTech, which named results it can show and who changes the workflow after go-live. The table on this page lists the eight questions and the answer to expect from each.

  • Mirage answers any request within two business hours and runs a proof of concept on your own documents one week after the first meeting. The first workflow reaches production in 4 to 6 weeks; the time to get an eAdaptor connection set up in your instance comes on top if it does not exist yet.