Online ordering is the most direct lever an independent restaurant has over its own revenue, and also the one most often bought on the strength of a demo. This guide walks through the whole system—what the pieces are, where the money goes, and the handful of decisions that matter more than the logo on the login screen. Read it before you sign anything.

1. What "online ordering" actually contains

A working online ordering setup is at least seven things pretending to be one:

  • A menu engine — categories, items, modifiers, combos, allergens, photos, availability.
  • A storefront — the page customers use, on a hosted URL or your own domain.
  • Checkout rules — collection vs delivery, delivery zones, minimum orders, ready-time calculation, coupons.
  • Payments — cash, card on delivery, online card processing.
  • Order flow — where the order goes: kitchen board, till, printer, tracking page.
  • Customer records — accounts, addresses, order history, reviews.
  • Reporting — what sold, when, through which channel.

Any evaluation should cover all seven. Most sales conversations cover two.

2. Where the money goes on a direct order

For a typical order, the flows are: the customer pays the full amount; the payment provider deducts processing fees; the restaurant keeps the rest. The software is paid for separately as a subscription. For TableSync, compare the published software plans and confirm all applicable charges before activation. Live online-card checkout is not currently available. Compare that with a marketplace order, where commission is deducted before anything reaches you. Direct vs marketplaces works through the full comparison.

3. The channels, and why they should be one flow

Customers now order from a website, a QR code at the table, the counter, a marketplace app, and increasingly by phone or message. A restaurant does not need six ordering systems; it needs one order flow with six entrances. Judge any platform on whether a web order, a QR order and a till order look identical to the kitchen.

4. Hosted page, own domain, or full website?

Start on a hosted ordering page (subject to activation and menu readiness), move to order.yourrestaurant.com when you control DNS, adopt a full website when marketing needs it. The important property is that all three steps use the same menu and orders. Four architectures compared works through the choice; restaurant websites on TableSyncAI explains the current hosted storefront and controlled domain setup.

5. Menu design for ordering, not for print

  • Name dishes the way the kitchen names them; tickets should be instantly recognisable.
  • Model modifiers as rules (choose 1 of 3 sizes; up to 2 extras) rather than free text.
  • Keep allergen data on the item, maintained with the menu—not on a separate sheet.
  • Photograph the eight dishes that sell, not all forty.
  • Check which connected channels receive an availability update; do not assume unconnected marketplaces follow it.

6. Pickup vs delivery: decide the operation first

Collection is simpler and higher margin; delivery is demand you would otherwise lose. If you deliver directly, define zones and minimums explicitly and let the system validate addresses before checkout. If you rely on marketplaces for delivery, keep collection direct. Most independents run collection and local delivery direct, and marketplaces for reach.

7. The order after the order

A good repeat-ordering experience can help turn the first order into a longer relationship. Customer accounts, saved addresses, order tracking, a sensible ready time and a reason to return (not always a discount) are what turn a direct channel into a habit. See direct ordering on TableSyncAI.

8. Non-negotiables

  1. Server-authoritative totals. Prices, availability, coupons, delivery rules and totals are validated by the platform, never by the browser.
  2. Customer identity separate from staff identity. A customer account must never grant staff-level access.
  3. One menu record across every channel and every screen.
  4. Order tracking that reflects what the kitchen actually did.
  5. A path to your own domain without re-platforming.

9. A short evaluation checklist

  • Show me a web order and a QR order side by side on the kitchen board.
  • Mark an item sold out—where does it disappear from?
  • What does the customer see after paying, and when does it change?
  • What do I pay per order, per month, and to whom?
  • How do I move from your hosted page to my own domain?

Where to go next