How We Find, Test, and Verify Coupon Codes

Every code on this site comes from one of three places: a retailer's affiliate program, the retailer's own public channels, or a reader submission. Before an offer goes live, a person applies the code to a real cart at that retailer and records what happened, including the restrictions attached to it. A passing test proves that the code worked on one cart at one point in time. That is a useful signal, not a guarantee, and the gap between those two things is what this page explains.

The process is in five stages.

Here is the full path an offer takes, and what each stage produces on the page you see.

No coupon site watches every code continuously. A site can test before publishing, retest on a schedule, and tell you when the last test occurred. That last part is the one most sites leave out.

Where our codes come from

Three sources, and each has a different failure mode worth knowing about.

Retailer affiliate programs

An affiliate program is an arrangement where a retailer pays a commission on a referred sale, and most retailers distribute their public promotions to partners through an affiliate network. Networks, including Impact, CJ Affiliate, Rakuten Advertising, Awin, ShareASale, and Partnerize, pass active, upcoming, and expiring offers to approved publishers. Awin, for example, documents an offers endpoint that returns promotions and voucher codes from advertisers on its network.

Offers from this source carry the retailer's own wording, which is their advantage. Their failure mode is staleness: a retailer can end a promotion without updating the network entry, and the entry can list an offer that only runs in a market we do not cover. A feed entry is a candidate, not a published offer.

The retailer's own channels

Homepage banners, promotional emails, app-only offers, and the terms page are attached to a sale. These are the most accurate statements of what an offer covers, because the restrictions are written by the company that has to honor them. Their failure mode is scope: a newsletter code is often tied to the email address it was sent to, so it looks public and behaves privately.

Reader submissions

Anyone can send a code through/submit-coupon. Submissions run through the same test as everything else, and nothing is published on the strength of a submission alone.

We do not publish single-use codes issued to a single shopper. Posting one takes it away from the person it was issued to, and it fails for everyone who tries it afterward.

How do we test a code before it goes live

The test is deliberately boring because a test designed to succeed tells you nothing.

1. Build a real cart. Items an ordinary shopper would put in a basket, not edge cases picked because they happen to qualify.
2. Apply the code at checkout. Record whether a discount appears, what type it is (percentage off, fixed amount off, free shipping, gift with purchase), and which items it applies to.
3. Read the retailer's terms. Record the restrictions in the retailer's own words: minimum spend, excluded brands and categories, new customer limits, one per customer, eligible regions, stated end date.
4. Check how the threshold is measured. Retailers differ on whether a minimum spend is tested against the subtotal before or after other discounts. Where the retailer states it, we record it, because this is the restriction that most often makes a live code look broken.
5. Record the date and publish it. The date the test was run is shown with the offer.

The test stops at the point where the discount either applies or does not. We do not place the order, since a test purchase would only be returned, and a return costs the retailer money for no reason. The trade-off is, to state it honestly, a code that applies in the cart can still be rejected at the payment step by a rule we cannot see from the outside.

What "verified" means here, and what it does not.

Verified is a status with one meaning: a person applied that code to a real cart at that retailer on the date shown, and the discount applied.

The narrow definition is deliberate. Under the FTC's advertising substantiation policy, an advertiser needs a reasonable basis for an objective claim before publishing it. Where a claim implies a particular level of proof, the advertiser has to hold at least that level. "Verified" implies a test, so the label goes only on offers where a test happened, next to the date it happened.

You will not see a success rate percentage next to a code on this site. A percentage implies a measured redemption rate across many real checkouts, and that is data a coupon site does not have unless it observes actual orders. A date you can check is a smaller claim, and it is one we can stand behind.

Why a verified code can still fail at your checkout

A code that passed a test last night can fail for you this morning for reasons that have nothing to do with the test. Five causes cover most of it.

1. The code was single-use. Some codes are valid for a single redemption, or one per customer account. The first shopper through the door gets it.
2. Your item is excluded. Sitewide codes routinely exclude sale items, gift cards, new releases, and specific brands. Brand exclusions often result from MAP pricing, a policy that sets the lowest price a retailer is allowed to advertise, so retailers carve out those brands to stay compliant.
3. Your account is not eligible. New customer offers check the email address or the account history. Being logged in to an existing account, or using an address that has ordered before is enough to fail.
4. The offer is region-locked. Codes are often issued per storefront and per currency, so a code from a retailer's UK site will not apply on its US one.
5. The redemption cap was hit. Retailers cap total redemptions, and when the cap is reached, the code stops working even though the published end date has not arrived.

