Spend limits

Policy priority

1. Individual buyer override — the most specific setting.
2. Company policy — used when the buyer does not override it.
3. 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 company or merchant 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

1. Set a merchant default that is safe for the majority of buyers.
2. Create a company policy only where purchasing authority differs.
3. Add an individual override for exceptional buyer authority.
4. Test one cart below, exactly at, and above each important boundary.

Currency behavior

Configured limits are shown in the store currency. ApproveCart compares the checkout subtotal numerically and does not perform 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.

Related guides

Use approval rules for conditions beyond subtotal, then verify the result through the buyer workflow.