Delivery scheduling software for time slots, routes and drivers
Delivery scheduling software lets customers book a delivery window that your fleet can really meet. It checks every slot against the vehicles, drivers and routes that serve the address, builds the day's routes within driving-time rules, tells customers when to expect the van and records proof of every drop. We build delivery scheduling software for wholesalers, retailers, furniture and appliance sellers and distributors whose rules do not fit a generic route planner, hosted in an EU region and with the code in your company's name.
- You see the result before it goes live
- Fixed price for the agreed scope, in writing before work starts
- Source code, domain and accounts in your company's name
Why delivery scheduling is its own problem
Promising a delivery window is easy. Keeping it depends on many things at once: how many vehicles serve that area on that day, how much each one can carry by weight and volume, which drivers are working and for how long they may drive, whether the product needs two people or a tail lift, whether the customer also wants installation or the old appliance taken away, and how far apart the other stops already are. A slot that looks free in a calendar may be impossible on the road.
When the booking screen and the route plan are separate, the gap shows up as missed windows, overtime, half-empty vans in one area and turned-away orders in another. The system we build closes that gap: a slot is offered only when a route can absorb it.
What the system does
- Delivery zones and capacity. Areas, the days and windows each is served, and the capacity per window by vehicles, stops, weight and volume.
- Slot booking. Customers book in your online store or by link, and your sales and service teams book for customers, all from the same live capacity.
- Delivery rules. Two-person deliveries, tail lift, refrigerated goods, installation, collection of old goods, building access and time limits per site.
- Route planning. Routes built from the booked stops, with time windows, vehicle limits and drivers' hours, and dispatchers free to change them.
- Driver app. The day's stops in order, navigation, customer notes, photos, signatures and failed-delivery reasons.
- Customer messages. Booking confirmation, a reminder the day before, a narrower arrival estimate on the day, and a link to follow the van.
- Proof of delivery. Time, location, signature or photo per stop, stored with the order for disputes and invoicing.
- Reporting. On-time rate per window, failed deliveries and their reasons, cost per stop and use of each vehicle.
Slots that follow route density
The cheapest delivery is the one next to another delivery. A good slot system uses that: it shows the windows where a van already passes nearby first, it can price or limit windows by how full each route is, and it can offer a wider window at a lower cost to the customer who does not mind. Rules decide how far ahead each window opens, when it closes for booking, and how much capacity is held back for priority customers or same-day orders. You set the rules; the system applies them the same way every time.
Driving time and working time rules
A route that breaks the rules is not a plan. For goods vehicles whose maximum permissible mass, including any trailer, is above 3.5 tonnes, Regulation (EC) No 561/2006 (read 11 November 2026) sets the limits:
| Rule | Limit |
|---|---|
| Daily driving time | 9 hours, extendable to 10 hours at most twice a week (Article 6) |
| Weekly driving time | 56 hours (Article 6) |
| Two consecutive weeks | 90 hours (Article 6) |
| Break | At least 45 minutes after 4.5 hours of driving, which may be split into 15 and 30 minutes (Article 7) |
The planner treats these as hard limits, uses the driving already recorded for each driver this week, and adds your own rules for shift length, loading time and breaks. For smaller vans outside the regulation's scope, your national working time rules and your own shift patterns still apply, and the system holds them the same way. Where the regulation applies, tachograph records remain the legal source; the plan is checked against them, not instead of them.
Connected to the systems you keep
Delivery scheduling sits between ordering and the warehouse. Orders arrive from your online store, ERP or sales system with their products, weights and delivery requirements. Picking and loading are planned in the warehouse system in route order, and loading bays can be booked as our dock scheduling software page describes. After delivery, proof and any failed-delivery reason go back to the order for invoicing and customer service. Parcels and long-distance shipments handed to carriers are booked through the carriers' interfaces, and their tracking comes back into the same customer view. These connections are built as our API integration page describes.
Failed deliveries, rebooking and collections
Every failed delivery costs a second trip, so the system works to prevent them and to recover quickly when they happen. The day-before reminder asks the customer to confirm, and a customer who cannot be home can move the slot themselves within your cut-off. On the day, the driver records a reason for any failed drop, such as nobody home, no access, wrong address or goods refused, with a photo where it helps. The customer then gets a link to book a new window at once, and the order shows the history for customer service. Collections of returns, old appliances or empty pallets are booked as stops of their own, planned on the same routes so the van does not drive out twice, and their volume is counted in the vehicle's capacity on the way back. Reports show failed deliveries by reason, area and window, so a recurring problem, such as a building that needs a door code in every booking, is fixed at the source.
Customer data and drivers' location
Delivery systems hold customers' names, addresses, phone numbers and door codes, and they track drivers' location during the day. Both are personal data under the GDPR. We keep door codes and notes visible only to the driver of that stop and only on the day, share the van's location with the customer only within the delivery window, stop tracking drivers when their shift ends, and delete old location history on the schedule you set. Drivers are told what is recorded and why. Data is hosted in an EU region as standard, and the processing roles are written in a data processing agreement with us.
Route planning software and route optimisation
Route planning software decides the order of stops and which vehicle takes which stop; route optimisation software does it under constraints, which is where the real problem lies. A usable plan respects delivery time windows, vehicle capacity by weight, volume and pallet places, depot opening hours, loading order, driver skills and licences, driving and rest times, and stops that must be served by the same driver. Planners know it as the vehicle routing problem, and no tool solves it perfectly; good software finds a strong plan in seconds, shows why each stop sits where it does, and lets the planner move a stop and see the effect at once.
The same engine serves other kinds of rounds: service technicians, sales visits, waste and recycling collection, meal and pharmacy deliveries, and home care visits. For crews working on customer sites, see field service management software; for carers, see home care scheduling software.
Ready-made route planner or custom delivery scheduling?
There are many route planning and delivery management products, and for a fleet with simple parcels and standard windows one of them is often the right answer. We say so when it is. Custom software, or a custom booking layer on top of a product, fits when the rules do not fit:
| Situation | Usual answer |
|---|---|
| Simple parcels, standard windows, one depot | A ready-made route planning product |
| Two-person, installation or collection deliveries | Custom slot rules on top of route planning |
| Slots priced or limited by route density | Custom booking connected to the planner |
| Several depots, own fleet and carriers mixed | Custom scheduling with carrier integrations |
| A product you like that lacks customer booking or reporting | A custom layer through the product's interface |
For carriers and forwarders who need wider transport systems, such as electronic freight documents, see logistics software development. For technicians rather than goods, see field service management software.
How we build it
- A day in dispatch. We sit with your planners, drivers and customer service and collect every rule: zones, windows, vehicles, products, cut-off times and the exceptions.
- Scope and fixed price in writing. What the first version does, which systems it connects to and what is left out.
- Planning engine first. Slots and routes are tested against a real week of your past orders before the screens are polished.
- Booking, driver app and messages. Built in two-week rounds, used by a pilot area or depot first.
- Rollout. Area by area, with the old process kept as a fallback until the numbers hold.
The code sits in your company's repository, and the database and hosting are in your name. For staff rosters in the warehouse, see employee scheduling software. For forecasts, attendance and labour cost across depots, see workforce management software. For stock levels per depot and van, see inventory management software. See prices.
Questions we get
What is delivery scheduling software?
Software that decides when each delivery happens and who makes it. Customers or your sales team book a delivery window, the system checks it against the vehicles, drivers and routes that can serve that address, and on the day it builds the routes, sends the drivers their stops and tells customers when to expect them. Proof of delivery closes each stop.
How is it different from dock scheduling?
Dock scheduling books trucks into a warehouse's loading doors: inbound and outbound appointments at one site. Delivery scheduling plans the outbound trips from your depot to customers' addresses: time windows, routes, drivers and drops. Many companies need both, connected through the warehouse system.
Can the system respect driving-time rules?
Yes. For goods vehicles above 3.5 tonnes in the EU, Regulation (EC) No 561/2006 limits daily driving to nine hours, extendable to ten twice a week, weekly driving to 56 hours and two-week driving to 90 hours, and requires a 45 minute break after four and a half hours. The planner treats these as hard limits, together with your own shift rules.
Should we use route optimisation software or build our own?
For many fleets a ready-made route planning product is the right answer, and we will say so. Custom delivery scheduling fits when the slots must follow your own rules: products that need two people or special vehicles, installation or collection on the same visit, slot prices that depend on route density, or tight integration with your ordering, ERP or warehouse systems.
Does it work with our own drivers and with carriers?
Yes. Own drivers use the driver app with their stops, navigation and proof of delivery. Deliveries handed to carriers or courier companies are booked through their interfaces and their tracking is brought back into the same customer view.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.