POS for Billiard Halls — Per-Hour Billing + F&B in One System (2026)

1. Why billiard halls need their own POS category

Retail POS platforms (Loyverse, Square, KiotViet, generic Sunmi bundles) were designed to ring up a fixed-price SKU and print a receipt. They cannot price a service that costs S$12 per hour before 6pm and S$18 per hour after 6pm, doesn't finish until the customer racks the balls, and needs to merge with a bar tab that started 40 minutes into the frame.

Purpose-built billiard timer software (the Windows-era desktop tools still sold across SG/MY/PH) solves the timer half, but they were built before cloud POS existed. There is no aggregator queue, no recipe deduction on the bar side, no unified daily P&L, and adding a GCash or DuitNow QR usually means a second terminal on the counter.

So halls end up running two half-solutions in parallel. The manager tells you at close that revenue was ₱48,000; the timer software says ₱31,000 for table time; the POS says ₱17,000 for bar; ₱200 is unexplained. It's always ₱200. LOOP treats the table as a first-class object on the ticket — the timer runs on the same screen as the bar order pad, on the same tablet, against the same customer profile.

2. Per-hour timer + F&B tab on one ticket

The core primitive is a table ticket that has two revenue lines: cue-time and F&B. Staff start the timer with one tap when a group takes a table. Rates switch automatically at your configured peak-hour cutover (weekday 6pm is the SEA norm; weekend 2pm in most PH halls). Drinks and food orders punch to the bar and kitchen, but attach to the same ticket — the customer sees one running tab on a small display at the table, and closes both when they pay.

The cashier doesn't do math. Split-bill by player is a two-tap operation. Add a fourth player who arrived at frame 3 and the timer recalculates their share pro-rata against wall-clock join time, not the whole session. When a corporate group asks for the F&B bill to a separate card and the table time to another, LOOP splits by line type without staff having to reprint anything.

Practical impact: at a 12-table Metro Manila hall running 12pm–2am we've seen this collapse the nightly close from ~35 minutes of manual reconciliation to under 5 minutes of tap-through-and-print.

3. Member pricing via PEKO — where retention actually happens

Halls have naturally loyal customers: leagues, students, regular weekday singles players. The retention problem is not awareness — it is that most halls have no infrastructure to price those members differently at the counter without arguing about it every visit.

PEKO is LOOP's sister loyalty product. When a customer is scanned into PEKO (QR at the table or phone number lookup at the counter), their tier flows into the LOOP ticket automatically: student rate on cue-time, league discount on soft drinks, tournament pack pricing on food. Staff do not remember the rule; the till does. Second-visit conversion in the segments we've measured runs 34–41% inside 90 days against a hall industry baseline nearer 18–22%.

Because PEKO handles the retention side and LOOP handles the ticket side, you don't end up with two loyalty stacks fighting each other, and the pincer holds: booking stays with your existing app (or a whiteboard), operations = LOOP, retention = PEKO.

4. Hardware pattern — what a modern billiard counter looks like

One 10" Android tablet or iPad on a swivel stand at the counter runs LOOP. Timer and orders share the screen. A small 2.4" tableside display per table shows the running tab (optional but reduces "how much do we owe?" friction). An ESC/POS thermal printer at the bar and a second in the kitchen route drinks and food. Payment: PayNow / NETS QR (SG), DuitNow QR (MY), or QR Ph + GCash / Maya (PH) via dynamic per-ticket QR — auto-reconciled against the open ticket so the cashier never keys a reference number.

You do not need a dedicated Windows PC for timer software. You do not need per-table LAN cabling. Offline mode keeps the tablet running through the routine 30-minute power flicker most SEA halls hit twice a month; sync catches up automatically without duplicate tickets.

5. SG / MY / PH context — the local details that matter

Singapore: expect a mostly private-club or lounge-format hall (space is expensive; pure hourly-billed halls are rarer than in PH). GST-formatted receipts are required for GST-registered venues. PayNow load spikes hard at the 11pm last-order push — LOOP's dynamic QR handles the concurrency because reconciliation happens server-side, not on the terminal.

Malaysia: KL, PJ and Penang have a strong mix of dedicated halls and hotel-attached tables. SST rules apply on both cue-time and F&B where the operator is registered. DuitNow QR is the primary rail. LOOP's per-branch pricing model matters here because chain operators typically run 3–8 halls under one operating company and want one consolidated daily brief in the morning.

Philippines: this is the deepest billiard culture in Southeast Asia — from Metro Manila and Cebu commercial halls down to barangay-level 4-table pool rooms, plus the long shadow of Efren Reyes and the cue-sport league scene. BIR-format OR requirements bite hard: your POS must issue serial-numbered receipts with the operator's TIN and VAT breakdown, or the barangay compliance officer will flag it. GCash and Maya account for a majority of tender in most Metro Manila halls after 9pm; card is a distant third.

6. The pincer band — how LOOP fits with booking and loyalty

The honest framing: LOOP is not trying to replace your booking app if you already run one. Bookings for tournament nights or league slots typically live in a lightweight tool (or a WhatsApp group — which is fine, and which we say out loud). LOOP replaces the counter POS + timer stack. PEKO replaces stamp cards and loyalty spreadsheets.

Booking = your reservation tool (companion, not replaced). Operations = LOOP (the counter till + timer + F&B tab + payments + reporting). Retention = PEKO (member tiers, auto-applied pricing, win-back campaigns). That's the pincer. It's honest because none of the three tries to be all of the other two.

7. POS options for billiard halls — an honest mini-comparison

There is no perfect off-the-shelf answer in SEA today. The three real categories are: generic F&B POS (Loyverse, Square, Qashier) — great for the bar, cannot run hourly table timers, so you always run a second system; legacy Windows timer software (still sold via local IT resellers across SG/MY/PH) — solves timers, no cloud, no modern payments, no aggregator, no AI; and unified session + F&B POS (LOOP is the only credible SEA-native option in this row we're aware of in 2026).

The comparison table below is the shortlist we hand to a hall operator asking for a straight recommendation.

Top 5 mistakes new café owners make

1. Buying a Windows-era timer and a separate retail POS "because that's how it's always been done" — you lose 20–40 minutes a night on close, and the cashier will always find ways to pocket the difference.
2. Running the bar on a generic retail POS with no recipe deduction — a 12-table hall shrinks 6–9% of liquor per month invisibly without recipe-level inventory.
3. Ignoring BIR-format receipts in the Philippines because "nobody checks" — barangay compliance sweeps are increasing in Metro Manila in 2025–2026, and back-taxes on a 12-month gap will end the business.
4. Treating loyalty as a stamp card — hall regulars are the most retention-responsive customer type in F&B-adjacent retail, and stamp cards leave ~50% of that value on the table vs a proper tiered PEKO program.
5. Buying a POS without offline mode — SEA halls open late and every operator has been through a 9pm brownout with 8 tables running; if the POS can't take orders offline you lose the whole session's revenue capture.