Most coupon sites copy codes from each other and hope. We put each one in a real cart and watch what the total does. This is the whole method, including the parts that are not flattering.
Last updated 14 October 2026About 4 minutes to read
01
The one rule
A coupon code is worth nothing until someone has tried it. So there is one rule everything else hangs off:
No cart, no listing. If we have not put a code into a real basket and watched the total change, it does not go up as a working code. Not as "probably works", not as "reported working".
It is a slower way to run a coupon site, and it means we list fewer codes than most. That is the trade we have chosen: a shorter list you can trust beats a long list that wastes your time at checkout.
02
Where codes come from
We gather codes from four places:
Brand newsletters and emails that stores send to their customers.
Affiliate feeds from the networks and stores we work with.
App banners and on-site offers that stores show to shoppers.
Shoppers like you, who send us codes they have found.
Where a code came from changes nothing about what happens next. A code from a store that pays us well and a code a stranger emailed us go into the same queue and face the same test.
03
The four steps
Four steps, and a code can fail at any of them.
We collect it. The code goes into the queue with its store, its terms and where we found it. Nothing is live at this point.
We try it in a real cart. A tester opens the store, adds real products that meet the offer's terms, and applies the code at checkout. We stop before payment.
We publish it with the receipt. If the total dropped, the code goes live together with the cart total before and after, the time of the test and who ran it.
We re-check it. Live codes are tested again. If one fails, it comes off the page.
04
What counts as working
This is where most coupon sites are loose, so we are strict about it. A code passes only if the amount you would pay goes down.
Several things look like success and are not. A checkout can accept a code and apply nothing. A code can shave off delivery you were not going to pay anyway. A "discount" can appear on a product and vanish at the final step. None of these pass.
We also note what the code needs to work — a minimum spend, a first order, selected products, a particular card — and show those conditions with the code. A code that only works on a $200 basket is not a code that works.
05
The receipt under every code
Saying we tested something is easy. So we show the test. Under every working code is the receipt from the cart it came out of:
Example receiptTest record
Cart before the code$84.00
Code applied−$12.60
To pay after the code$71.40
Tested 11 Oct, 4:20 pm by the test desk
Four facts, every time: what the cart cost, what the code took off, what was left to pay, and when it was checked. If a code on this site has no receipt, it is not being presented as tested.
06
Re-checks and removals
Codes die constantly. Stores end offers early, change the terms, or cap how many people can use them. A code that worked this morning can be dead by evening, so testing once is not enough.
Live codes get re-checked, and a code that fails a re-check comes off the page straight away. We do not leave it up with a smaller promise, and we do not quietly relabel it. It goes.
Expired codes are not deleted and forgotten — they move to the expired list on the store page, so you can see what the store has offered before and roughly what to expect next time.
07
The labels you will see
These are the exact labels you will see on store pages.
Worked
The code changed the cart total in our most recent test.
Didn't work
The code was rejected, or the total stayed the same. It comes off the page.
Not tested yet
We have the code but have not run it through a cart yet, and we say so.
Nothing on the site is labelled as working on a store's say-so. A store telling us a code is live is a reason to test it, not a reason to publish it.
08
What we cannot promise
Testing makes a code far more likely to work. It cannot make it certain, and we would rather say that plainly:
A code can stop working between our checks. That is why every code shows when it was last tested.
Some offers are limited to certain shoppers — new customers, one use per account, a specific region or card — so a code can work for us and not for you.
Your basket is not our basket. Different products, totals and delivery options can all change the result.
Stores can withdraw an offer without warning, including mid-sale.
If a code fails for you, tell the desk. Reports of failed codes are handled first: we re-test the code and take it down if it no longer works.
09
Changes to this page
If we change how testing works, this page is updated and the "Last updated" date at the top changes with it. The rules about what we publish and take down live in our Editorial policy, and how we earn money is set out in our Affiliate disclosure.
Last updated 14 October 2026.
A code didn't work for you?
Tell the test desk. Failed-code reports go to the front of the queue, get re-tested, and come down if they are dead.