Connect Mendrix to your supply chain
We connect Mendrix to the systems of your customers, carriers and platforms — via Custom Link, the REST API or EDI, with support and maintenance included.
Without obligation · reply within one working day
Mendrix connected to the rest of your supply chain
Do you use Mendrix, the Dutch TMS? Then we connect it to the rest of your supply chain, so orders, status updates and documents flow through automatically. You keep the way of working you know; we take care of the integration around it: designed, built and monitored.
Mendrix offers more than one way to integrate, and the choice matters. Orders go in by a different route than status updates come out. We know which route suits which flow, so the integration does not run into one of the package’s limits halfway through.
We integrate Mendrix via EDI and API, depending on what your partners support. See also our TMS & WMS integrations.
What Mendrix offers for an integration
Custom Link for orders
Transport orders enter Mendrix via Custom Link, the Mendrix SOAP interface. Today that is the route for creating and updating orders, even when they start out at the customer as EDI or Excel.
REST API for everything else
Customer and supplier records, address books, invoices and payments, and updates to orders and tasks all run through the modern Mendrix REST API.
Webhooks on events
Mendrix can send a message itself when an order is completed, accepted or rejected, when a task status changes, or when a trip starts or ends. That way a status update reaches your customer without anyone having to ask.
Dozens of standard integrations
Mendrix itself has around fifty standard integrations, including accounting packages, parcel carriers and on-board computers. What is already covered there, we do not build again.
What we connect to Mendrix
- Orders from shippers into Mendrix, via EDI (IFTMIN), the shipper’s API, or from Excel, CSV and email. See importing orders without EDI.
- Status updates and POD back to the customer, as IFTSTA, an API call or a file, triggered by the Mendrix webhooks.
- Trips to subcontracted carriers and their status updates back. See carrier integration.
- Mendrix linked to a WMS, so orders that are ready to ship appear in the planning automatically.
- Invoices to the customer, for example as INVOIC, when the standard accounting integration is not enough.
What to plan for with Mendrix
Every package has its own rules. These are the points that, with Mendrix, make the difference between an integration that keeps running and one that stalls every now and then. We take them into account from day one.
One order per message
Mendrix explicitly asks for orders to be submitted one at a time, not in large batches. An integration that ignores this gets a warning from Mendrix itself.
An update replaces the whole order
When an order is updated via Custom Link, it is overwritten in full. Send only the changed fields and you wipe the rest. We first retrieve the current order and then send the complete record back.
Webhooks are set up in Mendrix
Webhooks are not an API setting but an event in Mendrix itself, configured by your administrator. An event outside the fixed list cannot become a webhook; in that case we retrieve the data another way.
Access via a token from Mendrix
The integration works with an API token that your administrator creates in Mendrix, under Custom Link. So you stay in control of who has access, and you can revoke the token at any time.
Orders from a shipper into Mendrix, status updates sent back automatically
Take a carrier that receives an Excel list of orders from a regular customer every morning. It is retyped line by line into Mendrix, and later in the day the customer calls to find out where their shipment is.
-
01
The Excel list is read and checked automatically. Unknown addresses or missing details are flagged before the order reaches Mendrix.
-
02
Each order goes to Mendrix separately via Custom Link, with the right customer, loading and delivery addresses and time windows.
-
03
On ‘order completed’, Mendrix sends a webhook. We turn it into a status message for the customer, with the delivery status and the name of the person who signed.
No more retyping in the morning, and the customer sees the delivery status without having to call.
Arian Masselink, Enschede
I own Transportkoppeling and build the integrations myself. So you don't talk to an account manager, but directly to the person who designs and builds your Mendrix integration and then keeps an eye on it.
Using Mendrix? Call Arian.
You speak straight away to the person who builds your integration. No salesperson and no call centre: within ten minutes you know whether and how your integration can be done.
Or email contact@transportkoppeling.nl
Useful to have to hand
- Which version of Mendrix you use
- Which customer, carrier or system you want to connect to
- How it works today: email, Excel, a portal or retyping by hand
Mendrix integration in brief
Which partners do you connect Mendrix to?
Any shipper, carrier or platform, via EDI, API or file exchange. We connect Mendrix to the partners you work with.
Doesn’t Mendrix already have a standard integration for this?
Sometimes it does, and then we will tell you so. Mendrix has standard integrations with accounting packages, parcel carriers and on-board computers, among others. We build what is not covered there, usually the integrations with your own customers and subcontractors.
Does it also work with Mendrix on your own servers?
In principle, yes. If Mendrix runs on your own server rather than in the cloud, we work with your administrator to make the integration securely reachable from outside.
Who looks after the integration once it is live?
We do. We monitor the integration proactively, so it keeps running day in, day out.
Other packages we integrate
Connect Mendrix to your supply chain?
Book an introductory call without obligation. Together we look at your systems and partners, and at what an integration will deliver for you.