How often do we re-check, and what happens to dead codes

Offers on active store pages are re-checked on a schedule, not only when someone reports a problem. When a code fails a re-check, it is either removed or relabeled as expired, and the last checked date is moved to the actual test.

We do not refresh a date without rerunning the test. A date stamp that advances on its own makes a page look current instead of being current, and it is one of the easier things for a reader to catch. If you want to see the range of what is live at any moment, /coupons carries the same dates as the individual store pages.

Some expired offers stay visible with an expired label rather than disappearing. Knowing that a retailer ran a 20% sitewide promotion in July is useful when deciding whether to buy now or wait, even if the code is dead.

What we will not publish

• Single-use codes are issued to an individual. They fail for everyone after the first use, and they cost the original recipient their discount.
• Employee, student, military, and first-responder codes are presented as open to everyone. Legitimate versions of these require verification through the retailer's own provider. Passing around a code that skips that step is fraud against the retailer and against the people the discount exists for.
• Codes produced by generating or guessing strings. Retailers treat this as abuse, and it can result in a shopper's account being closed.
• Offers whose terms we cannot find or read. If we cannot tell you what qualifies, publishing the code just moves the failure to your checkout screen.
• Headline discounts with no qualifying detail. "Up to 70% off" with no way to tell what is included is a number, not an offer.

How affiliate commissions fit in

Retailers pay us. When you click through to a store from here and buy something, we may earn a commission through that retailer's affiliate program, and that is the entire business model. Two consequences are worth stating plainly.

Commission rates do not change a test result. A code either applied to the cart or it did not, and a higher-paying program does not make dead code live. Our affiliate disclosure covers how this works in more detail.

The second one is less comfortable and rarely mentioned on pages like this. Most affiliate programs pay on a last-click basis, meaning the last partner link clicked before the purchase gets credit. Awin, describing its own reporting, notes that publishers who influence a purchase without being the last touchpoint can end up under-rewarded. In practice, opening any coupon site, or a coupon browser extension, after you have clicked a creator's link can move the credit for that sale away from the creator. If you meant to support a specific creator or publisher, click their link last.

How to check our work

You do not have to take a badge at face value. Three checks take about a minute.

1. Read the date, not the badge. The last checked date is the part that carries the information. An old one tells you to treat the offer as a lead rather than a sure thing.
2. Compare our fine print to the retailer's. Open the retailer's terms page for the promotion and check the restrictions we listed against it. If they disagree, the retailer is right, and we are wrong.
3. Tell us when something breaks. Send the store name, the code, and the error message through /contact. Broken codes get retested, and reader reports are the fastest signal we get. Our editorial standards describe who maintains the store pages.

Frequently asked questions

What does the verified label actually mean?

It means a person applied that code to a real cart at that retailer on the date displayed with the offer, and the discount applied. It is a record of a test that happened, not a prediction about your checkout. Restrictions, redemption caps, and account eligibility can all cause a genuinely verified code to fail for a specific shopper.

Do you test every code yourself?

Every code is tested before it is published, regardless of whether it came from an affiliate program, a retailer's own channel, or a reader submission. Offers sourced from a retailer's affiliate program are not treated as pre-verified, because network entries can remain live after a retailer ends or changes the promotion.

Why didn't a verification code work for me?

Most failures come down to five things: the code was single-use, your item is on an exclusion list, the offer is restricted to new customers, the offer is locked to a different country or currency, or the retailer's redemption cap was reached early. The error message at checkout usually points to which one applies.

Do you make money when I use a code?

Yes. Retailers pay a commission on referred sales, which is how the site is funded. It costs you nothing extra and does not change which offers get published or how they are ordered. If you clicked a creator's affiliate link before coming here, be aware that last-click attribution means our link can take the credit for the sale.

Can I submit a code I found?

Yes, through the coupon submission form. It goes through the same test as any other offer before it appears. We do not publish single-use codes tied to one shopper, or employee and student discounts presented as open to everyone, since both of those fail for the next person and cost someone else their discount.

How quickly do you remove expired codes?

Store pages are re-checked on a schedule, and codes that fail are removed or relabeled the same day the failure is found. Between scheduled checks, a code can die without us knowing, which is why the last checked date sits next to the offer and why reader reports go straight into the retest queue.

If a code is failing right now

Check the last checked date on the offer, then read the exclusions listed under it against what is in your cart. Those two steps resolve most failures. If the code still will not apply, /stores lists the other offers currently running, along with the restrictions that trip people up most often at that store.