Collect Structured Answers at Checkout

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 → Custom fields and create an organization-level field. Products choose from this shared library later. The field type is permanent after creation because it controls both the checkout control and stored value:

Type	Checkout control	Stored value	Validation
Text	Single-line input or optional textarea	String	Minimum and maximum length
Number	Numeric input	Number	Minimum and maximum value
Date	Date input	ISO 8601 string	Earliest and latest date
Checkbox	Checkbox	Boolean	Required state can enforce acknowledgement
Select	Menu of label/value pairs	Selected option value	Allowed options

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.

Ruba custom fields library in light mode

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.

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:

{
  "custom_field_data": {
    "terms": true,
    "source": "social_media"
  }
}

Launch Path

Shape the Offer

Run the Revenue Model

Deliver Customer Access

Build the Integration

Operate the Business

Implementation Playbooks

Collect Structured Answers at Checkout

Define the data before the form

Separate internal identity from customer copy

Attach questions to a product

Consume the answers

​Define the data before the form

​Separate internal identity from customer copy

​Attach questions to a product

​Consume the answers

Define the data before the form

Separate internal identity from customer copy

Attach questions to a product

Consume the answers