Industry · Transport & logistics

Custom yard dock management system.

We build custom yard and dock management software for distribution centres, multi-modal terminals and production sites. Slot booking, gate check-in, dock allocation and yard tracking in one environment, with integrations to your existing WMS, TMS and ERP.

SectorDistribution centres
SectorMulti-modal terminals
SectorCold chain & pharma
SectorRecycling & building materials

Dutch yard and dock operations in numbers.

~1.700
Distribution centres in the Netherlands
36 million
Truck movements per year
~9,7%
Logistics share of GDP
EU 561
Driving and rest times during waiting time

Source: CBS Logistics Monitor, Topsector Logistiek, EU Regulation 561/2006.

What a YMS does, and why your WMS and TMS weren't built for it.

A Yard Management System focuses on the zone your other systems skip: the yard. TMS manages what's on the road, WMS manages what happens inside the warehouse walls. In between lies the yard — with drivers waiting, dock assignments kept on a fax or in Excel, and trailers that can't be found on any live map. That's exactly where dwell time, demurrage and CO₂ emissions arise, and where your planning breaks down as soon as freight volume peaks.

A YMS links slot booking to gate check-in to dock allocation to yard tracking. A carrier books a time window in advance, the driver reports in via licence plate recognition or a driver app, the system assigns the right dock based on product, priority and refrigeration, and the WMS automatically receives a receiving trigger as soon as the truck docks. An audit log runs alongside every truck event, so afterwards you can show, at order or supplier level, where the time went.

We build it as a standalone component that complements your stack — not as a rip-and-replace. In most cases your WMS, TMS and ERP stay in place. The YMS layer picks up the yard flow and sends events back to the systems already running. For multi-site operations, we deliver a central dashboard showing dock occupancy and dwell KPIs in real time. Site managers see a heatmap of occupied versus free docks per location, and head office sees the benchmark between DCs so they can steer with precision.

For most clients, the greatest value comes not from a single module but from the combination: a slot portal that removes 80% of no-shows from the schedule is twice as valuable once ANPR check-in and automatic dock allocation are attached to it. That is why we almost always advise starting small with one pilot dock and running a complete loop on it, rather than rolling out all modules across all docks at once.

Modules per dock and yard flow.

A Yard Management System consists of separate modules that each deliver value on their own. We build what you need and integrate it into your existing stack in phases.

Slot booking and gate check-in

The start and end point of the yard flow. Carriers and freight forwarders book a time window in advance via a white-label portal or API; the driver reports to the gate using ANPR licence plate recognition or via a driver app on their phone. The system matches incoming licence plates to slots and immediately knows what is going to be unloaded or loaded.

Our module set includes a multilingual slot portal, a mobile-first gate app or self-service kiosk, ANPR camera integration with the usual manufacturers (Genetec, Milestone, Nedap), and advanced escalation rules for no-shows or late arrivals. For multi-site operations, everything runs on a single central tenancy with location-specific business rules, so a carrier visiting several DCs always works with the same portal.

The slot portal is the one component your carriers interact with most. We pay extra attention to it: a minimal, self-explanatory flow with logical time window suggestions, an automatic driving and rest time check, and instant feedback when a window is fully booked. The less support your planning team has to provide, the lower the barrier to making the portal mandatory.

If customs freight passes through your site, arrival also has a paperwork side. How to capture that at the gate and at the loading bay is covered in the app for paperwork on a customs shipment.

  • White-label slot portalCarriers book for themselves — multilingual, with an API for TMS integration.
  • ANPR licence plate recognitionGenetec, Milestone or Nedap cameras, matched to a slot in < 2 seconds.
  • Driver app or self-service kioskCheck in, scan documents, instructions in their own language.
  • No-show and late-arrival rulesConfigurable per carrier and per slot type.

Built within the regulatory framework for logistics and compliance.

A YMS touches on labour rules, privacy and sector-specific safety standards all at once. We work within those frameworks from the first sprint, so audits and certification are not a puzzle to solve after the fact.

EU Regulation 561/2006

Driving and rest times during waiting time

Waiting time on your yard counts towards the driver's rest time records. Our module logs arrival and departure times per licence plate, with export to tachograph reporting.

GDPR Art. 35 — DPIA

Privacy in driver tracking

Licence plate data, BLE tag locations and driver app events are personal data. With every project we deliver a DPIA, retention settings and data subject rights flows so that your DPO can sign off on it.

NEN-EN-ISO 22301

Business continuity management

For critical DC operations, we build the YMS with a failover path: in the event of an outage, gate check-in keeps working via a local cache and synchronises later.

ATEX Directive 2014/34/EU

Hazmat zones and dangerous goods

For chemical and fuel DCs, we link dock allocation to ATEX zoning and record the ADR classification of the load at slot level.

HACCP & cold chain

