Accept & Decline Workflow¶
This guide explains what happens from the Source Depot Officer's perspective when a transporter responds to a shipment assignment — either accepting or declining.
Prerequisites¶
- You have assigned a transporter to the shipment
- The shipment
handover_statusis currently awaiting - The transporter has received their assignment notification
Steps¶
Step 1: Monitor the shipment status¶
After assigning a transporter, the shipment's handover status shows as Awaiting. You can view this on the Shipment Detail screen. The transporter will respond by either accepting or declining the assignment.
Scenario A: Transporter Accepts¶
Step 2a: Transporter accepts the shipment¶
When the transporter accepts the assignment:
- The shipment
handover_statuschanges from awaiting to accepted - The shipment status changes to dispatched
- All orders in the shipment automatically transition to in_transit
- You receive a confirmation that the shipment has been dispatched
Step 3a: Verify order statuses¶
Navigate to the orders within the shipment to confirm they now show In Transit status. No further action is required from you — the transporter is now responsible for the shipment.
Scenario B: Transporter Declines¶
Step 2b: Transporter declines the shipment¶
When the transporter declines the assignment:
- The shipment
handover_statuschanges from awaiting to declined - The transporter's decline reason is displayed on the shipment
- Orders remain at at_courier_depot status — they are not dispatched
- You receive a notification that the transporter declined
Step 3b: Review the decline reason¶
The decline reason provided by the transporter is shown on the Shipment Detail screen. Common reasons include vehicle issues, scheduling conflicts, or route unavailability. Review the reason to decide your next action.
Step 4b: Reassign the shipment¶
After a decline, you can reassign the shipment to a transporter:
- Tap the Assign Transporter button on the shipment
- Select the same transporter (if the issue has been resolved) or choose a different transporter
- The
handover_statusresets to awaiting and a new notification is sent to the selected transporter
Tip
If a transporter repeatedly declines, consider assigning a different transporter to avoid further delays.
Result¶
| Scenario | Handover Status | Shipment Status | Order Status | Next Action |
|---|---|---|---|---|
| Transporter accepts | accepted |
dispatched |
in_transit |
None — transporter handles delivery |
| Transporter declines | declined |
pending |
at_courier_depot |
Reassign same or different transporter |
Notifications triggered¶
- On accept: Shipment marked as dispatched; orders move to in_transit
- On decline: Source Depot Officer notified of decline with reason; shipment available for reassignment
Troubleshooting¶
| Issue | Cause | Solution |
|---|---|---|
| Shipment stuck on "Awaiting" | Transporter has not responded yet | Wait for the transporter to respond, or contact them directly |
| Cannot reassign after decline | App may not have refreshed | Pull to refresh the shipment list, then try again |
| Same transporter declines again | Underlying issue not resolved | Assign a different transporter |
| Orders not moving to in_transit | Transporter accepted but status not updated | Pull to refresh; if issue persists, contact support |
Related Guides¶
- Assigning Transporter — Initial transporter assignment process
- Accepting Shipment (Transporter) — The transporter's perspective on accepting
- Declining Shipment (Transporter) — The transporter's perspective on declining