How we match products
Every spec on SnowSift earns its way onto the page. This is the methodology behind the “Verified specs” badge — written to be checkable, not impressive.
Last updated August 19, 2026
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:
- 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.
- 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.
- 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.
- 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.
Size-varying specs are quoted at one length
On a ski or a snowboard, several specs are not one number at all — sidecut radius, weight, effective edge, tip and tail width, and on many models the waist too. A manufacturer publishing a spec table for six lengths is usually publishing six different turn radii. Which specs move, and by how much, varies by model: some skis hold one waist down the whole size run, others widen it by several millimetres.
That breaks the comparison at the heart of our verification: two independent readings of the same page can each be perfectly correct and still disagree, simply because one read the 166 cm row and the other read the 184 cm row. So both readers are told to use the same anchor — the shortest length the manufacturer lists — and that is the length we quote.
Being precise about how strong that is: the anchor is an instruction to both readers, not something we can verify deterministically after the fact, and the tolerances we compare them with are deliberately wide enough that two different-size readings still count as agreement. The rule also post-dates our first catalogue crawl, so the oldest rows were read before it existed and have not all been re-read since. It is how we ask for the number, not a guarantee we can prove about every row — and we would rather tell you that than imply a precision we don't have.
So we mark the affected rows in the spec panel and, where the manufacturer publishes a length list, name the anchor length in a footnote beneath them. Two consequences are worth stating plainly. If you ride a longer size, your turn radius will be longer and the ski will weigh more than the headline figure. And because each product is anchored to its own shortest length, two products are not directly comparable on those rows — a women's ski anchored at 146 cm will show a much shorter radius than the same ski anchored at 164 cm, and that gap is the anchor, not the design. Check each product's footnote before reading anything into the difference.
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.