BookingIncluded on every planImproved in v3.1.1

Collect exactly
the info you need.

Add custom checkout fields, text, dropdowns, checkboxes, conditional logic, and plain text displays, to capture device passcodes, serial numbers, or consent forms during booking.

Get started View documentation

field types

width options (50%, 100%)

100%

translatable

Checkout Field Editor

Field configuration

⋮⋮⋮⋮⋮⋮

Namecore

Text · 50% · required

⋮⋮⋮⋮⋮⋮

Phonecore

Text · 50% · required

⋮⋮⋮⋮⋮⋮

Device passcode

Pattern · 50%

{custom_device_passcode}

⋮⋮⋮⋮⋮⋮

☐

I confirm data backup

Checkbox · 100% · required

⋮⋮⋮⋮⋮⋮

▾

Preferred contact

Dropdown · 50%

⋮⋮⋮⋮⋮⋮

Terms and conditionsv3.1.1

Plain text · 100%

9 field types · drag to reorderSettings, Checkout & Discount

New in 3.1.1

Plain text

field type

Why repair shops choose it

Your checkout, your fields.

Capture every piece of info you need to start a repair, without bolt-on form plugins or messy custom code.

9 field types

Text

Number

Textarea

▾

Dropdown

☐

Checkbox

◉

Radio

Pattern

Plain text

+ Plain text in v3.1.1

9field types

Every input type you need

Choose from Text, Email, Number, Textarea, Dropdown, Checkbox, Radio, Pattern, and Plain text field types. The Plain text type (added in v3.1.1) lets you display static terms, disclaimers, or instructions that don't need customer input.

Show on

Come by our store

Ship device

Pickup service

Repair on location

Return address only on Ship

4delivery methods

Show fields per delivery method

Restrict any custom field to specific service methods, Come by our store, Ship device, Pickup service, or Repair on your location. Show a return address field only for Ship device or a preferred time field only for Pickup service. Customers only see fields relevant to their chosen delivery method, and at least one method must be selected.

Visibility rules

IF "Has insurance" = Yes

Any · All

Show: Policy number

Show: Provider

Any / Allcondition relations

Smart conditional visibility

Set up rules so fields only appear based on what the customer selects. Use Checkbox, Radio, or Dropdown fields as triggers, and show dependent fields only when specific options are chosen. Set the Conditions Relation to Any or All to control how multiple conditions combine.

Email + webhook

{custom_device_passcode}

✉Email template

⚡Webhook payload

Email + Webhookdata flow

Use field data in notifications and integrations

Each custom field generates an email variable (e.g., {custom_device_passcode}) you can insert into notification templates under Settings, Notifications & Quotes. The same data flows through webhooks for integration with external systems like CRM or ticketing tools.

Drag to reorder

⋮⋮⋮⋮⋮⋮

Namecore

⋮⋮⋮⋮⋮⋮

Device passcodecustom

⋮⋮⋮⋮⋮⋮

Phonecore

⋮⋮⋮⋮⋮⋮

Notescore

Drag & dropreordering

Reorder default and custom fields

Drag handles let you rearrange any field on the checkout form, both defaults (Name, Phone, Email, Notes, Address) and your custom fields. The frontend reflects the new order immediately after saving, so you can position critical questions exactly where customers will see them.

Built-in validation

Emailformat check

Numberdigits only

PatternA-Z9999

Requiredblocks submit

Patternformat validation

Built-in validation for clean data

Email fields validate format automatically. Number fields restrict input to digits only. Pattern fields enforce a specific format you define, ideal for serial numbers or formatted reference codes. Combined with the Required toggle, you get clean, structured data without extra plugins.

How it works

Four steps from blank to live.

Add a field, set when it shows, translate it, then use the data downstream in emails and webhooks.

Step 1 · add field

TypePattern

Width

25%50%75%100%

Required

Add custom fields

Go to Settings, Checkout & Discount, Checkout Field Editor and click Add New + to create a field. Choose a field type, set the label, width (25%, 50%, 75%, or 100%), and whether it is required or optional. For Dropdown, Checkbox, and Radio types, add the selectable options.

Step 2 · visibility

IF "Insurance" = Yes

Ship device

Pickup service

Configure visibility rules

Set conditional logic so fields appear only when needed, pick a Checkbox, Radio, or Dropdown trigger field and choose which option triggers visibility. Restrict each field to specific delivery methods. Drag fields to reorder them on the checkout form.

Step 3 · translate

ENDevice passcode

NLApparaatcode

DEGerätecode

Globe icon per field

Translate and finalize

Click the globe icon next to any field label, option, or Plain text content to add translations for each configured language. Save the page so the changes appear on the frontend checkout form for every visitor in every language.

Step 4 · use the data

{custom_device_passcode}

✉Email body

⚡Webhook

Use the data

Customer responses appear in appointment details. Copy the read-only Email Variable shown when you expand the field (e.g., {custom_device_passcode}) and paste it into your notification templates. The same data is passed through webhooks for external system integration.

Plan availability

Included on every plan.

The Checkout Field Editor is part of the core booking flow. Available from Essentials onwards, with the new Plain text type added in v3.1.1.

EssentialsIncluded

Included

GrowthIncluded

Included

ScaleIncluded

Included

FAQ

Common questions.

Can I make the Name, Phone, or Email fields optional?

No. These core fields are always required and cannot be disabled. You can reorder them, but they always appear on the checkout form.

Can I use a text field as a trigger for conditional logic?

No. Only Checkbox, Radio, and Dropdown fields can be used as triggers. Text, Email, Number, Textarea, Pattern, and Plain text fields cannot trigger conditional rules.

How do I use custom field data in emails?

Each custom field has an Email Variable shown when you expand the field (e.g., {custom_device_passcode}). Copy that variable and paste it into your email templates under Settings, Notifications & Quotes.

What is the Plain text field type for?

Plain text displays static, read-only text on the checkout form, set by you, not editable by the customer. It is ideal for terms and conditions, disclaimers, or instructions. It supports translations via the globe icon.

What width options are available for fields?

Each field can be set to 50% or 100% width. Half-width fields appear side by side on the same row.

What happens if I delete a custom field?

The field and all its data are permanently removed when you confirm the deletion. There is no undo, consider hiding the field with conditional logic or service method restrictions if you only need to remove it temporarily.

Can I pre-fill a value in a custom field?

Yes, for Text, Email, Number, and Textarea fields. Use the Default Value setting to set a value that loads with the form, customers can accept it or change it before submitting.

How do Any and All condition relations work?

When a field has multiple conditions, Any makes the field visible if any single condition is met, while All requires every condition to match. The default is Any.

Documentation