tbltap

Run table ordering during service

Best practices for staff sign-in, server-entered orders, table sessions, bill readiness, Quick Pay handoff, and support during service.

Quick Pay guideTeam Access
Restaurant staffUpdated May 5, 2026

Staff sign-in

Staff order tools are private restaurant tools. Owners and admins should invite staff through Team Access, then use trusted devices and team PIN flows where shared service devices need fast sign-in.

  • Use individual team access for staff accountability instead of sharing one owner account.
  • Trusted staff devices can use a 4-digit PIN flow for faster service sign-in after enrollment.
  • Manager PIN approval may be required for sensitive payment actions, refunds, forced clears, or other protected service actions.

Server take-order flow

Server take-order tools let staff create or resume a table session and add items for guests, including guests who ordered verbally or never used the public menu.

  • Confirm the restaurant, table, and guest context before adding items.
  • Review item quantities, modifiers, notes, and unavailable items before firing or marking the order ready.
  • Use void, comp, or refund actions according to restaurant policy and manager approval requirements.
  • Keep the open bill accurate so Quick Pay and split-bill totals match what the guest expects.

Move the table to payment

When staff is ready to collect payment, the take-payment flow marks open orders bill-ready and moves the table session into billing.

  • Once a table is in billing, the table tag can route guests directly to Quick Pay for that table bill.
  • The same QR/NFC location can be used by guests who did not order through the menu because staff-entered items are part of the table bill.
  • Staff can show a payment QR or ask guests to scan the table tag, then monitor payment events before closing the session.

Service best practices

Good table operations keep the digital bill aligned with what the guest received and what the restaurant intends to charge.

  • Confirm tags open the correct table before a busy service period.
  • Watch for unavailable items and update them before guests order or staff add items.
  • Handle urgent order changes directly with the guest whenever possible.
  • Close or clear table sessions after payment according to restaurant procedure so the next party does not inherit the old bill.

When to contact support

Support can help with platform access, tag routing, payment page issues, and documentation gaps. Restaurant staff should still handle food, timing, and service decisions.

  • Include restaurant name, table, order time, and screenshots when possible.
  • For guest payment problems, include receipt or checkout context without sharing full card data.
  • For tag problems, include where the tag is placed and what page it opens.

Most likely questions

Quick answers

Should staff use one shared account?

No. Team access should be tied to the people who need it so the restaurant can manage permissions and accountability.

Can staff add items for a guest who never ordered through the tbltap menu?

Yes. Staff can use the server take-order flow to add verbal or in-person orders to the active table bill, then Quick Pay can collect payment from the table when the bill is ready.

Why does a table tag open payment instead of the menu?

When an active table session is in billing mode, the tag can route to the Quick Pay bill location so guests can pay the current bill.

Was this helpful?
Need help?

Contact tbltap support and include the document title so we can route your question quickly.

Contact support
Run table ordering during service | tbltap Docs