Why can trust scores only be compared within one rules version?

Because a change in the formula is our step, not the store's. When weights move, every score moves with them, and a chart that crosses versions shows movement that no store made. Each daily snapshot carries the version it was computed under, and this page says what each version changed and when it was in effect.

What is the current version of the StoreProfiles trust score?

Rules v0.8. Under it the verified tier is only added once a store's images, descriptions and pricing clear a quality bar, so collected facts cannot offset an unfinished catalog.

Changelog · DOC-0008

What each version of the formula changed

Scores are comparable only within one rules version — the dataset says so and every snapshot carries its version. That instruction is only usable if the version means something, so here is what each one changed and the days it was in effect. Dates and coverage below are read from the snapshots themselves.

rules v0.8in effect

2026-07-27 → 2026-07-29 · 1,139 stores

The verified tier sits on top of finished basics

→Collected external facts — policies, a sampled review rating, server speed — stop being worth points until images, descriptions and pricing clear 90% of their combined maximum. The facts are still collected and still shown; they just no longer offset an unfinished catalog.
→The gate excludes catalog depth on purpose. Gating on the whole feed tier would have stripped the verified tier from 491 of the 1,059 stores that had one, punishing small brands for being small; the quality gate touches 156.
→Every unclaimed profile now states its ceiling and the reason for it.

rules v0.7

2026-07-25 → 2026-07-27 · 1,066 stores

Recalibrated so the top of the scale is earned

→What every real brand does by default was made cheap and what has to be earned made expensive: on-record fell from 20 points to 5, claiming rose from 5 to 15, and the verified tier from 5 to 20.
→Full catalog-depth credit now needs 300 effective products rather than 100, counted as distinct titles scaled by the real catalog size.
→The artificial 95 cap was removed: the component maxima sum to exactly 100, so the published receipt adds up to the headline.

rules v0.6

2026-07-21 → 2026-07-24 · 737 stores

Collected facts entered the score

→A verified tier was added: points for a published refund and shipping policy, a sampled product rated 4.3+ across 50 or more reviews, and a sub-400 ms server response — awarded only when the fact was actually collected.
→Snapshots began carrying the rules version, so a change in the formula could never again read as movement by a store.

rules v0.5

2026-07-18 → 2026-07-20 · 736 stores

One formula, and honest catalog depth

→The scoring formula became a single source of truth shared by the scorer, the API, the profile and the smoke gate, so the receipt shown to a reader is the arithmetic that produced the number.
→Catalog depth started counting the store's real catalog size instead of the 100-product sample we happened to store.

unversioned

2026-07-19 → 2026-07-19 · 125 stores

Snapshots written before the version was recorded at all. We know which formula was live that day, but not with the certainty the rest of this page is held to, so they are labelled rather than guessed — and they are excluded from every comparison and from the snapshot count published on the dataset page. They stay on record because deleting inconvenient rows is not how this registry behaves.

Reading history correctly

The history[] array on every store returns rules_versionwith each row for exactly this reason. Filter on it before plotting. A profile’s own trend chart does the same and simply disappears for a few days after a version change rather than drawing a step that no store took.

The current formula The dataset