ApproveCart docs
Spend limits
Spend limits determine whether a cart subtotal requires internal approval. ApproveCart resolves the most specific applicable policy for each buyer.
Policy priority
- Individual buyer override — the most specific setting.
- Company or custom team policy — used when the buyer does not override it.
- Merchant default — the baseline when no more specific policy replaces it.
Policy modes
| Mode | Meaning |
|---|---|
| Custom limit | Use the configured amount as the approval threshold. |
| No limit | Do not require approval because of subtotal at this level. |
| Inherit | Use the next applicable group or store policy. |
Threshold boundary
ApproveCart requires approval when the cart subtotal is greater than the effective custom limit.
- Limit $1,000; subtotal $999.99: the threshold does not trigger.
- Limit $1,000; subtotal $1,000.00: the threshold does not trigger.
- Limit $1,000; subtotal $1,000.01: approval is required.
Configure a practical hierarchy
- Set a merchant default that is safe for the majority of buyers.
- Create a company or custom team policy where purchasing authority differs.
- Add an individual override for exceptional buyer authority.
- Test one cart below, exactly at, and above each important boundary.
Currency behavior
Custom team thresholds and approvals use the shop currency. For B2B purchases, configured limits are displayed in the store currency and compared numerically without an explicit exchange-rate conversion.
Starter usage and spend limits
Evaluating a cart or previewing why approval is required does not consume a Starter request. Usage increases when a new approval request is created. Starter supports 50 new requests in a rolling 30-day period.
These are approval thresholds per cart. They do not track a cumulative monthly spending budget. Active approvers bypass approval for their own purchases in the selected group.
Related guides
Use approval rules for conditions beyond subtotal, then verify the result through the buyer workflow.