{"section":"tutorials","requestedLocale":"en","requestedSlug":"buying-policies-overview","locale":"en","slug":"buying-policies-overview","path":"docs/en/tutorials/b2b/b2b-buyer-portal/buying-policies-overview.md","branch":"main","content":"> ⚠️ This feature is only available for stores using [B2B Buyer Portal](https://help.vtex.com/en/docs/tutorials/b2b-buyer-portal), which is currently available to selected accounts.\n\n**Buying policies** is a feature that allows users to configure mechanisms and define criteria to automatically authorize or deny orders. It operates as a control layer in the purchasing process, allowing users to create customized order review workflows.\n\nThe solution increases organizational governance and ensures compliance with buying policies. Its mechanisms allow combining various types of rules:\n\n- **Spending threshold:** Spending limits per order, ensuring that orders above, below, or equal to certain amounts require approval.\n- **Buying criteria:** Specific rules that determine whether an order requires approval, based on multiple factors (thresholds, budgets, order origin, among others).\n- **Approval flow:** A multi-level approval process, which may vary according to organizational complexity.\n- **Management of orders under approval:** Monitoring orders awaiting approval to ensure they only proceed in the flow after approval.\n\n## How it works\n\nThe steps to configure a buying policy are:\n\n1. The user configures the order review criterion.\n2. This criterion is associated with an action, which can be:\n   - Approve order with bypass (the order is approved regardless of the criteria)\n   - Deny order\n   - Require manual approval\n3. For manual approval, the user configures one to five levels of hierarchical approval. While any level can deny an order, final approval requires authorization from all levels.\n\n## Storefront Roles\n\nTo configure buying policies, the user's [Storefront Roles](https://developers.vtex.com/docs/guides/storefront-roles) role must have the `ManageBuyingPolicies` resource. To manually approve orders, the `ApproveOrders` resource is required.\n\n## Configuring buying policies\n\nUsers can add, edit, or remove buying policies through the organizational unit interface. For more information, see the article [Adding or editing buying policies](https://help.vtex.com/en/docs/tutorials/adding-or-editing-buying-policies).\n\n> ℹ️ To manage order authorization rules via API, see the [Buying Policies API](https://developers.vtex.com/docs/api-reference/buying-policies-api) and the developer guide [Buying Policies](https://developers.vtex.com/docs/guides/buying-policies)."}