StoreSteadyStoreSteady
StoreSteady taxonomy v1.0

Canonical product assertion

A single product fact (material, capacity, certification, compatibility, dimension, ingredient, warranty term) expressed in a machine-and-human-readable form, tied to a canonical source and timestamp, that serves as the atomic unit of `product-truth`.

Term code: TRU-ASSERTFamily: TRU · Product truth and identityLast reviewed: 2026-05-20

Definition

A single product fact (material, capacity, certification, compatibility, dimension, ingredient, warranty term) expressed in a machine-and-human-readable form, tied to a canonical source and timestamp, that serves as the atomic unit of `product-truth`.

StoreSteady treats canonical product assertion as a reference term because No canonical source: Assertion has no tied source artifact, so it cannot be verified.

Why it matters

  • No canonical source changes what a crawler, shopping channel, or AI assistant can safely infer about the merchant surface.
  • Without a named category, operators tend to treat canonical product assertion as generic AI noise instead of a reproducible finding with evidence and a validation path.

Evidence sources

  • discrete, verifiable, objective product facts; their canonical source artifact; the timestamp of last verification; the version of the canonical source.

How StoreSteady detects it

Live

Extract assertions from PDPs, marketing pages, and structured data. For each, verify the asserted fact against the cited source's current version. Flag assertions with no source, stale verification, or version mismatch.

False positive risks

  • "Best battery on the market" - subjective; not an assertion.
  • "Long-lasting" - vague; not a verifiable assertion.

How to fix it

  1. Identify the merchant-controlled source that creates the canonical product assertion signal.
  2. Reconcile visible copy, machine-readable data, policy text, feed state, and checkout behavior where the term applies.
  3. Keep the fix high-level in public docs; detailed remediation belongs inside paid scan workflows.

How to validate it

Rerun the same evidence capture used for detection. The finding is validated only when the original canonical product assertion signal no longer reproduces and adjacent source surfaces still agree.

Example finding

warning

No canonical source

Observed: Assertion: "Battery capacity: 5000 mAh" - source: manufacturer datasheet v2.1, verified 2026-05-01.

Likely impact: No canonical source: Assertion has no tied source artifact, so it cannot be verified.

Probable fix location: Public commerce source of truth

Related StoreSteady issue codes

CodeTitleScanner mapping
TRU-001GTIN or primary identifier mismatchstrong_id_inaccurate
CLM-001Unsupported objective claimPlanned detector

Related standards

See also

Sources

Run a scan against this category

StoreSteady scans public commerce evidence and maps findings back to documented taxonomy terms.

Run a free scan