LOGISTICS INTELLIGENCE / TMS DATA ENTRY
Stop Retyping Freight Data Into Your TMS
Send us a document your team currently keys into your TMS by hand. Mirage reads it and sends the structured data into CargoWise, Descartes, Magaya, Logitude World or whatever you already run, through the interface your TMS provides.
Running at Ofret and Transwin, on their existing TMS.
THE REALITY
Your TMS is only as good as what gets typed into it, and most of what feeds it still arrives as a document someone has to open, read, and re-key by hand, the exact bottleneck a TMS was supposed to remove.
WHAT MIRAGE DOES
From document to TMS field, without a person in between
Reads the document, whatever its format
Bookings, bills of lading, invoices, and PODs arrive as email, PDF, scan, or structured file: Mirage extracts the fields your TMS needs from any of them, without a template per document type.
Maps extracted fields to your TMS's own structure
Data is routed to the right shipment, booking, or invoice record in your TMS, not dumped as an unstructured attachment someone still has to process.
Connects through the integration you already have
Through the interface your TMS provides: eAdaptor for CargoWise, Magaya's XML web service API, Descartes messaging or product APIs, Logitude World's API, or an import file. No new system to adopt.
THE OUTPUT
Every document, routed to the right TMS record
| Source Document | Extracted Data | TMS Destination | Status |
|---|---|---|---|
| Booking confirmation, email | Shipment #22140, origin/destination, ETD | Shipment record created | Pushed to TMS |
| Carrier invoice, PDF | Rate lines, accessorials, total | Invoice record | Pushed to TMS |
| Bill of lading, scan↳ A damaged corner of the scan obscures part of the container number, flagged for a person rather than pushed with a guessed digit. | Container no. partially unreadable | Shipment record | Routed for review |
| POD, driver photo | Delivery confirmation, quantity | Shipment record, closed | Pushed to TMS |
BY SYSTEM
How the connection works with each TMS
The mechanism comes from each vendor's own documentation, read on October 5, 2026. Mirage holds no partnership or certified connector with these vendors; the integration is built for your instance, with the access your licence provides.
- CargoWise
- Through eAdaptor, the XML messaging interface WiseTech provides for outside systems, set up by your CargoWise administrator. CargoWise also captures some documents itself, so check that first. The connection, the documents, the mapping and the pilot are on their own page; the method, from field mapping to duplicates and failed writes, is in the guide to automating CargoWise data entry. See CargoWise integration
- Descartes
- Descartes is a portfolio, not one system: its broker and forwarder suite alone covers shipment management, a forwarder TMS, customs compliance and accounting. The first question is which Descartes product your team keys into. Descartes documents messaging through its network in XML, ANSI X12, EDIFACT and flat or CSV files, and lists product APIs on an API portal that requires an account. The connection follows whichever of these your product and contract include.
- Magaya
- Magaya documents its API as an XML web service, reached through the Magaya Communication Suite, on premise or in the cloud, with an employee account that has API access (see Magaya's getting started page). EDI has to be converted into Magaya XML first, and Magaya states a fee per document set up and per transaction for EDI. Magaya's customs product also extracts commercial invoices itself: check it before automating that document.
- Logitude World
- Through the Logitude World API. This is the TMS connection a published case study documents: at OFRET Groupe, more than 90% of standard quote requests are handled automatically. See the OFRET case study
PROOF
What TMS data automation looks like in production
Ofret
2 tailored logistics environments deployed, one per entity
1 shared TMS, zero extra software layers added
90%+ of standard RFQs handled without manual TMS entry
Transwin
The logistics agent deployed against Transwin's actual freight and customs document mix
70% less manual data entry on freight documents
Same TMS Transwin already ran, no platform switch required
Ready to stop retyping data into your TMS?
Send us a document your team currently keys in by hand, and tell us which TMS you run, we'll show you exactly what gets automated.
How a deployment runs: Observe, Map, Build, Run, Expand. See the method
Prefer to talk it through first? Book a call
FAQ
Frequently asked questions
No. Mirage doesn't replace your TMS or the workflows built on it. It reads freight documents, bookings, bills of lading, invoices, PODs, and pushes the structured data into the TMS you already run, instead of a person retyping it.
Mirage connects to the TMS you already run through the mechanism its vendor provides: eAdaptor for CargoWise, Magaya's XML web service API, Descartes messaging or the API of the Descartes product you use, Logitude World's API (in production at OFRET), or an import file where there is no API. ERPs such as Microsoft Dynamics or Oracle are reached the same way. Mirage holds no partnership or certified connector with these vendors: the integration is built for your instance. If you run something else, tell us in the first call.
No. Mirage reads documents and writes structured data through your TMS's existing API or import mechanism. Your fields, workflows, and permissions stay exactly as configured.
Whatever a document carries that your TMS needs: shipment and booking details from a bill of lading, rate and accessorial data from an invoice, delivery confirmation from a POD, read once, then routed to the right place in your system.
It's flagged for a person rather than forced into the nearest matching field. A wrong or invented data point in your TMS is a worse outcome than a short manual review queue.
It helps, but isn't required for every integration, some TMS platforms are reached through import files or a browser-based workflow instead of an API. Tell us how yours is set up during your first call.
4 to 6 weeks to a production deployment: confirming your TMS's integration path first, then a parallel pilot pushing real document data into a test environment before anything touches production.
Pricing starts with a fixed-price pilot run pushing a real batch of documents into your TMS, so you see it working before committing to anything larger. After that, it moves to an annual subscription priced by volume, quoted in your first conversation with us.
ALSO ON THIS SITE