ApproveCart B2B docs
Approval rules
Growth rules require approval for targeted purchasing conditions, including cases where the cart does not exceed a spend limit.
Available conditions
Rules can evaluate cart and buyer context, including:
- Cart total
- Line quantity
- Product or collection
- Company or company location
- Customer role or customer tag
How conditions combine
All conditions inside one rule must match. If a rule targets a specific collection and a line quantity above 10, both conditions must be true for that rule to match.
Any active matching rule can require approval. If two different active rules match the same cart, approval is required and the matching rule names are recorded.
Scoping a rule
Use the narrowest appropriate scope:
- All buyers for a merchant-wide risk condition.
- Company when the policy belongs to one B2B organization.
- Company location when a branch or business unit needs a different rule.
Example rules
| Policy | Suggested conditions |
|---|---|
| Always approve hazardous equipment | Collection is “Hazardous equipment” |
| Approve bulk orders | Line quantity is greater than the internal threshold |
| Control one branch | Company location is the selected branch |
| Junior buyer ceiling | Customer role or tag matches, and total is above the allowed amount |
Build and test one rule
- Name the policy so buyers and approvers can understand the reason.
- Choose the minimum conditions needed to represent it.
- Set the company or location scope if it is not merchant-wide.
- Assign a priority that makes the most useful reason appear first.
- Activate the rule.
- Test one matching cart and one nearly identical non-matching cart.
Related guides
Review spend limits for threshold policy and checkout protection for what happens after a matched request is approved.