Hundreds of orders into an optimised fleet plan, in seconds
DigiTS Dispatch Planner brings orders in from any API or file, builds optimal routes across your entire fleet accounting for vehicle space, delivery slots and permit areas, then turns the plan into dispatched routes with one click — with a full audit trail behind every step.
Plan · Tue 16 Sep
321 orders · 12 vehicles available
1 · Order intake
SAP orders API
REST · Bearer
184
B2B portal
Internal
96
Key accounts
SQL Server sync
41
2 · Route optimisation
Routes
12
Avg. fill
84%
Distance
612 km
Solve time
4.2s
3 · Fleet load
What Dispatch replaces on day one
The practical difference between running this process on paper and spreadsheets, and running it on DigiTS.
Orders re-keyed by hand from emails and spreadsheets
Pulled automatically from any API, or imported directly
Routes planned from memory on a whiteboard
Hundreds of stops optimised across the fleet in seconds
Vehicle space estimated by eye
Dimensional load fit calculated per vehicle
Permit zones and delivery windows missed
Both applied as constraints before the plan is built
No record of who changed what
Full login, user and order-processing audit trail
Everything in Dynamic Dispatch
19 capabilities across 4 areas — configured to your operation rather than switched on wholesale.
01
Multi-source order intake
Orders arrive from ERPs, marketplaces, customer portals and spreadsheets. Dispatch takes them all without anyone re-typing a line.
Pull from any API
Configure an endpoint, method and headers, then let orders flow in automatically.
Flexible authentication
Bearer token, API key, basic auth or open endpoints, configured per source.
Field mapping to the order schema
Fetch a live sample, map the response fields once, and every later call follows that mapping.
Direct import
Bring orders in by file where a source has no API to connect to.
External database sync
Scheduled SQL Server synchronisation for systems that expose data rather than endpoints.
02
AI-assisted route planning
The planner solves for the constraints a dispatcher normally holds in their head — and does it across the whole fleet at once.
Hundreds of stops in seconds
Optimise a full day across every available vehicle rather than route by route.
Dimensional capacity fitting
Unit-of-measure configuration with length, width and height, so load fit is calculated rather than estimated.
Delivery slot constraints
Respect booked windows at malls, hotels and institutional customers.
Permit area awareness
Account for restricted and permit-controlled zones when sequencing a route.
Plan by dispatch date
Build, review and compare plans for a chosen date before committing them.
Simulation before commit
Model a plan and review the outcome before it ever reaches a driver.
03
Live dispatch & fleet operations
The gap between a good plan and a dispatched fleet should be one click, not an afternoon.
One-click dispatch
Turn an approved plan into live routes for every vehicle at once.
Vehicle load history
See what each vehicle carried, on which route, on any given day.
Route history
A full record of planned versus dispatched routes for review and dispute resolution.
Fleet master data
Vehicles, capacities and packaging configurations maintained centrally.
04
Unified master data & governance
Dispatch reads the same customers and items as the rest of the platform, and records who did what.
Shared customers, items and packaging
One master set kept in sync, not a separate dispatch-only copy.
Single sign-on with SFA
Dispatchers sign in with the DigiTS SFA credentials they already have.
Login and user audit trail
Every sign-in and user action recorded for security review.
Order-processing counters
Volume counters supporting licence compliance and usage reporting.
What operations teams notice first
Planning measured in seconds
A dispatcher's whole morning of route building collapses into one optimisation run.
Fuller vehicles
Dimensional fitting uses the space that eyeballing a load leaves empty.
Fewer missed windows
Delivery slots and permit zones are constraints in the plan, not surprises on the road.
Defensible decisions
A complete audit trail means every plan and change can be explained afterwards.
Dispatch works with the rest of the platform
Same customers, same SKUs, same pricing — so adding a module is configuration, not a second integration project.
Dynamic Dispatch — common questions
How do orders get into Dynamic Dispatch?
Three ways: pulled automatically from any API you configure with its own endpoint, method and authentication; synchronised from an external SQL Server database on a schedule; or imported directly as a file. Response fields are mapped to the dispatch order schema once, and every subsequent call follows that mapping — so nothing is re-keyed.
What does the route planner optimise for?
Vehicle space using dimensional unit-of-measure data, booked delivery slots, and permit-controlled areas — solved across the whole available fleet at once rather than one route at a time. Plans are built for a chosen dispatch date and can be simulated and reviewed before they are committed.
How is this different from Last Mile Delivery?
Dispatch is the planning layer; Last Mile Delivery is the execution layer. Dispatch decides which orders go on which vehicle in what sequence. LMD runs the drop itself — driver tracking, electronic proof of delivery, returns and cash settlement. They are designed to work together and many customers run both.
Does it use our existing DigiTS logins?
Yes. Dispatch supports single sign-on with DigiTS SFA, so dispatchers use the credentials they already have, and every sign-in is captured in the audit trail.
Can we see what was planned versus what was actually dispatched?
Yes. Vehicle load history and route history are retained alongside a full login and user audit trail and order-processing counters, so any plan or change can be reconstructed later.
See Dispatch running your operation
A 30-minute walkthrough using your product hierarchy, your pricing rules and one of your real routes — not a generic demo dataset.
Or email sales@digitsrtm.com