Service · Web development

Custom TMS development for transport and logistics.

A Transport Management System that fits your planning, your drivers and your customers, not the other way round. We build custom TMS solutions for mid-market carriers and 3PL providers who have outgrown Excel but don't want a Transwide licence.

Route optimisationTelematicsDriver appeCMR-ready

A TMS is more than a planning board.

The Transport Management System is the heart of a haulier: from shipment acceptance and planning to dispatch, telematics, proof of delivery, invoicing and CO2 reporting. It touches every department (planners, drivers, operations management, finance, customer service) and integrates with every chain partner: shippers, subcontracted hauliers, customs, fuel suppliers, ERPs and accounting packages. The wrong TMS costs you years of workarounds; a TMS that fits well enables growth and margin control.

We don't replace Transwide, Descartes, Centric Distributievloer or Manhattan TMS for general commodity work. Those packages do what they need to do for broad flows, and the licence costs pay for themselves there. What we do build is custom TMS solutions for specialty transport, deep integrations between TMS, WMS, accounting and telematics, white-label customer portals and subcontractor cascades where enterprise packages are either too expensive or too rigid. See our broader view on building transport software and on your transport software partner for the long-term relationship.

Mid-market hauliers with ten to a hundred lorries, courier companies that have outgrown Excel but don't want to or can't make the step to Pionira or Cordel, 3PL and 4PL providers, logistics cooperatives, specialty hauliers (car transport, ship transhipment, hazmat, pharma cold chain), e-commerce fulfilment with their own transport and city distribution companies most often recognise themselves in our projects. What they have in common: their operation has a few specific traits that standard TMS packages keep getting stuck on.

The modules a TMS consists of.

A mature Transport Management System consists of modules that deliver value on their own but only show their full strength together. We don't build them all at once; we start where the pain is greatest and the business case strongest.

Order management and shipment acceptance processes orders from customers or shippers, validates pricing agreements and steers by service level (express, daily run, dedicated). Planning and dispatch handles route optimisation across multi-stop runs, with time windows per stop, required driver skills (ADR, Code 95 specialisms, language level) and vehicle types (refrigerated, tail-lift, crane, ADR-certified). Telematics integration pulls in real-time positions, fuel consumption and engine data via Webfleet, Trimble, Geotab, Volvo Connect or Daimler Truck Suite, and uses it for live ETAs and exception management.

The driver app gives the driver instructions per stop, photo evidence for damage and cargo, time registration in line with the Dutch road haulage collective agreement and EU 561/2006 driving times, and the digital signature for proof of delivery. The customer portal gives shippers and end customers real-time track and trace, document downloads and self-service for new bookings, white-labelled in your branding so it strengthens your brand, not a software vendor's.

Invoicing and rate structures calculates per km, per stop and per pallet, with fuel surcharge, ADR surcharge, waiting hours, weekend surcharge and tiered subcontractor rates. The document flow manages CMR, customs documents and eCMR, the latter increasingly becoming the norm for cross-border transport in 2026. Subcontractor management handles subcontracted and freelance hauliers: onboarding, contracts, automatic rate calculation and performance tracking. Fuel tracking and CO2 reporting provide the figures for CSRD Scope 3 and customer reports, while maintenance integrations with your CMMS prevent a lorry from unexpectedly standing idle. With an integration with yard and dock management, the handover from road to warehouse becomes seamless.

Finally, the reporting layer: KPIs per planner, margin per route, customer SLA reports, on-time delivery per depot, trip utilisation, empty kilometres and fuel efficiency per driver and per truck. And the integration layer with ERP systems such as Exact and AFAS, with shippers' customer systems (EDI, REST, portal), and with your accounting software for automatic invoice export and debtor monitoring. AI-augmented features, such as predictive ETA, dynamic re-routing and anomaly detection, are the last layer we build on top, so they are fed by a clean data foundation rather than by a TMS that is still rattling along itself.

Not every module has to go live at once. We work with a prioritisation: what solves the sharpest pain, what has the fastest payback, and which modules can come later without disrupting the architecture. A good TMS architecture leaves room to add a charter portal, a yard integration or an AI layer later, without having to start over.

Three flavours of TMS project.

Which approach fits depends on the complexity of your operation and the number of external systems that need to be integrated. We will advise which route suits you during the first conversation.

Compact project · fixed sprint budget

Planning and dispatch core

A working planning, dispatch and shipment flow for a single branch. Multi-stop routes, time windows, driver skills and truck types. A driver app with instructions, photo evidence and time registration. Ready to replace the first Excel files.

Order managementRoute optimisationDriver appProof of delivery
Mid-sized project · fixed sprint budget

Integrated TMS with customer portal

On top of the planning core: telematics integrations (Webfleet, Trimble, Geotab, Volvo Connect), a white-label customer portal with track and trace, invoicing with rate structures (per km, per stop, fuel and ADR surcharges) and the first accounting or ERP integration. Subcontractor management for charters.

TelematicsCustomer portalRate structuresCharter flow
Larger project · fixed sprint budget

Enterprise replacement TMS

