Throne Scanner · source to report
How we scan
Discover the catalogue. Read the exact product evidence. Show the result and its limits.
Current Standard 1.2.0 · Read the complete scoring methodology.
From a source page to a finding
| Step | What happens | What the report must show |
|---|---|---|
| 1 · Identify scope | Fix store host, market, locale and relevant product category | Identified source and scan date |
| 2 · Discover | Reconcile platform catalogue, feeds, sitemaps and product identities | Catalogue total and duplicate handling |
| 3 · Read | Attribute composition or ingredients to the exact SKU or component | Product URL, exact wording, date and extraction method |
| 4 · Separate outcomes | Distinguish assessed, undisclosed, unread, conflict and out-of-scope records | Counts, filter reasons and technical gaps |
| 5 · Calculate and review | Apply the relevant version and publication safeguards | Formula, denominator, coverage, score status and limits |
| 6 · Revisit | Re-read changed products and re-score usable evidence when rules change | Dated changes; prior source record preserved |
Public product evidence is the input. Customer accounts, orders, private checkout data and payment-card details are not catalogue evidence. Appearance comparisons such as “silky feel,” styling recommendations and unrelated page text cannot establish composition.
Successfully read but undisclosed products stay unknown. A failed page is unread, not undisclosed. Partial catalogue coverage is labelled; it does not become an authoritative full-range score. Paying buys access and processing, not approval or a favourable result.
Illustrative example · fictional catalogue
Read a textile report, line by line
This is a teaching example, not a finding about a real brand. One market, one locale, 100 eligible textile products; every product page was successfully read.
| Recorded outcome | Products | Credit toward verified plant rate |
|---|---|---|
| Complete plant-only composition | 80 | 80 |
| Quantified cotton/polyester blend | 10 | 0 |
| Complete wool composition | 5 | 0 |
| Readable page; composition undisclosed | 5 | 0 |
| Total eligible textiles | 100 | 80 |
80 verified plant products ÷ 100 eligible products × 100 = 80% → 3/5
The disclosed-only plant rate is 80 ÷ 95 = 84.21%; it is a different metric and does not replace the full-catalogue rate. The five undisclosed products are unknown, not synthetic. If three pages had timed out instead, the record would have a technical gap and would not qualify as an authoritative census.
| Example SKU | Product-specific source wording | Finding | Limit |
|---|---|---|---|
| DEMO-01 | 100% linen | Complete plant composition | Composition finding only; not proof of organic certification |
| DEMO-02 | 95% cotton, 5% elastane | Quantified mixed composition; no pure-plant credit | Not a statement about durability or toxicity |
| DEMO-03 | 70% cotton; other fibres not disclosed | 70% stated plant evidence, 30% unknown | No complete plant-product credit |
| DEMO-04 | Shell: 100% cotton; lining: 100% polyester | Separate complete components | Without physical weights, any permitted equal-component estimate is labelled |
| DEMO-05 | Composition unavailable on readable page | Undisclosed | No inferred fibre or vegan claim |
A real report must also identify the product URL, date, source wording, standard and reader versions, catalogue identities, exclusions, coverage, conflicts, market and locale. A brand-level result never substitutes for an unmatched SKU.
Reports, product widgets and exports
A supported product widget must match the product’s actual SKU or platform variant ID; it cannot use an unrelated brand average. Comparisons and per-product tables keep source links, market, dates and uncertainty visible.
Available access, report limits, refresh schedules and any Large Catalogue add-on are those stated for the selected product at checkout or in a written order. An existing approved result may be reused while it remains valid for that service. A refresh promise does not mean every source is continuously available.
Member exports use Throne Scanner branding, website and Account links, product sources and recorded dates. CSV and Google Sheets exports omit affiliate columns. Sheets are exported to the member’s connected Google account; disconnecting access prevents future exports, but does not delete a spreadsheet already created there.
For any Large Catalogue order sold with the existing 48-hour completion or add-on fee back promise, the clock starts after payment and usable catalogue access are both received. If the promised complete scan is not delivered in that period, the add-on fee is refundable. This promise does not buy an unsupported score and does not reduce statutory rights.
Your account and exports · Submit a source-backed correction · Products, payment and API terms