Integrations, EDI and APIs
Retrack TMS connects to mapping, accounting and reporting tools out of the box, and to everything else through EDI, APIs and webhooks. Where the standard route does not fit, our development team builds the connection rather than telling you to change how you work.
Request Demo
What not connecting really costs
Software that cannot exchange data does not just create typing. It creates two versions of the truth. An order updated in one system and not the other produces a delivery nobody expected, an invoice nobody can reconcile, and an argument that takes longer to settle than the job took to run.
That cost is easy to miss because it never appears as a line item. It surfaces as someone re-keying orders every morning, as a monthly reconciliation nobody enjoys, and as the quiet assumption that a certain report is always slightly wrong.
Retrack TMS is built to sit inside an existing landscape rather than replace it. Orders can arrive electronically, trip and delivery data can flow back out, and the systems your finance and warehouse teams already depend on keep working.
How Retrack TMS connects
Six routes in and out, so the right one exists for each system you run.
Native integrations
Mapping and routing through Google Maps, Bing Maps, HERE and PTV, reporting through Power BI, and accounting through Xero — connected without a project.
EDI
Electronic order intake and status messaging for the customers and partners who expect to exchange data that way.
APIs
Programmatic access to orders, trips and delivery data, so your own systems can read and write without a person in the middle.
Webhooks
Events pushed to your systems as they happen, so downstream tools react to a delivery rather than polling for it.
Customer web portal
For customers who would rather not integrate at all, a portal to place orders, track shipments and download delivery documents themselves.
Custom development
Where none of the standard routes fit, our development team builds the connection to suit your operation without disturbing the core platform.
When the standard connection is not enough
Most integration promises quietly assume your operation resembles the vendor's model. Ours often does not — transport companies accumulate arrangements, exceptions and customer-specific habits over decades, and those are usually the parts that matter most to the people doing the work.
Because we build and maintain Retrack TMS ourselves rather than reselling someone else's platform, a request to handle something differently goes to the team that wrote the code. That is also the honest limit: custom work is scoped and quoted like any development, not something we can promise in advance without seeing what you need.
What connecting properly changes
Mostly, it removes work that nobody ever agreed to take on.
No double entry
Orders arriving electronically are not re-keyed, which removes both the time and the transcription errors that come with it.
Systems stop disagreeing
When data flows both ways, the transport system and the finance system stop holding different answers to the same question.
Downstream tools react immediately
Webhooks push events as they happen, so a delivery updates the systems that care about it without anyone checking.
The developers are ours
We wrote the platform, so an awkward integration is a conversation with the people who maintain it rather than a support ticket to a third party.
Questions about integration
Which systems do you already connect to?
Google Maps, Bing Maps, HERE and PTV for mapping and routing, Power BI for reporting and Xero for accounting are connected natively. Anything else goes through EDI, APIs or webhooks.
Can our ERP or WMS send orders directly?
Yes, through EDI or the API depending on what your system supports. Orders arrive electronically and trip and delivery data can flow back, so neither side is re-keying.
What if we need something you do not support yet?
Our development team builds custom features and connections to fit how you work, without destabilising the core platform. It is scoped like any development work rather than promised sight unseen.
Do our customers have to integrate to see their shipments?
No. Customers who would rather not integrate get a web portal where they place orders, track shipments live and download delivery documents themselves, which removes most status phone calls.
Who maintains the connection afterwards?
We do. Retrack TMS is built and maintained by our own team, so the people supporting an integration are the people who wrote it.
Does data only flow into Retrack TMS, or back out too?
Both ways. Orders can arrive electronically from your systems, and trip, status and delivery data can flow back out to them once the work is done. The exchange is not one-directional, which is what stops the two systems drifting apart.
Bring us your systems list
Book a demo and tell us what you already run. We will be straight about what connects out of the box and what would take development.
Request Demo