Point of Sale

The terminal

The sell screen lives at pos.u.cash (the console's POS area links straight to it). It takes crypto, cards, bank rails, gift cards, and store credit at the counter, and it works offline: sales queue in an on-device outbox and settle with idempotency when the connection returns.

• Catalog - products, modifiers, and categories managed in the console
• Restaurant mode - open tabs, floor plan with tables, and a kitchen display system (KDS); disabled it stays completely out of the way
• Reservations and table management when restaurant mode is on
• Appearance - 12 skins plus density and tile-size controls so the terminal matches the room
• Receipts and printers - terminal and printer management from the console

Managed from pay.u.cash

The POS area in your console is the management surface: Terminals, Appearance, Settings, Cards & Credit, Staff, Status, Floor Plan, Modifiers, Reservations, and Reports. The terminal itself is for clerks - management never happens on the sell screen.

• Cards & credit - stored value: gift cards and store credit issued, redeemed, and reconciled from the console
• Discounts - a per-role approval matrix (clerk, teller, lead, supervisor, manager) with caps and void/refund gates, so discount authority matches seniority
• Tips and auto-gratuity - configurable per terminal or globally
• Tax - POS tax settings integrate with your tax configuration

Staff on the terminal

POS staff sign in with their U.CASH staff accounts. A teller-role staff member is a POS-only user - they are routed straight to the terminal and cannot reach the merchant console at all. See Roles & Permissions.

Offline behavior

When the network drops, the terminal keeps selling: every action lands in an IndexedDB outbox with a unique id, so nothing double-charges when connectivity returns. Cards and crypto confirmations obviously need the network - the terminal is explicit about what is queued versus settled.