How Savings Stacks verifies offers

Our standard, in one line

An offer counts as verified savings only when it's confirmed, recently checked, eligible to show, and clearly labeled — and we'd rather show fewer verified things than a long list of unchecked ones.

How an offer gets checked

For selected stores and products, a verified offer goes through a review that confirms:

1. The product page and price at a specific store, captured as evidence.
2. Each savings layer we claim — for example, whether a code applies at a real checkout, and what a cashback or card layer is worth (noting those values can vary by account, location, card issuer, portal, and timing).
3. The stack math — recomputing the final price from only the layers that actually applied.

Every confirmed item carries a last-checked date, and anything we can't confirm is labeled and demoted rather than presented as working. We verify where possible — and we don't claim every code works.

Why “last checked” is front and center

Prices, stock, and codes change constantly, so freshness is part of the claim: an offer that hasn't been re-checked recently stops counting as verified until someone looks again.

Demo and unverified data are labeled — on purpose

While we build out the verified catalog, some data is clearly marked demo / sample. We label it plainly rather than letting example data masquerade as live, verified offers. If we don't have a verified savings stack for something, we say so.

What this is not

• Not a price guarantee — retailers set and change prices.
• Not a claim to cover everything — we focus on selected stores and products.
• Not a guarantee your cashback or card reward will match an example — those can vary.

The takeaway

Verification here is a process, not a badge: confirm the offer, capture evidence, check the math, stamp the date, and label anything unconfirmed. The result is fewer, better-trusted numbers — and a clear statement when we don't have one yet. See also how affiliate links work.