Quick answer
Choose whether the website will link to a marketplace, use POS-native ordering, embed a provider flow, or run an independent direct channel. Then verify menu, payment, order routing, fulfillment, support, and analytics end to end.
Adding online ordering to an existing restaurant website is a six-part operating change: choose the order path, prepare the menu, connect payments, define fulfillment, add the customer entry point, and test the complete order. A restaurant can use more than one path. Document which channel owns the menu, customer relationship, payment, refund, support, and fulfillment state before launch.
Evaluation criteria
- website and brand experience
- menu and availability authority
- checkout and payment ownership
- POS and kitchen order routing
- pickup and delivery workflow
- customer consent, analytics, support, and accessibility
Add online ordering in six steps
- Choose the ordering path and its authoritative systems, and record current commercial terms, territory, support owner, and required integrations.
- Build and review the menu: items, modifiers, prices, taxes, availability, images, and scheduled changes.
- Connect the approved payment provider and test authorization, capture, tips, refunds, and failed payment states.
- Configure pickup and delivery hours, lead times, zones, fees, minimums, capacity, and unavailable-item handling, and connect order acceptance in the store.
- Add a clearly named Order Online link or embedded surface to the existing website and verify keyboard and mobile access.
- Place approved test orders for every fulfillment and payment path across devices and failure paths, reconcile the results, train staff, publish support ownership, and record rollback procedures.
What this looks like in the Ordering.co dashboard
On Ordering.co, delivery zones are drawn directly on a map (or imported from a KML file) and priced by distance or zone, so step 4 above does not require a developer. Menus can be scheduled by day and time — a separate breakfast, lunch, or dinner menu — under step 2. And once orders start coming in, the dashboard and the Merchant app send automatic order notifications by email and push, so step 6's test orders confirm staff actually gets alerted.
Compare the available approaches
Use this framework to compare approaches against your operating requirements. Confirm current figures, provider scope, and commercial terms before deciding.
| Approach | What it is useful for | What must be verified |
|---|---|---|
| Third-party marketplace | Demand discovery and outsourced marketplace reach | Current fee schedule, fulfillment option, customer-data access, branding, ranking rules, refunds, support, and local terms |
| POS-native ordering | A direct channel closely tied to one POS ecosystem | Exact POS product and account, supported version, menu and order sync, payments, locations, delivery, brand control, data access, and support |
| Independent direct channel | A branded website or app operated by the business | Platform plan, implementation, integrations, acquisition, payment processing, fulfillment, support, operating responsibilities, and all-in operating cost |
| Hybrid model | Keeping marketplace reach while growing a direct channel | Channel roles, menu parity, order routing, customer consent, attribution, and operational ownership |
Compare the paths with the same questions
- What does the provider charge in this territory and contract, including percentage, fixed, delivery, payment, promotion, refund, and support charges?
- Who controls branding, domain, customer access, consent, retention, and exports?
- Which menu, inventory, order, payment, and fulfillment objects move between systems, and in which direction?
- Who owns failures, retries, reconciliation, refunds, customer support, and vendor escalation?
- Can the team verify the complete order path on web, mobile, store operations, and delivery before launch?
Marketplace fees vary by provider, plan, fulfillment method, contract, and market. Use the current provider terms and the applicable agreement. Ordering.co plan details, inclusions, exclusions, and applicable charges remain on the pricing page.
Questions to settle before selection
For every answer below, verify current provider documentation, plan, territory, fees, exclusions, implementation responsibilities, and contract terms before relying on the result.
How do I add ordering to my restaurant website?
Follow the six steps above: choose the path, build the menu, connect payments, configure fulfillment, add the customer entry point, and test every order path before launch.
Should ordering be embedded or opened on another page?
Either can work. Whether you embed the ordering surface or link to a branded ordering flow, give it a clearly named Order Online entry point and verify that customers can complete an order with a keyboard and on mobile.
Does online ordering need a POS integration?
Not always. Decide which system is the authority for menu, availability, and orders, then confirm which objects move between the ordering channel and the POS, in which direction, and who owns sync failures. POS-native ordering ties the channel to that POS's own catalog, payment, location, and integration limits.
How do pickup and delivery fit the website flow?
Configure pickup and delivery hours, lead times, zones, fees, minimums, capacity, and unavailable-item handling before launch, and make sure customers receive accurate order status for each option.
What should be tested before launch?
Place approved test orders for every fulfillment and payment path, including tips, refunds, and failed payments, then reconcile the results. Timeline depends on data readiness, configuration, integrations, app review, testing, training, and support readiness, so request a written scope, timeline, owners, and exclusions that reflects those dependencies.
Which online ordering approach is best?
No universal winner is established. Score each approach against every evaluation criterion above, and require dated evidence and a live workflow demonstration for every material requirement.
Acceptance gate
The website is ready when a customer can enter the ordering flow, complete each supported payment and fulfillment path, receive accurate status, and reach a documented support path—and when the restaurant can receive, prepare, reconcile, cancel, and refund the order without relying on an untested assumption.
Discuss the operating model to evaluate these requirements against your restaurant.