Software for transport & logistics that brings your planning, fleet and consignment notes into line
We build software for transport companies, fleet operators and logistics service providers who want to connect their TMS, on-board computers, eCMR stack, fleet tracking and planning APIs into one workable chain. No more separate tools for planning, execution and invoicing, but a single coherent digital workspace with integrations that keep working.
Why transport software only delivers value when all systems talk to each other
A typical transport company quickly runs 8 to 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 disappears into manual rework.
Planning doesn't know what the driver sees
Onboard computers and TMS systems each keep their own order versions. Changes are made by phone or WhatsApp, so drivers end up driving routes whose schedules are no longer up to date.
eCMR data does not flow through to invoicing
Digital consignment notes are signed on a platform that sits apart from the TMS. Invoices only reconcile after manual checks, and complete shipments are spotted late.
Fleet tracking stops at visualisation
The fleet is visible on a map, but the data is not fed back into route planning, customer communication or fuel monitoring.
Customer portals maintained twice
Shippers want self-service insight into their consignments. In practice that means a separate portal pulling data from a single source, while customers expect several.
Cabotage and tachograph requirements
The EU Mobility Package, tachograph downloads and payroll administration all depend on driving and rest times. Without central data, compliance checks become a painful monthly exercise.
Planning based on averages
Without real-time fleet data, you plan around standard times rather than actual driving and unloading times at each location. Buffer time becomes conservative, and productivity is lost in the margins.
Our focus solutions for transport & logistics
Below are the subdomains where we regularly build software for haulage companies and logistics service providers. Each page goes into more depth on architecture and typical integration patterns.
Onboard computer integration
Bidirectional integration between your TMS and on-board computer providers (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 connecting your TMS to route planners (PTV, Ortec, Routyn, Greenway), customer systems (shippers and carriers) and your own optimisation algorithms. Includes 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 continuously, either on their own or in combination.
What we typically build
What we advise against
Architecture choices we make regularly
Good transport software stands or falls on 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 stay in near-real-time sync. No nightly batches that are always running behind.
Vendor-independent abstraction layer
We build our own API layer on top of your telematics provider or TMS. Switch vendors in five years? 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 separate application with its own scaling profile, rather than an add-on to the TMS that can't cope with the traffic volume.
Tachograph data in a dedicated data lake
Driving and rest times, breaks and overruns, stored in a structured way and linked to payroll administration and compliance reporting. No more loose Excel exports.
Tech stack for transport software
Pragmatic choices with strong vendor neutrality. We don't want tools that will be dead within two years.
Backend
.NET 8 / C#, Java 21 / Spring Boot, Node.js (NestJS). The choice depends on your existing IT stack and in-house expertise.
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 sufficient. 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 bears directly on 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 the Mobility Package
Driving and rest time recording in line with EU Regulation 561/2006 and the amendments in the Mobility Package I. Automated data extraction, storage, monitoring of overruns, and integration with payroll and scheduling systems.
Cabotage and posting of workers
International journeys are subject to complex rules on cabotage (maximum number of domestic journeys per country per cycle) and posting (registering 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 consignor, 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 and every status update is 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 do you 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 an existing TMS through an integration layer, customer portal, mobile app or planning features. We only fully replatform when the existing solution demonstrably no longer fits.
Which onboard computer vendors do you work with?
Transics/Wabco, BigChange, EBlox, Squarell, Webfleet (Bridgestone), Shotl, Geotab: most vendors have modern APIs or data feeds. We shield the specific API behind our own abstraction layer so you can switch without an application rewrite.
Is eCMR mandatory?
Not uniform 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 is now the de facto standard for modern logistics chains. For paper, a fallback is still needed where countries or clients require it.
How long does a project like this take?
A scoped integration (for example an eCMR integration between a TMS and invoicing) typically takes 6-12 weeks. A broader programme (on-board computer, eCMR, customer portal and planning API) is a 9-18 month project, split into phases with measurable deliverables.
Do you work with our TMS vendor?
Preferably, yes. We have good experience with TMS vendors who are open to integrations via their API or direct database replication. We coordinate technical sessions, agree on API contract changes and carry out 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 focused piece of work. We build modularly so that you can expand later without us having to redo earlier work.
How much 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 spanning several subdomains can reach €200,000-600,000. You will receive a concrete estimate after the discovery phase.
Do you have experience with international logistics?
Yes. We have worked for clients with cross-border activities in the Benelux, DACH and the wider EU supply 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 lie, which integrations deserve priority and which approach suits your scale and complexity. No sales pitch.