These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Courier & Parcel Management
- Who it's for
- Local parcel networks
Local parcel networks
Local parcel networks move work from collection through a sorting handoff to delivery. Dispatcher needs to know which load owns a parcel event and whether that event has been accepted. Transport Supervisor needs the evidence behind disputed milestones and a clear view of service that remains exceptional at the end of a shift.
How Courier & Parcel Management is set up for you
Pickup commitments
Prepare load stops and promised delivery before dispatch. Confirm actual pickup before the operating status moves forward, keeping the original promise available for the later performance review.
Sorting handoffs
Record Sortation events with the tracking number, physical scan time and supported package weight. Preserve provider event identity so a repeated notification does not become another accepted milestone.
Recipient evidence
Close a delivered load from actual time and the relevant proof reference. Keep partial or refused service explicit even when a parcel in the load already has a Delivered scan.
Local parcel networks move work from collection through a sorting handoff to delivery. Dispatcher needs to know which load owns a parcel event and whether that event has been accepted. Transport Supervisor needs the evidence behind disputed milestones and a clear view of service that remains exceptional at the end of a shift.
Begin with a familiar collection area and a bounded dispatch shift. App Administrator prepares the operating organization and partner records. Admin records the stop plan and eligible assignments, while Dispatcher prepares loads with clear ownership. Check the time zone before importing promises and scan times from another system.
Rehearse a parcel moving through Pickup and Sortation. Repeat the provider's Sortation notification and confirm that its event identity leads back to the existing result. Then send a valid later milestone for the same tracking number and confirm that it remains a distinct physical event rather than being dismissed as a duplicate parcel.
Finish with a delivery whose recipient proof arrives after the partner's status message. Preserve the physical scan while the team obtains the evidence needed to complete the load. Use [Accept a parcel scan](/courier-parcel-management/processes/accept-a-parcel-scan) and [Complete an evidenced delivery](/courier-parcel-management/processes/complete-an-evidenced-delivery) for the rehearsal before expanding to further collection areas.
Features to start with
Load planning
Build a feasible courier load around its partner, promised delivery and ordered stop windows.
Delivery evidence
Close a load from recipient proof and actual delivery, then compare the result with its original promise.
Exceptions and reconciliation
Investigate uncertain actions and preserve the evidence behind every correction or accepted completion.
Roles on the team
- Dispatcher
- Prepare assigned operational records and execute eligible reviewed actions.
- Transport Supervisor
- Review eligible revisions independently and reconcile operational evidence.
- Admin
- Maintain stop plans, assignment windows and vehicle defect evidence for authorized courier operations.
Set up Courier & Parcel Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.