Configure checkout fields
Every online booking ends the same way: your client fills in a short form before they pay. You decide what that form asks. It is a two-step idea — first you define a field once for your whole organisation, then you select that field on each thing that can be booked so it gets asked at checkout. This guide walks through the whole pipeline, from creating a field to placing it on a bookable item to seeing it at checkout, with a worked example you can follow step by step.
Define your fields on the Templates page
Open Templates and go to the Fields tab. This is your organisation's master list of custom fields — the place they are created, listed, and reordered. Pick Client in the entity selector (checkout fields are always client fields), then click + to add one. Each field opens in the field editor, covered in detail in Fields.
Worked example — a "Consent to SMS" field. Say you want written agreement before you text appointment reminders.
- Set Type to consent and Entity to Client.
- Give it an Identifier of
smsConsent(letters only, five or more is best). - Fill in the Heading for each of your languages — this is the wording the client actually reads, e.g. "I agree to receive appointment reminders by SMS."
- Enter a Journal type such as
marketing_consent— consent and process fields require this. An optional Interval next to it (once, per calendar year, or every 90/180/365 days) controls how often the client has to re-sign. - Tick Required so it must be answered, and leave Show in table off so it does not clutter your client list.
Choosing consent automatically ticks Show in profile, and the field will always appear read-only in the dashboard — only the client can sign it, on the booking page itself. Save, and it joins your master list.
A second field — "Allergies". Add another: Type textbox, Identifier allergies, a heading of "Any allergies we should know about?", and leave it optional. A textbox defaults to a 50-character limit, which you can raise on the same screen. Save it too.
Select those fields at checkout
Defining a field does not, by itself, ask anyone anything. You now choose it on each bookable item. Open the booking template you set up in Set up online booking and go to its Fields tab (treatments, session resources, and products each have the same tab).
You will see your full client-field list with a Use field checkbox on each row, plus columns showing Required, Self-managed, Scope, and Type. Tick Use field for Consent to SMS and Allergies, then drag the rows to set the order the client sees them. Save. Behind the scenes this stores a simple ordered list of the fields you picked, so your booking page now knows to ask for exactly these two.
What the customer is actually asked
Here is the part worth understanding. At Online booking checkout, the form is not taken from a single template. The customer is asked for the merged, de-duplicated set of fields from every item in their cart — each session's fields, each product's fields, and your organisation-wide fields, combined in that order with duplicates removed.
So if a client books a massage (whose template asks for Allergies and Consent to SMS) and adds a gift voucher product (which asks for a Recipient name), the single checkout form they see contains all three fields once each — even though you configured them on unrelated screens. Ask only for what you genuinely need on each item; the cart does the assembling for you.
One field appears without you choosing it: whenever there is an amount to pay, a billing address becomes required. A free booking skips it.
That is the whole pipeline — define once on the Fields tab, select per item, and let checkout merge the result into the exact form your client fills in.