Courier software: dispatch, delivery tracking and proof of delivery — buying checklist
From: https://www.iwantmywebsitenow.com/industry/transport/courier/
Workflow sources checked: 2026-10-02. Prices have separate capture dates.

Use this with a vendor or a builder. These are proposed evaluation tests, not claims that any product passed them.

YOUR BUSINESS
Current software:
What must work differently:
Records to bring across:
Budget and timing:

QUESTIONS TO TEST
1. A route that respects the order
Ask: Are service level, capacity and promised delivery window represented before dispatch?
Demonstrate: Create a multi-stop route with vehicle capacity limits and two delivery windows. Check which orders cannot fit and why.
Observed result:
Follow-up:

2. A controlled route change
Ask: What happens when a pickup is late or a driver cannot reach a stop?
Demonstrate: Reassign one delivery after dispatch. Confirm driver instructions, customer ETA and the dispatcher event history update.
Observed result:
Follow-up:

3. Evidence for each stop
Ask: Can the business require the right completion evidence for a particular customer or shipment?
Demonstrate: Complete one stop with a signature and another with a photo/barcode. Attempt a failed delivery and confirm it is not marked complete.
Observed result:
Follow-up:

4. Billing and export
Ask: Do completed, failed and returned shipments map back to orders and account charges?
Demonstrate: Export a route containing delivery, refusal and redelivery. Reconcile stop IDs, proof, timestamps and charges with the invoice.
Observed result:
Follow-up:

DEMO SCENARIO (SYNTHETIC)
Bring a six-stop route with one failed delivery
1. Create six stops with different time windows, parcel counts and vehicle capacity requirements.
2. Dispatch the route, then delay one pickup and reassign a later stop. Check driver instructions and customer ETAs.
3. Record a signature at one delivery and a photo at another. Mark one recipient unavailable and schedule a return or reattempt.
4. Export the route and reconcile each order, status, proof record and billable attempt.

MIGRATION
Move the order-to-stop relationship and delivery evidence
Request sample exports of accounts, orders, stops, service levels, promised windows, driver assignments, route events, proof photos/signatures, failed-attempt reasons, returns and invoices. Preserve the order ID on every stop and delivery event. Check how photos and signatures download, who can access them and how long they are retained. Reconcile open shipments and customer-specific billing rules before cutover.

A POSSIBLE FIRST BUILD
A custom order form or customer tracking view can sit around a proven dispatch platform if the API and account plan support the handoff. Route optimization, live-driver location, delivery proof and courier settlement are separate capabilities that need an operational pilot.

SOURCES
Onfleet: parcel delivery management
https://onfleet.com/parcel
Describes dispatch, routing, tracking, delivery notifications and photo/signature proof of delivery.

Onfleet: dispatch and assignment
https://stream.onfleet.com/assignment-and-dispatching
Documents reassignments and route changes, automated assignments and exception handling.

eLogii: courier and parcel routing
https://elogii.com/industries/courier-parcel/
Describes courier route planning, delivery windows, returns, proof of delivery and API/webhook integrations.

CXT Software: pricing and product information
https://www.cxtsoftware.com/pricing
Vendor page for a demo and quote; validate the features and service model against your operation.

Research by Don, I Want My Website Now.
A product description is not hands-on testing. Verify the plan, current price and export access before committing.