Operations

How to take payments faster when the restaurant is packed

The bottleneck is almost never the kitchen. It's the end of the meal.

July 8, 2026 · 5 min read

Guest paying the check from their phone

Pick any night and measure how long it takes from a table asking for the check to that table standing up. In most restaurants it's between eight and fifteen minutes. Multiply that by every table on a Friday.

Why the end gets stuck

The guest is done and just wants to leave. But for that to happen three things have to line up: the server is free, the card reader is free, and both happen to be at the same table.

No card reader can charge five tables at once.

When four tables ask for the check at almost the same time, you have a math problem, not an attitude problem.

What every extra minute costs

  • A table sitting there can't seat the people waiting at the door.
  • The server makes trips instead of serving another table.
  • The guest takes home the last impression of the night: waiting.
  • During the rush, fifteen minutes is a lost turn.

Three ways to shorten it

First, don't let payment depend on a single card reader. Second, let several tables pay in parallel. Third, make sure splitting a check doesn't mean fifteen minutes of arithmetic with the server standing there.

When guests can pay from their phone, all three get solved at once.

Something to measure this Friday

Write down when each table asked for the check and when they stood up. If the average is over ten minutes, that's the cheapest place to grow without opening another location.

S

The Snap It Go team

We write from the floor: management at Applebee's and Chili's, and a lot of Fridays at 8:30 p.m.

Restaurant technology. Human support for real life.

Tell us how your restaurant runs and we'll tell you where to start.

Call or text