Custom Fields
Collect order metadata on the checkout - sizes, account names, license ids, anything - and receive it back on the transaction.
Setup#
Under Settings → Checkout custom fields, add as many fields as you need. Each field has a type, a name, and an optional required flag; set a section title (default "Information") for the group.
| Type | Renders as |
|---|---|
text | Single-line input |
textarea | Multi-line input |
select | Dropdown - list options in the name: Size:Small:Medium:Large |
checkbox | Checkbox (e.g. terms acceptance) |
Required fields block checkout submission until filled. The section can be toggled off entirely without losing your field definitions.
Where the answers go#
Customer answers are attached to the transaction and appear:
- In the transaction's notes in the console
- In the webhook payload, inside the transaction description as
Field name: valuelines - In your downloadable transaction exports
Common patterns#
selectSize:Small:Medium:Large(required) for merchandisetextUsername or email to activate(required) for digital goodstextareaDelivery notesfor servicescheckboxI accept the license terms(required) for compliance
Customer details (built-in)#
Separately from custom fields, shops can switch on required customer details - the personal-information block (name, email, address) captured at checkout and attached to the transaction for receipts and invoices. It unlocks at a lifetime funding tier; custom fields are the more flexible tool for order-specific metadata.