A play room or a VR club is a business where the value isn't in the number of rides, but in how much time a guest spent inside. For formats like this, RentOS has a separate accounting mode — "Stays": not a counter reading, not a manual total at the end of the shift, but real time recorded the moment it happens.

A Wristband at Entry, a Stop at Exit
A typical picture: every child gets a numbered wristband at the entrance, the employee starts a launch by that number in the PWA — and stops it when the child leaves. Time runs from start to stop, with no pauses, and it's tracked not by the employee's phone but by the server: even if the app restarts or the device changes, the count doesn't skip or reset.
There can be any number of open launches at once — it's rarely just one child at the entrance at a time. Wristband numbers don't just keep climbing forever: once number four frees up, the next child gets number four, not number five. Every asset in a zone has its own separate set of numbers, so the same number can easily be in use on two different assets at the same time.
Two Ways to Calculate the Price
The Owner picks one of two rate options for a zone. "Per Entry" is a fixed price — the employee picks the needed duration (say, one or two hours) right when handing out the wristband, and payment is taken right away at the start. "Per Fact" is a price for the actual time spent, with minutes rounded up, and payment is asked for at exit, once the time is known.
The Owner Doesn't Watch Every Wristband — and Shouldn't Have To
RentOS has no "live monitoring" screen of open launches for the Owner, and that's a deliberate choice: an employee on-site sees what's happening in the zone better than an Owner watching through an app. The only thing available to the Owner after the fact is voiding a specific mistaken entry, if one slipped into an already-submitted day. There's no auto-stop either: time isn't invented by the system, only what the employee actually recorded.
The Till — Per Asset, Not One Line for the Whole Zone
At results submission, the system calculates on its own how much should have come in from launches finished during the shift — separately for each asset. The employee enters next to it how much cash and non-cash was actually collected, and immediately sees the gap between the calculation and the fact — per asset, not as one lump figure for the whole zone. As long as unclosed launches remain in the zone, results can't be submitted — the system will state exactly how many launches need to be finished first.
How This Differs From Counter-Based Tracking
If the previous article was about rides — electric cars, go-karts, where the number of rides is counted — here it's time spent inside that's counted. Different businesses by nature, but the same underlying principle: the system calculates what should have come in on its own, and the person only enters what actually ended up in the till.