Do product variants need separate technical files or can one file cover an entire range?

Default hero background
Uncategorized
Jason van de Zande

One technical file can cover an entire range of product variants when the variants share the same core design, materials, intended use, and safety profile, and when the risk assessment and safety information remain valid for every model. If a change affects safety-relevant characteristics or the evidence needed to show safe use, each affected variant needs its own technical documentation set or a clearly separated addendum.

For EU GPSR compliance under the General Product Safety Regulation (EU) 2023/988 (GPSR), the practical rule is simple: authorities must be able to verify, quickly and unambiguously, that the exact variant being sold is safe and properly documented.

The questions below explain when a shared file works, what triggers a separate file, and how to structure a variant family file so EU market surveillance can check each model efficiently.

When can multiple product variants share one technical file?

Multiple product variants can share one technical documentation file when they are a true product family: the same base design and manufacturing controls, the same intended and reasonably foreseeable use, and no changes that alter hazards, risk levels, or required warnings. The file must still identify each variant clearly and show that the safety evidence applies to all.

In practice, a shared file works best when differences are cosmetic or administrative rather than safety-relevant. Examples that often fit a single family file include:

  • Color changes using equivalent, proven safe pigments and coatings
  • Branding or labeling layout changes that do not remove required safety information
  • Packaging artwork changes where packaging does not create new hazards
  • Minor dimensional tolerances that do not affect stability, strength, heat, sharp edges, or access to hazardous parts

To keep EU market surveillance reviews smooth, the technical documentation should map each SKU or model number to the same underlying safety justification, and it should explain why the differences do not change the risk assessment.

What changes require a separate technical file for a variant?

A separate technical documentation file, or a clearly separated variant-specific annex, is needed when a change can affect safety, compliance evidence, or the conditions of safe use. If the variant introduces new hazards, changes risk controls, or requires different instructions or warnings, authorities will expect documentation that specifically covers that exact product variant.

Common triggers for splitting out a variant include changes to:

  • Materials or chemical composition such as a new plastic, coating, adhesive, dye, or flame retardant that could affect toxicity, migration, flammability, or skin contact risks
  • Electrical or electronic design such as a new power supply, battery chemistry, charging method, firmware behavior tied to safety functions, or different operating voltage
  • Mechanical safety such as load-bearing parts, fasteners, stability, moving parts, pinch points, sharp edges, or small parts that affect choking risk
  • Thermal performance such as higher operating temperatures, different heat dissipation, or new hot surfaces
  • Intended use or user group such as marketing a general product for children, or changing from indoor to outdoor use
  • Manufacturing site or critical process when the change affects quality controls tied to safety, for example welding, molding parameters, or supplier changes for critical components

A useful test is whether you would need to update the risk assessment, instructions for use, warnings, or test evidence to stay confident the variant is safe. If the answer is yes, treat it as variant-specific documentation.

How should you structure a “family” technical file so authorities can verify each variant?

A family technical documentation file should be structured so an authority can pick any product variant and immediately find its exact identifiers, configuration, safety-critical parts, and the evidence that supports safe use. The best approach is a shared core file plus controlled variant annexes, with a clear index that links each SKU to its documents.

To make verification straightforward for EU market surveillance, include:

  • Variant register listing model names, SKUs, batch or serial logic, photos, and distinguishing features
  • Configuration matrix showing what differs by variant, including components, materials, ratings, and software versions where relevant
  • Risk assessment mapping that states which hazards are common to the family and which are variant-specific, with controls and residual risk per variant
  • Evidence mapping linking each variant to applicable test reports, calculations, supplier declarations, and quality checks
  • Instructions and warnings with a clear indication of which language versions and which warnings apply to which variant
  • Change control documenting when a variant was introduced, what changed, and why the existing safety justification still applies or what new evidence was added

Also ensure the file is searchable and internally consistent. If a marketplace listing shows Variant B, the technical documentation should use the same identifiers and images so there is no ambiguity during an authority request.

Finally, remember that under the Market Surveillance Regulation (EU) 2019/1020 (MSR), the Responsible Person is an economic operator role that must be able to provide information and documentation to authorities upon request and must inform the manufacturer when there is a risk concern under Article 4. Clear variant structure makes that response fast and accurate.

How [COMPANY] helps with technical documentation for product variants under the GPSR?

For product variants, the fastest path to EU GPSR compliance is a documentation system that proves each SKU is covered, keeps variant evidence organized, and stays ready for EU market surveillance requests. We support this by reviewing your technical documentation for completeness, setting up a family file structure, and maintaining controlled access and storage so the right variant materials can be provided when requested.

  • Variant family mapping to define what belongs in the shared core file versus variant annexes
  • Completeness checks to verify required safety documents are present for each product variant and aligned with identifiers used in listings and labels
  • Documentation storage and retrieval so technical documentation can be made available to authorities efficiently when requested
  • GPSR Responsible Person support to help keep your EU market access stable as your catalog changes

To discuss your product range and set up a compliant variant documentation approach, contact us at our contact page or review our services to see the best fit for your catalog.

Related Articles