A workshop business does not sell a calendar slot alone. It sells a seat, materials, instructions, a group experience, and sometimes a private buyout that begins as an enquiry and ends as a deposit, guest list, and production plan.
The right workshop booking software keeps that promise legible to both customer and staff. It helps the team see capacity, preparation needs, payment status, participant information, and the next action without turning email into the operating system.
A workshop business normally has three sales motions
| Sale | What is being bought | What the system must handle |
|---|---|---|
| Public class | One or more places at a specific time | Capacity, price, form answers, confirmation, arrival, refund |
| Course or series | A commitment across several dates | Enrolment, attendance, missed-session policy, communication, completion if relevant |
| Private event | A custom group experience | Enquiry, qualification, availability, quote, deposit, balance, requirements, final handoff |
Many tools are excellent at one of these. The purchase decision gets difficult when the business relies on all three. Do not buy software based on the easiest sales motion; buy it based on the one that causes the most manual work or risk.
Map the operation before comparing products
For one real workshop, write down what changes after somebody pays. Do staff prepare a materials list? Are there waivers, allergy details, accessibility needs, age rules, or personalised choices? Can a teacher see the attendee list? Does a late cancellation release material, capacity, or revenue? Is a private group required to pay a balance before the date?
That map tells you whether you need ticketing, appointment scheduling, a course platform, a lightweight sales workflow, or a connected combination. “Workshop software” is a search term, not a uniform product category.
The vendor-demo script
Ask every vendor to run the same scenario:
> A studio is selling a 12-seat public workshop, a four-week course, and a 14-person private birthday booking. One public attendee wants to transfer, one course attendee misses a session, the private group changes its headcount, the deposit has been paid, and the final balance is due next week.
Then ask the vendor to show, not merely describe, the actions below.
Public seats and preparation data
Create capacity, more than one price or ticket type if relevant, a booking form, a discount, and an early sales close. Confirm where the participant’s choices appear for the person preparing materials. If materials depend on choices, the staff export must be usable at the moment it is needed.
Repeating and multi-week sessions
Decide whether the customer is buying a series of independent dates or one course commitment. Those are different products. Ticket Tailor’s published guidance, for example, distinguishes recurring occurrences from a weekly course sold through a single ticket. Its current documentation is a useful reminder to test the actual model rather than equating repeat dates with a course.
Private buyouts
Follow the full process: enquiry, qualification, available date, quote, deposit, terms, balance, guest count, special requirements, and final staff brief. It is fine for a human to manage the conversation. It is risky when the date, scope, money, and next task live only in different email threads.
Forms and sensitive information
Collect only information needed to operate safely and fairly. Ask who can see it, how it travels to staff, whether the customer can correct it, and how the business exports or removes it when appropriate. Have local counsel review waivers, safety language, and retention policy; a booking tool does not make a form legally sufficient.
Cancellation, transfers, and refunds
Test the policy you actually publish. A transfer may change capacity, participant details, materials, revenue, and attendance. A refund needs a clear customer message and a finance record. Confirm who has permission to make each decision.
Capacity and materials: calculate the real constraint
The number of seats is not always the available capacity. A pottery class may be limited by wheels, firing space, clay, or a staff ratio. A cooking workshop may be limited by stations and dietary preparation. A craft activity may have a capacity reduction if a group needs additional assistance.
Create a simple capacity sheet before configuration:
| Constraint | Maximum | What changes it? |
|---|---|---|
| Physical places | 12 | Room layout or a private buyout |
| Staff ratio | 10 | Instructor absence or assistant availability |
| Equipment | 8 | Broken or reserved tools |
| Material kits | 12 | Supplier delivery or personalised choices |
| Safety/accessibility | Set by the activity | Participant needs and local requirements |
Your chosen system should make the binding constraint easy to enforce. It cannot solve a capacity policy the business has never made.
Price the private-event administration honestly
Use your own enquiry volume and times, not a generic ROI promise. If a studio receives 20 qualified private enquiries a month and each takes 35 minutes across emailing, quoting, deposit chasing, and updating a sheet, that is roughly 11.7 hours of admin. Multiply by the studio’s actual loaded hourly cost, then add the risk of a slow reply or a missed balance.
Automation should protect the human part of a custom booking, not remove it. A good process gives the customer a considered response while keeping dates, money, requirements, and staff handoffs visible.
Payment terms and cash flow
Decide and publish the deposit, balance date, cancellation, transfer, and refund policy before software configuration. Then test those terms as a buyer would see them.
If Gomry is on the shortlist, its current public business terms say payout requests are generally processed within one to two business days unless a separate written arrangement applies; actual receipt can vary with payment method and banking systems. Check the terms for the current contractual language. Do not advertise a payout speed, payment method, geography, or refund outcome that your actual account agreement does not support.
Where Gomry fits, and questions that remain
Gomry’s public site lists ticketing, bookings, payments, memberships, distribution, and mobile operations. For a workshop business, the strongest fit is when public classes are only one revenue stream: repeat customers, private groups, memberships, and event-day operations all need a coherent customer and payment context. That is the operating case to demonstrate, rather than asking whether it can merely sell a twelve-seat workshop.
That public description is not proof that Gomry covers every specialised requirement: material planning, complex quoting, course assessment, legal waiver review, or country-specific payments. Bring the vendor-demo script above and get the answers in the product and contract, not in an assumption.
Frequently asked questions
Should workshop software collect waivers?
If the activity requires them, the acceptance record should be connected to the participant and booking. The wording, enforceability, accessibility, and retention policy require appropriate local legal review.
Can I sell add-ons?
Often, but test whether an add-on affects stock, preparation lists, tax, transfers, and refunds correctly. A checkout option is not useful if staff cannot act on it.
How should deposits work?
The customer and staff should be able to see the deposit, outstanding balance, due date, cancellation terms, and current payment state. Avoid a process where the balance is tracked only in email.
Do small workshops need QR check-in?
Not always. A small, stable group may be faster with a straightforward attendance list. Check-in tooling becomes more valuable with multiple entrances, larger volumes, staff handoffs, or frequent changes.
What should be exportable?
At minimum: customers, consents, bookings, attendees, form answers, payments, refunds, memberships, and upcoming obligations. Check how relationships and identifiers appear in the export.