Checkout Link Custom Fields
Collect extra customer information during checkout.
Custom fields let you collect information that is not part of the default customer name and email fields.
Add only fields the team will actually use during fulfillment, support, or reporting. Extra fields slow down checkout and can reduce completion.
Add a Custom Field
- Open the checkout link form.
- Go to Custom Intake Fields.
- Select Add Field.
- Enter the field label.
- Choose the field type.
- Mark the field as required when customers must answer it before checkout.
- Save the checkout link.
After saving, open the public checkout link and confirm the field appears in the right order. Required fields should block checkout when empty and optional fields should allow the customer to continue.
Field Types
- Text for short answers.
- Textarea for longer notes, instructions, or project context.
- Select for a controlled list of choices.
- Checkbox for confirmation-style inputs.
Select Options
For select fields, enter options separated by commas. Keep choices short and clear so they fit cleanly in the checkout form.
Use select fields when the answer should be standardized for fulfillment or reporting. Use text or textarea only when customers need to provide unique details. Standardized options make order review faster and reduce the chance of missed instructions.
Good Uses
- Project brief.
- Preferred start date.
- Website URL.
- Team size.
- Package option.
- Delivery instructions.
- Approval checkbox.
Avoid using checkout fields for long onboarding forms. If you need detailed qualification, use a CRM form before checkout or follow up after purchase.
Write Clear Field Labels
Use labels customers can answer without support. Website URL is better than
URL, and Preferred project start date is better than Date.
For required fields, make the label specific enough that customers know what will happen with the answer. If an answer changes fulfillment, say so in the field label or surrounding checkout copy.
Keep Sensitive Data Out
Do not ask customers to submit passwords, private keys, full card details, government IDs, or production credentials. Use a secure handoff process after checkout when sensitive access is required.
Map Fields To Fulfillment
Before publishing a field, decide who reads the answer and where it should go after checkout. A delivery instruction may belong on the order, a project brief may need to be copied into a project, and a support-related answer may need a ticket or customer note.
Remove fields that no one reviews. If the field is required, make sure the team has a clear reason for blocking checkout without that answer.
Before Publishing
Open the checkout page in a private window and submit a test order when it is safe to do so. Confirm required fields block checkout when empty, optional fields can be skipped, select values are readable on mobile, and the answers appear on the order where your team will review fulfillment details.
Do not collect sensitive information such as passwords, full payment card details, government IDs, or private access tokens through checkout custom fields.
Review Answers
After a customer checks out, open the order and review custom-field answers before fulfillment. If the answer affects delivery, copy or link the relevant detail to the task, project, ticket, or customer record used by the team.
If an answer is missing or unclear, contact the customer before marking the order completed. Do not guess fulfillment details from incomplete checkout answers.