Configure the checkout flow: header, steps, fields, consents, payment, and confirmation.
Settings > Checkouts > [Checkout] > Content
The checkout flow is built from a global header and footer, a step indicator, and a sequence of steps. Each step and section can be enabled, titled, and described. The steps run in this order:Delivery → Contact → Additional details → Payment → Confirmation.Not every step appears in every checkout. Delivery and Contact appear when you enable them, Additional details appears when an item in the order asks for extra information, and Payment always appears. The step a customer lands on first is whichever of these comes first in your own configuration — it is not always Contact.
Every step before Confirmation carries a back button on the left. On most steps it sits opposite Continue; the Payment step has no forward button of its own — the payment method tiles submit the order — so the back button stands alone there. Which back button a step shows depends on where the customer is in the flow:
Step
Button
Where it goes
Any step after the first
Go back
The previous step in the flow
The first step
Back to store
Leaves checkout for the storefront cart — the same destination as the checkout header logo
The first step, when there is no store to return to
No button
—
Back to store appears only on checkouts the customer started from your storefront. A customer who opened a checkout link sent from the admin never came from a store, so on those checkouts the first step has no back button and Continue sits alone on the right.
Leaving checkout for the cart is a full page load, not in-app navigation, so it tears down the checkout page’s state. Details the customer already submitted on an earlier step are stored on the checkout; anything typed on the current step and not yet submitted is lost.
The three button labels — Continue, Go back, and Back to store — are system strings, not content fields. Reword them per checkout on its Translations tab, in any language including your default one.
Logo position (left or center) and sticky behaviour (off, on scroll up, always, or always with a reduced logo).
Step indicator
Enable it and choose a variant — bar, numbered, or minimal. Toggle step labels and step numbers, and override the label for any step.
Footer
Show payment icons and policy links, and choose which policy documents appear.
Submit button
The Continue, Go back, and Back to store labels — see Step navigation. They are system strings, edited on the checkout’s Translations tab rather than in the content editor.
The Contact step collects customer details through a dynamic form you assemble.
Form items
Add and order form items:
Standard fields — first name, last name, email, phone. Set each required or optional and override its label.
Customer profile fields — built-in fields that already exist on the customer profile, such as date of birth, billing address, and tax ID. Values save to the customer record. See below.
Custom fields — text, select, number, or checkbox inputs you define. Each custom field can be marked required and given a custom label.
Attributes — bind a field to an attribute. If the attribute’s resource is Customers, the value saves to the customer profile. If the resource is Orders, the value saves to the order and appears in the confirmation email.
Use the Same row as previous field option to place two fields side by side.
An attribute-backed field inherits the attribute’s input masks. The field formats the value as the customer types, fills in the format’s fixed start when the attribute has exactly one accepted format, and normalises a value pasted without its separators.A value matching none of the accepted formats blocks the step. Leaving the field empty is still allowed unless it is marked required. Custom fields carry no masks — only attribute-backed fields do.
Checkout editor — Add field picker with the Customer fields group
Fields already placed on the form leave the picker — in the screenshot, Language and Company name are missing from the list because they are already on the Contact step.
Seven built-in fields from the customer profile can be collected at checkout. In the Add field picker they sit under Customer fields, next to the standard fields. Each value writes to the matching column on the customer record when the order is placed — these are profile fields, not attributes.
Field
Renders as
Date of birth
Date input
Billing address
Grouped address lines
Shipping address
Grouped address lines
Language
Dropdown of the languages TWICE storefronts support
Customer type
Dropdown — Individual or Business
Company name
Text input
Tax ID
Text input
Each field can be added once per checkout. Per field you set:
Required — the customer must fill it before continuing past the Contact step.
Label — replaces the default label above the field. Leave it empty to keep the default.
Placeholder — placeholder text inside the input.
Same row as previous field — place it beside the preceding field.
Billing address and shipping address render as a group of labelled lines rather than one input: Street address, then ZIP / Postal code and City side by side, then Country. The field’s label — yours or the default — sits above the group as a bold heading.
Storefront checkout — Billing address renders as labelled lines
The street line stands in for the whole address in configuration and validation. Your placeholder, the required marker, and the inline error all attach to it, so marking an address required means the customer must fill Street address — the ZIP, city, and country lines stay optional.
A custom field of type Select field renders as a dropdown at checkout. To configure one:
Add a custom field and set Type to Select field.
Add at least one option. Each option has a name that is both the label customers see and the value stored on the order.
Option names must be unique (compared after trimming whitespace). Empty names are ignored.
At checkout, the dropdown includes a blank choice so customers can clear their selection if the field is not required.
The stored value is the option’s name string. If you rename or remove an option after orders have been placed, existing orders keep the original value. The old value still appears on those orders in the admin.
Consents
Add consent checkboxes:
Marketing consent — a system consent that saves to the customer’s marketing attribute.
Custom consents — your own consent text with a link to a policy document or an external URL.
Each consent can be marked required and given prefix and suffix text around the link.
Choose which fulfillment options the customer can pick: pickup, shipping, and delivery. Override the label for each, set the pickup method and pickup location, and configure the date and time schedule customers select from.
An optional step for extra information — for example a gift message or order reference. Toggle it on and set its title and description.Fields on this step that are backed by a customer attribute inherit that attribute’s input masks and behave the same way as masked fields on the Contact step.
Select which payment methods appear: system methods (your connected providers) and any custom methods you have defined. Override method labels, and set the step’s title and description.
Manage the providers themselves under Payments settings. The Payment step controls which of your configured methods are offered in this checkout.
