POS Settings

These switches decide how selling feels — and how much a cashier can do alone. They deserve a deliberate pass when a business goes live, and a review whenever cash discipline needs tightening.

Cash and register controls#

• Manual register closing — cashiers count and enter their drawer at close (the normal mode for cash-heavy businesses). With strict denomination counting, the count is entered note-by-note and coin-by-coin instead of one total.
• Maximum cash variance — the hard limit on how far a counted drawer may differ from expected before the close is refused. Every refusal and acceptance is journaled with full figures. Start generous, tighten with data. See Registers & Shifts.
• Blind cash count — hides expected cash from the cashier entirely; they count what's physically there and the server judges. Pairs naturally with the variance limit.

Day-close pacing#

• Auto-commit day close — when stock consumption finishes cleanly, the close commits itself instead of waiting for a manager's Finalize. Multi-shift branches want this ON so shift changes don't queue behind a review; single-shift businesses often keep the manual Finalize as a nightly checkpoint. Details in Day Close.

Manual charges and their signatures#

Some businesses allow the POS to adjust amounts that move the bill without touching an item:

• Manual VAT / GST — override the order's tax figure for special cases.
• Manual service charges — adjust the service charge on eligible order types.
• Delivery charges — set or change the delivery fee on an order.

Each of these can be placed behind a second-person signature, the same pattern as discount authorization: the branch keeps a list of people trusted to approve, and a cashier's edit prompts for one of them. Two switches govern it — one for the charges (delivery and service travel together), one for manual VAT — and the signature is enforced on the server, not just in the dialog. See Authorizations for the complete signature model.

Discounts#

Discount behaviour — percentage vs amount, per-user caps, complimentary orders, and the discount authorization flow — follows the same philosophy: the branch decides what needs a signature, the system enforces it identically for everyone.

Reviewing an existing business: pull the register close journal and the authorization log for the last month before touching these. The data tells you whether the variance limit is too loose, whether signatures are being asked for the right things, and who is actually signing.