What software does a play area need, and how do you pick it?

This is a method for choosing rather than a list of vendors. We name no other products and rank nothing, partly because we are one of the options and partly because a ranked list flattens the only differences that matter. What follows is the jobs a play area needs software for, what good looks like in each, the questions worth asking anyone who wants to sell you one, and a trial you write yourself.

Why is "the best indoor playground software" the wrong question?

Because best for whom. A single-floor soft-play centre with two staff, a trampoline park running timed jump slots across three sites, and a family entertainment centre with rides and a restaurant all type the same phrase into the same search box and need entirely different things. A ranked list turns those differences into a score, and the score usually measures how many features a product has rather than whether it runs your Saturday.

The better question: what does my day need, and which system runs it with the fewest workarounds? That one has a real answer, and you can find it yourself in a fortnight with the method below.

The six jobs

Every play area needs the same six jobs done, whether by one system, by several, or by a clipboard. Sorting your own needs into these categories before you look at any product is what keeps the shopping honest.

1. Selling and timing play

The POS, and the thing that knows which child is on the floor and for how long. In a play area these are one job: starting a session is a sale, and the sale starts a clock. The category covers per-child timers, colour wristbands, time-up alerts, overstays, extra time and a live count against capacity. It runs all day, and it is the one to test hardest.

2. Waivers

A signed record for every family before a child plays, findable in seconds while a parent stands in front of you. Digital, QR-signed, versioned when your wording changes, one record per family rather than one per visit. The waiver management guide covers what good looks like.

3. Party bookings

Packages, a calendar, deposits and balances, a public form parents can book on without ringing, and the messages that go out on their own: confirmation, reminder, thank-you. Parties are booked weeks ahead and touched by hand at every step, which is why this is where much of the time saving lives.

4. Passes, loyalty and customer messaging

Multi-visit passes punched at the POS, loyalty stamps, vouchers with a way to validate them, a customer record that remembers the family, and the channels you reach them on. The WhatsApp guide explains why owning your own messaging profile matters more than any feature in this category.

5. Staff, rota and payroll

Who is working when, a clock-in that proves they were there, leave that blocks the rota, and payroll that fits your country. Payroll carries the sharpest local rules of the six: a system built for one country's payroll may be useless for another's. In the UAE that means the WPS file, the SIF and gratuity, covered in the WPS payroll guide.

6. Money, stock and reporting

Shift close and cash reconciliation, bills and purchase orders, stock for the cafe, tax at your own country's rate, a profit and loss you can read, and reports across sites if you have more than one. Plus the dull, vital job underneath all of it: backups you can restore, and an export that lets you leave.

One system or several?

Fewer systems is usually calmer, because the value in a play area is in the joins. A party booking that becomes a sale at the POS, a waiver that follows the family to the timer board, a rota that becomes a payslip: each join is a re-typing you no longer do and a mistake you no longer make. Against that, one system is better only if it does each job properly. An excellent POS beside a token party module will push you back to a spreadsheet for parties inside a month.

So decide per job. For each of the six, ask whether the single-system candidate handles it well enough to replace what you use now. Where it falls short, keep a specialist for that job and make sure the two can at least share a customer export.

What to look for in each category

• Selling and timing play. A sale that starts a timer in one action. A time-up you can see across a loud room. A clean way to add more time, and a separate way to give some. A live count you trust. What the POS does when the internet drops, and what happens to those sales when it returns.
• Waivers. Signed on the parent's own phone from a QR code, with nothing to install. Versioned wording. Search by parent or child name. A clear rule for what happens at the POS when a waiver is missing: a warning is workable, a hard block on a busy Saturday is not.
• Parties. Packages you can edit yourself, including how children beyond the base headcount are charged. A public booking form. Deposits and balances. Reminders on the channel your parents actually use. A month calendar the host can read at a glance.
• Passes and messaging. Passes punched at the POS rather than tracked in a separate app. A request to stop messaging handled properly, everywhere, at once. Your own messaging profile, in your name, that survives changing vendor.
• Staff and payroll. A clock-in that is hard to fake. Leave that blocks the rota rather than sitting beside it. Payroll for your country, producing the files your bank and ministry actually accept, with the accountant still in the loop for what is theirs.
• Money, stock and reporting. A shift close that reconciles. Bills captured without re-typing. Tax rates that match your country rather than a rate assumed for you. Per-site reports if you have sites. Nightly off-site backups, with a restore you have watched work.