Temperature monitoring for food and pharma

For cold-chain DCs, we link trailer temperature to the dock record via a tag or refrigeration unit API, so that deviations are spotted immediately on receipt.

EU AI Act

Responsible AI in dock allocation

When we deploy AI-driven slot or dock allocation, we map the risk classification, document the governance and always keep human override available.

Seamlessly connected to your existing logistics stack.

We don't replace your enterprise YMS. We integrate with what you run, and only build the modules your stack is missing. That keeps your investment in WMS, TMS and ERP intact.

SAP EWM
Warehouse integration
Manhattan
WMS & TMS
Blue Yonder
Supply chain platform
Transwide
TMS & carrier portal
Genetec / Milestone
ANPR & CCTV
Nedap
RFID & access
FourKites
Visibility & ETA
In-house ERP
Custom integration

Integrate rather than replace.

The big YMS vendors (C3 Solutions, PINC, Manhattan Yard, Blue Yonder, Centric) suit global retailers with hundreds of DCs very well. For mid-market operations they are over-engineered and expensive. We also see that enterprise packages in sectors with unusual rules (cold chain, hazmat, recycling, building materials) don't quite fit the actual flow. Those packages often lack exactly the modules your sector considers important, such as ADR classification at slot level for hazmat, or weighbridge integration for waste processors.

Our approach: we build the YMS layer to order, with the same modules the big packages offer, but focused on your site-specific flow and your existing system landscape. For deep combinations of custom WMS, transport software and YMS, we often deliver a single integration layer in which all three work together. That stops data being translated three times between systems, which in practice accounts for most of the integration maintenance time.

Important: we first ask whether a custom YMS makes sense for your situation at all. If you are a single-site DC with a fixed number of regular carriers and seven docks, and a standard SaaS tool would serve you perfectly well, we will tell you so. Our added value lies in the combination of scope, integration depth and sector-specific rules, not in the fact that we build it ourselves.

From first workshop to live on the yard in clear steps.

A YMS implementation has its own rhythm. Five phases that we go through for every project, with operational continuity as a hard requirement.

01 · Audit

Yard walkthrough

A day at your site with the site manager, a dock supervisor and a driver. Result: the current flow mapped out and dwell-time bottlenecks marked.

02 · Design

Module scope

Which modules come first (often slot and gate), which integrations take priority, and what the cutover looks like per dock block.

03 · Build

Sprints with dock tests

Iteration in short sprints, testing straight away on one pilot dock. Operations gets a working flow to practise with every sprint.

04 · Cutover

Phased rollout

First one dock block, then site-wide, then multi-site if needed. Every rollout comes with training, a runbook and a parallel-run period.

05 · Maintenance

Ongoing

Monitoring of dwell-time KPIs, ANPR uptime and integration status. We provide first-line support, while your operations team manages the business rules.

Work for distribution and logistics operations.

Retail DC · Brabant

Slot booking and gate check-in

White-label slot portal for 180 regular carriers, ANPR check-in and an automatic SAP EWM receiving trigger.

−42%
average dwell time
8 docks
centrally managed
Cold chain · Rotterdam

Dock allocation with temperature check

Reefer temperature linked live to the dock record, HACCP event log per delivery, alerts when limits are exceeded.

100%
temperature log per truck
3 sites
one dashboard
Recycling hub · Eastern Netherlands

Yard tracking with BLE tags

Real-time yard map with trailer locations, demurrage flag for overstays, integration with weighbridge data.

−31%
demurrage claims
multi-modal
truck + rail track

Recognised within logistics and supply chain.

Topsector Logistiek Innovation Programme 2024

"Yard management remains the weak link between TMS and WMS. Mid-market operations in particular are looking for affordable, sector-specific solutions rather than enterprise packages."

Logistiek Magazine, June 2024

"ANPR check-in and automatic dock allocation are the modules that are winning Dutch DCs the most time right now, regardless of which vendor sits behind them."

Client review, Brabant retail DC

"Dwell time has measurably dropped within a few sprints. The carriers are especially pleased: they now plan around our window instead of gambling on arrival times."

Answers for site managers who want to digitise the yard.

The questions we hear most often from operations directors and logistics managers.

