CouponFYI Frequently Asked Questions

We don’t pull coupon codes from one place, and I’m not going to pretend we do.

Some of the offers we share here come straight from stores and service providers, through their websites, promotions, or marketing emails. Some come through affiliate and partner networks, where retailers and their partners share coupon information with sites like ours. A lot come from the same places you’d find them yourself: the open web, social media, search results, and other public sources.

Shoppers help too. When someone uses a code from CouponFYI, they can tell us whether it worked. That matters, because a code that was solid last week can be dead today, and a shopper’s report can be a useful way for us to find that out.

The source can be different from one listing to the next. So we don’t treat every coupon like it came straight from the retailer, because not every listing does.

One more thing worth being clear about: where a code comes from and whether it’s been verified are two separate things. A code can come from a retailer, a partner network, the open web, or a shopper report, none of that by itself makes it Verified by Editor. Verification is about what I was actually able to confirm at checkout, not where the code originally showed up.

Finding a code is easy. Knowing whether it actually still works is the hard part.

I’m not going to claim every single code gets a personal checkout test from me, because that’s not true. When I can test a code myself, I do. That means going through an actual checkout, adding something to a cart, entering the code, and seeing whether the discount actually shows up.

Beyond that, we work with what’s available: shopper reports, source information, freshness, the discount itself, and whatever terms are attached to the offer.

Here’s why that combination matters. A checkout test tells you the code worked at that exact moment, under those exact conditions. It doesn’t tell you it’ll work an hour from now, for a different product, or for someone in a different country. That’s where shopper reports can help.

That’s also where the labels you see next to our codes come in.

Verified by Editor means a CouponFYI editor personally tested the code at checkout, and it worked at the time of that test. The timestamp shows you when that happened.

Reported Working means a shopper told us the code worked for them recently.

Last Used shows the most recent recorded activity associated with the code on our site, such as when someone copied or tried it. Think of it as an activity or freshness signal. It does not prove that the discount was successfully applied, and it doesn’t guarantee the code will work for you.

One important distinction: these status badges apply to coupons only. They don’t apply to regular deals or to listings in our “Expired Coupons & Deals” section. Expired coupons and past deals are kept separate from the active coupon listings, so a badge shouldn’t be taken as a verification or freshness signal for those listings.

That’s the whole idea. Test a code when we can, use shopper feedback as another piece of information, keep an eye on how fresh the information is, and be honest about what we actually know. No pretending every code is guaranteed.

Testing a code isn’t just about whether the retailer accepts it at checkout. I’m looking at whether the discount actually shows up on the total, and whenever the retailer’s checkout makes it visible, what conditions come attached, things like a minimum order, first-time-customer restrictions, specific products, or account requirements.

A code getting accepted isn’t the whole story. What matters is whether the discount it promised actually applied, under the conditions I was testing it with.

We go off what we actually know: how fresh the code is, whether it’s been tested, what shoppers are reporting, and what restrictions we’re aware of.

A bigger number doesn’t automatically win.

A 10% code that’s fresh, relevant, and getting recent positive activity can be more useful than a 50% code that’s months old, loaded with restrictions, and hasn’t had supporting activity in a while.

So when we sort what you see, we’re going off the information and evidence available to us, not just slapping the biggest percentage at the top and calling it a day.

Then I just say that.

Not every code gets tested, and not every code has shopper reports yet. When that’s the case, I’m not going to slap “Verified” on something I haven’t actually checked. You’ll see it listed with whatever information is available, source, freshness, maybe nothing at all yet, and that’s the honest state of it. “I don’t have enough evidence” is a real answer here, not a gap I’m trying to hide.

Here’s the part nobody likes hearing: even a code I’ve personally tested can fail for you.

That doesn’t mean I got it wrong or the code was fake. It can simply mean the promotion works differently depending on who’s using it.

Maybe it’s limited to first-time customers. Maybe it only applies to certain products. Maybe there’s a minimum order, a country restriction, an account-specific rule, or the retailer simply ended the promotion after I tested it.

Retailers can change things without warning.

I can’t control a store’s checkout system. No coupon site can. What I can do is tell you exactly what I know, when I knew it, and skip the part where I pretend every code is bulletproof.

For more help, read Why is My Promo Code Not Working? and Can You Use Expired Coupons?.

A code testing successfully once doesn’t mean it stays that way forever.

If shoppers report a code has stopped working, or I find out the store changed the promotion, I go back and update the listing to reflect that. A code that passed my test last month isn’t proof it’s still good today, that’s exactly why the timestamp matters. It tells you when the test happened, not that the result still holds now.

I’d rather update the page than leave an old test sitting there looking like current proof.