A mission-critical TMS for 3PL or 4PL providers with multiple depots, subcontractor cascades, deep ERP integration (Exact, AFAS, SAP), eCMR flow, fuel and CO2 tracking and AI-augmented planning. Including shipper integrations and SLA reporting per customer.

Multi-depotERP integrationeCMRAI planning

What a TMS project delivers.

A production-ready Transport Management System, plus everything around it to manage and extend it yourself.

  • The TMS environment itselfProduction, staging and dev environments, running in your cloud (GCP/AWS/Azure) or with us. Including a PWA driver app for iOS and Android.
  • Telematics and interfacesLive integrations with Webfleet, Trimble, Geotab, Volvo Connect and Daimler Truck Suite. ERP and accounting integration with Exact or AFAS. eCMR flow for the European requirement from 2026.
  • Codebase and documentationComplete source code, API documentation, architecture overview and build instructions. You are the owner.
  • Admin and planner manualWritten for your planners and your IT team: managing rate structures, onboarding charters, exporting reports, reading the audit log.
  • Training for planners and driversSessions for key users (planners, operations manager) and a short video tutorial for drivers in NL/EN/PL/RO, depending on your fleet composition.
  • Maintenance contract (optional)Monitoring, backups, security patches and ongoing development for new legislation (eCMR, NIS2, CSRD). Fixed monthly price, four response-time levels.

When a custom TMS is the right choice.

Four patterns where standard TMS packages fall short and custom development pays for itself. If you recognise one, we would be happy to talk further.

Specialty transport

Your cargo doesn't fit in a box

Car transport, ship cargo handling, hazmat (ADR), pharma cold chain (GDP), food (HACCP) or last-mile city distribution: standard TMS fields don't cover your reality. You have too many exceptions, too many manual workarounds, and planners keeping side-of-desk spreadsheets to plug gaps the package refuses to see.

Integration depth

TMS, WMS and accounting should feel like one

You run Exact or AFAS, a WMS, a separate accounting system, and telematics from three brands side by side because your fleet is mixed. A standard TMS integrates at a single point and squeezes the rest into a nightly export. You need a platform where everything works together in real time, with a single source of truth for shipment, trip and invoice.

Charter cascade

Lots of charters, little control

You are a 3PL or 4PL with twenty or more charters, freelance carriers and partners. Subcontractor management, automatic rate calculation, document flow (CMR, eCMR), performance reporting and a charter portal become business-critical, and standard packages usually handle your own fleet well but charters barely or not at all.

Mid-market budget

An enterprise package is too expensive or too rigid

Manhattan, Oracle TM and SAP TM are priced for large multinationals and require an implementation team that a mid-market carrier does not have. Pionira, Centric and Cordel are often good for purely Dutch transport but get stuck on a specialty or international variant. A custom system scales with you without per-shipment licences, at a TCO that is workable for the mid-market.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How a TMS project runs.

1

Introduction and quick scan

We map out your current flows: how a shipment runs from customer to invoice, which telematics are already in use, and where the pain points are. We assess whether a custom solution is the right route or whether an off-the-shelf package will do — and if it's the latter, we will tell you.

2

Planning and user research

A workshop with your planners and ops team, plus shadowing sessions at dispatch and with a driver on the road. At the end: scope, planning, and a first screen flow for planning, the customer portal and the driver app. Includes a data migration plan from your current system.

3

Building in sprints

A working build with a walkthrough every two weeks. Your planners test with real shipments, and telematics integrations are validated early so there are no surprises at go-live. After a few sprints, a first working core is ready for the pilot branch.

4

Rollout and maintenance

A phased rollout: first one branch or one customer flow, then scaling up. Training for planners and drivers, running in parallel with the old system during the transition, and ongoing maintenance for security and further development in response to new legislation such as eCMR and CSRD.

The TMS landscape we know.

We deliberately don't reflexively shout "custom". The standard TMS landscape is mature, and for broad flows a package is often the wiser choice. We know the market: Transwide (Wabco/ZF) and Transporeon Platform for shipper-carrier networks, Descartes and Manhattan TMS for enterprise logistics, Trimble Transportation and MercuryGate for US-oriented flows, Alpega and BluJay for European multimodal, and at the top end Oracle Transportation Management and SAP TM for the largest multinationals.

In the Dutch SME market we often see Centric Distributievloer, Pionira, Cordel, Routyn and eMagic. Solid packages with deep roots in the Dutch transport sector. For pure trip administration with standard integrations they are often fine, and the licence pays for itself. The tipping point towards custom comes when your operation has niche traits the package doesn't support, when you really want multiple systems to work as one whole, or when, as a 3PL or brand, you need your own customer portal that must not carry a "Powered by [package vendor]" label.

We're also honest about when custom isn't the sensible route. If your needs fit a package and you have no specific integration or branding requirements, we'll recommend the package and happily point you to an implementation partner. Our value lies in building something a package can't be, not in rebuilding something that already exists.

Compliance we include as standard.

