Skip to main content
Checkout already collects identity and billing information. Custom fields cover information specific to your business, such as terms acceptance, marketing consent, attribution, or fulfillment details.

​
Define the data before the form

Open Settings → Checkout questions to manage organization-level questions. Products choose from this shared library later. Ruba custom fields library in light mode Ruba custom fields library in dark mode The field type is permanent after creation because it controls both the checkout control and stored value:

​
Separate internal identity from customer copy

The slug is the unique organization-wide key used in orders, subscriptions, and API responses. It can be renamed later; Ruba updates existing data to the new key. The name identifies the field in the dashboard and becomes its initial checkout label. Choose New question to create an organization-level question. Ruba custom field creation form in light mode Ruba custom field creation form in dark mode Form options let you replace the label, add help text beneath the control, and add an empty-state placeholder. Label and help text accept basic Markdown including emphasis and links.

​
Attach questions to a product

Edit or create the product, select the fields that belong on its checkout, and mark each one optional or required. A required checkbox must be checked before confirmation, which makes it suitable for explicit agreement to linked terms. Product checkout questions with Company name required and Website optional in light mode Product checkout questions with Company name required and Website optional in dark mode

​
Consume the answers

Sales views add the organization fields as columns on orders and subscriptions. The Orders API and Subscriptions API return the same values under custom_field_data, keyed by slug: