Logistics software development for Dutch forwarders, carriers and 3PLs that have outgrown their standard TMS

What is logistics software development, and who needs custom work?

Logistics software development is building software for moving and storing goods: planning, tracking, documenting, invoicing and communicating about shipments. Custom work is needed when standard products cover the core but not the way your customers, drivers and warehouse actually work together.

The Dutch logistics landscape is full of capable standard systems. Most forwarders, carriers and 3PLs already run a TMS, a WMS or both, plus a bookkeeping package and a telematics service. The gaps sit between them: a customer wants a portal your TMS does not offer, a carrier's API is not in your vendor's list, drivers still carry paper CMRs, and hauliers phone the warehouse to ask when they can unload.

That is where custom logistics software development pays. Not as a grand replacement of everything, but as specific modules that remove phone calls, retyping and guesswork, connected to the systems you keep.

• Freight forwarders near Rotterdam and Schiphol: booking and status portals, document exchange, partner integrations.
• Road carriers: driver apps, proof of delivery, trip status for customers.
• 3PLs and DCs in Venlo, Tilburg and Moerdijk: dock scheduling, client dashboards, billing data.
• E-fulfilment operators: carrier label and tracking integrations across several parcel networks.

Signs your off-the-shelf TMS or WMS is no longer enough

You have outgrown a standard system when your people spend more time working around it than in it. The clearest signal is a spreadsheet or inbox that has quietly become part of your operation.

• Planners answer the same “where is my shipment?” email many times a day.
• A carrier you use heavily is not supported by your TMS vendor's integrations.
• Drivers photograph paper CMRs and someone types the details in at the office.
• Hauliers turn up without appointments and trucks queue at the gate.
• Monthly client reports are assembled by hand from three exports.
• Customers ask for data feeds your system cannot produce in their format.
• The vendor's answer to every request is “it is on the roadmap”.

One sign alone is not a reason to build. Three or four together usually are, because each one costs hours every week and none of them will be fixed by the vendor on your timescale. The next question is whether to build around your system or replace it.

Build around your TMS or replace it? A decision rule for Dutch operators

Build around it in almost every case. Replace the core only when it blocks the business itself, for example when it cannot handle a new transport mode, cannot scale, or the vendor is ending support.

A TMS or WMS holds years of configuration, rates, customer rules and staff habits. Replacing it is expensive, risky and slow, and rarely what an operator actually needs. Building around it means adding modules that read from and write to the core system through its API, database views, EDI or file exports, and leaving the core in charge of what it does well.

This approach also lets you replace the core later, one function at a time, if you ever need to. Each module talks to the core through a small integration layer; swap the core and only that layer changes. Software people call this gradual replacement the strangler pattern. For you, it simply means no big-bang go-live weekend.

For the general version of this choice, see off-the-shelf versus custom software.

Customer portals and shipment dashboards for shippers

A customer portal gives your shippers a login where they book transport, follow shipments, download proof of delivery and invoices, and see their own volumes. It is usually the first custom module a Dutch logistics company builds, because it cuts status calls immediately.

The portal reads shipment status from your TMS and carrier APIs, and documents from wherever they are stored. It writes bookings back into your TMS so planners work in one place. Each customer sees only their own data, with separate user accounts for their staff and roles for booking, viewing and finance.

Dashboards follow naturally: on-time delivery, exceptions by reason, volumes per lane or week, and pallet or parcel counts per client. For 3PLs, the same data supports monthly client reviews without a day of spreadsheet work beforehand.

• Booking form with address validation and your service types.
• Track and trace timeline combining your TMS milestones and carrier scans.
• POD, CMR and invoice downloads per shipment.
• Exports and API access for customers who want data in their own systems.
• English and Dutch interface, with your team approving the Dutch wording.

The general approach is described on portal development and dashboard development.

Carrier API integrations: PostNL, DHL and DPD in one flow

Carrier integrations let your system create labels, book pickups and receive tracking events without anyone logging into three carrier portals. Each carrier documents its own API and issues credentials under your contract with them.

PostNL's developer portal lists APIs for shipments, returns, address checks and track and trace, among others. According to PostNL's documentation, existing customers request a production API key in MijnPostNL, while sandbox keys for testing are available to developers first. DHL's Shipment Tracking – Unified API covers several DHL business units in one interface; DHL's documentation says initial access allows 250 calls per day at no more than one call every five seconds, is intended for development only, and must be upgraded for production. DPD offers its own web services for shipment creation and tracking under your DPD contract.

