The right dine-in ordering flow depends on a simple question: where will the guest be when they place the order, and where will they receive the food?
OmNom’s current dine-in guidance describes three options. Counter Dine-In supports ordering ahead and collecting at the counter. Table Service lets seated guests order with a table code. Book a Table collects a scheduled arrival time and party size with the order, but it does not guarantee a table through a live table-availability system.
Choose the flow your team can explain and deliver consistently. Then make the guest’s next step clear on your own signs, website, and staff instructions.
1. Start with the guest’s journey
Use these three questions before choosing how to present dine-in ordering:
- Will guests order before they arrive and collect food at the counter? Start by considering Counter Dine-In.
- Will guests already be seated when they order? Consider Table Service and its table-code workflow.
- Do you need a planned arrival time and party size alongside the food order? Consider Book a Table, with a separate explanation of how your restaurant handles seating.
Treat those as different service promises. A guest ordering from home needs to know where to go on arrival. A seated guest needs to know which code belongs to their table. Someone entering a party size needs to understand whether anyone has actually confirmed seating.
Before printing instructions, check the options available in your restaurant’s setup. If the expected option is missing or unclear, ask OmNom support before advertising it to guests.
2. Use Counter Dine-In when collection happens at the counter
Counter Dine-In lets customers order ahead and collect their food at your counter. Build the instructions around that handoff.
Decide with your team:
- Which counter or pickup point receives online guests
- How staff will identify the correct order
- Whether guests should approach the counter on arrival or wait for the restaurant’s usual collection cue
- How guests find out about seating under your restaurant’s own policy
These are operating decisions for your restaurant. The name of an ordering option cannot explain them on its own.
For example, a café that uses a clearly marked collection counter could adapt this wording: “Ordered ahead for dine-in? Collect your food at the collection counter. Ask our team if you need help finding a seat.” Use it only if it matches how your café actually works.
Avoid putting “we’ll bring it to your table” on the same instructions unless your team has deliberately arranged that service. Consistent wording keeps counter staff from having to correct expectations after payment.
3. Explain exactly what Book a Table collects
Book a Table collects a scheduled arrival time and party size with the order. Those details can help your team understand the intended visit. The important limit is that the flow is not a guarantee from a table-availability system.
Keep your restaurant’s seating policy separate and explicit. If a guest needs a confirmed table, explain how to obtain that confirmation through the process your restaurant actually uses. Do not describe an entered arrival time as a confirmed reservation just because the ordering option is named Book a Table.
A possible explanation is: “Add your planned arrival time and party size with your order. Contact the restaurant to check table availability.” Adapt that to your real contact process and seating policy; do not promise that a particular party can be seated until your team has checked.
Walk through these situations with the person greeting guests:
- A party arrives at its entered time, but all tables are occupied.
- More people arrive than the party size supplied with the order.
- A guest assumes the food order also reserved a particular table.
Agree on who checks the situation and what staff should explain. The article cannot decide your capacity or reservation policy, and the collected order details do not replace that decision.
4. Use Table Service for guests who are already seated
Table Service lets seated customers order using a table code. The practical check is whether a guest can confidently identify the code for the table where they are sitting.
Review the physical setup as well as the ordering instructions:
- Make the relevant code easy to find and read
- Check that any sign or card is placed at the intended table
- Remove obsolete instructions when you change your layout
- Tell guests how to ask for help if they cannot use the code or their phone
- Decide how staff will handle a guest who moves tables after ordering
If you place a QR code beside the table instructions, open it on a phone and check its destination. A QR code is only a way to open a link; your instructions still need to explain any table-code step required by the ordering flow.
Do not assume that moving a sign, changing a seating plan, or moving a guest automatically updates an existing order. Have staff verify where that order belongs before taking food out.
5. Rehearse the instructions before promoting the flow
Ask someone who did not write the instructions to read them and describe the next step. Can they tell whether to order before arriving, collect at a counter, enter an arrival time, or use a code after sitting down?
Check the same path with the staff who will receive the guest:
- The advertised option matches what your restaurant’s ordering page offers
- The guest knows where to go and how to identify the order
- Staff know who handles seating questions and changed plans
- Any table-code instructions match the current floor layout
- Scheduled-arrival wording does not promise unconfirmed table availability
Customers place OmNom orders in a browser on a phone or computer; they do not need to install an app. Keep guest-facing instructions focused on your ordering link and the service steps they need.
If something in the flow does not match your setup, send support the restaurant name, a short description, and the order number when an existing order is involved. Keep sign-in codes and sensitive payment information out of the request.
The useful choice is the one your team can carry through from the first instruction to the final handoff. Make that journey clear before inviting guests to use it.