The Bar
Bar-staff-operated handpulls, taps, and box-cider boxes. Tap a slot to assign a product, swap it, mark line-cleaning, or vacate. The till's Cask / Keg / Box cider pages render these slots in order, so a swap here updates what staff see on the till instantly.
Sign in to view tap banks.
Staff discount
Set the staff discount percentage for each product category. When a manager taps Staff on the till's discount modal, each line on the sale is discounted at its category's rate. Leave blank to use the house default (25%) — set in Settings. 0 means no staff discount on that category.
Deals
Multibuy offers the till applies automatically — ring the items and the saving appears when the count is reached. Any mix of the products in a deal counts. A deal price is final: no staff, manager or percentage discount ever touches a deal line.
Loading…
Members
Loyalty card holders. Manual balance adjustments are recorded against the member with a reason note for the journal.
| # | Name | DOB | Balance | Status | ID check | Receipts |
|---|
Seen today
Every card UID that scanned at any reader today — registered members, deactivated cards, unclaimed gift cards, and unknown cards. Click a row to see what we know about that UID and (where appropriate) register the card to a customer.
| UID | Status | Who / What | Scans | Last seen | Reader |
|---|
Till settings
Live EPOS tunables from the settings registry (the epos.* keys, and bookings.* for table bookings, in app_settings). Changes apply immediately on the server — no restart; the till picks them up on its next hard refresh. Money values are in pence (e.g. 1000000 = £10,000). Edits require the office PIN.
| Setting | Value | Source | Updated |
|---|
Xero — daily takings
Posts each trading day to Xero as one sales invoice (line-level VAT, exact till figures) paid into clearing accounts — the MTD-safe shape. Figures are validated against the Z report to the penny before any post; mismatches refuse to post. Start in dry_run mode: preview a few days, let the accountant bless the account mappings, then set mode to live.
Connection & settings
| Setting | Value | Source | Updated |
|---|
Monthly takings for the accountant
One row per trading day: cash (what's banked, after any cashback), card (what SumUp pays), and VAT, with sales inc/ex VAT and gift cards so each row adds up. Every day is checked against its Z to the penny first; if any day fails, no file is made.
Preview / post a trading day
Preview builds the exact invoice + payments and runs the Z tie-out without touching Xero. Post respects the mode setting (dry_run never posts).
Posting history
| Day | Status | Invoice | Net | VAT | When | Error |
|---|
SumUp account credentials
API key, affiliate key, and merchant code from the SumUp merchant dashboard. Same credentials for every paired Solo. Secrets are masked — click Edit, type the new value, save. Changes take effect immediately.
| Setting | Value | Source | Updated |
|---|
SumUp Solo readers
Pair each physical Solo to your SumUp account, then assign it to one or more places that take cards — the kiosk wall, the tip station, or any EPOS till. A Solo can be shared between multiple tills (handy as a fallback when one breaks): payments queue up automatically and start as soon as the Solo is free.
Where readers serve
Every place that can take a card payment. Empty rows mean that surface can't take cards yet — assign a Solo from the Paired Solos panel below, or use Pair / Adopt to add a new one.
| Target | Assigned Solos (by priority) |
|---|
Paired Solos
Physical readers paired with your SumUp account. Click Assign… to change which places a Solo serves.
| Name | Reader ID | Status | Serves | Paired at |
|---|
Pair a Solo
On the Solo (logged out) → Connections → API → Connect. Copy the pairing code (8 or 9 alphanumeric characters) and paste it below. You’ll pick where it serves on the next screen.
Adopt a reader already on this account
Lists every reader paired to your SumUp merchant account. Useful when a Solo has been paired upstream but we don’t have a local row for it yet — click Register on a row to adopt without re-pairing physically.
Test connection
Verifies your API key works and reports each configured reader’s status. Run this after changing credentials, or any time card payments stop working.
WiFi
Pi 5 only. Uses host nmcli via nsenter — on a non-Pi dev box this tab will error.
Current connection
Scan & connect
| SSID | Signal | Security |
|---|
Untappd For Business
Untappd integration has two halves. Search & import uses the read-only token to find beers and prefill the editor (ABV, style, tasting notes, pumpclip). Wall sync uses the read+write token to push beer changes back to your UTFB Wall menu so the public TV updates automatically — pump 1 at the top, pump 10 at the bottom.
Credentials
Find these at business.untappd.com → Account → API Access Tokens.
No locations selected yet.
Connection & locations
Wall sync
Mirror kiosk beer assignments onto your UTFB Wall menu. Pump number determines order: pump 1 is top, pump 10 is bottom. Each beer needs an Untappd ID (set automatically when you import from Untappd in the beer editor).
Advanced: menu/section IDs
Defaults match The Rock account. Change only if your Wall menu is at a different ID.
Bar sync
The till keeps the Bar menu's three sections (Cask / Keg / Cider) in step with its taps by tap number: Cask 3 on the till is the item with tap number 3 in the Cask section. A new beer on a tap replaces that tap's item, a price change updates it, an emptied tap removes it. Items with no tap number are never touched, and the till never creates one without a tap number. Each beer needs an Untappd ID (picked in the till's tap wizard).
Sync log (latest first)
Menu/section IDs (required)
The Bar menu has three sections (Cask / Keg / Cider) — one per bank. A bank whose section ID is blank simply doesn't sync. There are no defaults: set this venue's own IDs.
Fridge sync
Mirror the bottle and can products onto the UTFB Fridge menu. Each product writes one container at its configured size (e.g. a 330ml bottle product writes a "330ml Bottle" container at the product's price).
Menu/section IDs (required)
The Fridge menu has two sections (Bottles / Cans). Defaults below match The Rock account.
Wine sync
Push wine prices (125ml / 175ml / 250ml / 75cl bottle) to your UTFB Wine menu. Update-only — create new wines on UTFB first, then run reconcile to link by name.
Menu/section IDs (required)
Defaults below match The Rock account.
Raw probe
Send a GET request to UTFB with our auth header attached. For diagnosing the API. Common paths: /current_user, /locations, /locations/<id>/menus, /locations/<id>/items/search?q=ostara.
SMTP server
Outgoing mail server credentials. The password is masked — click Edit, type the new value, save. Changes take effect on the next email; the transporter cache invalidates automatically.
| Setting | Value | Source | Updated |
|---|
Outgoing emails
Each row is one outgoing email. Enable, set who gets it, and how often. Schedules read live — change a time and it takes effect on the next minute.
Daily summary email
Sent automatically after each Z-read close. Owner sees yesterday's takings, top sellers, cash position, and anything that needs attention (variance, missing cashup, refusal count).
Settings
Preview
Send a real email
Use this to verify the email actually arrives. Sends today's data (or whichever day you pick above). Leave the override blank to use the configured recipients.
Send a test email
Sends a test email using the current SMTP settings. Useful after editing credentials to confirm they work before relying on them.
Wall — licensing hours
Hours when the self-pour wall is allowed to dispense alcohol. Outside these times the wall shows a "Bar closed until X" overlay AND the server refuses pour requests at the API layer. Edit a day's open/close times below and Save.
Current status
Schedule
Up to two sessions per day (e.g. lunch service + evening). Toggle the "Closed all day" box for any day the bar wall doesn't serve at all (e.g. private events). Times in 24-hour format. A close time before the open time means the session wraps past midnight (e.g. open 22:00, close 02:00).
Card readers (Till Companions)
Each Till Companion (a small Pi with a USB card reader at the bar or cafe) sends card taps to the server tagged with its reader id. Bind a reader to a till here so its taps go to the right place. Swap a Companion? Just re-point the binding — no need to touch the device.
Current bindings
| Reader id | Bound to till | Label | Last seen | |
|---|---|---|---|---|
| Loading… | ||||
Seen recently, not bound
These readers have sent taps in the last 24h but aren't bound to a till yet. Bind one:
Add / update a binding
Live activity
Real-time view of what the kiosk is doing. Polls once a second while this tab is open. The active-pour card ticks live as flow-meter pulses come in — useful for calibration and diagnosing “why didn’t my pour finish”.
Recent pours
| Time | Member | Pump | Beer | Measure | Pulses | Status | Charged |
|---|---|---|---|---|---|---|---|
| loading… | |||||||
Security & PINs
The office PIN protects edit/delete on cash-up records, settings changes, and admin endpoints. Engineer recovery PIN (2416) is hard-coded — never displayed, never editable; use it to recover if the office PIN is lost.
| Role | Status |
|---|
What's On
Messages and adverts for the website and the beerboard, in one planner (also in the Boar Dash app): scrolling text and full-screen adverts, in the order they will appear. Set a start and an end and an item shows up on the day and removes itself after — nobody has to remember. Leave the dates blank for something that always shows. Tick which screen it belongs on: the website's banner, the beerboard wall, or both.
Errors
Faults nobody on the floor can see: server errors, tickets that didn't print, emails that didn't send, backups, stuck card top-ups, member balances that don't match their history, wall pours that went wrong. The same fault counts up on one line. Checks run every 5 minutes and clear themselves when the problem goes; mark the rest resolved once you've dealt with them.
UPS & power cuts
The UPS on the NUC, read over its USB cable. On a power cut the tills show AC LOST and a bar (FULL · FAIR · LOW · CRITICAL · SHUTTING DOWN); the NUC shuts itself down safely at the low mark. Every cut is logged here so you can see how long the battery really lasts at our load.
Now
How long it lasts
Power cuts
Backups
Automatic SQLite backups (intraday / daily / weekly), verified after every write, kept locally, pushed offsite over SFTP and replicated to other estate Pis. The SSH private key stays file-mounted on the server and is never editable here.
Status
Restore from a backup
Pick a backup to restore. The current database is safety-snapshotted first, the chosen backup is integrity-checked, then the server restarts to swap it in — so tills will drop for a few seconds. This replaces all current data with the backup's.
Schedule & retention
Offsite SFTP
Leave host blank to disable offsite push (local + Pi replication still run). The private key is mounted at the path shown — add the public key to the SFTP server's authorized_keys.
Offsite FTP (web hosting)
For hosting that gives an FTP account rather than SSH (cPanel). The chosen backups go to folder/daily, folder/weekly on the server, encrypted (FTPS), and the oldest are deleted there once the keep count is reached. Leave host blank to turn it off.
Staff hours
"Actual" is the worked time recorded on the rota (drag each shift's actual bar); holiday / sick days are unpaid and excluded. "Hours to pay" defaults to Actual — hand-adjust only for edge cases (cover, no-shows, maternity, etc). You can also confirm & send straight from the Rota page. Set the payroll recipient in Admin → Email → "Staff hours → payroll".
| Staff | Type | Scheduled | Actual | Hours to pay | Δ | Note | |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
| Total | — | — | — | — | |||
Reset & wipe
Two separate, heavily-guarded operations. Clear sales data wipes trading history but keeps your whole setup. Full factory reset wipes everything — setup, settings, credentials and staff — for moving to a new site or handing the box on. Both take an un-prunable backup first.
1 · Clear sales data
Wipes trading history — every sale, tab, payment, kitchen ticket, cash-up, Z-read, audit-log entry, and till session. Keeps products, staff, layouts, settings — your entire configuration. Use it to clear test data before going live.
What this DOES wipe
- All sales, tabs, payments, refunds
- Kitchen tickets + KDS history
- Cash-up records + Z-reads + X-reads
- No-sale audit + cash movements
- Receipt + order number sequences (restart at 1)
- Till sessions + active members ("seen today")
- Admin audit log + failed-login records
What this KEEPS
- Products, categories, modifier templates, allergens
- Beers, pumps, taps, SumUp readers, printers
- Staff, permissions, PINs
- Rotas + shifts + staff rota tokens
- Tills, layouts, tables
- App settings, VAT rates, email rules
- Refusal log + ID checks (unless you tick the box below)
- Members + balances (unless you tick the box below)
✓ An automatic backup is taken into backups/pre-reset/ before the
wipe and is never pruned by retention — it's your get-out clause
if you change your mind after.
Optional extras
Confirm
Type the phrase exactly as shown, enter your own PIN (the one you sign in with), and click reset. The PIN is checked freshly here (not the cached session) so this can't be triggered by someone who walked up to a logged-in keyboard.
2 · Full factory reset — wipes EVERYTHING
⚠ This is the migrate-to-a-new-site / decommission button. It wipes the ENTIRE database, not just sales.
What this wipes — everything the "clear sales data" button keeps
- All trading data, members, balances, compliance logs
- Products, categories, modifiers, allergens, beers, pumps, taps
- Tills, layouts, tables, printers
- App settings + DB-stored credentials (SumUp, SMTP, backup/SFTP)
- SumUp reader pairings
- All staff accounts, permissions, rotas
✓ A pre-reset backup is taken first (un-prunable, in backups/pre-reset/).
✓ A bootstrap admin is recreated so you're not locked out — log back
in as John / PIN 0000 (or your BOOTSTRAP_ADMIN_*
env values) and rebuild from there. Change that PIN immediately.
Note: secrets in the .env file (SumUp API keys, SMTP password,
relay/flow/NFC, TLS certs, office PIN) live outside the database and are NOT touched —
rotate those separately when moving sites. DB-stored credentials wiped here are all
re-enterable in admin (SumUp account, SMTP, Backups pages).
Confirm full reset
A deliberately different phrase + a fresh manager-PIN check. There is no undo beyond the pre-reset backup.
About this server
Version, uptime, and basic health. Useful when something feels off and you want to know what build is running.
| Version | — |
| Build | — |
| Uptime | — |
| Node | — |
| Memory (RSS) | — |
| Database | — |
| Hardware mode | — |
| Email enabled | — |