Software for transport & logistics that brings your planning, fleet and consignment notes into line
We build software for haulage companies, fleet operators and logistics service providers who want to connect their TMS, onboard computers, eCMR stack, fleet tracking and planning APIs into one workable chain. No more separate tools for planning, execution and invoicing, but one coherent digital workspace with integrations that keep working.
Why transport software only delivers value when all systems talk to each other
A typical haulage company quickly ends up running 8-15 systems: TMS, FMS, ERP, telematics, eCMR platform, customer portal, planning tools, fuel card administration, VAT returns for cabotage, tachograph data. Without coherence, much of the return is lost to manual rework.
Planning doesn't know what the driver sees
The onboard computer and the TMS each hold their own order versions. Changes are phoned or messaged through, and drivers run trips that planning no longer has up to date.
eCMR data doesn't reach invoicing
Digital consignment notes are signed in a platform that is separate from the TMS. Invoices are only correct after manual reconciliation, and completed shipments are noticed too late.
Fleet tracking remains just visualisation
The fleet is visible on a map, but the data isn't fed back into planning optimisation, customer communication or fuel control.
Maintaining customer portals twice
Shippers want self-service insight into their shipments. In practice that means a separate portal pulling data from a single source, while customers expect multiple sources.
Cabotage and tachograph requirements
The EU Mobility Package, tachograph downloads, payroll administration dependent on driving and rest times: without central data, compliance checks become painful every month.
Planning based on averages
Without real-time fleet data, you plan on standard times rather than on actual driving and unloading times per location. Buffer time is conservative, and productivity is lost in the margin.
Our focus solutions for transport & logistics
Below are the sub-areas in which we regularly build software for haulage companies and logistics service providers. Each page goes deeper into the architecture and typical integration patterns.
Onboard computer integration
A two-way integration between your TMS and onboard computer suppliers (Transics/Wabco, BigChange, EBlox, Squarell, Shotl, Webfleet). Orders, status updates, trip completion and tachograph data in one coherent flow.
eCMR integration
Digital consignment notes via Transfollow, eCMR.org or your own eCMR platform, integrated with your TMS, FMS and invoicing process. Including signed signatures, photos on delivery and support for multi-carrier chains.
Fleet tracking dashboard
Real-time insight into fleet position, driving and rest times, fuel consumption and geofencing events. Not just visualisation, but also event-driven triggers to planning, the customer portal and compliance reporting.
Transport planning API
Planning APIs that connect your TMS to route planners (PTV, Ortec, Routyn, Greenway), customer systems (shippers and carriers) and your own optimisation algorithms. Including slot booking, ETA broadcasting and exception handling.
Types of software we build for the transport sector
Not every transport organisation needs the same thing. Below are the types of solutions we work on on an ongoing basis, separately or in combination.
What we typically build
What we advise against
Architecture choices we regularly make
Good transport software stands or falls with its integration architecture. Below are the choices we most often explain to clients.
Event-driven integration
Order updates, status changes and location events flow through an event bus (Kafka, RabbitMQ, Azure Service Bus) so all systems synchronise in near real time. No nightly batches that are always behind.
Vendor-independent abstraction layer
On top of your telematics vendor or TMS, we build a dedicated API layer. Switching vendors in five years? Then you rebuild the adapter, not the applications that use the data.
Customer portal as a first-class citizen
Shippers and end customers expect real-time visibility. We build the portal as a standalone application with its own scaling profile, not as an add-on to a TMS that can't handle the traffic volume.
Tachograph data in a dedicated data lake
Driving and rest times, breaks, violations: stored in a structured way and linked to payroll administration and compliance reporting. No more scattered Excel exports.
Tech stack for transport software
Pragmatic choices with strong vendor neutrality. We don't want tools that are dead in two years.
Backend
.NET 8 / C#, Java 21 / Spring Boot, Node.js (NestJS): the choice depends on your existing IT stack and in-house knowledge.
Real time and events
Kafka, RabbitMQ or Azure Service Bus for event flows. WebSockets/SignalR for live tracking updates to customer portals and planners.
Maps and routing
HERE Maps, TomTom, Google Maps, Mapbox for visualisation. PTV, Ortec, GraphHopper for route optimisation. OSRM where self-hosting is required.
Mobile (drivers)
React Native, Flutter or native iOS/Android. Offline-first, because connectivity on the road isn't always reliable.
Integration and EDI
Mendix, n8n, Boomi where low-code is enough. Custom middleware in TypeScript/Python for specific EDI flows (EDIFACT D96A IFTMIN/IFTMSC).
Cloud and observability
Azure, AWS or GCP depending on your existing contracts. Datadog or the Grafana stack for monitoring event flows and API latency.
Compliance and data integrity in transport
Transport software directly touches driving and rest times, customs, VAT returns, cabotage rules and the EU Mobility Package. We build with this reality from the start, not as an afterthought.
Tachograph and Mobility Package
Driving and rest time recording in line with EU Regulation 561/2006 and the amendments in Mobility Package I. Automated data download, storage, violation checks and integration with payroll and planning systems.
Cabotage and posting of workers
International trips are subject to complex rules on cabotage (maximum number of domestic trips per country per cycle) and posting (notifying workers in the customer's country of establishment). The platform automates counts, alerts and declarations.
eCMR and signed consignment notes
Digital consignment notes under the CMR protocol, with digital signatures from sender, carrier and consignee. Retention obligations, readable archives, and integration with invoicing and claims handling.
End-to-end audit trail
Every change to an order, every route adjustment, every status update traceable to who, when and why. Important for customer claims, damage handling and internal quality control.
Frequently asked questions about transport and logistics software
Do you build your own TMS, or integrate with existing TMS systems?
By default we choose to integrate or extend rather than replace. TMS systems such as Transwide, Microsoft Dynamics 365 SCM, RoadIT, Datachance, KS-Tools and TeXuS have years of product development behind them. We build on top of an existing TMS with an integration layer, customer portal, mobile or planning features. We only replatform fully when the existing solution demonstrably no longer fits.
Which on-board computer suppliers do you work with?
Transics/Wabco, BigChange, EBlox, Squarell, Webfleet (Bridgestone), Shotl, Geotab: most suppliers have modern APIs or data feeds. We shield the specific API behind our own abstraction layer so you can switch without rewriting the application.
Is eCMR mandatory?
Not uniformly across the EU. A growing number of countries recognise the eCMR protocol; the Netherlands has recognised eCMR since 2017. In practice, the digital consignment note has become the de facto standard for modern logistics chains. You still need a paper fallback where countries or customers require it.
How long does a project like this take?
A well-defined integration (for example an eCMR integration between your TMS and invoicing) typically takes 6-12 weeks. A broader programme (on-board computer + eCMR + customer portal + planning API) is a 9-18 month effort, split into phases with measurable deliverables.
Do you work with our TMS supplier?
Preferably, yes. We have solid experience with TMS suppliers that are open to integrations via their API or direct database replication. We coordinate technical sessions, align on API contract changes and do joint testing where needed.
Can you also build something for one specific subdomain?
Yes. We can deliver a customer portal, an eCMR integration or a planning API as a clearly scoped piece of work. We build modularly so you can expand later without us having to redo earlier work.
What does a transport software project cost?
A targeted integration typically runs €30,000-80,000. A customer portal or mobile driver app €80,000-180,000. A broader integration platform covering multiple subdomains can reach €200,000-600,000. You get a concrete estimate after the discovery.
Do you have experience with international logistics?
Yes. We have worked for clients with cross-border operations in the Benelux, DACH and the wider EU chain. Cabotage rules, posting, customs (NCTS), multi-currency and multi-VAT are familiar territory.
Ready to untangle your transport and logistics stack?
We start with a transport discovery: you get an honest picture of where the biggest value leaks are, which integrations deserve priority and which approach fits your scale and complexity. No sales pitch.