What exactly is a Yard Management System?
A YMS manages everything that happens on your yard: trucks arriving, dock allocation, waiting-time monitoring and departure. It sits between your TMS (what is on the road) and your WMS (what happens inside the warehouse). At its core: advance slot booking, gate check-in on arrival, dock allocation during the visit, and yard tracking so you know where every trailer is. A good YMS also reports on dwell time, demurrage risk and CO₂ from idling.
What is the difference between a YMS, WMS and TMS?
A TMS plans and monitors transport on the road: routes, ETAs, vehicle costs. A WMS manages stock and order picking inside the warehouse. A YMS bridges the two: from the moment a truck arrives until it drives off again, it is the YMS's territory. In practice, the YMS is often the weak link. Many DCs have expensive WMS and TMS packages but handle dock allocation through Excel or WhatsApp. That is where most of the dwell-time gains are to be found. Also read how we build custom transport software.
Do you replace enterprise packages such as C3 Solutions or PINC?
No, that's not what we're for. If you run on C3, PINC, Manhattan Yard, Blue Yonder Yard or Centric and it works, it should stay that way. We build when you're a mid-market company and those packages are too expensive or too heavy, when you're in an industry with unusual rules (cold chain, hazmat, recycling, building materials), or when you need such a deep integration between WMS, TMS, YMS and ERP that a standard package can't handle it. We also see situations where enterprise vendors have a long roadmap for specific features you need now, and then a custom module that connects to the vendor can be a smarter choice than waiting for a release cycle. We make that distinction honestly up front, in the first workshop.
Do you work with ANPR licence plate recognition at the gate?
Yes, it is one of the modules we deliver most often. We integrate with Genetec, Milestone, Nedap and other common ANPR systems. The flow: the camera reads the licence plate, the system matches it to a booked slot, and the barrier opens or sends the driver to a self-service kiosk for extra steps. For sites without fixed cameras, we also provide a mobile variant through the driver app, where the driver confirms their own licence plate or scans a QR code. For unmanned night or weekend check-ins, we combine ANPR with biometrics or a second-factor SMS to the driver. For driver data we comply with GDPR requirements and deliver a DPIA with the system. Camera footage and licence plate events are stored separately so that retention settings can be configured per category.
Can you build a slot-booking portal for our carriers?
Yes, that is often the first thing a DC wants. We build a white-label slot portal in your branding, with multilingual support (NL/EN/DE/PL as standard), an API integration with your carriers' TMS, and escalation rules for no-shows or late arrivals. The portal works on desktop and mobile, and can optionally also be used through a carrier account with API access, so large carriers can book from their own system. For less experienced carriers, a simple web flow with just a few clicks works well; for your top carriers, API booking is more realistic because they use their own planning system. We can run both flows side by side so that you don't exclude any carriers on technical grounds.
How do you integrate with our WMS and TMS?
Where possible, we choose a standard API: SAP EWM, Manhattan, Blue Yonder and Transwide all have documentation for receiving and dispatch events. For less common or legacy packages, we build a middleware layer with a message bus (often Azure Service Bus, RabbitMQ or a simple REST poll). The YMS triggers receiving in your WMS as soon as a truck docks, and the WMS confirms unloading completion so the YMS knows when the dock is free again. For more in-depth integration questions, see also our integration page. In the first sprints, we always get one pilot integration to a production-ready state before starting the second system integration. That way you don't have to wait for all integrations to be finished before going live.
Does the YMS also work for multi-modal terminals with rail or sea?
Yes. For terminals with truck plus rail or barge, the yard flow becomes more complex because a rail set arrives differently from a truck, and the ETA update from the rail operator often has a different format. We integrate in the same way: an API or EDI feed to the terminal operating system, with truck and rail as separate arrival types. For sea container terminals, we work with partners who run TOS integrations, and we connect the yard layer to them neatly rather than building the entire terminal system ourselves.
How long does a typical YMS project take?
That depends on scope and the number of locations. A project with a single site and the basic modules (slot + gate + dock allocation) is considerably shorter than a multi-site rollout with yard tracking and cold-chain integrations. From the first sprint, we work towards operational value: after a few sprints, a pilot flow is usually already running on one dock, long before the system is rolled out site-wide. During the planning phase, we provide a well-founded timeline with phase boundaries, so you can adjust course along the way or postpone a phase.
What does a custom YMS project cost?
That depends heavily on scope: a single DC with slot + gate is a different project from a multi-site operation with dock allocation, BLE yard tracking and cold-chain integration. We work with fixed sprint budgets, and after the first workshop we give a well-founded estimate for the full build. We never bill hourly after the fact, and subscriptions for ANPR cameras or BLE tags are paid directly to your supplier. You can also compare with our page on custom order management for a similar scoping process. What we include as standard, regardless of scope: a DPIA, a runbook for your operations team, and monitoring of the critical integrations for the first months after go-live.
How do you handle GDPR for driver tracking?
Licence plate, BLE tag location, driver app logins: these are all personal data. With every project, we deliver a DPIA with data flow mapping, retention settings per category, and data subject rights flows for drivers who want to view or delete their data. For multinational carriers, we work with multilingual privacy statements in the driver app as standard. AI-driven dock allocation is classified and documented under the EU AI Act. Also read how we use AI responsibly in transport.

Talk to us about your yard and dock challenge.

A half-hour introduction with your site manager or operations director. We listen, ask questions about your current flow, and give an initial direction for a project. No obligation.

Edit content