Pre-release Documentation for Ascent Direct Booking. Not yet approved for commercial release. View availability details
Services
The locally accepted service editor, plus catalogue behaviour the later pilot did not re-run.
Creating and editing a service, choosing who can perform it, and weekly hours were accepted as a local slice on 22 October 2026. Candidate 1.2.104 is a later, unaccepted whole. Stored timings were kept on an upgrade in that later pilot.
The owner can add and edit a bookable service, including who can perform it.
Previously accepted slice, carried forward
The 22 October 2026 slice accepted service and practitioner edits, including eligibility. Failed creates were repaired in that slice so one record could be resumed. The 1.2.104 pilot did not repeat the service form.
Before you start. Currency must already match the business. A stale form must not overwrite a newer save; that rule was part of the accepted slice.
Limit. Several services in one visit were not re-verified. Archiving a service was not repeated in the 1.2.104 ledger. The whole candidate is not commercially accepted.
Technical details
Why it matters. The business publishes its own treatments instead of waiting for a vendor to type them in.
Example. The owner adds a 45-minute service, sets a price in the business currency, and chooses the practitioners who can perform it.
Who uses it. The business owner. The owner catalogue.
Status: Cited local evidence. This is not commercial acceptance. Origin: Accepted as a local slice, then carried into 1.2.104. Not rerun on the fresh pilot. Candidate 1.2.104 is not an accepted commercial release. M2A local acceptance dated 2026-10-22. The later 1.2.104 candidate contains that slice and is not accepted as a whole. This guide did not re-run the slice.
Scoped reading. A named appointment, its price in the business currency, and its duration live on one service record. An initial visit and a follow-up are two records when they differ. A 30-minute session and a 60-minute session are also two records, not a duration picker. A cut and beard written as one service is still one record, not several services added during booking. Duration-led choices, Combined appointment, Massage practices, Barbers
Stored duration and buffer times
An upgrade kept stored service timings and buffer values on the cloned site.
New pilot result on 1.2.104
The populated upgrade clone preserved timings and buffers. The pilot did not show a fresh edit of preparation or cleanup time.
Before you start. Values that were already stored. Creating a new buffer was part of the earlier services slice, not a new 1.2.104 check.
Limit. Keeping a stored buffer is not a new editor demonstration. This guide does not claim a specific buffer length as a default for every business.
Technical details
Why it matters. Existing appointments and catalogue timings are not silently rewritten because the plugin was updated.
Example. A service that already had a cleanup buffer still has that buffer after the candidate is activated twice.
Who uses it. The business owner, for the stored values. The catalogue data kept by the upgrade.
Status: Cited local evidence. This is not commercial acceptance. Origin: New result recorded on the 1.2.104 local pilot. This guide did not re-run that pilot. Candidate 1.2.104 is not an accepted commercial release. R11 local-pilot ledger, record dated 2026-10-24. This guide did not re-run the pilot. Candidate 1.2.104 is not an accepted commercial release.
It is not determined whether a customer can book more than one service in a single visit on 1.2.104.
Not determined
Older source inventory marked the idea as present and not runtime-tested in that audit. The 1.2.104 ledger does not record a combined visit.
Before you start. Unresolved.
Limit. Do not sell combined treatments as included. Booked historical lines, where they exist, are a different fact from a new combined booking.
Technical details
Why it matters. Businesses need a straight answer before they promise combined appointments. The honest answer is that this guide does not have one.
Example. A customer tries to add a second treatment before confirming. Do not promise that the page allows it.
Who uses it. Unknown. The public booking page, if a future check shows the control.
Status: Not determined. Origin: Not determined. Candidate 1.2.104 is not an accepted commercial release. Not verified for this guide. Described as unresolved rather than as an available feature.
It is not determined here what a customer sees after a service is archived, beyond the upgrade keeping stored timings.
Not determined
The upgrade kept stored prices and timings. An archive action was not the 1.2.104 check.
Before you start. Unresolved for the archive action.
Limit. Do not promise that historical booked prices survive every catalogue edit until that case is re-checked. Do not promise that archiving deletes history either.
Technical details
Why it matters. Existing bookings should keep the facts they were booked with. This guide does not have a fresh archive demonstration.
Example. The owner hides a service and expects old visits to keep their original name and price. Treat that expectation as unverified here.
Who uses it. The business owner. The catalogue.
Status: Not determined. Origin: Not determined. Candidate 1.2.104 is not an accepted commercial release. Not verified for this guide. Described as unresolved rather than as an available feature.
The accepted M2A review AB-SELF-SERVICE-M2A-R3, candidate 1.2.90-ab-self-service.m2ar3, states that service price and timing edits preserved stored appointment snapshots. That review also describes archive and pause impact handling inside the slice. This was not rerun on 1.2.104. It does not establish every later edit, archive, or reschedule on 1.2.104, and it does not establish pausing or reopening public booking.
Gap. Not established.
Treatment CSV updates
Updating services from a CSV is not established. The accepted service editor is a manual edit. It does not import or update services from a spreadsheet.
Not determined.
Timing bulk edits
Bulk edits of timings were not determined. The archive record asks what a customer sees after one service is archived, and that too is not determined. Archive is not a bulk timing editor.