Data quality

Listings we refused to publish

Vendor search is fuzzy. Ask a store for “Hexarelin” and it will cheerfully hand back Dihexa — a different molecule at ten times the price. Before any price reaches this site, a guard checks that the product actually is the compound we asked for. Everything it turned away is listed below, with the reason.

Why show this at all?

Because the failure is invisible from the outside. A row reading “Dihexa · $469” under a Hexarelin heading looks like odd vendor naming, not a mismatch — and it came with a working buy button. Publishing the rejections is the only way to show the filter exists and is doing something. This page is generated from assets/data/price-rejections.json, written by the same job that refreshes prices.

Loading…

How the check works

A product is accepted only when its title names the compound on whole-word boundaries — not as a stray substring. Dihexa contains the letters hex, but not the word Hexarelin, so it is turned away. Roman numerals are folded first, so Melanotan II and Melanotan 2 are recognised as the same thing while neither is confused with Melanotan I.

When a title legitimately names two compounds, the more specific one wins. CJC-1295 NO DAC (Mod GRF 1-29) really does contain Sermorelin’s alias “GRF 1-29” — but it names CJC-1295 more precisely, so the listing is filed there and rejected from Sermorelin. The rule lives in scripts/identity.mjs and is pinned by tests in scripts/identity.test.mjs.