How we match products

The core rule: verified, or not shown

SnowSift never publishes a spec it isn't confident in. When our verification pipeline can't confirm a product's data, that product is held back in a review queue for a human to adjudicate — it simply doesn't appear on the site. We'd rather show you fewer products than show you a wrong number.

Verification means independent channels agreeing

A single automated reading of a page — however sophisticated — can be wrong in ways it can't see itself. Two similar systems can even be wrong together. So a product is verified on SnowSift only when independent channels, each with different failure modes, agree about it:

1. Source capture. We fetch the manufacturer's own product page — the primary source for what a ski or board actually is — and store a snapshot of it.
2. Independent double extraction. Two separate automated systems each read the same snapshot and independently produce the full spec sheet (geometry, flex, profile, weights, MSRP). Neither sees the other's answer — so they can't rubber-stamp each other. The two sheets are compared deterministically, field by field, with strict tolerances (a ski's waist width must match exactly; a weight may differ by a few percent). Identity signals — brand, model, season, category — must agree outright.
3. The manufacturer's structured data. Most manufacturer pages carry machine-readable product data (schema.org markup — the same data Google reads). We parse it with plain deterministic code — no AI involved — and it must agree with the extracted identity and pricing. This is a genuinely independent check: a parser and a language model do not make the same mistakes.
4. Verdict. Channels agree → the product is published with its source URL and its verification channels attached (you can see them under each product's specs). Channels disagree → the product goes to the human review queue, not to you. Pages with no structured data are held to a stricter agreement bar and are automatically re-verified as new channels come online.

More independent channels are coming: when live retailer data feeds arrive, their product attributes become another cross-check, and products verified today are automatically upgraded against them.

Never guess, never pad

If a manufacturer doesn't publish a spec, the field shows a dash (“—”). We don't estimate, interpolate, or copy numbers from third-party sites. A dash is a fact about the manufacturer's data; a guessed number would be a lie about ours.

Why we don't quote an accuracy number

You'll notice this page claims no percentage. That's deliberate. An honest accuracy figure requires an independent measuring stick, and we won't manufacture one to have a marketing number. What we can honestly promise is structural: every published spec survived agreement between independent checks, anything that didn't is hidden, and every product shows which checks verified it. No number, no vibes — just a process you can inspect.

What happens when price comparison launches

For the 2026/27 season, SnowSift will add live cross-retailer price comparison from official retailer data feeds. Every price row will be matched to its product using the same philosophy: multi-signal agreement (brand + model + season + key dimensions), a strict confidence threshold, and asymmetric disclosure — a listing that can't be confidently matched is hidden, never shown with a “maybe”. Visible rows will carry a “✓ Verified match” badge; you'll never see a raw confidence percentage, because a number like that isn't information you can act on — hiding the row is.

Found an error?

Tell us: data@snowsift.com. Spec reports go straight into the review queue, get re-verified against the manufacturer source, and fixed. See also About SnowSift.