Oopbuy coupons explained: a scorecard for judging any code you find

What a scorecard is for

Coupon hunting has a bad signal problem. The number of pages claiming to hold working codes is far larger than the number of codes that still work, and the pages that rank highest are usually the ones with the strongest template rather than the freshest list. A scorecard does not fix that. It does something narrower and more useful: it tells you how much weight to put on a claim before you spend time on it.

We score the source, not the code, because the code itself is the cheapest thing in the transaction to test. The expensive part is the five minutes you spend reading a page that turns out to be a template with last year's codes. Six criteria, five points each, thirty points maximum. A high score does not mean the discount is large. It means the claim is checkable.

The six criteria we score

Score the source before you score the discount

Not every source type deserves the same baseline. A page on a seller's own domain has an incentive to keep its codes current, because an expired code on your own site is an embarrassment. An aggregator has an incentive to publish many pages, and freshness is expensive. A screenshot in a chat has no verification path at all. Our baseline scores below are our own rubric, not a measured study, and you can move them around to match your own experience.

The discount claim: what we can check and what we cannot

Here is the part most coupon pages skip. We can check whether a code is accepted at a checkout field and whether the total changes. We cannot check whether the resulting price is the lowest price that item has ever carried, because establishing a historic low requires a price history, and our own index is a single snapshot dated 2026-11-08. One snapshot cannot prove a low, and neither can a page that shows a crossed-out number.

So when a page says a price is 40% off, the honest reading is that the page says it. We have no way to verify the crossed-out baseline, and we are not going to claim that any discount is misleading, because we cannot prove that either. If a discount matters to your decision, compare the discounted total against the ordinary total from the same day, which is a comparison both numbers can survive.

A worked scorecard on a typical code

Take a code found on an aggregator page with a block of text, no author, and a countdown timer that resets when you reload. It claims a percentage off and shows a crossed-out price. Score it with our six criteria and it does not reach double digits. That does not make it false. It makes it unverifiable, which is a different and more manageable problem.

The useful output of that table is not the score. It is the two cells that would raise the score fastest: a date and stated terms. When you see both, the page has done the work that separates a maintained list from a copied one. When you see neither, you already know how much of your afternoon it deserves.

Where coupon pages go wrong

The failure modes are structural rather than malicious. A page is built to rank, codes are harvested from anywhere, and nobody is paid to remove the ones that stopped working. The result is a page that gets traffic precisely because it looks comprehensive. Three patterns are worth recognising on sight.

• The undated list: dozens of codes, no check date, no author, no contact route.
• The resetting countdown: urgency that re-creates itself every time the page loads.
• The screenshot offer: a picture of a discount with no code, no link, and no way to test it.
• The copied list: identical wording and order on several unrelated domains.

None of those patterns proves anything about the discount. What they prove is that the page is not being maintained, and a page that is not maintained is the wrong place to spend attention on a purchase decision. That is the whole judgement, and it takes about ten seconds.

How to test a code in four minutes

Testing is cheaper than reading, so here is the order we use. It assumes you already have an item in a cart, because a code that cannot be applied is not a code. Each step either produces evidence or ends the exercise, and most wrong codes end it at step two.

• Step 1: note the total before you touch anything, including the shipping line you selected.
• Step 2: apply the code and read the error, if any, word for word.
• Step 3: if the total changes, screenshot both totals with the date visible.
• Step 4: if it does not change, check the terms for a minimum basket you have not met.

Our position on codes

oopbuy.sbs is an independent guide. We are not oopbuy.com, we do not sell anything, and we do not run a coupon list, because we cannot verify a list well enough to publish one. We earn a commission when readers use our outbound links, and we do not publish a percentage because we have no commission figure to publish. That is the full disclosure, and it is why this page teaches a method instead of printing twenty codes.

The only coupon claim I fully trust is the difference between two totals I checked myself on the same day.

If you want a number to carry away, make it the score threshold. Anything under 12 out of 30 is a lead to test if you happen to be at a checkout anyway. Anything over 20 is worth reading before you buy, because a maintained source with dates and terms is telling you something even when its code has expired.

Back to the top