We are an affiliate: if you order from Growth Guys using this code we earn a commission, at no extra cost to you. We are not Growth Guys and have no ownership of or role in the company.
A code that fails on one cart and works on another is usually hitting a minimum, a product exclusion or a per-account limit — not expiry. Change one variable at a time to tell which.
A minimum purchase, a category or product exclusion, and a single-use or per-account limit. Each produces a different failure: a minimum refuses below a threshold and works above it, an exclusion refuses one product while another works, and a use limit works once and never again.
Change one variable at a time. Raise the basket and retry — if it now applies, it was a minimum. Swap the product and retry — if it now applies, it was an exclusion. Try a fresh guest cart with no account — if it now applies, it was tied to the account.
A code tested against one cart proves only that it works on that cart. Across 818 reads the basket has been rotated over 90 distinct products and from $40.00 to $1,800.00, so a minimum or an exclusion would have surfaced as a failure rather than hiding behind a single repeated test.
That no restriction exists. It tells you none has appeared across the range we have tested. A restriction outside that range would not have been caught, and the honest claim is the narrow one.
A code is dead when it fails across the range, not when it fails once. Our standard is a failure that repeats on a fresh guest cart, at more than one basket value, on more than one product, across more than one run. Anything short of that is a reading we publish and keep watching. That threshold is deliberately hard to meet, because the cost of wrongly declaring a working code dead is a reader who stops checking.
Some limits are published and cost nothing to check: a minimum order, a category exclusion, a first-order-only flag, an expiry date. These usually sit in small print beside the code or on a terms page, and reading them takes less time than a failed checkout. The useful habit is to look for what is NOT said: a code advertised without a minimum, without exclusions and without an expiry is making three claims by omission, and each is checkable on a cart in seconds.
The ones that matter are usually invisible until you try. A code that applies to most of a catalogue but silently skips one category. A percentage that caps at a maximum reduction. A single-use flag that only reveals itself on a second order. None of these produce a helpful error — the discount line is simply absent or smaller than expected. This is why a cart test at a realistic order size is worth more than any amount of reading, and why testing at several different values catches limits that one test at one value never would.
A single cart test at a convenient amount proves the code works at that amount. It cannot distinguish a flat sitewide discount from one that caps, tiers, or excludes a category you did not happen to add. Running the same code at a low value, a mid value and a high value costs three minutes and separates those cases cleanly: a flat rate produces exactly the same percentage at every point, and anything else produces a visible break. The cart values behind this site are deliberately varied between runs for that reason, rather than re-testing the same comfortable number.
The claims on this page about what a code restriction actually looks like in a cart can be checked against sources outside this site: