How We Review Offers
How provider facts become clear, reviewable shopping information.
Live database totals—not marketing estimates.
Our review process is designed to answer practical shopping questions: Is this a real destination? What does the shopper receive? Who is eligible? Where does it apply? Is the evidence complete enough to publish responsibly?
No automated system can guarantee merchant acceptance. The purpose of review is to preserve evidence, reduce avoidable errors and communicate uncertainty honestly.
Evidence begins with the source
Every imported record starts with its provider identity and original content. The system can retain the raw title, description, image reference, offer identifier and other supplied facts separately from shopper-facing editorial text.
Approved sources
Integrations must be enabled, permission-reviewed and connected using configured credentials.
Source identity
Provider and offer identifiers help updates reach the same record instead of silently creating copies.
Destination ownership
Affiliate or merchant destinations must match trusted routing and safety rules.
Missing evidence
A missing expiry, country or discount is recorded as unknown rather than guessed.
Initial safety and quality checks
Before an imported item reaches publication, automated checks can reject unsafe URLs, unsupported content and advertising creatives that do not describe a usable offer. These controls reduce noise in the human review queue.
Records may also be quarantined when a merchant mapping is unresolved, a tracking host is not allowed, the source payload is malformed or important facts conflict. Quarantine is a safety state—not a public verification label.
Facts are normalized carefully
The offer-facts pipeline attempts to distinguish percentage discounts, fixed savings, recorded prices, minimum spend, coupon codes, plan or product variations, eligibility, dates and country scope.
Coupon code
The exact string a shopper is expected to enter at checkout, when one is supplied.
Code-free deal
A priced or promotional destination that does not require a code.
Geographic scope
Global, specific-country or unknown evidence is kept distinct.
Offer variation
Country, plan, product, minimum spend, code and landing-page differences can be legitimate variants.
A code-free deal without a supported discount should be presented as “Deal” or with a recorded price—not as “0% off.”
Duplicate and variant decisions
Exact source identities and canonical facts are compared so repeated imports update an existing record. At the same time, legitimate variants should not be collapsed merely because their store or headline is similar.
A UK landing page and a US landing page, two different plan lengths, or the same code with different minimum-spend requirements may remain separate when the source evidence supports those distinctions.
Human review and evidence labels
Offers requiring judgment remain private in the verification queue. A reviewer can open the merchant destination, inspect provider facts, edit shopper-facing content and choose the evidence level actually completed.
“Guru Verified” is reserved for the site's supported verification state. “Limited Evidence” communicates that a useful offer is public but some evidence remains incomplete. Neither label promises that a merchant will accept the offer for every visitor.
Guru Score is context, not a guarantee
Guru Score summarizes recorded signals such as review recency, checkout or proof evidence, community results, source reliability and terms clarity. It helps visitors compare the evidence available on the site.
The score may change as evidence ages, community feedback arrives or terms are updated. It is not a product rating, merchant rating or probability of success, and it must not replace the merchant's final checkout information.
Publication and ongoing monitoring
Publication policy evaluates status, destination safety, geography, expiry and evidence. Scheduled maintenance can reverify offers, expire records with known end dates, check link health, refresh scores and surface failed checks for review.
An offer may be corrected, temporarily held, expired, rejected or archived when the source disappears, the link fails, the terms change or reliable reports contradict the listing.
Community and merchant corrections
Yes/No feedback is an input, not proof by itself. Reports are reviewed alongside source facts, timestamps and destination evidence. Merchants may request corrections, but a request does not automatically erase legitimate shopper feedback or grant a verified status.
The safest final check is always the merchant checkout: confirm the item or plan, customer eligibility, region, currency and total immediately before payment.
Help us keep the record clear.
Questions about this website belong with our team. Questions about an order, delivery or refund belong with the merchant.