Transport is regulated. A TMS without compliance built in is a ticking time bomb for your ops and finance teams. As standard, we cover: GDPR for the personal data of drivers and contacts, EU 561/2006 for driving times and rest breaks (linked to tachograph data or telematics), AETR for journeys outside the EU, the Dutch road haulage collective labour agreement (CAO Beroepsgoederenvervoer) for working hours and allowances, and ADR protocols for dangerous goods (UN numbers, classes, segregation rules).

For specific cargo we add extra layers: GDP (Good Distribution Practice) for temperature-controlled pharma with temperature monitoring and an audit trail, HACCP for food with cooling-chain logging, and eCMR as a digital alternative to the paper CMR (the legal infrastructure has been ratified across the EU; a mandatory requirement for cross-border transport is on the horizon for 2026). At IT level, we build to NIS2 (essential entities in logistics) and CSRD scope 3 for CO2 reporting to your shippers. See how we design AI features in transport within these compliance frameworks.

Frequently asked questions.

What clients in transport and logistics usually want to know before we start.

What exactly is a TMS?
A Transport Management System (TMS) orchestrates everything that happens between a customer order and the invoice for a carrier: shipment acceptance, planning and dispatch, route optimisation, integrations with telematics and the driver app, proof of delivery, customer portal, invoicing with rate structures, document flow (CMR, eCMR, customs), subcontractor management for charters, and reporting on KPIs and SLAs. It is more than a planning board — it is the operational and financial heart of your transport company, and the place where growth sooner or later hits a ceiling if the tooling can't carry it.
What is the difference between a WMS, TMS and YMS?
A WMS (Warehouse Management System) runs the warehouse: stock, picking, packing. A TMS runs transport: planning, trips, drivers, invoicing. A YMS (Yard Management System) runs the yard and the docks: which vehicle is where, which gate is free. The three constantly overlap, and with custom development we can make the handovers seamless — with off-the-shelf packages they remain three systems communicating via interfaces.
Do you replace Transwide, Descartes or Centric Distributievloer?
For general commodity haulage, honestly, no — these are solid packages with a large ecosystem that we're not going to rebuild one-to-one. For broad flows, the licence simply pays for itself. We do build custom when you handle specialty transport (hazmat, car transport, shipping, temperature-controlled pharma), when you want deep integrations between TMS, WMS, accounting and telematics together, when you need a white-label customer portal that can't carry a "Powered by [package vendor]" label, or when you manage a large charter cascade. Even when the enterprise licence of Manhattan, Oracle TM or SAP TM doesn't fit your mid-market budget, custom is often the healthier TCO.
Which telematics integrations and interfaces do you build?
As standard, we integrate with Webfleet, Trimble, Geotab, Volvo Connect and Daimler Truck Suite for real-time positions, fuel consumption and engine data. For customer systems, we integrate with Exact, AFAS and the common ERPs used by shippers — often via EDI, a REST API or a shipper portal. On the warehouse side, we integrate with the WMS packages you already use so the handover from shipment to transport is smooth. For the driver app, we build a PWA that also works offline — instructions, photo evidence, time registration in line with the road haulage collective labour agreement (CAO Beroepsgoederenvervoer), and the eCMR signature. See also our proof-of-delivery approach.
How do you handle eCMR (mandatory from 2026)?
As of 21 August 2024, all EU member states have ratified the Additional Protocol to the CMR Convention (e-CMR); the practical obligation for cross-border transport gets going in 2026. We build the eCMR flow in from day one: digital signing by sender, carrier and consignee, integration with customs systems where needed, and archiving in line with the retention periods that apply to your cargo (ADR, pharma, food).
How does AI relate to a TMS?
AI is not a replacement for good planning, but it is a strong amplifier. Predictive ETAs based on historical trips and real-time traffic, dynamic routing when a trip goes off course, anomaly detection on fuel consumption or driving behaviour, and LLM assistance for the planner when exceptions arise. We build this modularly so you get the basics in order first and add AI features afterwards. See our in-depth explanation of AI in transport.
What determines the cost of a custom TMS?
Four factors: the scope (planning only, or including a customer portal, driver app and invoicing), the number of integrations with external systems (telematics, ERP, WMS, customs), the data migration from your current system, and the scale of the rollout (one site or a European network). After an initial conversation we give you a well-founded range for your situation, and we work with fixed sprint budgets so there are no open-ended bills.
Do you work with our planners and IT department?
Almost always. Planners are our most important co-designers: a TMS that planners don't back will not succeed. With your IT department we clearly agree responsibilities for hosting, security and maintenance, we deliver a runbook for incidents, and we hand over knowledge in the final sprint so you can carry on independently if you wish.
How long until we can go live?
A first working planning and dispatch core for a single site can be up and running in a few sprints. An integrated TMS with a customer portal, invoicing and the first telematics integrations is a project of several sprints. An enterprise replacement TMS with multi-depot, ERP integration, eCMR and AI features is a longer journey that we deliver phase by phase: you don't only go live at the end, but with every phase.

Talk to us about your TMS.

A half-hour introductory conversation, no obligation. We listen to your workflow, look together at which parts are causing pain, and give you direction you can actually use, even if the outcome is that an off-the-shelf package suits you better than custom.

Edit content