Operations control
Quote, book, price, assign and recover exceptions from a shared staff workspace.
Review staff workflowsCourier operations software
RouteHut Courier TMS
Run parcel operations from booking to proof and billing.
In developmentExplore the current product scope
Keep staff, drivers, hubs and finance working from the same shipment history.
Built for delivery teams. Courier companies and businesses running their own fleets can use RouteHut to manage the work.
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
1,284 drafts and jobs
- Active
- 286
- Due today
- 104
- Past due
- 8
- Exceptions
- 7
- Delivered
- 914
- Unassigned
- 12
Shipment queue286 active
EXAMPLE-1042Sample Retail · Rosebank
BookedSipho Dlamini
EXAMPLE-1044Sample Grocers · Stellenbosch
Delivery failedReview next action
EXAMPLE-1045Sample Parts · Centurion
CollectedThabo Mokoena
| Shipment | Customer | Status | Collection | Delivery | Driver | Actions |
|---|---|---|---|---|---|---|
| EXAMPLE-1042critical | Sample Retail | Booked | Urban Warehouse | Rosebank Store | Sipho Dlamini | Manage |
| EXAMPLE-1043 | Sample Pharmacy | Booked | Acme DC | Sea Point | Unassigned | Assign |
| EXAMPLE-1044high | Sample Grocers | Delivery failed | FreshCart DC | Stellenbosch | Lerato Nkosi | Review |
| EXAMPLE-1045 | Sample Parts | Collected | Parts Depot | Centurion | Thabo Mokoena | Manage |
Driver application
The next stop stays in focus.
Drivers see the work they can act on now: where to go, what to collect or deliver, the instructions for the stop and the proof still needed.
Sipho DlaminiDriver
Today’s workMonday, 28 Sept
Synced 05:47 PMRoute changes and proofs sync automatically.
LocationOff
- Remaining
- 16
- Completed
- 4
- Total stops
- 20
Up nextUrban Outfitters6 Dock Road, Cape Town · Collection
- Know the work at every stop.Each stop is marked collection or delivery, whether dispatch separates the work into dedicated routes or combines it in sequence.
- Separate collections from deliveries.Every stop shows the job type, sequence, expected work and proof required.
- Recover without losing the record.Pending updates and delivery proof remain on the device until they can sync safely.
Across the operation
One system for the work around every parcel.
Give each team the view and actions it needs without breaking the shipment history between them.
Driver execution
Work assigned stops, record failed attempts and capture proof even through a network drop.
Review driver workflowsHub custody
Scan parcels in and out, build transfer manifests and investigate discrepancies.
Review hub workflowsCustomer and finance
Share tracking updates, retrieve proof and carry completed work into invoicing.
Review billing workflowsCourier network control
Direct routes and parcel hub transfers.
Keep collection, custody scans, transfer manifests and final delivery connected to the same parcel history.
- Direct route
- Collection and final delivery remain on a local route.
- Parcel transfer
- Hub receipt, manifest transfer and release preserve custody.
Built to connect
Documented interfaces. Explicit boundaries.
- OpenAPI 3.1
- Versioned external REST contracts
- Signed webhooks
- Retryable, auditable event delivery
- Published posture
- Implemented, aligned and planned standards
Evaluation
Questions to answer before you evaluate RouteHut.
Is RouteHut a courier service?
No. RouteHut is software for courier companies and businesses running their own delivery fleets. It helps them book, dispatch, track, deliver and bill shipments. The business operating the vehicles remains the delivery provider.
Do drivers need a constant internet connection?
No. Once an assigned route has synced to the phone, drivers can record arrivals, failed stops, completed deliveries and proof while offline. RouteHut keeps those updates on the device, retries them during normal sync and flags anything that needs attention. A connection is required to sign in, receive new or changed assignments and confirm that the central record is up to date.
Can RouteHut integrate with our existing systems?
Yes. The external REST API covers customers, addresses, quotes, shipments, tracking, proof of delivery and invoice reads. Signed webhooks report selected changes. Integration requires a RouteHut environment, scoped credentials and work by your integration team or implementation partner. Review the current contracts in the API reference.
How does route planning work?
Dispatchers can build routes manually or preview an allocation of eligible work across active drivers, then sequence geocoded stops using road travel times. RouteHut checks availability, required skills, collection-before-delivery order, service windows and weight capacity before release. Live traffic re-optimisation, multi-dimensional capacity and embedded turn-by-turn navigation are not yet included. See the dispatch workflow.
Does RouteHut support hubs and inter-hub transfers?
Yes, at parcel and manifest level. Staff can record hub custody, assign bays, build and close manifests, scan parcels out and in, and review discrepancies. RouteHut does not yet manage scheduled linehaul trips, vehicles, carriers, seals, whole-load closeout or dedicated scanner hardware. See the hub workflow.
What does RouteHut cost, and what support is included?
The plan is to publish RouteHut plans and pricing, but the packaging, prices and included support have not been decided yet. Before production use, RouteHut and the operator would need to agree the commercial scope, implementation responsibilities, support coverage, data handling, service commitments and rollout plan. There is no self-service purchase today.
Product development
See whether RouteHut fits your operation.
RouteHut is under active development. We are looking to work with courier operators who want to examine the product against real workflows before launch.
- Use your shipment scenario.Follow it from booking to billing.
- Include a failure.Check recovery, evidence and ownership.
- Map what adoption would require.Identify the data, devices, integrations and acceptance checks involved.
Explore what works today.
The workflow reference distinguishes current, configurable and planned capability.
Review current product scope