Pay at table vs order at table: what's the difference, and do you need both?

Order at table and pay at table solve two different waits. Order at table moves the order from the server’s notepad to the guest’s phone, so nobody waits to be seen before they can order or reorder. Pay at table moves the payment to the phone, so nobody waits for the check or the card machine. Some tools do both. WaiterPilot does only the ordering side, plus a live bill and a check request; guests still pay your staff on your own terminal.

So the real question isn’t which is better. It’s which wait costs your restaurant more, and whether you want to fix one or both.

What exactly is the difference?

Short answer: what moves to the guest’s phone. Order at table moves the order; pay at table moves the money.

The categories overlap more each year. Qlub and sunday sell both sides. Toast’s Mobile Order & Pay lets guests order and pay from their own device, and Square’s self-serve ordering takes Apple Pay, Google Pay and Square Pay. Ask any vendor which column it really sits in for the plan you’d buy.

Which wait costs you more?

Short answer: the best evidence points to the end of the meal. Paying is where tabletop devices showed the clearest time savings.

Here is what the research shows, with its limits:

• Paying. In a 2016 Cornell report on one US full-service chain, guests who paid on a tabletop device had a table-turn time of 45 minutes 21 seconds, against 53 minutes 45 seconds for guests who didn’t, a “15.5-percent reduction” (Susskind and Curry, Cornell, 2016, p. 7). Guests chose whether to use the device, so this is an association, not proof.
• Server time. In one restaurant from the same report, server time per table fell 36% when guests paid by device and 65% when they ordered and paid by device (p. 6). That was 63, 33 and 7 tables, so treat it as a hint.
• Both, in a stronger study. A peer-reviewed study of a 66-restaurant US chain found tabletop devices cut meal duration by about 10% (Tan and Netessine, Management Science, as reported by Restaurant Technology News, 2019).
• What guests ask for. In the NRA’s 2024 survey, making paying easier and faster (30%) edged out making ordering easier and faster (28%) as the thing full-service diners most want technology to help with (NRA, 2024, p. 7).

Guests are about equally willing to do either. In the same NRA survey, 48% would order with a QR code at a full-service restaurant and 46% would pay with one. On a tablet at the table, 60% would order and 65% would pay.

We say this plainly because it doesn’t flatter us: if your slowest moment is the end of the meal, a pay-at-table tool attacks it more directly than WaiterPilot does.

Where do the waits fall in one meal? A Casa Olivo example

Casa Olivo is a fictional restaurant we use for examples. The minutes below are assumptions for illustration, not measurements.

Casa Olivo’s owner times a typical Friday table of four over a 90-minute meal and finds four waits:

“Touched” is not “removed”. Each tool shortens a wait by some amount you can only find by measuring your own room. But the table shows the shape of the choice. If Casa Olivo’s Friday problem is guests waving for a server to order, order at table is the fix. If it’s the queue for the card machine at 21:30, pay at table is.

What does pay at table do that WaiterPilot doesn’t?

Short answer: it takes the payment, and with it the tip and the card split.

Pay-at-table tools let each guest pay their share on their own phone, usually by card or a phone wallet. sunday sums up its product as “Scan, split, tip, pay. 10 seconds, no app.” That is sunday’s own description, not a figure we’ve checked.

WaiterPilot does none of that. It has no payment processing and no guest tip feature. If guests paying on their phone is the point, choose a pay-at-table or order-and-pay tool. Our guide to tipping and QR ordering covers what that means for servers.

What does WaiterPilot do on the bill side?

Short answer: everything up to the payment itself.

• A live bill on every phone at the table. It lists each order with its status, the subtotal, the charges you set (tax, service charge or a gratuity line) and the total. Broadnet Cafe, our own demo restaurant, set Service 5% and Tax 7.5%, which is what the screenshot at the top shows. Your charges are your choice.
• Split the bill. Guests can split it evenly or see just their own share.
• Check please. A guest taps it, or asks in the chat, and WaiterPilot asks whether they’ll pay by cash or card. The request shows on the staff floor screen within seconds, so the server walks over with the card machine already in hand.
• Payment with your staff. On the terminal you already have, at the processing rates you already pay. WaiterPilot takes no cut: it’s a flat $200 per location per month, 0% commission, no contract.

More detail is on the waiter call and bill page, and we work through split methods in splitting the bill at the table.

Can you use both together?

Short answer: in principle yes, but it depends on your POS, and we have not tested any combination.

Pay-at-table tools say they integrate with POS systems, so in most set-ups the order needs to be in the POS before a guest can pay it. Qlub says its SoftPOS is “fully integrated with your POS system”, and sunday shows logos for POS systems including NCR VOYIX, Clover, Toast, Lightspeed and Micros (vendor pages, checked 15 Oct 2026).

WaiterPilot has no POS connection. So for a pay-at-table tool to see a WaiterPilot order, a staff member has to ring it into the POS first. That works only if your team enters each order in the till as they confirm it, not at the end of the meal. We explain both ways of working in how to reconcile QR orders with your till.

What does each cost?

Short answer: published prices are rare on the payment side, and processing fees are almost never on the pricing page.

Which do you need? A quick decision guide

Answer in order:

1. Do guests need to pay on their phone? If yes, you need a pay-at-table or order-and-pay tool. WaiterPilot alone won’t do it.
2. Is the slowest part of your night the end of the meal? If yes, start with pay at table.
3. Is it the start: guests waiting to order, asking about dishes, or not reading the menu’s language? If yes, start with order at table. A chat that answers in the guest’s language (WaiterPilot is tested in English, Arabic and Spanish, and answers most other languages too) helps most here.
4. Are you changing POS anyway? Then look at your new POS’s own order-and-pay first, so you run one system.
5. Want both and keeping your POS? Check that the pay-at-table tool supports your POS, and plan for staff to enter orders in the till as they go.

What to do next

Time the four waits at your busiest service for one week. Whichever is longest tells you which side to fix first. If it’s ordering, try a sample order to see how WaiterPilot handles it, and compare it with the payment tools on our comparison page.