Why recurring appointments matter
Your best customers come back on a cadence — color every six weeks, weekly training sessions, monthly maintenance. Most booking tools treat every visit as a one-off. Merchants rebook by hand at the end of each appointment, or hope the client remembers to return.
Recurring appointment workflows turn that cadence into a real series on the schedule instead of a sticky note.
The merchant workflow
- Define the service, staff, and recurrence pattern.
- Create the recurring series (frequency and start — confirm available patterns during onboarding).
- Revenu generates instances on the schedule from that pattern (`AppointmentService.createRecurringAppointment()`).
- Reminders can go out per instance when configured.
- Staff see each visit on the same booking record as one-off appointments.
Verify before publish: Supported frequency patterns (weekly, biweekly, monthly, custom), whether customers can self-book a series on the storefront, and how editing one instance vs the whole series works — confirm during early access onboarding.
Recurring vs packages
| | Recurring appointments | Appointment packages | | -------------- | ---------------------------------------- | ----------------------------------- | | What it is | Scheduled instances on a cadence | Prepaid sessions redeemed over time | | Payment | Per visit / deposit rules as configured | Up-front package purchase | | Best for | Standing bookings (same day/time rhythm) | Bundled series sold as one SKU |
Cross-link: appointment packages for prepaid bundles; this page is for scheduled repeat visits.
Where Revenu fits
- Recurring pattern creation and instance generation in `AppointmentService`
- Same services, staff, and booking data as core appointment booking
- Staff scheduling for multi-provider shops
- Reminders per instance when enabled
Verify before publish: Deposit or payment behavior per recurring instance — confirm on demo before claiming a specific checkout path.
Use case: standing weekly session
A coach sells a weekly 1:1 session. The merchant sets a recurring pattern, generates the next months of instances, and the calendar stays full without manual rebooking after every visit.
Merchant checklist
- List which services are truly recurring vs one-off.
- Confirm frequency options and who creates the series (admin vs customer).
- Align staff availability with the generated instances.
- Turn on reminders for each instance.
- Train the desk on editing one date vs the whole series (confirm behavior on demo).
Common mistakes
- Manual rebooking for every regular client.
- Selling a "package" when the merchant really needs a standing calendar series (or the reverse).
- No reminder on recurring instances — same no-show risk as one-offs.
- Promising retention or LTV percentages without your own data.
FAQ
Can customers set up recurrence themselves?
Verify before publish: Storefront self-serve recurrence vs admin-created series — confirm for your shop during onboarding.
How do I change one date in a series?
Verify before publish: Edit-one vs edit-all behavior — confirm on demo before publishing step-by-step instructions.
Deposits on recurring visits?
See booking deposits and confirm per-instance payment during onboarding.
Get early access
Request early access for recurring appointments inside Shopify-native booking.