How We Verify Coupons
We want the word "verified" to mean something. Here is exactly what our review checks, what it does not, and how we show community feedback honestly.
A real person reviews every code before it publishes
Coupons reach us from three places: verified affiliate feeds, direct merchant relationships, and community submissions through our submission form. Nothing auto-publishes. Before a code goes live, a real person on our team reviews it.
That review checks the things we can confirm at review time:
- The code is attached to the correct merchant and store page.
- The format looks like a real code, not discount text or a feed fragment.
- The discount and any expiry date are sane and readable.
- Obvious duplicates and junk entries are removed.
What our review does not claim
Being honest means naming the limits. Our review does not mean:
- That we completed a test purchase at the merchant checkout for that code.
- That the code will still work at the exact moment you use it, since stores can deactivate a code at any time.
- That a discount is the best available, though we surface the best ones we track.
If a code stops working, community feedback and expiry handling pull it out of the active listings.
Community feedback, shown honestly
After using a code, shoppers can report whether it worked. We only count these genuine reports, never any seeded or historical placeholder numbers.
Because a handful of reports is not proof, we hold back until there is enough real data:
- No reports yet: we say "Not enough shopper feedback yet." We do not invent a percentage.
- A few reports: we show the plain count, for example "3 of 4 shoppers reported success," without a percentage.
- Enough reports: we show a success percentage together with the number of reports it is based on.
The Health Score badge follows the same rule. When there is little real evidence, it is shown muted and labeled as an estimate from freshness and expiry, not a confirmed rating.