No signal at the stop?
The driver app keeps pending updates and proof on the device for retry. A saved update is shown as pending until it syncs.
Driver delivery workflowCourier operations software
RouteHut Courier TMS
Run the delivery operation from one shipment record.
Give dispatchers, drivers, hub teams, customer service and finance the same operational history from booking through delivery proof and billing.
Built for operators. RouteHut supplies the transport management software; your business runs the courier network.
Early accessReview current scope and roadmap
The operational workspace
See the work that needs attention.
RouteHut keeps booking, dispatch, custody, delivery evidence and financial follow-through connected to the shipment that created the work.
Staff operations
Example CouriersAdministratorReady
Shipments
18,742 drafts and jobs
- Active
- 4,286
- Due today
- 1,034
- Past due
- 28
- Exceptions
- 17
- Delivered
- 13,908
- Unassigned
- 92
| Shipment | Customer | Status | Delivery | Actions |
|---|---|---|---|---|
| EXAMPLE-1042critical | Sample Retail | Booked | Rosebank Store | Manage |
| EXAMPLE-1043 | Sample Pharmacy | Booked | Sea Point | Assign |
| EXAMPLE-1044high | Sample Grocers | Delivery failed | Stellenbosch | Review |
| EXAMPLE-1045 | Sample Parts | Collected | Centurion | Manage |
The shipment journey
Follow the shipment across every handoff.
Use one history for a direct local round or a network delivery moving through hubs and linehaul.
- 01BookCustomer, parcels, addresses and service
- 02PlanAssign, sequence and release the route
- 03CollectRecord pickup and custody
- 04MoveUse a local route or transfer through hubs
- 05DeliverCapture proof or a failed attempt
- 06ReconcileNotify, charge and report
Direct local jobNo hub transfer required
Network deliveryHub and linehaul movement
When the day changes
The unsuccessful stop matters too.
A completed-deliveries count is not enough. Drivers and operations need the evidence and the next action.
Recipient unavailable?
Record the failed attempt, then manage the return or redelivery without erasing the first attempt.
Return and redeliveryA customer needs an answer?
Review the shipment history and authorised proof rather than asking the driver to reconstruct the delivery.
Trace a shipmentProduct fit
Parcel operations first.
Manage daily collections and deliveries, with pallet distribution on the roadmap.
In the current product
Multi-stop parcel collections and deliveries, driver routes, hub scanning, manifests, public tracking, POD and billing.
Dedicated customer runs can use booked shipments and assigned routes. Your rates, service areas and operational policies still need setup.
Inspect the current dispatch flowOn the roadmap
Planned: pallet-specific handling units, pallet-space capacity and partial-quantity reconciliation, plus automatic recurring shipment generation.
You can already create parcel shipments in bulk. Multi-pallet load management is a separate, planned capability.
Explore planned pallet workflowsEarly access
Start with your operation.
Explore how RouteHut fits your delivery process, then plan a pilot around your team, service rules and integrations.
- Follow your own shipment scenario.Booking, collection, hub handoff if needed, delivery proof and billing.
- Try the exception path.Missed delivery, offline recovery, a repeated update and proof retrieval.
- Agree what must be ready for a pilot.Data import, devices, integrations, operating rules, support and acceptance checks.
Review the operating modelInspect detailed scopeReview API contracts
Before you decide
Questions about fit and rollout.
Is this a service for sending parcels?
No. RouteHut supplies the software. Your business provides the delivery service, customer relationships and operating network.
Can drivers work without a connection?
The driver app stores route information and pending actions on the device. Updates and proof need a connection to sync; operations should not treat pending work as server-confirmed. Device permissions and recovery behaviour should be tested before a pilot.
Can it connect to our existing systems?
The external REST API covers quotes, shipments, tracking, POD, customer data and invoice reads. Signed webhooks report changes. Your integration team can use the API reference to plan the connection.
Does it optimise routes and handle hubs?
RouteHut supports route planning and sequencing with readiness checks, as well as hub scans, custody and transfer manifests. Validate your capacity and service rules in the current workflow. Advanced optimisation, linehaul scheduling and scanner integration have limits described in the workflow reference.
What would moving from our current system involve?
Review customer and address data, pricing, service areas, driver devices, hub processes and integrations. Start with a pilot and reconcile the results before moving live work.
What does it cost, and what support is included?
Pricing and production support terms are not published yet. These need to be agreed alongside the proposed scope and rollout; there is no self-service purchase or production SLA offered on this site.
Evaluate RouteHut
Start with one real delivery scenario.
Use your booking, dispatch and delivery process to identify where RouteHut fits and where work remains. Include an exception, not only a successful delivery.
For a useful discussion: your operating model, current system and the problem you need to solve.
Find the workflow that matters to your team.
Explore booking, dispatch, delivery and reconciliation, with the exception paths and next steps for each team.
Explore operational workflows