1. Operational Mission & Pre-Flight Verification Gate
The mission of this standard operating procedure is to eliminate cold food deliveries, eradicate missing sides or sauces through standardized packaging checklists, ensure rapid customer handover at the counter, and guarantee 100 percent financial accountability for Cash on Delivery fleet collections. By interfacing with the kitchen display systems and cashier counter billing, the dispatch hub coordinates seamlessly between cooks, packaging staff, and mobile couriers.
Operator Security Tier & Role Permissions
- Assigned Persona: Dispatch Expeditor, Takeaway Lead, Delivery Coordinator
- Required Security Tier: Tier 2 Station Lead
- Supervisory Override Required For: Cancelling out-for-delivery orders, Re-assigning an in-transit rider, Manually voiding unpaid COD balances
Takeaway & Dispatch Pre-Flight Verification Checklist
2. Environmental Pre-Conditions & Station Readiness Matrix
Prior to accepting rush-hour parcels and dispatching delivery fleets, the expeditor must audit station nodes:
| Subsystem / Node | Required Environmental State | Verification Method | Contingency Remediation Action |
|---|---|---|---|
| Dispatch Screen Runtime | Two-panel Kanban active: Takeaway Queue (Left) / Delivery Fleet (Right) | Green heartbeat pill in top bar; active count badges match pending tickets | Trigger soft reload via Refresh Queue button; inspect network gateway socket |
| Acoustic Token Chime | Audio output unmuted; sound buffer pre-loaded | Click test bell button; harmonic chime rings across counter area | Check auxiliary audio cable; verify browser audio permissions are granted |
| Rider Handheld Gateway | Cellular / SMS dispatch channel active for customer address deep-links | Send diagnostic route ping to test courier device | Switch to direct phone dialer fallback via Call Rider link |
| COD Collection Cache | Pending rider cash ledger synchronized with active till shift | Pending COD total renders accurate outstanding figure | Verify active shift is opened on counter register before collecting cash |
3. Granular Procedural Execution Workflow
The parcel dispatch lifecycle operates across four sequential phases:
Phase 1: Order Ingress & Packaging Checklist Verification
- Trigger Condition: Kitchen expeditor bumps complete takeaway or delivery ticket from kitchen line.
- Operator Action: Takeaway packager collects hot items from passthrough counter. Verify physical packaging checklist:
- Main containers sealed with tamper-evident tape.
- Cold items (salads, raita, drinks) bagged separately from hot entrees to prevent thermal degradation.
- Cutlery, paper napkins, and matching sauces included.
- Adhesive ticket slip printed and affixed to exterior bag handle.
- Terminal System Response: Ticket appears in PACKING status on dispatch board with prep elapsed timer.
- Verification State: Package sealed; all items on digital checklist verified.
Phase 2: Token Calling & Ready-for-Pickup Status
- Trigger Condition: Packager completes bagging and places parcel on the numbered heated pickup rack.
- Operator Action: Click Mark Ready for Customer Pickup.
- Terminal System Response: Status transitions to READY_FOR_PICKUP. The central lobby screen highlights the order token, acoustic calling chime plays, and if configured, a notification SMS or digital receipt and fiscal QR link is dispatched to the customer's mobile phone.
- Verification State: Card border pulses emerald; token displayed on guest lobby board.
Phase 3: Fleet Rider Assignment & Route Handover
- Trigger Condition: Delivery parcel marked ready, and courier reports to dispatch counter.
- Operator Action: Open the courier assignment dropdown on the delivery card. Select the courier (e.g., "Muhammad Ali - Bike 4"). Verify route address with courier and hand insulated thermal carrier. Click Update Status -> OUT_FOR_DELIVERY.
- Terminal System Response: System logs courier timestamp, assigns financial COD liability to the courier's profile, and updates tracking status.
- Verification State: Courier departs; delivery card updates to OUT_FOR_DELIVERY with running transit timer.
Phase 4: Delivery Confirmation & Cash Collection Handover
- Trigger Condition: Customer arrives at counter to claim takeaway, or courier returns from delivery route.
- Operator Action:
- Takeaway: Customer presents physical token or phone; operator clicks Handed Over to Customer. Order transitions to COLLECTED and archives.
- Delivery COD: Courier returns to desk with collected cash. Settle COD via the dedicated handover protocol.
- Terminal System Response: Delivery marked DELIVERED; COD cash credited to active cashier register.
- Verification State: Zero pending delivery items remaining on active dispatch queue.
4. Interactive Operational Decision Logic & Routing Schematic
The following schematic outlines the operational branch points for off-premises fulfillment:
Takeaway & Fleet Dispatch Operational Flow
5. Deviation Handling & Exception Protocol Matrix
Operational exceptions in takeaway and delivery fulfillment must be handled according to the following protocols:
| Incident / Deviation Symptom | Operational Root Cause | Immediate Frontline Action | Escalation Authority | Ledger / Audit Impact |
|---|---|---|---|---|
| Unclaimed Takeaway Parcel (> 30 mins ready) | Customer delayed in traffic or abandoned pickup | Dial customer via Call Guest button; stage food under heated warming lamp | Tier 2 Takeaway Lead | If uncollected after 90 mins, check cancelled under food waste code |
| Delivery Courier Breakdown In Transit | Courier vehicle mechanical failure or puncture | Re-dispatch standby backup courier to breakdown coordinates; transfer bag | Tier 2 Dispatch Lead | Incident note appended to delivery tracking voucher |
| Incorrect / Incomplete Customer Address | Customer typo during online ordering or unclear house numbering | Contact customer direct via phone link; request GPS pin drop via WhatsApp | Tier 1 Dispatcher | Delivery timer paused; address revision saved |
| Customer Refuses Delivery at Doorstep | Excessive delivery delay or cold food complaint | Courier contacts dispatch desk; expeditor assesses food state | Tier 3 Duty Manager | Order flagged as DELIVERY_REFUSED; write-off to GL 5008 Comp Expense |
| Courier Cash on Delivery Shortage | Courier gave incorrect customer change or miscounted cash | Settle verified collected sum; log courier shortage in HR deduction journal | Tier 3 Duty Manager | Discrepancy logged against courier liability ledger |
6. Rider Cash on Delivery (COD) Reconciliation & Shift Deposit
Upon completing delivery routes, couriers return collected currency directly to the cashier counter:
- Access COD Handover Interface:
- Cashier clicks Rider COD Cash button on the counter top bar or parcel dispatch screen.
- System displays all active couriers with pending cash balances, delivery order counts, and itemized check numbers.
- Physical Currency Verification:
- Courier counts physical cash in the presence of the cashier.
- Cashier verifies bills under ultraviolet lamp and matches total against Pending Cash figure on screen.
- Trigger Cash Collection:
- Click Collect Cash (کیش وصول).
- Financial Impact:
- Automatically credits physical cash into the active shift till float (Debit 1001 Till Cash).
- Clears the courier's pending COD liability ledger (Credit 1050 Accounts Receivable - In-Transit Deliveries).
- Updates the active shift's expected drawer closing total.
- Receipt Generation:
- Thermal printer emits an official Courier Cash Clearance slip signed by both the courier and cashier.
For broader register shift closing and blind counting protocols, consult the Register Shifts & Blind Cash Drops SOP.
7. Operator Quick-Reference FAQs & High-Frequency Triage
How does the dispatch expeditor notify a takeaway customer that their food is ready if they are waiting outside in their car?
The system offers both lobby token display and 1-click WhatsApp / SMS notification.
- Clicking Mark Ready for Customer Pickup updates the public lobby display with the customer's token number.
- For curbside guests who provided mobile numbers, the expeditor clicks the phone link to send a pre-formatted WhatsApp readiness alert or trigger direct phone calling.
Can an expeditor re-assign an order to a different rider after it has already departed?
Only if the original rider returns the bag or coordinates with a replacement courier.
- The duty supervisor must open the delivery card, select Reassign Courier, select the replacement rider, and enter a mandatory operational reason note.
What happens if an order is cancelled while the kitchen is still packing the parcel?
The order is immediately dropped from the takeaway queue.
- If a cashier executes a supervisor-approved cancellation on the counter checkout desk, an event broadcast
order:updateddrops the parcel from the dispatch Kanban within 15 milliseconds, alerting the packager to halt bagging.
8. Technical Architecture & Structural Schema
The technical specifications of the parcel and dispatch SOP are documented below:
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "TechArticle",
"headline": "Orbit Dine Takeaway Queue & Rider Dispatch SOP: Parcel Tracking, Fleet Assignment & COD Reconciliation",
"description": "Standard operating procedure for takeaway packaging, customer token calling, courier fleet dispatch, and COD reconciliation.",
"proficiencyLevel": "Intermediate",
"articleSection": "Parcel & Dispatch",
"inLanguage": "en-US",
"publisher": {
"@type": "Organization",
"name": "FrontOrbit Core Engineering",
"url": "https://frontorbit.com"
}
},
{
"@type": "HowTo",
"name": "How to Process a Takeaway Order from Packaging to Customer Handover",
"description": "Procedural runbook for packaging staff to assemble, seal, alert, and hand over takeaway food parcels.",
"estimatedCost": {
"@type": "MonetaryAmount",
"currency": "PKR",
"value": "0"
},
"step": [
{
"@type": "HowToStep",
"name": "Packaging Checklist Audit",
"text": "Inspect all hot and cold items against the order ticket; seal bag with tamper-evident tape."
},
{
"@type": "HowToStep",
"name": "Ready Status Trigger",
"text": "Mark order Ready for Pickup to engage lobby calling chime and update customer display."
},
{
"@type": "HowToStep",
"name": "Customer Token Verification",
"text": "Match physical token slip presented by guest against order card."
},
{
"@type": "HowToStep",
"name": "Collection Handover",
"text": "Hand parcel to customer and mark order as Collected on the dispatch board."
}
]
},
{
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What deterministic state transitions govern a takeaway parcel order in Orbit Dine?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A takeaway order transitions through three rigid states: PACKING (kitchen is preparing and bagging items), READY_FOR_PICKUP (all items assembled, verified against packaging checklist, customer token alerted), and COLLECTED (customer presents token, receives bag, check archived)."
}
},
{
"@type": "Question",
"name": "How does the dispatch station assign orders to delivery fleet riders?",
"acceptedAnswer": {
"@type": "Answer",
"text": "The expeditor selects the delivery ticket on the dispatch board, opens the rider assignment dropdown, and selects an active on-duty employee. The system binds the courier identity to the delivery record and broadcasts route information."
}
},
{
"@type": "Question",
"name": "How is Cash on Delivery (COD) collected from riders reconciled back into the cashier's physical register till?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Upon returning, the rider reports to the counter. The cashier opens the Rider COD Reconciliation modal, reviews the list of delivered orders pending collection, and clicks Collect Cash. The system atomically credits the active shift till float."
}
}
]
}
]
}