HOW IT WORKS

Follow the work once. Update the business automatically.

The same operational event should not have to be entered again in a spreadsheet later. LeisureOS connects the customer action, staff action and management record from the start.

A NORMAL TABLE SESSION

What happens from the customer’s first scan to the final report.

The workflow is designed to stay understandable for the customer, the staff member and the owner at the same time.

01

The customer scans the table QR

The signed QR securely identifies the venue, branch and table. The customer does not need to create an account or install an app.

02

The customer places the first order

The server loads current menu prices, creates or uses the live table session, and makes the new table visible to eligible staff.

03

One staff member accepts responsibility

The first eligible staff member to claim the table becomes its assigned owner. Follow-up orders and service requests route back to that person.

04

The order is accepted and served

Serving the order records the sale and, where the menu item is connected to stock, deducts inventory and snapshots the real item cost.

05

The customer sees one running bill

Additional orders stay inside the same session, so the customer and staff see one bill rather than separate disconnected transactions.

06

Payment is recorded against the real balance

Staff can record Cash, POS or Transfer payments, including part payments. The system will not allow recorded payments to exceed the outstanding balance.

07

The table closes only when the session is settled

Once there are no unserved orders and no outstanding balance, the table can be closed and is ready for the next session.

08

Management reports are already updated

Revenue, cash received, outstanding, COGS, gross profit, inventory and staff activity are based on what actually happened in the same workflow.

THE ACCOUNTING FLOW

Revenue is not the same thing as money received.

LeisureOS keeps these concepts separate so the dashboard does not make the business look healthier or worse than it really is.

Sale is served
→
Revenue is recognized
→
COGS is snapshotted
Customer pays
→
Cash received increases
→
Outstanding falls
OTHER OPERATIONS

The same logic continues beyond table service.

P

Pool admissions

Admission value becomes revenue when access begins. Payments remain separate from outstanding balances.

B

Bookings

Deposits can be collected before the service is earned, and overlapping resource bookings are blocked server-side.

R

Reports

Reports read the operational records rather than recalculating from prototype estimates or browser data.

SEE IT IN YOUR VENUE

Set up your first branch and work through a real service flow.

View product