Data Sources & Verification

Every commercial claim on DatesOracle — price, availability, merchant — is tied to a verifiable source record. Here is exactly how that works.

Where our data comes from

Product attributes (variety, texture, sweetness, origin) are compiled from merchant product pages, brand specifications and, where available, our own editorial testing notes. Commercial data — prices, availability, and merchant links — is sourced directly from the merchant’s own product page at the time of verification.

How verification works

Each offer carries an explicit verification record covering five checks: the merchant URL is reachable, the product page matches the listed item, the variant and weight match, availability is confirmed, and the price is current. An offer only displays a live price after all five checks pass. Every verified offer shows a last-checked timestamp so you know exactly how current the information is.

What happens when data can’t be verified

If a price cannot be verified, we display “Price unavailable” rather than showing a stale or estimated number. We do not interpolate or guess at pricing.

Price history and benchmarks

Where price history is shown, it is built exclusively from recorded snapshots at the time they were captured — not projected or estimated. If no snapshot history exists for a product, no benchmark is shown.

How often data is refreshed

DatesOracle refreshes the catalog through structured verification batches rather than a fixed automatic interval. Each offer carries its own last-checked timestamp, and a price is displayed only when that offer has passed the full verification record in its most recent batch — merchant URL reachable, product page matched, variant and weight matched, availability confirmed, price current and affiliate link valid. An offer that has not passed its checks is shown as “Price unavailable”, never estimated.

Reporting an issue

Noticed outdated or incorrect data? Let us know through our Contact page.