Across all six, two things matter more than any single feature. First: can you change every price, package, rate and piece of wording yourself, in the app, without raising a support ticket? A venue's prices move; software that needs the vendor to edit a menu becomes a venue that stops editing its menu. Second: does it run on the devices you already own, in a browser, or does it want you to buy hardware and licence each screen?

Fifteen questions to put to any vendor

Ask every candidate the same list, in writing, and keep the answers. Vagueness on any of them is itself an answer.

1. What hardware do I have to buy, and what runs on the tablets and laptops I already own?
2. What happens at the POS when the internet drops? What happens to those sales when it returns?
3. Is card processing part of your system, or does it sit with my bank's terminal? If it is yours, what are the terms?
4. Can I change every price, package, tax rate, role and piece of message wording myself, without contacting you?
5. Is the price per venue, per device, per user or per transaction? What changes when I open a second site?
6. Who owns my WhatsApp Business profile and message templates: me, or you? What happens to them if I leave?
7. How are backups taken, where are they stored, and can I restore one myself? When did you last test a restore?
8. Which country's payroll rules do you support, and which files does the system produce for my bank and my regulator?
9. Which staff roles can I define? Can a part-timer work the POS without seeing the day's takings?
10. What can I export, in what format, and can I do it myself on any day, including the day I cancel?
11. How long do you keep my data after I leave, and how is it deleted?
12. Which of the six jobs would I still need a second tool for?
13. How do I get my existing customers, passes and party bookings in? Is there a check report before the import commits?
14. Who answers support, in which hours, and what is the route when the POS is down on a Saturday afternoon?
15. Of the things you have just shown me, which are live for customers today and which are still being built?

How do you run a trial properly?

A demo shows you the vendor's best path. A trial on the vendor's sample data shows you the vendor's second-best path. What you need is your own path, so the trial has to be scripted from your own day.

1. Write your Saturday down, hour by hour: opening, the first family, a sibling discount, a party arriving, a time-up during the party, the cafe rush, a parent asking for their waiver, a voucher, the shift close.
2. Put the POS person in front of it, not the owner. Whoever will tap that screen four hundred times a day is the judge.
3. Run the script on each shortlisted system, in the same order, and count the workarounds. Every time somebody says "we would just do that on paper", write it down.
4. Try to break the joins. Does the party booking become a sale? Does the waiver follow the family to the timer board? Does the rota become the payslip?
5. Import your real data as far as the trial allows, and read the check report. A system that takes your customer list cleanly on day one saves you a month.
6. Export it back out before the trial ends. If you struggle to get test data out, you will struggle to get real data out.

Score it simply. Count the workarounds per system across the whole scripted day, and count how many of your must-have lines survived untouched. The winner is usually obvious by the second run-through, and it is often the one with the least impressive demo.

What are the warning signs?

• Export is a support request rather than a button.
• The price is per device, and the devices have to be theirs.
• Every price and package change goes through the vendor.
• The messaging profile would sit in the vendor's name.
• "We will build that for you" is the answer to more than one must-have.
• Backups exist, but nobody can say when a restore was last tried.
• The demo skipped past the shift close.
• The ranking that led you there was written by somebody who is paid when you click.

Switching, once you have chosen

Whatever you pick, the move has the same shape: export from the old system, load it into the new one with a check report before anything commits, review what the report found, set your opening balances, pick a cutover day and keep the old system readable for a while afterwards. The migration guide walks through each step, and the switching page describes what PlayAreaOS takes from a common retail POS export or a spreadsheet. A candidate that struggles to describe its import path in that much detail has not thought about your first week.

A checklist to take into the decision

• Your busy day is written down, hour by hour.
• Your needs are sorted into the six jobs, with the must-haves marked.
• Every candidate answered the same fifteen questions, in writing.
• The POS person ran the script on each shortlisted system and counted the workarounds.
• You imported real data and read the check report.
• You exported it back out again.
• You know, in each candidate's own words, which jobs it leaves to a second tool.
• You know exactly what you get on the day you leave.

Do that, and the ranking you were originally looking for writes itself — for your venue, which is the only ranking that was ever going to be true. What PlayAreaOS covers is set out feature by feature if you want to run the same list against it.