{"section":"tutorials","requestedLocale":"en","requestedSlug":"b2b-buyer-portal","locale":"en","slug":"b2b-buyer-portal","path":"docs/en/tutorials/b2b/b2b-buyer-portal/b2b-buyer-portal.md","branch":"main","content":"> ⚠️ **B2B Buyer Portal** is currently available for selected accounts.\n\n**B2B Buyer Portal** is a VTEX solution that provides a self-service storefront for corporate purchasing. It enables buyer organizations to manage their own accounts, commercial agreements, spending controls, and purchasing workflows, reducing the operational burden for both retailers and their B2B customers.\n\nThis article summarizes the main **B2B Buyer Portal** features and redirects to the detailed documentation for each topic.\n\n- [Contracts](#contracts)\n- [Organizational management](#organizational-management)\n  - [Organizational units](#organizational-units)\n  - [Scopes](#scopes)\n  - [Members and roles](#members-and-roles)\n- [Finance and compliance](#finance-and-compliance)\n  - [Budgets](#budgets)\n  - [Buying policies](#buying-policies)\n  - [Accounting fields](#accounting-fields)\n- [Address and payment management](#address-and-payment-management)\n- [Organization account](#organization-account)\n- [Punchout](#punchout)\n\n## Contracts\n\nA [contract](https://help.vtex.com/docs/tutorials/b2b-contracts) defines the commercial relationship between your store and a buyer organization. It centralizes the terms of the agreement, including:\n\n- Products the buyer can access (product assortments).\n- Prices applied (price tables).\n- The payment methods available.\n\nContracts are the foundation of the buyer experience. All the company's [organizational units](#organizational-units) inherit the contract conditions, ensuring consistency throughout the organization. The [Scopes](#scopes) feature can then control which of these attributes each unit can see and use.\n\nTo simplify contract management at scale, the [Contract Management Agent](https://help.vtex.com/docs/tutorials/contract-manager-agent) allows store operators to update contracts in bulk using natural-language instructions, such as adding collections or changing payment methods across hundreds of contracts at once.\n\n## Organizational management\n\nThe **B2B Buyer Portal** allows buyer organizations to replicate their internal structure on the platform, so each department, branch office, or subsidiary can operate with its own rules while sharing a single contract.\n\n### Organizational units\n\n[Organizational units](https://help.vtex.com/docs/tutorials/organizational-units) represent subdivisions of a buyer organization, such as departments, regional offices, or subsidiaries. They follow a hierarchical tree model. A root unit represents the organization as a whole, and the child units reflect its internal areas.\n\nEach unit can have specific settings for product visibility, payment methods, shipping addresses, accounting fields, and order approval rules, allowing the store to align with the buyer organization's internal policies without needing multiple contracts or accounts. Unit-specific settings are always subject to the contract conditions.\n\n> ℹ️ Learn more about settings in [Adding or editing organizational units](https://help.vtex.com/docs/tutorials/adding-or-editing-organizational-units).\n\n### Scopes\n\n[Scopes](https://help.vtex.com/docs/tutorials/scopes-overview) control which organizational attributes are visible and available to each organizational unit. Admins can restrict access to contracts, payment methods, credit cards, collections, addresses, and accounting fields per unit, ensuring buyers see only what is relevant to their organizational unit.\n\n### Members and roles\n\n[Members](https://help.vtex.com/docs/tutorials/adding-users-to-buyer-organizations) of a buyer organization are assigned storefront roles that define what they can view and do in the store. Examples of predefined roles include:\n\n- **Buyer:** Places orders.\n- **Order Approver:** Approves or rejects orders in approval workflows.\n- **Organizational Unit Admin:** Manages the unit's structure, users, and settings.\n- **Budget Manager:** Creates and manages budgets and allocations.\n- **Buying Policy Manager:** Configures purchase approval rules.\n\nThese and other available roles can be combined to meet each user's responsibilities, creating a granular permissions model for complex organizational structures. For the full list, see [Adding users to buyer organizations](https://help.vtex.com/docs/tutorials/adding-users-to-buyer-organizations).\n\n## Finance and compliance\n\n**B2B Buyer Portal** provides financial governance and purchasing compliance tools, allowing organizations to control spending and enforce internal procurement rules.\n\n### Budgets\n\n[Budgets](https://help.vtex.com/docs/tutorials/budgets-overview) enable organizations to set spending limits and distribute them into allocations associated with specific entities such as users, addresses, or accounting fields. The main features include:\n\n- Defining total amounts and expiration dates for each budget.\n- Splitting budgets into allocations for different departments or projects.\n- Tracking remaining balances and transaction history.\n- Configuring notifications when consumption reaches defined limits.\n\nDuring checkout, the system automatically verifies applicable allocations, ensuring orders are financed based on the organization's financial rules.\n\n> ℹ️ Learn more about settings in [Adding or editing budgets](https://help.vtex.com/docs/tutorials/adding-or-editing-budgets).\n\n### Buying policies\n\n[Buying policies](https://help.vtex.com/docs/tutorials/buying-policies-overview) are authorization rules that determine whether orders are auto-approved, denied, or sent for manual review. Organizations can configure:\n\n- **Spending limits:** Orders above, below, or equal to certain amounts can trigger different approval requirements.\n- **Approval workflows:** Up to five hierarchical approval levels, where final approval requires all levels' authorization.\n- **Custom criteria:** Order approval rules based on budgets, order origin, and other factors.\n\nThis governance layer ensures purchasing activity complies with internal policies before orders are placed.\n\n> ℹ️ Learn more about settings in [Adding or editing buying policies](https://help.vtex.com/docs/tutorials/adding-or-editing-buying-policies).\n\n### Accounting fields\n\n[Accounting fields](https://help.vtex.com/docs/tutorials/accounting-fields) capture additional business information during checkout, such as cost center, PO number, project codes, or expense classifications. Fields can be applied at the order, item, or address levels and configured as required or optional.\n\nOrganizations can also set default values per organizational unit to autocomplete checkout fields, reducing manual entry and ensuring data consistency in purchases.\n\n> ℹ️ Learn more about settings in [Adding or editing accounting fields](https://help.vtex.com/docs/tutorials/adding-or-editing-accounting-fields).\n\n## Address and payment management\n\n**B2B Buyer Portal** supports managing multiple shipping and billing addresses per organization, including internal delivery points (such as loading docks or departments) and designated recipients who may be different from the user placing the order.\n\nPayment cards can be stored at the contract level (shared across the organization) or individual buyer level, with tokenized storage for security.\n\n> ℹ️ Learn more about settings in [Contract settings](https://help.vtex.com/docs/tutorials/contract-settings).\n\n## Organization account\n\nThe [Organization account](https://help.vtex.com/docs/tutorials/organization-account) is the self-service interface where buyer organization admins manage all the settings mentioned above. On a single screen, they can:\n\n- View and update contract details, including roles, addresses, payment methods, and product assortments.\n- Manage users, roles, and organizational units.\n- Configure budgets, buying policies, and accounting fields.\n\nThis centralized interface allows buyer organizations to manage their operations autonomously without relying on the merchant for routine administrative tasks.\n\n## Punchout\n\nPunchout allows integration with external procurement systems, enabling purchasing users to authenticate in the VTEX store and browse the catalog directly from their procurement platform. After selecting the products, buyers can transfer the cart back to the procurement system for internal approval.\n\nThis feature serves organizations that use centralized procurement software and need their suppliers' storefronts integrated into existing purchasing workflows.\n\n> ℹ️ This feature is exclusively supported by the [Punchout API](https://developers.vtex.com/docs/api-reference/punchout-api#overview). Learn more in the [Punchout integration guide](https://developers.vtex.com/docs/guides/punchout).\n\n## Learn more\n\n- [Adding or editing organizational units](https://help.vtex.com/docs/tutorials/adding-or-editing-organizational-units)\n- [Adding users to buyer organizations](https://help.vtex.com/docs/tutorials/adding-users-to-buyer-organizations)\n- [B2B Buyer Portal integration overview](https://developers.vtex.com/docs/guides/b2b-buyer-portal-integration-overview) (developer documentation)"}