How we verify coupons

What gets tested, what the date means, and what we do when a code dies.

Last updated: 23 July 2026

The usual model is bulk-scraping: pull every code you can find, publish all of them, let the shopper do the testing. It costs nothing and it fills a page fast. We work the other way round, which is slower and means fewer codes on the site. Here's the whole process, so you can decide whether the "verified" label on our coupons, and the price check sitting next to it, is worth anything.

The process, start to finish

1
Sourcing
Store newsletters, in-app promos, direct and affiliate partnerships, plus offers we find ourselves. Submissions from readers are welcome but never auto-published, they go through the same test as everything else.
2
Testing
The code goes into a real cart on the store's site. That's where we find out whether it applies at all, what the actual discount is, and what the fine print says: minimum order, excluded brands, new-customer-only.
3
Recording
Each check is written down with the date it happened, one of three outcomes (worked, failed, or still works but the terms moved), and what the cart actually showed. Not today's date, not the date the coupon was added.
4
Re-checking
Live codes get re-tested on a rolling basis, and again before a big sale event when retailers rewrite their promos overnight. Every re-test adds another entry rather than overwriting the last one.

Every check is on the record, including the ones we failed

Open any coupon that has been checked more than once and you'll find its full history near the bottom of the page: each date, what happened, and what we saw in the cart. The failures are in there too. A log that only ever said "worked" would be marketing, and you'd be right not to believe it. The useful version is the one that shows a code breaking on the 14th and a replacement going up on the 20th. Have a look at any coupon on the coupons page and judge for yourself.

When a code stops working

We don't quietly delete the page. The code is struck through, the page says when it failed and links whatever does still work at that store, and the failed check stays in the history. Deleting it would be tidier for us and worse for you: you'd search the same code next week and land on someone else's page telling you it's live.

What the "Last verified" date means

It's the last day someone at Savooh actually put that code into a cart. Nothing else. If a coupon hasn't been through the test yet, it shows no date at all. An empty field is more honest than a stamp we didn't earn, and it also tells you which codes to try first. Separately, each coupon page counts how many shoppers have told us the code applied at their checkout. That number is reader-reported, labelled as such, and never folded into our own checks.

How often we come back to a code

Not on a fixed schedule. High-traffic stores and anything with an expiry attached get looked at most often. Seasonal codes, like White Friday, Ramadan, Eid, and back-to-school, get re-checked going into the event and again during it, because that's the window where discounts change fastest and dead codes do the most damage.

Found a code that didn't work?

Two ways to tell us. On the coupon itself there's a "Did this code work?" question, one tap either way, and a yes is what sets the shopper-confirmed date other people see. For anything that needs explaining, email info.savooh@gmail.com with the store name and the code. Whatever you send gets re-tested, and the result goes into the log like any other check.

Independence and disclosure

No store can buy a "verified" label, a higher position, or the removal of a failed check from its history. Verification answers exactly one question: does the code work today. Where the money does come from is set out in the affiliate disclosure.