Pottery studio booking software: what to look for in 2026

If you search for booking software today, you will find dozens of tools built for hairdressers, driving instructors and yoga studios. Most of them can hold a diary slot and take a payment, and most studio owners try one before finding out it was never built for what a pottery studio actually does on a Saturday afternoon: a table of eight painting together as one party, a six-week course sold as a single purchase, a deposit taken online with the balance settled at the counter, and a shelf of drying and firing pieces the booking system has no idea exists. This is what to actually check before you sign a contract, not what the sales page promises.

Why a generic booking tool runs out of road

A salon books one person into one chair for one hour. A pottery studio books a party of any size onto a table that seats a fixed number, and the two numbers rarely match on the day. Add a birthday group of ten to a studio with benches of six and eight, and a system that only understands "one slot, one person" cannot tell you whether that party fits, let alone which table to give them.

Courses make the gap wider. A six-week wheel throwing course is one purchase with one price, but it needs a register across six dates, a seat that stays reserved even in the week nobody attends because their bowls are still drying, and a waiting list once it fills. None of that maps onto software built around single appointments.

And then there is the kiln, which has no place at all in a hairdresser's diary. A booking ends when the customer leaves in most software. In a pottery studio, the booking is only the start: the piece still has to be glazed, fired, dried and collected, often weeks later, by which point most systems have already forgotten the visit happened.

The six things to check before you sign

Ask about these directly, because a demo built around a generic template will skate past all of them.

Capacity per table, not per head. Availability should be worked out from the tables and seats in the room, including combinations of small tables pushed together for a big group, not from a single "spaces remaining" counter that ignores where people actually sit.

Deposits and pay-on-arrival. Can a customer pay part of the price online to hold their spot and settle the rest at the counter, with that balance visible to the till when they arrive, not buried in a separate report?

Courses with rest weeks. Can a multi-week course be sold and booked as one thing, with a week built in for pieces to dry before glazing, shown honestly on the public page rather than hidden?

Gift cards. Can someone buy a gift card online and have it work at the counter and at checkout, not just as a code a member of staff has to look up by hand?

Waitlists. When a popular class fills, can customers join a waitlist and be notified themselves, rather than a member of staff working through a spreadsheet of names?

A customer record that outlives the booking. Does the system know that the person who painted in March is the same person who bought a gift card in June, or does every visit start from a blank slate?

The drop-off and collection cycle nobody else models

This is the one that catches people out, because it never appears on a generic feature list at all. A pottery visit does not end when the customer walks out. Their piece goes through glazing, waits for a kiln load, fires, dries, and only then is it ready to collect, often two to three weeks after the booking that made it.

Software built for other trades has nothing to say about any of this. So studios build their own patchwork instead: a name on a strip of masking tape stuck to the base of a mug, a photo taken on a staff member's own phone so they can recognise the piece later, a paper list by the till of who still needs to come back. None of it is connected to the booking that started it, and none of it survives a staff change.

What it costs when it is missing

The costs are ordinary and constant rather than dramatic, which is exactly why they get tolerated for too long. A table gets double-booked because two members of staff took bookings over the phone against different views of the same day. A customer messages the studio's WhatsApp asking whether their mugs are ready, and someone has to walk over to the shelf and look, because there is no record that says otherwise. The shelf itself grows quietly through the year: plates and bowls nobody claims, a scene the kiln room ends up living with, things that came out clean and never left.

None of this shows up as one big failure. It shows up as ten minutes lost here, an apologetic phone call there, and a studio where the person who knows what is happening is a person, not a system, so the knowledge leaves whenever they do.

Published pricing and commissions: read the small print

Booking software is usually priced one of two ways: a flat monthly fee, or a percentage taken from every booking you sell through it. Neither is wrong on its own, but they behave very differently as you grow, and it is worth doing the sum for your own numbers rather than trusting a headline figure. A percentage model costs little when you are small and more once you are busy; a monthly plan works the other way round.

Ask, too, who actually pays any booking fee: does it come out of your takings, or is it added to what the customer sees at checkout? And ask what the customer is shown before they pay. Since April 2025, when the Digital Markets, Competition and Consumers Act's rules on drip pricing came into force, the total a customer hands over needs to be visible before they reach checkout, not assembled afterwards from fees that only appear at the final step. If a vendor cannot tell you plainly what a customer will see on their card statement and why, that is worth pressing on before you sign anything.

A short checklist to take to any demo

Take this list into the room and ask the vendor to show you each one live, on their own product, rather than describe it:

• Book a party of ten onto tables that seat six and eight, and watch how it is seated.
• Sell a six-week course as one purchase and see the register and the rest week on the calendar.
• Take a deposit online, then find that balance at the till.
• Move a piece from painted to ready to collected, and see what the customer is told at each stage.
• Sell and redeem a gift card in the same flow.
• Ask what a booking actually costs on the plan you're likely to pick, once you know your own numbers.

Kilndar was built around exactly this cycle, from the first booking to the piece handed back at the counter, with published pricing rather than a sales call. See what it does on the features page.