{"section":"tutorials","requestedLocale":"en","requestedSlug":"custom-checkout-fields","locale":"en","slug":"custom-checkout-fields","path":"docs/en/tutorials/b2b/b2b-buyer-portal/custom-checkout-fields.md","branch":"main","content":"Custom checkout fields let you collect additional information during purchase in the B2B Buyer Portal, such as cost center, internal order number (PO), and other control data. These values are associated with the order, helping the company standardize data, enforce internal rules, and support audits.\r\n\r\n> ⚠️ This feature is only available for stores using B2B Buyer Portal, which is currently available to select accounts.\r\n\r\n## What custom fields are for\r\n\r\nWith custom fields, your company can:\r\n\r\n- Standardize purchase information across organizational units and buyers.\r\n- Require mandatory data before order completion.\r\n- Reduce checkout input errors.\r\n- Improve traceability, auditing, and compliance.\r\n\r\n## User profiles\r\n\r\nThere are two main profiles for custom fields:\r\n- **Administrator**: creates the fields required by the company and defines where each field appears in checkout.\r\n- **Buyer**: fills the fields during the purchase flow.\r\n\r\n## Field application levels\r\n\r\nFields can be configured at different levels:\r\n\r\n- **Order**: applies to the whole purchase.\r\n- **Item**: applies to specific products in the cart.\r\n- **Address**: applies to shipping or billing information.\r\n\r\n## Field types\r\n\r\nWhen creating a custom field, the administrator must choose one of the following types.\r\n\r\n### Text (`text`)\r\n\r\nAllows the buyer to enter a free-form value at checkout.\r\n\r\n- Accepts any character sequence.\r\n- No format validation beyond the required constraint (when configured).\r\n\r\n### Number (`number`)\r\n\r\nAccepts numeric values only.\r\n\r\n- Only numbers are allowed.\r\n- Use when the value must follow a strictly numeric format.\r\n\r\n### Option (`option`)\r\n\r\nDisplays a list of pre-registered values for selection.\r\n\r\n- The buyer must select one of the available options.\r\n- Enables data standardization.\r\n- This is the only type that can have a **default value per Organizational Unit**.\r\n\r\n## Field settings\r\n\r\nWhen creating a field, the administrator configures:\r\n\r\n- Field name.\r\n- Type (`text`, `number`, or `option`).\r\n- Application level (order, item, or address).\r\n- Requirement (required or optional).\r\n- Status (enabled or disabled).\r\n\r\n## Default values in checkout\r\n\r\nTo reduce manual input and avoid inconsistencies, you can configure default values by Organizational Unit.\r\n\r\nYou can set the following as defaults:\r\n\r\n- Address.\r\n- Card.\r\n- Custom fields of type `option`.\r\n\r\n> ⚠️ Only fields of type `option` can be set as default values.\r\n\r\n> ℹ️ For more information on how to add or configure custom fields, see [Add or edit custom checkout fields](https://help.vtex.com/en/docs/tutorials/adding-or-editing-custom-checkout-fields)\r\n\r\n## Impact for administrators\r\n\r\n- Consistent data across organizational units.\r\n- Better enforcement of internal purchasing rules.\r\n- Improved reliability for reports and audits.\r\n\r\n## Impact for buyers\r\n\r\n- Fields appear in checkout with clear instructions.\r\n- Some values can be prefilled (when configured by the Organizational Unit).\r\n- Orders are completed with less rework and lower error risk.\r\n\r\n## Usage examples\r\n\r\n### Require mandatory information on all orders\r\n- **Scenario:** the company must record cost center and PO on every order.\r\n- **Configuration:** create required fields at the `order` level (`option` for cost center and `text` or `number` for PO).\r\n- **Outcome:** orders can only be completed when the data is provided, ensuring compliance.\r\n\r\n### Checkout prefilled by Organizational Unit (OU)\r\n- **Scenario:** the company wants to reduce errors and purchase time across multiple units.\r\n- **Configuration:** set default values per Organizational Unit for address, card, and `option` fields.\r\n- **Outcome:** checkout appears prefilled after login, reducing rework.\r\n\r\n### Project or activity classification\r\n- **Scenario:** the company needs to associate each purchased item to a project or activity.\r\n- **Configuration:** create an `option` field at the `item` level with the list of active projects or activities.\r\n- **Outcome:** each item is linked to a project, simplifying cost allocation and control.\r\n\r\n### Differentiate resale vs internal consumption purchases\r\n- **Scenario:** the company needs to identify purchase type on the order.\r\n- **Configuration:** create an `option` field at the `order` level with predefined values (Resale / Internal consumption).\r\n- **Outcome:** enables order segmentation and application of fiscal or commercial rules.\r\n\r\n### Segmentation for management reports\r\n- **Scenario:** the finance team needs to classify orders by expense type.\r\n- **Configuration:** create standardized `option` fields at the `order` level (e.g., CAPEX, OPEX).\r\n- **Outcome:** reports can be filtered without manual post-processing.\r\n\r\n### Mandatory justification for specific purchases\r\n- **Scenario:** the company requires justification for sensitive purchases or purchases above a certain amount.\r\n- **Configuration:** create a required `text` field at the `order` level.\r\n- **Outcome:** justification is recorded on the order for review or audit.\r\n\r\n### Centralized standardization and governance\r\n- **Scenario:** the company needs to avoid variations in data entry.\r\n- **Configuration:** use `option` fields instead of free text and define values per Organizational Unit.\r\n- **Outcome:** more consistent and auditable data across the operation.\r\n\r\n### Compliance control in regulated companies\r\n- **Scenario:** the company needs to record regulatory codes per item.\r\n- **Configuration:** create a required field at the `item` level (for example, `text` or `option`).\r\n- **Outcome:** each purchased item includes the information needed for regulatory audits."}