A till that doesn't stop when the pipe does.
Rental shop, ticket window, cafeteria and retail on the same registers, with the reconciliation to prove what happened at the end of the day.
- Complete sales while the internet is down
- Kiosks and phone ordering take the queue off the counter
- No silent comps — discounts always need a manager
An add-on module, on top of the base plan.
A catalogue that knows what it is selling
Products carry modifiers, multiple barcodes, cost and markup, tax-inclusive pricing, age limits and sale windows. Some products are more than merchandise: ringing a ticket product issues and prints a real lift ticket, and a gift-card product issues a real card and books the liability.
- Attach a waiver to a product and the sale demands a signature before it tenders
- Per-location category visibility, so the cafeteria till isn't showing ski wax
- Route lines to bar, kitchen or grill printers, or to a bump screen
Every way a guest actually pays
Cash, card, cheque, voucher, comp, store credit, gift card and on-account. Stored-value tenders validate against a balance the cloud owns, so two registers cannot spend the same gift card twice.
Controls that hold on a register you've never seen
Discounting requires a manager approval on every register regardless of how that company is configured — including one that has never finished a sync. Void, refund, cash-out, paid-out, no-sale, Z-report and over-threshold close are each independently configurable.
- Manager approval is a badge scan at the till, not a shared PIN on a sticky note
- Refunds are per-line and partial, with double-refund protection
- Refund-to-store-credit can sit at a lower authorisation tier than refund-to-card — the money stays with you
The end of the day adds up
Drawer sessions per register or shared, paid-ins and paid-outs, audited no-sales, X reads and Z closes kept as history with a reconciliation report against them.
Let the queue serve itself
The bottleneck at a mid-size area is almost never the kitchen — it's the one person taking orders while forty people in ski boots wait. Self-service kiosks take tickets and food orders directly, on the same catalogue and the same prices as the counter, so there is no second menu to keep in step.
- Weather-rated touchscreens for the ticket window or the cafeteria
- Guests pay at the kiosk and collect against a QR code — the money is already taken before anyone reaches the counter
- Age-restricted products are ordered and paid at the kiosk but only issued at pickup, where a person checks ID. No camera, no age estimation, no biometric data
- Kitchen routing is unchanged: a kiosk order hits the same bump screen as a counter order
Order from the hill, collect in the hut
Guests on your wifi order and pay from their phone and pick it up at the warming hut. It keeps people on the mountain instead of walking down for lunch, and it flattens the noon rush into something a kitchen can actually pace.
- Same catalogue, same modifiers, same prices as the till
- Orders land on the kitchen display with everything else, in the order they arrived
- Collection is the same QR scan the online store already uses, so staff learn one thing rather than three
- Runs on your own network — the ordering path doesn't depend on the guest having signal at 9,000 feet
Registers you don't have to build
A register is imaged, not assembled. The installer carries its own package pool, so it needs no network — and a stick left in the wrong machine boots that machine's existing system and does nothing.
- Updates are cached once by the on-site gateway and served to every register over the LAN, not pulled a dozen times over your uplink
- Two screens per register with stable identity, so the customer display doesn't swap sides after a reboot
- Customer pole displays in three command dialects; screensaver and monitor sleep while the machine keeps syncing
A full sale — tender, receipt, kitchen ticket, printed lift ticket — completes with the uplink dark, then reconciles idempotently when it returns. Card payments follow whatever offline policy your gateway is set to; terminal-based processors delegate to the terminal itself.
How that worksReports, and all of them export
Card data never touches the gateway or the register — payment runs through the terminal or the processor, and we store none of it.
It doesn't run on its own
One customer record, one employee record, one set of reports. These are the parts of the system this one touches most.