A service prerequisite stops a pet booking a service until another service is met, or until you set a per-pet override. For drop-in services, Petboost checks this when it builds the service list. For courses, it also checks again when the pet is enrolled.

Open Who Can Book on the service (or the course template) to turn on Require Prerequisite Service, pick one or more services that must come first, then pick What counts as met. If you pick two or more services, How they combine also appears so you can choose whether the pet must meet any of them or all of them.

A cancelled or declined appointment does not count as booked or completed. If the pet's only Initial booking was cancelled, that Initial service is available again. Regular services that require the Initial to be Completed stay locked until the pet sits it.

Completed all sessions is the type to use when the prerequisite is a course. Enrolment creates one appointment per session up front. The next course stays locked while future sessions remain. If the remaining sessions were cancelled (a dropout), the next course unlocks. Use a Not satisfied override if that pet still should not continue.

Booked sibling-equivalence does not apply to Completed all sessions. Completing a different service of the same type does not finish a course.

If you select two or more prerequisite services, How they combine appears. What counts as met still applies to each selected service. How they combine decides how those results combine.

If you select one service only, How they combine is hidden. One service with either match is the same rule.

Use any when two gateway appointments should unlock the same return service. Example: a local drop-off assessment or a bus assessment, then boarding.

An any return service does not consume the unused alternative. A dog that sat the local assessment and then boarded can still book the bus assessment.

Use one gate, then stick to it.

Required badges use all of the listed attributes: the pet must have every one. Blocked badges use any: one matching attribute is enough to refuse the booking.

Shared library attributes and your custom attributes both count. A Business Only custom attribute still gates booking even though the pet owner never sees it. Award and revoke badges on the pet in Manage Attributes. Do not use tags for this.

If a pet is blocked by a badge, that drop-in service is hidden from online booking. A blocked course stays on the list with the reason Not available for this pet. Staff booking still lists both and marks the pet not eligible. Open the service's or course template's Required badges or Blocked badges list to see which attributes apply.

Badges on a course template are the same badges as on its lesson service. Required badges, blocked badges, custom attributes, and the owner-facing reason work the same way on both.

If you set a prerequisite and required badges on the same service, the pet must pass both. Use one gate unless you mean to stack them.

Appointment history is the default. Use a per-pet override when history is the wrong source: a dog trained elsewhere, a migrated graduate, or a failed assessment you are holding back.

If an override already exists, tap its badge. Choose the other state and select Save override, or select Remove override and confirm.

Satisfied treats that prerequisite as met. The next service unlocks without appointment history.

Not satisfied treats that prerequisite as unmet. The next service stays locked until you remove the override, even if the pet later completes the service. If the prerequisite is an Initial assessment, that assessment becomes bookable again, so you can send the pet back for a retake after a fail. After a passed retake, remove the Not satisfied override so appointment history can unlock the next service.

A dropout who had remaining course sessions cancelled will pass Completed all sessions. If they should not continue, add a Not satisfied override on that course service.

Removing the override returns the pet to automatic history.

Overrides live on the pet in your business. They do not copy to the pet owner's global record.

Skip Service Prerequisites is a customer-level override on Settings & Overrides. When it is on, that customer bypasses prerequisite checks for every pet on the account.

Use it when the whole household should book without the gate. Use a per-pet override when only one pet should be treated differently.

Staff can still create a drop-in appointment that the booking form would have hidden. Prerequisite evaluation for drop-in services runs when services are queried, not when that appointment is created. If you need the gate to hold for a drop-in, book from the form or check the pet's eligibility first.

Course enrolment is different. Staff who enrol a pet that fails a badge, prerequisite, capacity or attendance-cap rule must confirm an override. The pet owner booking form cannot override. An attendance-cap override is recorded on the appointment.

An attendance cap limits how many pets carrying a given badge can be in the same class at once. Set the cap on the attribute in Manage Attributes. The cap is checked on every session of the course. If any session would go over, the whole enrolment is refused.

Attribute pricing does not apply to courses. A course is priced on the template and charged once at enrolment, not as a per-pet surcharge on each lesson line.

Duration adjustments on an attribute also do not apply to a course session. Every attendee shares one start and end. Extending the session for one dog would move it for all of them.

Add-on pairing hides an add-on from the booking form unless one of the services you list is already selected for the same pet. It sits on the same Who Can Book tab as prerequisites and appears on add-on services only. A prerequisite reads the pet's appointment history. Add-on pairing reads what is in the booking right now.

Leave it off unless the add-on only makes sense with one or two services. An add-on with no pairing set shows with every service, which is how an add-on behaves until you change it. Retail products are add-ons in Petboost, so a pairing set by mistake hides part of your shop.

To pair an add-on:

You can list more than one service. The pet owner sees the add-on once any one of the paired services is selected for that pet. They do not need to select all of them. If the pet owner then removes the last paired service, Petboost drops the add-on from that pet's booking too and tells them what it removed, so nobody is charged for a line they can no longer see.

Staff booking in the business webapp see every add-on whatever its pairing. The rule applies to the pet owner booking form.

An add-on cannot be paired with another add-on, or with itself. If you archive or delete a service that an add-on is paired with, Petboost refuses the change and names the add-on.

Pairing also covers an add-on a pet owner redeems from a package credit or a membership benefit. Until one of the paired services is in the booking, the add-on is not offered as an extra, and the button to add it from the credit or the benefit stays greyed out with the reason beside it.