Customers can reach a purchase limit through several storefront paths. After the basic rule verification, test each entry point your store actually uses: product page, full cart, cart drawer, and quick-buy buttons. This checks whether customers receive the expected feedback and checkout result whichever path they take.
Prepare one test rule
Choose a simple rule, such as “no more than two units of the target product per order.” Note the rule name, product and variant, eligible customer, and expected message. Confirm that the Theme App Embed is on in the published theme and checkout validation is enabled at both shop and rule level.
Test each entry point
| Entry point | Passing test | Failing test |
|---|---|---|
| Product-page quantity field and stepper | Select two units | Change to three; inspect the message and button state |
| Product-page Add to cart | Add two units | Try to add or accumulate three |
| Full cart | Keep two units and proceed | Change to three, then try checkout |
| Cart drawer or mini-cart | Keep two units | Change to three in the drawer or click Checkout |
| Buy now or another quick-buy control | Select two units | Select three and inspect the final checkout result |
Change only one condition at a time. If a button is disabled, record the customer-facing explanation. If you reach checkout, confirm whether Checkout Validation ultimately blocks the failing cart. Product-page messages provide early feedback; checkout validation performs the final check.
Record the outcome
For each path, record the entry point, theme name, device, product or variant, quantity, customer login state, visible message, and checkout result. If one path fails while the others pass, these details help isolate a theme or entry-point compatibility issue.
If a message is missing, use Troubleshoot a missing limit banner. If a failing cart can still check out, use Troubleshoot checkout not being blocked.
Use a test product or cart to check the outcome before applying this setup across your store.
All guides