During a busy service, a phone-only pickup process competes with in-store guests and kitchen work. A digital pickup path can make demand visible, but it must fit the restaurant's menu, capacity, payment, preparation, and handoff operation.
Map the missed-call problem
- Calls received, answered, abandoned, and converted
- Order-entry time and correction rate
- Peak periods and staffing
- Items and modifiers that are hard to capture by phone
- Customer support and refund contacts
Define the digital pickup flow
A customer chooses a location, orders from the current menu, selects ASAP or a supported future time, pays through the configured method, receives confirmation, and gets a clear ready-for-pickup message. Staff need the same order, timing, and status in their operating queue.
Plan for franchises and multiple locations
Define menu and pricing authority, store hours, capacity, taxes, payment accounts, brand rules, reporting, and local overrides. Confirm what is centralized and what each location operates.
Plan for marketplaces
Vendor onboarding, location mapping, catalog quality, payment responsibilities, status consistency, support, and settlement need explicit owners. Growth should be tested against support and operational capacity rather than an unlimited-scale promise.
Measure the change
- Completed pickup orders
- Abandoned calls and checkouts
- Order accuracy and refunds
- Preparation and wait time
- Staff workload
- Repeat use and customer feedback
Roll out with a baseline
Measure the current phone process first, pilot with selected locations, compare the same periods, and document external factors. Publish observed results only with a defined period, sample, source, and permission.
Indoor pickup versus curbside: different handoff work
For indoor pickup, the guest enters the restaurant and collects at the named counter or shelf. For curbside, the guest remains at an agreed spot and a staff member takes the order out. Both need the correct store, order reference and ready state; curbside also needs the location or vehicle detail and an owner available to leave the counter.
Ordering.co order types include pickup and curbside, configured for the project and store. Checkout can collect the applicable spot or vehicle detail and the Business App shows the order's fulfillment context. A pickup code and a curbside code are not interchangeable: QR settings allow a code for a specific curbside spot, while ordinary pickup does not require a spot number.
Arrival signal, ready state and POS responsibility
Keep three events separate: food ready, customer arrived and order handed over. Ordering.co has approaching/arrived order statuses and configurable push triggers; the Business App follows the applicable pickup states. Confirm who changes the arrival state, who receives the alert and which device actually receives it. A saved trigger, a customer address or a QR scan alone does not prove a staff member was notified or food was handed over. Push delivery depends on the configured connection, recipients and devices.
| Step | Indoor pickup | Curbside |
|---|---|---|
| Customer instructions | Store, counter/shelf and order reference | Store, allowed spot, identifying detail and arrival route |
| Staff action | Check identity/reference and hand over at pickup point | Acknowledge arrival, locate the correct spot and carry out the order |
| Completion | Record collection after the actual handoff | Record collection after delivery to the identified guest |
| Exception | Wrong store, missing bag or uncollected order | Changed spot, no arrival signal or no staff available |
A POS integration may receive the order, but it needs explicit mappings for modifiers, payment and the statuses it supports. Do not assume it receives vehicle/spot details or can set every arrival/handoff event. Decide whether staff operate that step in the Business App or a demonstrated POS workflow, and name the support owner when the two disagree. Use available order types documentation and your specific POS connection to scope the path.
Illustrative acceptance task: order for curbside at the selected store and spot, confirm the same details in merchant tools, signal arrival through the proposed route, verify receipt on the staff device and complete the physical handoff. Repeat with indoor pickup, a wrong spot and a missed alert. Keep a visible staffed fallback; do not infer automatic vehicle sensing, location detection or lane hardware from an arrival-status feature.
Measure ready-to-arrival and arrival-to-handoff time separately, plus wrong-location incidents, missed alerts, no-shows and manual corrections. Compare the same stores/service periods before expanding. Review the pickup flow in a demo with the POS and staff roles you will actually use.