A service is the core building block of your Nabooki account — it defines what you're offering, who can book it, and how it's organised for your customers.
Before you start building, it helps to understand how services are structured. The four concepts below shape what your customers see on your booking page and how your offerings are grouped and managed behind the scenes.
This article covers:
If you're ready to configure how your service behaves — things like booking type, location, and timing rules — head to Service Behaviour: Key Concepts.
Sub-services are variations of a single parent service that share the same schedule and capacity. You can't control their availability independently — they all live on the same timetable.
Think of them as: different ways to buy the same experience.
Example — Yoga Class:
All three appear on the same schedule. A customer picks which package suits them, but they're attending the exact same session.
Use sub-services when:
Service options are fully independent variations grouped under one service. Each option has its own schedule, capacity, and staff — essentially its own bookable product.
Think of them as: different ways to run the same service.
Example — Kayak Tour:
Each operates on its own terms, but they're logically grouped so customers can compare and choose.
Use service options when:
Price categories are different prices applied to the same booking. They don't affect the schedule, capacity, or any operational setup — they only change what someone pays.
Think of them as: who is booking, not what is being booked.
Example — Museum Entry:
Same session, same seat, same everything — just a different price depending on who shows up.
Use price categories when:
Categories are organisational labels only. They have no effect on bookings, pricing, capacity, or availability — they simply group services together in the dashboard.
Think of them as: folders or tags for your own navigation.
Examples:
Use categories when:
Concept | Schedule | Capacity | Prime Purpose |
Sub-services | Shared | Shared | Same service, different packaging. |
Service Options | Seperate | Seperate | Different ways to run the service. |
| Price Categories | Shared | Shared | Different prices per person. |
Here are 5 tourism operator scenarios mapped to each concept:
A operator runs a single 3-hour whale watching cruise each morning. They want to sell individual tickets, family passes, and annual memberships — all for the same departure.
| Concept | Application |
| Sub-services | Individual Ticket / Family Pass / Annual Membership — same boat, same time |
| Service Options | Not needed — there's only one way the cruise runs |
| Price Categories | Adult / Child / Senior pricing within each ticket type |
| Categories | "Cruises" or "Marine Tours" |
Key decision: The passes are sub-services (not price categories) because they represent different products being sold, not just different prices for the same seat.
A studio runs weekly classes — Vinyasa, Yin, and Breathwork — on a fixed timetable. They want to sell casual visits, 10-class packs, and monthly unlimited memberships.
| Concept | Application |
| Sub-services | Casual Pass / 10-Class Pack / Monthly Unlimited — same classes, same timetable |
| Service Options | Not needed — all members attend the same classes |
| Price Categories | Adult / Student / Concession |
| Categories | "Guided Walks" or "Nature Experiences" |
| Concept | Application |
| Sub-services | Not needed — the variations are operationally different |
| Service Options | Morning Group Tour / Sunset Tour / Private Charter — each has its own schedule, guide, and capacity |
| Price Categories | Adult / Child within each option |
| Categories | "Water Activities" |
Key decision: Because each tour runs differently, these must be service options — not sub-services. A sunset tour with 6 spots and a different guide can't share a schedule with a morning group tour.
An operator offers a single guided bush walk. The walk itself never changes, but they sell it as a casual drop-in, a 4-walk bundle, or a season pass.
| Concept | Application |
| Sub-services | Drop-In Walk / 4-Walk Bundle / Season Pass — same trail, same guide roster, same time slots |
| Service Options | Not needed — the walk is always the same experience |
| Price Categories | Adult / Child / Concession |
| Categories | "Guided Walks" or "Nature Experiences" |
Key decision: This is the clearest sub-service use case — the experience is identical, only the purchase format changes.
A clinic offers remedial massage, relaxation massage, and hot stone massage. Each requires different therapist training, different room setup, and different booking lengths.
| Concept | Application |
| Sub-services | Not needed — each massage type runs completely differently |
| Service Options | Remedial (60min, therapist A) / Relaxation (45min, therapist B) / Hot Stone (75min, therapist C) |
| Price Categories | Standard / Health Fund Member (different out-of-pocket price) |
| Categories | "Massage" or "Bodywork" |
Key decision: Even though it's all massage, each type is operationally distinct — different duration, different therapist, different setup. These must be service options, not sub-services.
An operator runs a full-day reef trip and wants to offer it as a standard ticket, a premium ticket (includes equipment hire), and a photography add-on package — all on the same boat departure.
| Concept | Application |
| Sub-services | Standard / Premium (with gear) / Photography Package — same boat, same reef, same departure |
| Service Options | Not needed — it's all the same trip |
| Price Categories | Adult / Child / Concession within each sub-service |
| Categories | "Reef Experiences" or "Day Trips" |
Key decision: The premium and photography packages might feel like they should be separate services, but since they all depart together and share the same capacity, sub-services keeps the backend simple — one schedule to manage.
| Signal | Use This |
| Same time, same resources, different purchase format | Sub-Services |
| Different times, staff, or capacity | Service Options |
| Same session, different type of person paying | Price Categories |
| Just needs a label in the dashboard | Categories |