Purchase Limits FAQ

Use an order limit for combined quantity, value, or weight across the order; use a product limit to cap selected products separately. Collections and variants have their own rule types. Combinations, total sales, and product eligibility are separate use cases. Compare them in choose a limit type, then test a cart that should pass and one that should fail.

Check that Theme App Embed is enabled on the published theme and that an active rule matches the cart and its warning trigger. Test cart drawers, custom themes, and quick-buy paths separately. Follow the banner troubleshooting guide.

The storefront warning and checkout protection are separate settings. Enable both shop-level and rule-level Checkout Validation, and turn off Allow all customers to complete checkout. Follow the checkout troubleshooting guide.

Orders before the rule was created are not counted. Frequency is tracked per customer account and requires login; a guest cannot be tracked as that same signed-in account. Test a normal second purchase with a signed-in account, then read frequency delay and concurrency.

Yes. Use Weekly orders per customer under Limits. It counts this week's paid orders for a signed-in customer across the store, including orders created before you enabled the rule during this week. A full refund or void returns a slot to the original week after synchronization; a partial refund does not. The rule does not guarantee blocking two nearly simultaneous checkouts.

It cannot guarantee blocking near-simultaneous checkouts before payment. Combine a per-order quantity cap, a frequency rule, and Checkout Validation; use order tags and optional email for after-payment review. See the flash-sale example.

No. Open the violation list to check the earlier order, matched rule, tag, and email status. Handle payment, customer contact, or refunds manually under your store policy.