Delivery App and In-Store Orders Together
5 min read ·
When dine-in, telephone, and delivery-app orders arrive together, the challenge is coordinating work, not simply reducing screens. The kitchen needs clear instructions, and supervisors need to know each order’s source and status. A shared operational flow can help, but it must be built around verified behavior rather than assuming a connection settings page proves an integration is live.
Map each channel before changing the workflow
Write down how each order arrives, who reviews it, when preparation starts, and who handles collection. Mark every manual entry step because these are common points for omitted modifiers and duplicate orders. Assign responsibility for checking the original channel whenever its information differs from what the restaurant team sees.
Keep the external order reference alongside the internal reference during operations. A customer name is not a reliable way to distinguish similar orders, and a spoken instruction should not be the only record of a change. Mapping the process makes it easier to judge whether a proposed connection removes work or merely moves it somewhere less visible.
Separate connection controls from live availability
ORO has aggregator connection settings covering a webhook address, signing secret, and active status. It also has a code path for receiving a suitable order and passing it into POS order ingestion. Availability depends on your plan and setup. These technical capabilities do not establish an official or live delivery-app integration for your restaurant.
Before relying on a connection, verify account availability, the other party’s requirements, and the expected data format. Request an end-to-end test rather than treating successfully saved settings as proof. Do not assume order receipt includes menu publishing, price synchronization, cancellations, or delivery-status updates. Each direction of communication needs its own evidence and operational acceptance.
Test the details the team actually receives
ORO’s ingestion path handles order items, delivery fees, and discounts, with customer-name and note fields when supplied, before calling an order-ingestion procedure. The existence of these fields does not mean every source sends them consistently. Review the order information reaching the team, not just the appearance of an incoming-event notification.
Test modifiers, preparation notes, discounts, delivery fees, and a repeated submission of the same order. Check quantities, prices, references, and whether staff can identify the source. Record anything that fails and establish the fallback. Do not increase operational dependence on the flow until the team knows how errors are detected and who is responsible for resolving them.
Plan exceptions and end-of-shift reconciliation
Define what staff should do when an order appears in the delivery app but not in the restaurant workflow. Before entering it manually, check whether it already arrived under another reference. Give amendments and cancellations their own procedure: removing a kitchen ticket does not necessarily cancel the customer’s order in the channel where it originated.
At shift end, reconcile references and statuses, then review financial differences against channel statements and contract terms. Gross order value is not necessarily the amount transferred after charges and adjustments. Use discrepancies to improve the process. Keep a documented fallback so a connection problem or an absent supervisor does not leave staff inventing their own rules.
Frequently asked questions
Does saving a connection make an app live?
No. Both sides must be configured appropriately, and orders must be tested for the restaurant’s actual account.
Does receiving orders include menu and cancellation sync?
Not automatically. Order intake, menus, pricing, and cancellation handling are separate capabilities that require separate verification.
What if a channel order is missing internally?
Check its reference and look for an existing copy before using the documented manual fallback and recording the incident.