{"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 to selected accounts.\n\n**B2B Buyer Portal** is a VTEX solution that provides a self-service storefront designed for corporate purchasing. It enables buyer organizations to manage their own accounts, commercial agreements, spending controls, and procurement workflows, reducing operational overhead for both merchants and their B2B customers.\n\nThis article summarizes the main capabilities of **B2B Buyer Portal** and directs you to the detailed documentation for each topic.\n\n- [Contracts](#contracts)\n- [Organization management](#organization-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- [Addresses and payment management](#addresses-and-payment-management)\n- [Organization account](#organization-account)\n- [Punchout](#punchout)\n\n## Contracts\n\nA [contract](https://help.vtex.com/en/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- Which products the buyer can access (product assortments).\n- Which prices apply (price tables).\n- Which payment methods are available.\n\nContracts serve as the foundation of the buyer's experience. All [organizational units](#organizational-units) within the company inherit the contract's conditions, ensuring consistency across the entire organization. The [scopes](#scopes) feature can then control which of these attributes each unit can see and use.\n\nTo streamline contract management at scale, the [Contract Manager Agent](https://help.vtex.com/en/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## Organization management\n\n**B2B Buyer Portal** allows buyer organizations to replicate their internal structure within the platform, so each department, branch, or subsidiary can operate with its own rules while sharing a single contract.\n\n### Organizational units\n\n[Organization units](https://help.vtex.com/en/docs/tutorials/organizational-units) represent the subdivisions within 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 child units reflect its internal areas.\n\nEach unit can have specific configurations for product visibility, payment methods, delivery addresses, accounting fields, and order approval rules, allowing the store to align with the buyer company’s internal policies without requiring multiple contracts or accounts. Unit-specific settings are always subject to the contract conditions.\n\n\n> ℹ️ Learn about configurations in [Adding or editing organizational units](https://help.vtex.com/en/docs/tutorials/organizational-units).\n\n### Scopes\n\n[Scopes](https://help.vtex.com/en/docs/tutorials/scopes-overview) control which organization-level attributes are visible and available to each organizational unit. Administrators can restrict access to contracts, payment methods, credit cards, collections, addresses, and accounting fields per unit, ensuring that buyers only see what is relevant to their organizational unit.\n\n### Members and roles\n\n[Members](https://help.vtex.com/en/docs/tutorials/buyer-organization-members) of a buyer organization are assigned storefront roles that define what they can see 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 match each user's responsibilities, creating a granular permission model that supports complex organizational structures. For the full list, see [Buyer organization members](https://help.vtex.com/en/docs/tutorials/buyer-organization-members).\n\n## Finance and compliance\n\n**B2B Buyer Portal** provides tools for financial governance and purchasing compliance, allowing organizations to control spending and enforce internal procurement rules.\n\n### Budgets\n\n[Budgets](https://help.vtex.com/en/docs/tutorials/budgets-overview) let organizations define spending limits and distribute them across allocations tied to specific entities, such as users, addresses, or accounting fields. Key capabilities include:\n\n- Setting total amounts and validity periods for each budget.\n- Subdividing budgets into allocations for different departments or projects.\n- Tracking remaining balances and transaction history.\n- Configuring notifications when consumption reaches defined thresholds.\n\nDuring checkout, the system automatically checks applicable allocations, ensuring orders are funded according to the organization's financial rules. \n\n> ℹ️ Learn about configurations in [Adding or editing budgets](https://help.vtex.com/en/docs/tutorials/adding-or-editing-budgets).\n\n### Buying policies\n\n[Buying policies](https://help.vtex.com/en/docs/tutorials/buying-policies-overview) are authorization rules that determine whether orders are automatically approved, denied, or sent for manual review. Organizations can configure:\n\n- **Spending thresholds:** 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 sign-off from all levels.\n- **Custom criteria:** Order approval rules based on budgets, order origin, and other factors.\n\nThis governance layer ensures that purchasing activity complies with internal policies before orders are placed.\n\n> ℹ️ Learn about configurations in [Adding or editing buying policies](https://help.vtex.com/en/docs/tutorials/adding-or-editing-buying-policies).\n\n### Accounting fields\n\n[Accounting fields](https://help.vtex.com/en/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 level and configured as required or optional.\n\nOrganizations can also set default values per organizational unit to pre-fill checkout fields, reducing manual input and ensuring data consistency across purchases.\n\n> ℹ️ Learn about configurations in [Adding or editing accounting fields](https://help.vtex.com/en/docs/tutorials/adding-or-editing-accounting-fields).\n\n## Addresses and payment management\n\n**B2B Buyer Portal** supports managing multiple shipping and billing addresses per organization, including internal delivery points (such as docks or departments) and designated recipients who may differ from the user placing the order.\n\nPayment cards can be stored at the contract level (shared across the organization) or at the individual shopper level, with tokenized storage for security.\n\n> ℹ️ Learn about configurations in [Contract settings](https://help.vtex.com/en/docs/tutorials/contract-settings).\n\n## Organization account\n\nThe [Organization account](https://help.vtex.com/en/docs/tutorials/organization-account) is the self-service interface where buyer organization administrators manage all of the above settings. From a single screen, admins can:\n\n- View and update contract details (profile, addresses, payment methods, product assortment).\n- Manage users, roles, and organizational units.\n- Configure budgets, buying policies, and accounting fields.\n\nThis centralized interface empowers buyer organizations to manage their operations autonomously, without depending on the merchant for routine administrative tasks.\n\n## Punchout\n\nPunchout enables integration with external procurement systems, allowing procurement users to authenticate into the VTEX store and browse the catalog directly from their procurement platform. After selecting products, buyers can transfer the cart back to the procurement system for internal approval.\n\nThis capability supports organizations that use centralized procurement software and need their supplier storefronts integrated into existing purchasing workflows.\n\n> ℹ️ This feature is supported exclusively through the [Punchout API](https://developers.vtex.com/docs/api-reference/punchout-api#overview). Learn more with [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/en/docs/tutorials/adding-or-editing-organizational-units)\n- [Adding users to a buyer organization](https://help.vtex.com/en/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)"}