Those details shape the design. Tracking should be event-driven or batched rather than polled per parcel per minute, rate limits need queues and retries, and every failed call must be logged and visible to someone, not lost. The integration layer then maps each carrier's status codes into your own set, so customers and planners see one consistent timeline.

Carrier contracts, pricing and account set-up stay between you and each carrier. For webshop-specific shipping plugins, see the sibling page on a WooCommerce developer in the Netherlands.

Driver apps with digital CMR (e-CMR) capture

A driver app replaces paper stop lists and consignment notes with a phone: the day's trips, navigation hand-off, photos, signatures, damage remarks and timestamps, synced to your office as soon as there is signal. Digital CMR capture is part of that, within the rules on electronic consignment notes.

The CMR Convention was extended by an Additional Protocol adopted in 2008 that allows electronic consignment notes for international road transport. The international road transport union IRU reports that 39 of the 58 CMR contracting parties have ratified or acceded to the e-CMR protocol, so for a cross-border trip both countries' status matters. e-CMR platforms have been used in the Netherlands for years; many operators work with an established e-CMR provider and have the driver app feed it rather than becoming a platform themselves.

Looking ahead, the EU's eFTI Regulation requires member state authorities to accept freight information shared electronically through certified eFTI platforms from 9 July 2027. That concerns certified platforms; a custom driver app can capture the data and pass it to one.

• Offline mode: work saved on the phone and synced later.
• Photo and signature capture linked to each stop and consignment.
• Hand-off to your chosen e-CMR provider where one is used.
• Driver location shared only during working trips, with retention limits.

Which documents are legally valid on a given route is a question for your legal adviser or trade association. We build the capture and the connections. Apps start from US$600; see the sibling page on choosing an app development company in the Netherlands for the app side.

Warehouse dock and time-slot booking tools

A dock booking tool lets hauliers and suppliers book a loading or unloading slot online, shows warehouse staff the day's plan per dock, and records arrivals, delays and no-shows. For busy DCs around Venlo, Tilburg or Moerdijk, it turns a queue at the gate into a schedule.

The core is a calendar per dock with rules: slot lengths by load type, capacity per hour, opening times, blocked periods and which customers or carriers may book which docks. Hauliers receive a booking reference and can change or cancel within limits you set. At the gate, staff check the reference, and the system logs actual arrival and departure times.

Integration makes it useful beyond the gate. Expected inbound orders from your WMS can pre-fill bookings, and actual times feed a dashboard showing dock utilisation and punctuality per carrier, which gives your account managers facts rather than impressions.

• Public booking page per site, in Dutch, English and other languages you supply.
• Dock-by-dock day view for warehouse leads on a tablet.
• Automatic reminders and change links for bookers.
• Arrival and departure logging, with reports per carrier.

How much does logistics software development cost?

With BtechWaleTech, a custom logistics module starts from US$900, a driver or warehouse app from US$600, and AI document reading from US$600. Quotes from Dutch logistics IT suppliers and freelancers vary widely, largely because of rates, whether a licence is bundled, and how much on-site analysis is included.

Within any quote, these factors move the number most:

• Systems to connect: each TMS, WMS, carrier API, EDI partner or bookkeeping package adds work, more so when documentation is thin.
• User groups: planners, drivers, warehouse staff, customers and hauliers each need their own screens and rights.
• Offline and devices: apps used in trucks or on warehouse floors need offline storage and testing on real devices.
• Status mapping: harmonising different carriers' event codes is detailed work.
• Languages: Dutch and English are common; drivers may need further languages you supply.
• Data migration and history: importing years of shipments for reporting takes time to verify.

There is no per-shipment or per-user licence fee on custom code; you pay for hosting and any third-party services directly. After two free months of maintenance per go-live, care continues from US$120/mo. See the pricing page for every starting price.

How long does custom logistics software take, and how is it phased?

A single module usually takes 6–12 weeks, and an app 6–10. Larger programmes are split into phases of that size, each going live and paying back before the next starts, so operations never depend on one big switch-over.

A typical sequence for a forwarder or carrier: first the carrier integrations, because everything else uses that data; then the customer portal, which removes status calls; then the driver app, replacing paper; and finally dashboards and document automation. A 3PL might start with dock booking instead, because the gate queue is the most visible problem.

Each phase runs alongside current systems. The portal shows TMS data; the TMS stays the source of truth. The driver app runs in parallel with paper on a few routes before rolling out. If something goes wrong, the old way still works, which keeps your customers unaware that anything changed except the improvement.

