Custom MendriX integration development
Appfront builds custom integrations around MendriX, the Dutch Transport Management System for route planning, order management, ETA communication and eCMR. We connect your MendriX environment with ERP, customer portals, driver apps, telematics and customs systems via REST and webhooks, so that MendriX becomes the hub of a transport landscape in which orders, planning, execution and invoicing always align.
What is MendriX and what does a MendriX integration do?
MendriX is a Dutch Transport Management System (TMS) used in the road freight and logistics sector for route planning, order management, ETA communication, driver dispatch, invoicing and digital consignment notes (eCMR). For Dutch transport companies, the platform acts as the operational core between order intake and execution: orders come in, are planned across drivers and vehicles, go out as trips to the driver app, return status updates and ETAs, and end up in an invoice and a reporting layer. Shippers, planners, drivers and finance all work from the same dataset.
A MendriX integration ensures this core actually communicates with the rest of your IT landscape. In practice, that means: orders received via a customer portal or webshop automatically land in MendriX, trip status and ETA are pushed back to the portal in real time, invoiced trips flow smoothly into AFAS, Exact or SAP, vehicle and driver data from Webfleet or Trimble enrich the planning, eCMR consignment notes are exchanged digitally, and BI dashboards draw from the MendriX database to provide management information on margin, revenue per kilometre and vehicle utilisation.
Appfront builds these integrations to measure for Dutch hauliers who want more than a standard plug-in. We work through the MendriX REST API and webhook events, use idempotency keys for stable processing, and align the data model with your actual processes, whether you run national distribution, international freight with customs and eCMR flows, or specialist supply chains such as construction logistics, food and pharma. Our role is often that of the technical link between MendriX, your ERP and the systems your drivers and customers use every day, and therefore the architect of the wider integration layer around your transport operation. If you are new to this landscape, start with our explanation of what an API integration actually is.
One planning board, all sources
Orders from customer portals, EDI feeds, webshops and loose emails come together in MendriX. Planners see the same data as customer service and finance, regardless of the channel through which the order arrived, without manual re-keying.
Real-time ETA for the customer
Trip status and estimated arrival times flow from MendriX to your customer portal, app or email. Shippers track their consignments without phoning the planning desk, and your customer service team spends less time on status updates.
eCMR & customs from a single source
Digital consignment notes, customs declarations and EU mobility data flows are driven from MendriX. No separate paper trail or double data entry towards the DMS and eCMR provider; the trip data from the TMS is leading.
Our development process for MendriX integrations
We work to a proven methodology that surfaces the complexity of a TMS integration early and delivers a stable end result. From mapping your MendriX environment and adjacent systems through to go-live and ongoing management, every step is aimed at an integration that your planning, drivers, customer service and finance teams can rely on, including during peak weeks and public holidays.
We map out which MendriX modules you use, which adjacent systems are relevant and which data flows take priority, whether orders, status updates, ETAs, financial postings or eCMR. From that scope, a concrete integration roadmap takes shape.
We design the integration architecture, choose between webhooks and polling for each scenario, define the master data mapping (customers, cost centres, VAT codes), determine the idempotency strategy and arrange the correct API credentials together with your MendriX supplier.
Implementation with automated tests, structured logging and monitoring from day one. You see working integrations along the way in a test environment, checked against realistic trip and order scenarios drawn from your own operations.
Controlled go-live with data validation and a safety net for the first working week, followed by ongoing management, monitoring and further development: additional customer portals, a new telematics provider or an extra eCMR corridor.
What a MendriX integration delivers in practice
Every MendriX integration is tailored to your market, fleet and adjacent systems. Below are the functionalities we most often deliver for Dutch transport companies that use MendriX as their core system and want to connect the platform with their ERP, customer portal, driver app and telematics provider. Our experience with transport planning APIs and smart API integrations comes together here.
ERP integration
AFAS Profit, Exact, Unit4 or SAP integrated with MendriX for master data (customers, debtors, cost centres), financial postings (sales invoices, fuel costs, vehicle costs) and general ledger synchronisation. The ERP stays in charge of finance, MendriX of operations, without the two working against each other.
Customer portal & ETA
A dedicated customer portal for shippers, powered by MendriX: create orders, track trip status, view the ETA per shipment, download documents and review invoices. For large clients, bespoke flows with differing rates, credit limits and order history.
Driver app integration
Trip assignments, tasks, scans, photos and signatures sent from a driver app back to MendriX. Whether you use the standard MendriX app or your own Android or iOS app, we ensure stable bidirectional synchronisation, including where mobile coverage fluctuates on the road.
Telematics integration
Webfleet, Trimble, Geotab or another telematics provider integrated with MendriX: vehicle location, driving behaviour, fuel consumption and digital tachograph data enrich your planning and give real-time insight into trips in progress. One source for driving-time administration.
eCMR & customs
Digital consignment notes via an eCMR provider, customs declarations via a DMS, and connection to EU mobility data spaces for international trips. One consignment note, one status, one archive, regardless of which combination of countries a route covers.
BI & reporting
A read-only integration from MendriX to your BI tool (Power BI, Looker, Metabase, Tableau) for margin per trip, revenue per kilometre, vehicle utilisation and driver performance insights. No more export-to-Excel cycles; a dashboard that refreshes daily.
Typical MendriX integrations in practice
A MendriX integration looks different for every organisation. A number of scenarios come up again and again among Dutch transport companies, and for each of them we have a working setup that takes into account the specifics of the platform, the Working Hours Act for transport, and the particular rules around eCMR and EU mobility data spaces.
National distribution transport
Hauliers with daily stops across the Netherlands: distribution to shops, construction sites, hospitality or food service. We integrate MendriX so that orders from customer portals land directly in the planning, trip status flows back to the shipper and invoicing goes automatically to AFAS or Exact. Customer service works from a single screen and finance keeps track of trip margins.
International transport with eCMR
Carriers running trips between the Netherlands, Belgium, Germany and further across Europe, with digital consignment notes and customs declarations as a standard part of the process. We integrate MendriX with an eCMR provider, a DMS customs solution and, where relevant, an EU mobility data space, so that a single trip record carries all the necessary documents and statuses. See also our page on custom transport software for broader context.
Construction logistics & project transport
Contractors and construction logistics companies that deliver materials to building sites within tight time slots and with changing combinations of resources (lorry + crane + unloading assistance). We integrate MendriX with construction site portals, estimating software and the ERP, so planners can reschedule quickly and finance can see returns per project.
Logistics service provider with multiple clients
Logistics service providers that plan for several shippers at once, with data segregated per client. We integrate MendriX with shippers' portals, their ERP or WMS systems and the shared driver and telematics layer, with clear authorisation per client so that data never accidentally crosses boundaries. See also how we build transport planning APIs for this type of environment.
Technology we use
We build MendriX integrations using the platform's available APIs: REST endpoints for orders, trips, stops, status updates and invoice lines, supplemented by webhook events for real-time updates. We align the backend stack with your IT landscape so that your own team can manage or further develop the integration over time. Idempotency keys, audit trails and structured logging are standard parts of the architecture, so that even with retries, network glitches and unreliable telematics feeds we guarantee a consistent result.
Why choose Appfront for your MendriX integration?
Appfront has extensive experience with API integrations for transport and logistics organisations in the Netherlands. We always start with a thorough analysis of your MendriX environment and the surrounding systems. A TMS integration needs to be technically sound, but it also has to add practical value for planners, drivers, customer service and finance.
For every integration, we write clear documentation so that your own team, or a future supplier, can understand and manage what is running. No black box, just transparent code and clear agreements on monitoring, alerting and maintenance. This keeps you independent and in control of your integrations at all times.
You work with a dedicated point of contact who understands both the technical and the operational side. That keeps lines short and speeds up decisions when choices need making during the build around data models, return flows or telematics mappings. We don't see MendriX as a standalone plug-in but as part of a wider chain, which is why we also think from a broader transport software perspective, not just from the API.
You may also be interested in our wider services around smart API integrations, transport planning APIs and the broader overview of integrations we build.
- Experience with the MendriX REST API and webhook flows
- Specialist in Dutch transport and logistics integrations
- Experienced with ERP integrations to AFAS, Exact, Unit4 and SAP
- Telematics integrations with Webfleet, Trimble and Geotab
- eCMR and customs integrations (DMS, EU mobility data spaces)
- Customer portals and driver apps built on MendriX data
- Idempotency keys and stable retries for webhook flows
- Secure by default: API key rotation, scoped permissions, signature validation
- Comprehensive logging and monitoring from day one
- Clear documentation that your operations and IT teams can read
- A fixed point of contact, no account managers passed around
- Ongoing maintenance and proactive further development
Security, GDPR and driver data in transport integrations
Transport data is sensitive: customer details, route planning, driver locations, driving and rest times and financial data fall under the GDPR, the Dutch Working Hours Act for transport and, for international journeys, EU regulations on driving times and eCMR. Appfront builds in line with the OWASP ASVS and the specific requirements around personal data and transport: minimal collection, encrypted storage and strictly separated permissions per integration and per client.
We document the data flows between MendriX, your ERP, customer portals, driver apps and the telematics provider so that your record of processing activities is complete and you can demonstrably comply with the GDPR. For driver data we take the Working Hours Act and tachograph rules into account; for digital consignment notes we align with the eCMR convention and the EU mobility data spaces so that transport data is shared between parties in a standardised way.
We keep EU data within EU regions by default, so no unexpected data transfers to third countries occur. Webhook payloads are signed and validated, API keys are rotated, and all communication runs over TLS 1.2 or higher. More about our approach: our information security policy and vulnerability disclosure policy.
- GDPR-compliant processing of customer and driver data
- Working Hours Act compliance for driving and rest time administration
- eCMR-compliant exchange of digital consignment notes
- Connection to EU mobility data spaces
- EU data kept within EU regions
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- HMAC-signed webhooks with replay protection
- Idempotency keys on all status and order events
- Audit logs with traceable data flows
- Monitoring and alerting for anomalies
- Documentation for your record of processing activities
Frequently asked questions about MendriX integrations
Answers to the questions we are asked most often about MendriX integrations for Dutch transport and logistics organisations.
MendriX is a Dutch Transport Management System (TMS) used in the road transport and logistics sector for route planning, order management, ETA communication, driver dispatch and digital consignment notes (eCMR). The platform is aimed at Dutch transport companies that want to bring order intake, planning, execution and invoicing into one environment. A MendriX integration means connecting MendriX with the rest of your IT landscape, including ERP, accounting, customer portals, driver apps, telematics and customs systems, so that there is a single source of truth for order status, route planning, ETA and invoicing. Note: MendriX (with an X) is something different from Mendix, the low-code platform from Siemens.
We see a consistent set of recurring integration patterns: ERP integrations with AFAS Profit, Exact, Unit4 or SAP for master data, cost centres, invoicing and general ledger synchronisation; customer portal integrations where shippers track their orders, trip status and ETA in real time; driver app integrations for routes, tasks, scan events, photos and signatures; telematics integrations with Webfleet, Trimble or Geotab for vehicle, driving time and location data; customs and eCMR integrations with DMS, eCMR providers and EU mobility data spaces; and BI or data warehouse feeds to Power BI, Looker or Tableau for management information on margin, revenue per kilometre and trip profitability.
MendriX offers a REST API covering the main objects: orders, trips, stops, status updates, customer details and invoice lines. For real-time scenarios, we use webhooks wherever possible, so status updates and ETA changes flow straight through to the customer portal or driver app. For reconciliation, bulk syncs and historical exports, we rely on paginated REST endpoints. Idempotency keys are a standard part of our setup: if an order or status event arrives twice due to network issues, it is processed only once. For each project, we first map out which endpoints, scopes and rate limits are relevant to your scenario, and then agree the correct credentials and environments with the MendriX vendor.
Yes. For transport companies with non-standard processes, such as a bespoke customer portal for large shippers, a tariff module tailored to each client, or a driver app with an additional workflow alongside MendriX, we build custom flows around the TMS. The custom layer communicates with the core system via the MendriX REST API, so MendriX's standard upgrades are not blocked and you can continue to extend the solution independently. See also our page on custom transport software.
The scope depends on the number of connected systems, the complexity of the master data mapping (customers, cost centres, debtors, VAT codes), whether synchronisation is bidirectional or one-way, the volume of trips and status updates, and the requirements for error handling, monitoring and restart scenarios. Compliance requirements also play a role, including GDPR, the Dutch Working Hours Act for driver data, eCMR conformity and any customs or DMS integrations. We always provide a clear quote following a no-obligation analysis of your situation.
Yes. Driver data, driving and rest times and parcel details fall under the GDPR and the Dutch Working Hours Act for transport, as well as EU regulations on driving times and the eCMR directive for electronic consignment notes. Appfront builds in line with OWASP ASVS, limits personal data to what is strictly necessary for the process, uses encrypted connections and documents the data flows between MendriX and the connected systems so that your record of processing activities is complete. By default we keep EU data within EU regions, and we align with the guidelines of EU mobility data spaces for sharing transport and logistics data between parties.
Yes. Appfront regularly takes over existing MendriX integrations, including those originally set up by another party or built in-house. We review the API calls, idempotency, error handling, monitoring and data quality, document the current setup and propose improvements. From that point on, we can handle adjustments, extensions and ongoing maintenance, for example adding a new customer portal, an additional telematics provider or a modified eCMR flow without disrupting the rest of the chain.
A MendriX integration is especially worthwhile for Dutch transport companies that already use MendriX, or are considering it, and don't want the platform to sit as an isolated silo. Typical profiles include medium-sized and large road hauliers, distribution companies, couriers, food and pharma logistics, construction logistics, and international carriers working with eCMR and customs systems. The more adjacent systems you have — ERP, customer portal, driver apps, telematics, BI — the more value a well-built integration delivers, as manual re-keying, duplicate orders and miscommunication between the office and drivers would otherwise quickly add up.
MendriX (with a capital X in the middle) is a Dutch Transport Management System for the transport and logistics sector. Mendix (without the X) is a low-code application platform owned by Siemens, used by organisations to build business applications. They are two entirely different products with different vendors, target audiences and use cases. This page concerns MendriX, the TMS, exclusively. If you are looking for a Mendix integration or a Mendix developer, that is a different project — do get in touch, and we can point you in the right direction or refer you on.
Read more
Explore related topics around MendriX and the wider transport and logistics chain.
Talk to us about your MendriX integration
Tell us how you use MendriX and which systems the TMS needs to integrate with: ERP, customer portal, driver app, telematics, eCMR provider or customs systems. We are happy to think along about scope, priorities, data model and alignment with your MendriX supplier. A no-obligation first conversation will give you a clear picture of what is possible.