Table reservations without cover fees

Why per-cover booking fees feel wrong

You already pay rent, labour and produce for every seated guest. A booking tool that charges per cover adds a tax on the outcome you want most: a full dining room.

Independent restaurants need something simpler:

• Guests book online with party size
• Capacity rules prevent impossible turns
• Confirmations and reminders cut no-shows
• The floor team sees one list — not a paper diary plus WhatsApp

What a modern reservation page needs

1. Party size limits that match your tables
2. Service windows that match the kitchen
3. Automatic confirmation to the guest
4. Reminder before arrival
5. Same dashboard as orders if you also run takeaway

Orderzest puts reservations beside online ordering so managers are not context-switching mid-service. Read more on the table reservation system page.

No-shows are an operations problem, not only a software problem

Reminders help. So do clear policies on your page, a phone number for large parties, and not overselling turns you cannot cook. Software should support that discipline, not invent cover fees as the solution.

Pricing

Reservations are included in the same €10/month Orderzest plan as ordering — no cover fees, no commission. Trial is 14 days free. Pricing details.

If you used FoodBooking / GloriaFood reservations

Those flows are part of the wider GloriaFood retirement story. Export settings you care about, then rebuild capacity rules on the new system before guest-facing links change. See GloriaFood shutdown.

Practical setup afternoon

1. Draw or list tables / party limits
2. Set bookable hours
3. Write a short house policy (late arrivals, cancellations)
4. Take three test bookings
5. Put the Book button on your site and Google profile

Start your free trial or contact us if you want help migrating an existing booking link.

Extra operational notes restaurants ask about

Staff adoption matters more than feature lists. Pick one person to own the new link for the first two weeks: they check that tickets arrive, that printers or phone alerts work, and that delivery drivers still understand the address format. A quiet Tuesday is a better cutover day than Saturday brunch.

Write a three-line guest message you can reuse on Instagram Stories, WhatsApp broadcasts and email: what changed, what stayed the same (your food), and the new link. Guests forgive a software change when the message is clear and the food is familiar.

If you run more than one branch, migrate one location first. Prove the kitchen flow, then clone hours, zones and menus. Trying to flip every branch on the same afternoon creates support noise you do not need during service.

Keep a short rollback plan for seventy-two hours: old link still live but unpromoted, new link in every bio, one manager with authority to pause online ordering if the POS or printer misbehaves. After three clean services, remove the old buttons.

Finally, measure the right thing. Track orders on your own link weekly, marketplace commission paid monthly, and no-show rate on reservations. Those three numbers tell you whether the switch is working faster than any vanity dashboard.

For Orderzest specifically, use the free trial to place real test tickets, then subscribe only when the floor team is comfortable. Migration help and pricing are on the site; the goal is a boringly reliable Friday night, not another complicated vendor relationship.

A second-week checklist

• Confirm every public QR code resolves to the new page
• Remove outdated “Order with …” buttons from the website footer
• Train one backup person on refunds and cancelled bookings
• Screenshot your delivery zone map for the records
• Add the ordering link to Google Business Profile if you have not already
• Ask three regulars to place a real order and reply with friction notes
• Schedule a thirty-minute review after fourteen days of live traffic

None of this is glamorous. It is how restaurants keep weekends calm while the industry toolscape keeps changing.