Software

POS System for Pool Halls and Snooker Clubs: What Actually Matters

A pool hall POS is not a supermarket scanner. It has to understand table time, food tickets, and groups that pay separately.

August 4, 2026 · 7 min read · CuePos

Software

Checkout is where clubs lose patience and money. If the POS cannot merge a two-hour session with drinks, staff will round down, forget items, or make guests wait while someone does math on a calculator.

A pool hall POS has a different job than retail or cafe software. Guests occupy timed inventory, order while they play, and often split the bill among friends. The same timed-play reality applies to billiards POS floors. The system has to keep the clock honest while the kitchen keeps moving.

Owners sometimes evaluate POS like they evaluate a card machine: “Does it print a receipt?” That bar is too low. The real bar is whether a tired cashier can close four tables in ten minutes without inventing numbers. If closing depends on a senior staff member’s memory, you do not have a POS — you have a dependency.

POS features built for cue sports

  • Session line items that update with elapsed time.
  • Add F&B without opening a second app.
  • Split payments across friends at the same table.
  • Discounts and comps that require a manager PIN.
  • Receipts guests can screenshot or take on paper.
  • Peak and off-peak rates applied by time of day, not staff memory.

Those features sound obvious until you try to fake them with a “per hour” SKU in a grocery-style till. Mid-session changes, table moves, and midnight rate shifts expose the gap quickly. A purpose-built snooker POS system treats open time as a first-class object, not a product you re-ring every fifteen minutes.

What “good enough” looks like on a normal bill

A normal bill should show play time clearly, list food and drink under the same table, and accept mixed payments without rewriting the ticket. Guests should understand the charge without a speech from the cashier. If every close needs a verbal explanation, the receipt design — or the rate logic — is failing.

Why generic POS tools struggle

Retail POS thinks in SKUs. Clubs think in open time. You can fake a “per hour” product, but you will fight the software every time someone starts late, switches tables, or plays past midnight. Purpose-built session billing is cleaner, and it belongs inside the same checkout as food.

Generic tools also tend to orphan payments. A QR sticker on the wall that is not tied to the open ticket creates “we paid, you didn’t mark it.” Cashless only helps when settlement happens on the bill — see cashless payments.

Another failure mode is kitchen isolation. Cafe software may print tickets beautifully and still leave table time in a notebook. Then closing becomes a merge job: add the timer total, hope the food list is complete, and hope nobody ordered after the last print. That merge is where minutes and items disappear.

Signs you have outgrown a workaround POS

  • Staff keep a parallel notebook “just in case the app is wrong.”
  • Table moves require voiding and recreating a bill.
  • Peak pricing is applied by asking who remembers the wall chart.
  • Splits are done by collecting cash in a pile and guessing.
  • Owners only learn daily sales after messaging the night cashier.

One bill for time and the kitchen

Attach rate dies when guests must close the table, then queue again for food. Kitchen tickets should show a table number. The counter should see the same open session. That single thread is what separates a snooker POS system from two apps that staff reconcile by memory.

If F&B is a real revenue line, inventory and selling items should also connect to what left the ticket. Otherwise “free drinks” and missing chips only show up as a vague margin problem. Pair POS choice with inventory habits.

Train the kitchen language to match the POS: table numbers on tickets, modifiers that matter (spice level, no ice), and a clear path when an item is 86’d. Floor staff should not walk to the kitchen to ask whether fries are still available while a session clock is running and a queue is forming at the counter.

Floor scenario: mid-session order rush

Picture eight tables playing, three drink rounds landing at once, and one guest asking to move because a light flickered. In a linked POS, the move keeps the session, the drinks attach to the correct table, and the light issue can be logged as a manager adjustment later if you choose to comp time. In a split-system world, someone stops the timer “for a second,” forgets to restart, and the drinks ticket floats without a table.

Permissions, voids, and comps

Busy nights create pressure to discount. Software should make comps visible, not easy to hide. Limit who can void. Require a reason when something comes off a bill. Owners who review voids on Monday catch training issues before they become culture.

Set ceilings that match your club. A floor lead might comps a soft drink for a wait; only a manager removes an hour of play. When every courtesy needs the owner’s phone, guests wait and staff stop offering reasonable fixes. When every courtesy is free for anyone, margins erode quietly.

  • Require a reason code on voids above a small amount.
  • Separate “comp item” from “edit closed bill” permissions.
  • Review the void report with the shift lead weekly.
  • Watch for the same SKU voided repeatedly — that is usually a menu or stock issue.

Splits, groups, and payment reality

Cue sports are social. Four friends splitting unevenly is normal, not an edge case. Your POS should let staff assign items or shares without rebuilding the ticket from scratch. If split means “void everything and re-enter,” staff will avoid splits by undercharging or arguing.

Mixed tender is equally normal: cash for snacks, QR for time, card for the rest. Settlement must mark the open bill paid in full, not leave a side note that “they paid on the wall QR.” Orphan payments create the worst guest conflict — they are sure they paid, and your system disagrees.

Closing time test

The real test is Saturday 11:40pm: four tables ending, kitchen still sending fries, two groups splitting. If that scene is calm, your POS is doing its job. If it is a negotiation, you are still reconstructing time by hand.

  1. Stop the session and show elapsed charges immediately.
  2. Confirm open food tickets are on the same bill.
  3. Split cleanly without rewriting the whole ticket.
  4. Mark cash, QR, or card paid against that bill — not a side note.

Run that test in the demo with your actual rate card. Ask the salesperson to play the tired cashier, not the product expert. Speed and clarity under fatigue matter more than a polished slide about “insights.”

Hardware and setup choices that matter

You do not need a retail fortress of scanners and cash drawers on day one. Many clubs run well with a counter tablet, a kitchen printer or display, and a reliable network. Avoid hardware lock-in that forces a full printer replacement before you have proven the workflow.

  • Prefer software that works on devices you can replace locally.
  • Put the counter device on a charged, always-on power plan — dead batteries create paper nights.
  • Test kitchen print latency during a simulated rush, not in an empty room.
  • Keep one spare device configured for backup on peak nights.

Network quality is part of POS reliability. A beautiful system that freezes when the room is full will lose to a simpler tool that stays responsive. Ask how sessions behave during brief disconnects, and what staff should do if a printer jam hits during closing.

What to ask in a demo

  • Show a table switch mid-session without losing time.
  • Show peak rate changing while a session is open.
  • Show a manager-only void with a log entry.
  • Show how the owner sees today’s sales from a phone.
  • Show a four-way split with mixed cash and QR.
  • Show adding kitchen items after play has already started.
  • Show what happens if the counter tablet reconnects after a short outage.

If the demo needs a spreadsheet to explain the bill, the product is not ready for your floor. Choose software that treats timed tables as first-class, then train for speed — not for workarounds.

Migration checklist for POS switches

Map selling items and modifiers before go-live. Align table names with what staff shout across the room. Configure tax or service charges the way your locality actually works, then practice closing — do not only practice starting sessions.

  1. Build the menu and rate card in a staging setup if available.
  2. Train two people to close without the owner present.
  3. Run one quiet night fully on the new POS with paper backup.
  4. Retire parallel notebooks after a supervised peak night.
  5. Compare first-week voids and F&B attach rate to the prior month.

A POS change fails when old and new systems run forever “just for a bit.” Pick a cutover. Support the team through it. Then judge the tool by whether Saturday midnight feels quieter — not by whether the dashboard looks impressive on Monday morning.

Keep reading