Listara

Test report vs Declaration of Conformity: what should match the SKU?

Understand the difference between a test report and Declaration of Conformity, and how to map both to SKU-level marketplace evidence readiness.

Last reviewed
2026-06-10
Short answer

A test report and a Declaration of Conformity play different roles in the evidence chain. For marketplace readiness, both should point to the same product, model, manufacturer, applicable standards, and technical documentation where relevant.

Direct answers

definition

What is Test report vs Declaration of Conformity evidence readiness?

Test report vs Declaration of Conformity evidence readiness means checking whether the relevant document or evidence set can be connected to the exact SKU, model, manufacturer, and marketplace listing being reviewed.

risk

What is the main evidence risk?

The main risk is that a document exists but cannot be traced to the product, variant, model, or listing that triggered the review.

risk

Does Listara certify CE compliance?

No. Listara provides an operational evidence-readiness review and does not provide legal advice, certification, laboratory testing, or official marketplace approval.

Source-backed points

official

The European Commission states that manufacturers are responsible for conformity assessment, the technical file, the EU Declaration of Conformity, and CE marking where required.

Listara uses this as context for checking whether CE-related evidence is organized and mapped to SKU-level records.

Source: CE marking
official

Your Europe explains that technical documentation must demonstrate that a product complies with EU requirements and supports the EU Declaration of Conformity.

Listara translates that document chain into an operational evidence-readiness workflow.

Source: Preparing technical documentation
CriterionOption AOption BListara angle
PurposeA Declaration of Conformity states the responsible party's declaration for the product.A test report can support the evidence chain by showing testing or assessment evidence.Listara checks whether both records point to the same SKU or model.
Typical mismatchThe DoC names one product family.The test report names a different model or variant.The mismatch becomes a SKU evidence gap.
Operational next stepConfirm declared product, manufacturer, standards, and date.Confirm report scope, model, standard, and version.Map both to the SKU evidence record before marketplace review.
Evidence areaTypical evidenceCommon gapListara output
Product identityproduct name, model number, SKU or ASIN, batch or serial referenceDocument names a product family or model that does not clearly match the SKU.SKU-to-document match status
Responsible partymanufacturer, authorised representative, importer where relevantManufacturer or responsible party differs between listing and document.Identity mismatch flag
Standards and rulesEU legislation, harmonised standards, directive or regulation referencesStandards are missing, outdated, or not linked to the product feature.Standards review action
Support evidencetechnical file, test report, risk assessment, labels and instructionsSupport file is missing, unavailable, or not linked to the declaration.Missing support evidence queue

Where teams usually get stuck

  • Gaptest report covers different variant
  • GapDoC references standard not shown in report
  • Gapmanufacturer mismatch
  • Gapmodel number mismatch
  • Gapreport date/version unclear

Sample SKU evidence-record table

SKU / ASINEvidence areaStatusExample gapNext action
SKU-CE-101Test report vs Declaration of ConformitypartialDocument exists but model does not clearly match SKU.Request matching document or map to correct variant.
SKU-CE-214Technical documentationunclearSupport file reference is missing.Link DoC to technical file and test evidence.
SKU-CE-309Manufacturer identitymissingManufacturer differs between listing and declaration.Resolve manufacturer record before review.

Related evidence checks

FAQ

What is Test report vs Declaration of Conformity?+

Test report vs Declaration of Conformity is treated here as a product evidence topic: the relevant document or evidence field must be traceable to the SKU, model, manufacturer, and marketplace listing being reviewed.

Why does SKU mapping matter?+

A document can exist but still be weak evidence if it cannot be connected to the exact product, variant, or ASIN being sold.

What should teams check first?+

Start with product identity, model number, manufacturer, standards, support files, and whether the document matches the listing or SKU export.

Can Listara create or certify these documents?+

No. Listara reviews operational evidence readiness. It does not provide legal advice, certification, laboratory testing, or official marketplace approval.

Does the free check require document upload?+

The free check can begin from public listing signals. A full SKU Evidence Readiness Pilot can review uploaded catalog and evidence files.

Sources and references

  1. CE marking, European CommissionCE marking responsibilities and documentation context
  2. Preparing technical documentation, Your EuropeTechnical documentation and EU Declaration of Conformity context
SKU Evidence Readiness

Find evidence gaps before marketplaces ask for them.