Checkout literacy · eligibility limits
Code restrictions: how to read an accepted, rejected, or limited promo-code result
A code can be accepted in one cart and limited in another. The merchant checkout—not a third-party page—is the only authority on eligibility for a particular session.
Why restriction language matters
Online discounts can be affected by current promotions, product categories, minimum thresholds, inventory, cart composition, location, customer status, timing, or merchant rules. A rejection or limitation message is information about the current checkout state, not an invitation to search for a workaround.
A truthful code page explains the difference between a documented acceptance event and universal eligibility. The former can be observed and logged. The latter cannot be inferred from one test, especially when merchants change cart rules or product availability.
Readers should treat the code field and order summary in their own cart as the source of truth. If the store indicates a restriction, the correct response is to read the message and the merchant’s current terms, not rely on an old generalized claim.
Common categories of cart outcomes
An accepted result means the storefront displayed a successful code response in that cart context. A rejected result means the storefront did not accept the code in that context. An unavailable result may mean no suitable in-stock item could be used for a test. A blocked result means the normal permitted path could not be completed without bypassing a control.
These categories should not be blended together. Calling an inventory shortage a code failure, or calling a blocked checkout a verified result, produces misleading records. A good archive preserves the exact condition so readers can see whether the issue was the code, the item, or the ability to run a normal cart check.
The category also belongs in the date log. A fresh date only means something when the reader can see what event occurred on that date and why the resulting status was assigned.
No bypassing is part of verification integrity
Verification stops at normal storefront controls. It does not use alternate identities, hidden fields, coupon stacking tricks, automated evasion, or fake orders. A code record is more credible when it can state that it used the same ordinary cart path available to a reader.
This page does not offer instructions to obtain a discount when the store has rejected it. It explains why a limitation record is more useful than a false promise: it lets readers distinguish an honest current-state report from a page that treats every failed cart as a problem to defeat.