Soft-play and kids’ birthday booking: rooms, packages, deposits
Saturday at 3 pm is one slot, not “we will squeeze a second group”. Soft play lives on birthdays and weekends. A room calendar, a package (host, cake, hours) and a deposit — instead of Facebook and two bookings on the same room.
A play centre sells weekend windows and a package (2 h room + host + a printed cup + cake). Parents search “kids birthday [city] soft play” and want to see a free Saturday 15:00, not message you. A double-booked room is two families at the door, a reputation hit and an evening you cannot sell twice. bday.love (bookings + deposits, from about 199 PLN/month, 0% cut on bookings), BookGame, OOS Manager, Going Places — ready tools for kids’ parties. Fine for one room and three packages. They break when you have room A/B, a garden, weekday open play, two hosts and a cake kitchen.
Owners who answered the phone all weekend, after a calendar with payment, have a three-week diary on Monday and money in the account — that is a real bday.love-style outcome, not a slogan. Birthday no-shows without a deposit are common: “we moved it, we didn’t call”. The same lever as the empty-hour article: deposit + reminder + a waitlist for Saturday 15:00.
What the system must guard
- Rooms / zones as resources (small, large, garden, VIP) with child and adult caps — fire rules and house rules, not “they’ll fit”.
- Packages: open-play hour, standard / premium birthday, sleepover, christening — different cleanup time after the event (a 30–60 min buffer).
- Host, kitchen, décor, photo booth as separate calendars (do not promise the same clown twice at 15:00).
- An online deposit (BLIK/card); unpaid slots return after 12–24 h. Balance at the door or pay-in-full.
- Weekday open-play tickets like event tickets, with a safety cap on the floor.
- SMS: confirm, day-before, what to bring, a post-visit note. Cake diet / allergen in the form.
- A name list for the party and photo consent — minimum data, retention like a preschool.
Weekday open play vs weekend birthdays — two products
Two businesses in one site. The system must lock open play on room A when a birthday sits 15–17. Staff see the day: 10–14 open (tickets, cap 40), 15–17 birthday room A, room B free for open play or a second party. Parents must not see “free” if the safety cap is full or an event is on. Mixing open-play till with a birthday pack in one notebook ends with 15 unknown kids walking into someone’s party.
Package pricing: children included, extra per child, adults (often free or capped), veg diet, piñata, extra host. The form computes it at booking or leaves “on approval” for odd requests. Parents should see the price up front on a standard pack — otherwise they return to Messenger, which is what you were leaving.
Host and kitchen are not “a note on the booking”
Clown, host, cake cook — resources with their own graph. Two 15:00 birthdays in two rooms need two people or a “no host” pack. The kitchen has a cake cutoff like catering: “flavour and icing text by Wednesday”. A system that does not know that promises a cake that does not exist. A cousin of an escape room: slot + cleanup + a person. Not “a free room in Excel”.
Room-hire SaaS or your own system
One space, three packages — bday.love, BookGame or a generic calendar with a deposit. Custom when: several rooms, hosts, open-play till plus parties, a door tablet (guest list, open ticket, extras), a chain under one brand, or you want 0% cut and SEO “soft play [estate]” on your domain. A kids-party marketplace can be a channel; the parent should stay with you for the sibling’s second birthday.
- MVP: room calendar + packages + deposit + day-before SMS.
- Open play vs birthday lock. A headcount cap.
- Host and kitchen as resources. Diet / photo-consent form.
- Weekday open tickets when the queue needs it.
- A second site, a gate tablet, open-play passes.
Tell us room count, open-play and host, how you take deposits and whether Saturday doubles hurt. MVP: birthday calendar + deposit. Open-play tickets when the weekday queue needs them, not forced into the first sprint.
Weekend is till, Tuesday is open play — how not to kill both
Saturday 12:00, 15:00, 17:30 are three slots, not “continuous flow”. Each has cleanup, a host, a cake, a child cap. Sunday similar, weaker. Tue–Thu: open play with an hourly ticket, another till, another cap, other staff. A system that does not lock open play on room A during a birthday lets strangers onto the cake. A system that does not sell open play leaves Tuesday empty. bday.love and BookGame run birthdays with a deposit; open play is often a second product we add as tickets with a headcount cap. An open-play pass (10 entries) is estate revenue — decrement at a gate tablet, not a slip.
Weekend staff: host 1 and 2, kitchen, a gate person, cleanup. A graph like an event, not a beauty salon. A host ill Friday night: an internal waitlist or an SMS to the parent “pack without host / move / other room”. Without a “host” resource you promise a clown who is not there. Sleepovers and christenings: another buffer, another consent, another quote — a separate type, not “birthday × 3”.
Child data, photos, an allergen on the cake
A name list for the party, age, allergen (nut on the cake), photo consent, parent phone. Minimum. Retention after the event — you delete the list after X days, photos only with social consent. No national ID, no nursery file. The same approach as a preschool, lighter. The kitchen gets an allergen cutoff, not “mum will write on FB Saturday morning”.
A chain of two–three sites under one brand: shared prices, separate diaries, a parent with a second child in the second site without a second account. Custom starts here, not at one room and a 199 PLN widget. How many rooms, open play or birthdays only.
Gate, tablet, open-play ticket, extra child
Saturday 14:50 at the gate: a birthday family and three open-play people. Staff must in 10 seconds: check the pack list, tick adults, let in or sell an open ticket for room B, refuse when room A’s cap is full. A door tablet with two paths (booking code / hourly ticket) is till and safety, not a gadget. Extra for the 11th child, a diet, an extra hour — on site, on the same bill, not “I’ll add it on a slip”. The fiscal till stays a till; the system holds the cap and the list. A 10-entry open pass: scan at the gate, child on the parent, not “a card in a wallet they lost”.
Reviews and Google: an SMS after the event asking for a review, not during the cake. Photo consent for the party is separate — without it we do not post faces on the venue Instagram. A “the host was late” complaint: resource status in the diary is your defence, not a Messenger memory. A chain: one parent number, two diaries, the same pack in the second city for a sibling’s 7th. That is when a 199 PLN widget stops being enough. Gate, passes, second site.
What we do not promise in a play centre
We do not certify the venue for the fire service. We are not a fiscal till. We do not keep a nursery file. We watch rooms, packs, deposit, headcount and the host graph. The rest is your house rules and your bookkeeper. An MVP that survives the first Saturday: three slots, a deposit, a list, a day-before SMS. Open play and a tablet — when the Tuesday queue or gate chaos really hurts, not when “everyone has an app”.
The host is ill, the cake did not arrive, a second group at 15:05
Three weekend disasters Messenger will not run. Host as a resource: cover from a list, SMS to the parent, an extra or a discount. Cake: kitchen cutoff, allergen, status “in the oven / ready”. A second group at 15:05: the diary does not show free, because 15:00 + 40 min cleanup. A waitlist for 15:00 gets the slot when someone does not pay a deposit in 24 h. bday.love closes that on one room. Several rooms, open play and a gate — we add a tablet and a cap. We do not promise the system will bake a sponge.
Package prices should be on the site, not in a PDF the parent loses. Extra per child in the form. A birthday voucher (code, validity, room) is phase two after the deposit. A company kids’ day: invoice, several rooms at one hour, another consent. That is an event, not “a large birthday”. KSeF when the company pays from the panel. Staff see the day like a game master in an escape room: who enters, what is in the pack, what to clean.
Fire cap, adults, a pram at the gate
House rules and fire rules give a headcount, not “they’ll fit”. The system enforces a child and adult cap on the room. A pram, a sibling outside the pack, a host — they count too if you write it that way. The parent on the site sees “4 places left”, not a free slot that is physically full. That is safety and reputation: two families at 15:00 is not only a refund, it is a TikTok. We do not certify the venue. You set the cap; the diary holds it.
Adults often enter free, but with a cap (e.g. 2 per 10 children). The form counts it. Photo consent for children is not the same as SMS consent for the date. Two checkboxes, retention of the name list after the event. Gate staff see who is on the list, who paid extra, who is open play. Without a tablet you return to the notebook on the first wet weekend. Room cap, adults, whether open play mixes with cake.
A Saturday 15:00 MVP
Three rooms or one — a calendar with a cleanup buffer, a pack with a child cap, a 24 h deposit, a day-before SMS, the host as a resource. Open play and a gate tablet we add when Tuesday or the cake queue needs it. We leave bday.love on one room. Custom when open play mixes with birthdays and you have a second site. Child data: a list and consent, not a nursery file. Weekend slots, open play, whether you already doubled 15:00.
A waitlist for Saturday 15:00 pays back in the first month someone misses a deposit. The listed parent gets “a slot freed, 30 min to pay”. Without a waitlist 15:00 sits empty and the second family already went to a competitor. Same mechanics as an escape room and a salon — only the weekend rate is higher.
Tuesday open play and a 15:00 birthday — two businesses
Saturday 12:00 / 15:00 / 17:30 are three slots with a 30–60 min cleanup buffer, not continuous flow. The system locks open play on room A when a birthday pack sits there. bday.love (from ~199 PLN/month, 0% cut on bookings) closes a deposit on one room. BookGame, OOS Manager, Going Places — kin. They break with room A/B, a host, a cake kitchen and weekday open play. The headcount cap is fire rules and house rules, not “they’ll fit”. The system enforces the cap; it does not certify the venue.
- Host and kitchen as resources: two 15:00 birthdays need two people or a no-clown pack.
- A cake cutoff like catering: flavour and icing text by Wednesday, allergen in the form.
- A 20–50% deposit, the slot returns after 12–24 h unpaid, a waitlist for 15:00.
- A name list and photo consent — minimum data, retention like a preschool, no national ID.
A gate tablet and an open-play pass
14:50: a birthday family and three open-play people. Staff in 10 seconds check a pack code or sell a ticket for room B. A tablet with two paths is till and safety. A 10-entry pass decrements at the gate. The receipt stays on the fiscal till — we do not fake a printer. A company kids’ day: invoice, several rooms, another consent — an event, not “a large birthday”.
Sleepovers, christenings and a voucher for a seventh birthday
That is not “birthday × 3”. Another duration, another cleanup buffer, another consent (adults at a company event), another quote. A voucher: code, validity, room, pack — phase two after the deposit. A two-site chain: one parent, two diaries, the same child for a sibling’s 7th in the other city without a second account. A 199 PLN widget stops being enough here. Reviews: SMS after the event, not during the cake. Photo consent separate from SMS consent for the date.
Frequently asked questions
- Is the price shown up front?
- Yes on a standard package. Extras (more children, diet, extra host) in the form or after you accept an odd request. A hidden price returns people to Messenger.
- Adult caps / children’s GDPR?
- A name list and photo consent in the form. Child data like preschool: minimum and retention. We do not collect national IDs “just in case”.
- A fiscal till for open play?
- The system sells the ticket and the cap; the receipt stays on your till. We do not fake a printer. Open play and birthdays may use different documents — that is your books.
- Several sites?
- One brand, separate room diaries, a shared package list, a shared parent file (second child, second site).
- bday.love / BookGame instead of custom?
- One room, a deposit, a widget — often yes. Custom for several rooms, open play + parties, hosts, a gate tablet and a chain. We do not replace a working widget if Saturdays are clean.
- No-shows without a deposit?
- Common. A 20–50% deposit + day-before SMS + waitlist. A “write to us” form will not cut them. Saturday 15:00 is not recoverable.
- Sleepovers / christenings / corporate kids’ days?
- A separate package type, another duration, another cleanup buffer, another consent (adults at a company event). Do not force it into “birthday 2 h”.
- How long is an MVP?
- Room calendar + package + deposit: weeks if the price list is clear. Open tickets, a second host, a gate tablet — after a first month of Saturdays without doubles.
Describe your project