For a general view on project length, see how long it takes to build an app.

Driver location, customer data and confidentiality

Logistics software handles two sensitive kinds of data: personal data about drivers and recipients, and commercial data about your customers' shipments. Both need access control, logging and clear limits.

Driver location and photos are personal data under the AVG. Track only during working trips, show positions only to people who need them, set retention periods, and tell drivers what is recorded and why. If your organisation has a works council, involve it early, since systems that monitor staff often need its involvement. Recipient names and addresses on consignments should be kept only as long as your business and legal needs require.

Commercial confidentiality matters as much. In a customer portal, one shipper must never see another's volumes or rates. That is enforced in the database queries and tested explicitly, not left to the interface. Hosting sits in an EU region in your account; where our team needs access to live data, a processing agreement with Standard Contractual Clauses is the usual basis, since India has no EU adequacy decision. Your own adviser confirms the set-up.

The sibling page on GDPR-compliant website development covers processing agreements and consent for public-facing sites.

How to choose a logistics software development partner

Choose the partner who asks about your exceptions: missed slots, damaged goods, partial deliveries, returned pallets. Anyone can build the happy path; logistics software lives or dies on what happens when things go wrong.

Working with a remote logistics software team from the Netherlands

Development work fits the time difference well: our day starts before yours, so fixes and test builds are often ready when your planners arrive. Operational support at night is a separate question, answered honestly in the quote.

We do not visit depots or warehouses. A phone video of a gate, a dock or a driver's paperwork routine gives us what we need to design the screens.

Ownership, handover and not getting locked in

Everything you pay for should be yours: the code, the hosting, the database and the documentation. That is especially important in logistics, where software becomes part of daily operations within weeks.

The repository sits in your organisation from the first commit. Hosting runs in your cloud account in an EU region. Carrier API credentials are issued under your contracts and stored in your secrets manager. Copyright in the code written for you transfers in writing as set out in the quote, with your lawyer checking the wording.

The handover pack includes an integration map showing which system sends what to which, a runbook for common failures such as expired carrier credentials, and set-up notes for a new developer. The test for success: another team could take over without asking us anything.

Risks and red flags in logistics software projects

Most logistics software projects that fail do so on integrations and change management, not on screens. Watch for these signs with any supplier.

• A quote that lists screens but not integrations, status mapping or error handling.
• No test plan with real carrier sandboxes before go-live.
• A big-bang switch-over with no parallel running period.
• Driver apps tested only in the office, never on a real route.
• Customer data separation left to the front end rather than enforced in the database.
• Carrier credentials stored in the supplier's accounts.
• No plan for what happens at 03:00 when an integration fails.

Each of these can be fixed in the plan before you sign. For projects that already went wrong, see what to do when a developer leaves a project midway.

Worked example: a hypothetical Venlo 3PL with a gate queue and a status inbox

Say a mid-sized 3PL near Venlo runs a standard WMS, receives inbound trucks from dozens of hauliers without appointments, and has two staff members answering client emails about order status. Outbound parcels go through PostNL and DHL, booked in each carrier's portal.

Phase one would be a dock booking tool: hauliers book slots online per dock, the warehouse lead sees the day on a tablet, and arrivals are logged at the gate. Quoted from US$900, over roughly seven weeks, with a two-week parallel period where walk-ins are still accepted.

Phase two would connect PostNL and DHL through their APIs so labels are created from the WMS and tracking events come back automatically, feeding a client portal where each client sees orders, parcels and delivery status. That would be a second module, again quoted from US$900. A later phase could add AI reading of inbound delivery notes from US$600.

This example is hypothetical, meant only to show how phases fit together; it is not a client story or a promised outcome.

Checklist before commissioning logistics software development

Prepare these answers before talking to any supplier; they make quotes comparable and shorten the project.

• Which problem costs the most hours each week: status questions, gate queues, paperwork, reporting?
• Which TMS, WMS and bookkeeping systems are in use, and do they have APIs or exports?
• Which carriers do you use, and do you have API credentials under your contracts?
• Who are the users: planners, drivers, warehouse staff, customers, hauliers?
• Do drivers need offline use, and which languages?
• Do you use an e-CMR provider already?
• What must happen when an integration fails at night?
• Who in your team signs off each phase?
• Where will the code, hosting and credentials live?
• What does support after go-live include, and when is it available?

Send your answers, or just the one problem you want gone first, and you will receive an itemised, phased quote in about two working days. The Netherlands overview lists our other services.