Order Management for Last-mile delivery companies
Retain the merchant’s accepted delivery-service request and unresolved parcel, attempt or return outcomes.
Does this function belong in your operation?
Use when the operator coordinates delivery of parcels entrusted under accepted merchant instructions and needs to distinguish request, custody and final outcome.
The delivery operator accepts a merchant request within its actual service agreement.
The merchant’s delivery request is a service commitment for identified parcels entrusted for delivery. Record the actual instructions, recipient details needed for the work and any contracted collection amount. Physical intake, rider assignment, attempt outcome and return acknowledgement are separate milestones. A requested reattempt or address change needs the agreed merchant authority and retained history. Closing the delivery order should expose unresolved custody, disputed evidence or merchant money instead of assuming that every assigned parcel was delivered.
Bring the records the workflow depends on.
- Merchant service agreement and individual parcel references
- Recipient details necessary for the accepted delivery
- Actual intake and instruction-change authority
- Collection instruction only where expressly contracted
Outputs to check
- Merchant delivery-service order and revision record
- Parcel intake, attempt and return references
- Unresolved custody and commercial follow-up
Follow the order management workflow.
Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.
Who uses the module, and who approves?
Keep responsibilities distinct even when one person holds more than one role.
Decide how exceptions are handled.
These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.
Can this work independently?
The merchant supplies authorised instructions and the operator confirms actual service capability. Tasks and evidence records establish work outcomes. Goods custody, customer collections and service billing need distinct references; a delivery order does not decide merchant refunds or recipient entitlement.
Systems and records it connects with
- Task management: Actual pickup, attempt and return assignments.
- Service reports: Reviewed outcome and permitted handover evidence.
- Collection and invoice records: Separate merchant money and service charges.
Configure, test and introduce the workflow.
- Compare actual prepaid work and a contracted collection request.
- Agree parcel identifiers, change authority and evidence needed for intake and return.
- Test a missing piece, failed attempt and requested return without closing unresolved custody.
Check the result before rollout.
Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.
- Order creation does not establish physical parcel receipt.
- Failed attempts and later actions retain separate history.
- A return instruction does not mark goods received by the merchant.
- Goods entrusted for delivery do not become operator stock or merchandise sales revenue.
How the business operates.
A last-mile delivery company takes custody of a merchant’s parcels at a hub or pickup point and coordinates their delivery attempts and authorised returns. The goods are entrusted for delivery under the accepted merchant instructions and remain outside operator-owned stock; the delivery operator manages the service and custody records. This proposed software scope connects merchant instructions, actual parcels, rider assignments, attempt evidence and commercial reconciliation. Where cash on delivery is contracted, money collected for the merchant must remain separate from the operator’s delivery-service revenue. A completed rider task can represent a failed attempt, so delivery, return and cash outcomes need their own evidence.
The records that hold the operation together.
- Merchant order and accepted delivery-service reference
- Parcel identifier, expected and actual piece counts and custody acknowledgements
- Recipient instructions and authorised changes with access restrictions
- Rider assignment, attempt outcome and supporting evidence
Operational bottlenecks to check
Assignment changes but parcels stay with the first rider
A reassigned task is not a custody transfer. Both workers’ acknowledgements and unresolved parcels need to remain visible.
A closed attempt appears as a delivery
Failure, refusal and incomplete evidence need explicit outcomes. A closed work item must not inflate the delivered-parcel count.
How work flows across this business
This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.
1. Accept the merchant request
Confirm the actual delivery service, parcel references and collection instruction if contracted. Keep specialised goods or handling outside acceptance until separately reviewed.
2. Receive and allocate custody
Match physical parcels to the request and record exceptions. Assign the work and acknowledge the actual handover to the rider.
3. Record each attempt
Capture the attempt outcome and required evidence without turning an address visit into delivery. Refer refused, inaccessible or disputed handovers for the agreed decision.
4. Resolve undelivered parcels
Retain prior attempts while recording an authorised reattempt or return. Confirm physical custody and merchant receipt rather than closing a return from its instruction alone.
5. Reconcile money and fees
Review any customer collection, rider-to-office handover and actual merchant remittance. Separately bill the accepted delivery services and approved additional work.
Industry reports to connect with
- Parcels by merchant, custodian and unresolved mismatch
- Unassigned work and attempts awaiting review or instructions
- Delivered, failed, reattempted and physically returned parcels
- Collection differences by rider, payment evidence and merchant
Questions before implementation.
When should last-mile delivery companies consider order management?
Use when the operator coordinates delivery of parcels entrusted under accepted merchant instructions and needs to distinguish request, custody and final outcome. The delivery operator accepts a merchant request within its actual service agreement.
What should we bring to the requirements discussion?
Bring anonymised examples of Merchant service agreement and individual parcel references; Recipient details necessary for the accepted delivery; Actual intake and instruction-change authority; Collection instruction only where expressly contracted. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.
Does this replace our existing business software?
The starting point is your current system and the gap you need to close. Retain the merchant’s accepted delivery-service request and unresolved parcel, attempt or return outcomes. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.
What is outside this module?
This module does not authorise restricted goods, certify parcel contents or establish delivery, payment or refund from a planned status.
How are scope, price and rollout decided?
The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Order creation does not establish physical parcel receipt. Use this check when reviewing the first working version.
Related functions for last-mile delivery companies.
Discuss order management for your business.
Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.
What happens after you share your requirements
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- Review the scope and commercial terms before deciding whether to proceed.
Start with your requirements
Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.
Share your requirements