DIRECT REVENUE · OPERATOR GUIDE
First-party online ordering
Let a restaurant accept orders on its own digital channel while controlling the menu, fulfillment rules and customer relationship.
THE OUTCOME
What this offering is for
Restaurant-controlled checkout
Give guests a direct path from menu discovery to a confirmed pickup or delivery order.
Operationally valid orders
Apply item availability, modifiers, lead time, minimums, taxes and service zones before acceptance.
Consented first-party data
Retain the order relationship and record marketing permission separately from transactional communication.
FUNCTIONALITY
What it offers
These are the core jobs the feature should make understandable and controllable for a restaurant operator.
Orderable menu
Turn approved menu items into products with modifiers, required choices, quantity limits, availability windows and sold-out states.
Fulfillment controls
Configure pickup and delivery independently, including opening windows, prep lead time, order throttles, minimum baskets and service areas.
Cart and checkout
Calculate the basket, display fees and taxes clearly, capture the customer’s instructions and hand payment to the configured provider.
Order lifecycle
Move an order through received, accepted, preparing, ready, handed off, completed, cancelled or refunded states with a visible history.
Guest communication
Send transactional confirmations and status changes without treating them as blanket permission for marketing.
Exception handling
Give staff a defined response for failed payments, unavailable items, duplicate orders, late pickup, refund requests and delivery failures.
IMPLEMENTATION
How to set it up
- 1Choose fulfillment modesEnable only the modes the venue can consistently operate. Define delivery boundaries, collection instructions and kitchen capacity by daypart.
- 2Configure the menuSet prices, taxes, modifiers, required selections, allergen disclosures and time-based availability. Test every high-volume item.
- 3Connect paymentUse an approved payment provider and determine which system owns capture, void, refund, settlement and dispute evidence.
- 4Define order routingChoose the staff device or production workflow that receives orders and assign an acknowledgement target. Do not assume a POS or kitchen-display connection.
- 5Write policiesPublish cancellation, refund, substitution, allergen and delivery terms in plain language before checkout.
- 6Run test ordersTest success, declined payment, sold-out items, closing time, address outside the zone, refund and notification delivery before launch.
IN THE RESTAURANT
How the team runs it
Open the channel
Confirm hours, staff coverage, menu availability, prep time, payment status and delivery capacity.
Acknowledge quickly
Accept or reject incoming orders within the restaurant’s target and give the guest a realistic completion time.
Manage exceptions
Contact the guest through an approved channel, record substitutions or refunds and preserve an audit trail.
Close and reconcile
Compare completed, cancelled and refunded orders with payment settlements and delivery charges.
MEASUREMENT
Metrics that make it operational
DEPENDENCIES & LIMITS
Know what must be confirmed
[CONFIRM: supported payment providers, currencies, taxes, refund flow and settlement owner for every launch market.]
[CONFIRM: whether GrowthOS routes orders to a POS, kitchen display, printer or only the GrowthOS order inbox.]
Any environment that stores, processes or transmits payment account data must address the applicable PCI DSS responsibilities.
Allergen notes and guest instructions support communication but do not replace trained kitchen procedures.
RESEARCH
Primary sources and market references
Official sources establish platform, privacy or security requirements. Vendor sources are labeled as industry patterns, not proof of a GrowthOS integration.
NEXT GUIDE