Skip to content
N
NoPOS
Back to Blog
Best PracticesOctober 23, 20266 min read

Tips Without the Headaches

A practical guide to tips, gratuities, and service charges on NoPOS: tip prompts, pools, payouts, and receipts your staff will trust.

N
NoPOS Team
Developer Relations

The NoPOS developer relations team writes practical guides for building on the NoPOS REST API — from first smoke test to production POS.

Tips are where good service meets messy math — percentages, pools, chargebacks, payday. NoPOS keeps it clean: the register prompts, the pool splits itself, and payouts reconcile to the penny.

Prompt at the right moment

  • Show tip options as percentages with a custom-amount fallback, after the total is final — never before discounts.
  • Keep cash and card tip flows identical so the receipt tells one story at close.
  • Let each lane set its own defaults (quick-serve low, full-service higher) without forking the catalog.

Pools, shares, and service charges

  • Route tips into named pools (bar, floor, support) with share weights per role, settled per shift.
  • Treat auto-gratuities and service charges as separate lines from tips — taxed and reported differently.
  • Require manager approval to edit or redistribute a pool after close, and log who did it.

Payouts your staff will trust

  1. Show each staffer their cards tips, cash tips, and pool share on one slip before payout.
  2. Reconcile tip payouts inside the end-of-day close, not in a spreadsheet the next morning.
  3. Export tip and service-charge totals straight to payroll each week.

Use Swagger UI or OpenAPI for the current tip-config, pool, and payout request shapes.

Build from the current contract

Open the gateway for OpenAPI, Swagger, AGENTS.md, llms.txt, and the first X-API-Key smoke test.

Developer Gateway