Most betting platforms are written for a browser and later asked to cope with a shop. Ours went the other way: it runs counters with real cash, real printers and real connectivity problems, because that is the business we operate. If you run shops, this is the part of the stack that decides your day.
A shift is a sequence of small operations that have to be quick and unambiguous. That is the whole design brief.
Singles, accumulators and system bets built at the counter, ticket printed immediately.
A winning ticket is scanned and paid — no searching, no manual reference numbers.
Account history, loyalty points and promotions applied from the counter rather than a separate system.
The cashier is told when a price has moved, before the bet is taken.
This is the feature retail operators ask about second and value most. It exists because we lost tickets before we built it.
Tickets keep being taken into a local queue when connectivity drops, and sync automatically once the line returns.
The counter does not stop trading, and the reconciliation at the end of the shift still balances.
Designed against unstable mobile data rather than an office connection, because that is what a shop actually has.
Cash businesses are won or lost at handover. The reporting is built for the person holding the float, not for a quarterly deck.
End-of-shift reports reconcile cash, payouts and float automatically, ready to hand over.
Turnover and payouts by counter and by member of staff.
Several terminals in a shop, several shops in one dashboard, without a separate rollup.
The same customer, balance and bonus rules whether they bet at the counter or on their phone.
Both. It powers our own franchise outlets, and it is licensed to independent bookmakers who run their own estate. If you are looking at opening outlets under our brand instead, the franchise programme is a different offer with different terms.
A standard workstation, a ticket printer and a barcode scanner. We specify against what is available in your market rather than reselling hardware, because import costs and service availability differ far more than the spec does.
Yes. Multiple counters per outlet and multiple outlets under one dashboard, with turnover, payouts and staff performance visible per till. That was a requirement from day one, not an enterprise add-on.
Tickets taken offline are held locally with their own sequence and reconciled on sync, so a shift balances even if the line was down for part of it. Markets that closed while offline are handled at settlement rather than silently accepted.
Each part is a module on the same core — take one, take all of them, or add the rest later as configuration rather than a migration.
