Loading
Every carrier tells you about their leg. We connect TMS, WMS, carriers and customs into one shipment record, so an exception surfaces while there is still time to do something about it.
Four systems · one shipment
Where it breaks
The TMS has a booking, the WMS has a handoff, the carrier has a tracking number and the broker has a declaration. Four records, one physical box, and no agreement on what to call it.
A leg changes carrier and the reference changes with it. Stitching the journey back together happens in a spreadsheet, by someone who knows which column to trust.
One canonical shipment with every party's reference attached to it, matched as the events arrive.
Status is pulled on a schedule, so a missed connection surfaces hours later. By then the recovery options that existed at the terminal have gone, and the conversation is about credit rather than delivery.
Events stream in as they happen, with exception rules that fire the moment the event lands, without waiting for the next poll.
Customers and internal teams call because they cannot see for themselves. Every enquiry is someone re-reading a screen the caller could have read, if it existed.
One shipment API behind your portal and notifications, so the update reaches them before the call does.
How it works
We normalise each event, match it to a shipment, check it against the plan and publish it to whoever is waiting on it.
Scroll the diagram sideways →
EDI 214 and 204, EDIFACT IFTSTA and IFTMIN, carrier REST APIs and portal scrapes where there is nothing better. Adding the next carrier is a mapping against the same model.
The runtime sits on your cloud tenancy, in your data centre, or locally at sites with unreliable connectivity, so scanning and load events queue until the link returns.
Carrier feed health, event lag and unmatched references land on one dashboard, so you spot a silent carrier before a customer reports it.
Products
MetricMonitor, Easy-Invois and DwaniAI read the same shipment model, so a consignment is the same consignment in all three.
Shipment throughput, SLA breaches, carrier feed health and integration pipeline status on one screen, with alerts on the thresholds your operation cares about.
Explore MetricMonitor →Freight billing and e-invoicing across carriers, forwarders and brokers, with multi-country tax rules and reconciliation against the freight that moved.
Explore Easy-Invois →Where-is-my-shipment questions answered over chat and voice from the same live record your operations team sees, with escalation when the answer is not good news.
Explore DwaniAI →How we work
Every new feed runs beside whatever you use today. Both receive, your team compares a full week of traffic against the carrier's own portal, and the old route stays open until you close it.
It is included in every engagement. Every carrier onboards this way, on the first and on the fiftieth.
A feed is correct when your reconciliation says so, checked against the events you were already receiving.
When a feed goes quiet the shipment shows its last known state and the time it was known, rather than an empty screen nobody can interpret.
Recent work
Anonymised at the client's request
A freight forwarder held each carrier in its own portal and each customer in its own spreadsheet. Answering where a consignment was meant opening several windows and trusting the person who had done it longest.
We defined one shipment model, matched every party's reference against it, and put exception rules on the events rather than on a nightly report. Carriers moved across in waves, each running in parallel until the counts agreed.
Talk to us about your network →Questions
Through API-led middleware, usually webMethods or Apache Camel depending on what you already run. Each system maps into one canonical shipment and event model rather than into each other, so the number of platforms you operate stops driving the number of interfaces you maintain.
Get started
Tell us which systems and carriers you are trying to join up. An integration architect reviews it and comes back within two working days.
