LOGISTICS INTELLIGENCE / TMS DATA ENTRY
Send us a document your team currently keys into your TMS by hand. Mirage reads it and pushes the structured data straight into CargoWise, Descartes, Magaya, or whatever you already run.
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
01
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.
02
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.
03
CargoWise, Descartes, Magaya, Bluejay, Freightview, and ERPs like Microsoft Dynamics, Oracle, and Salesforce are all supported — through your TMS's own API or import mechanism, no new system to adopt.
THE OUTPUT
| 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 |
PROOF
Ofret
2 tailored CargoScribe environments deployed, one per entity
1 shared TMS, zero extra software layers added
90%+ of standard RFQs handled without manual TMS entry
Transwin
CargoScribe 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
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.
Book a 30-min call →or fill out the form below instead
FAQ
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.
CargoWise, Descartes, Magaya, Bluejay, Freightview, and ERPs like Microsoft Dynamics, Oracle, and Salesforce are all supported today. If you run something else, tell us during your first call — most integrations are a matter of confirming the API or import format, not a rebuild.
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.
Under four weeks on average 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