Regulatory guidance and project coordination

Product Compliance Consultant

Scope and evidence must be confirmed before any paid tests or filings.

A product compliance consultant is most useful before you buy testing, submit an application, print a mark, or commit to a launch date. The consulting task is not to produce a generic list of standards. It is to determine which legal and technical routes are actually relevant to a defined product in defined markets, identify what is still unknown, decide which existing evidence can be reused, and sequence the next steps so that testing and filings are purchased only when their purpose is clear.

Start with the facts that can change the compliance route

The route can change when the product, intended use, user group, technology, target market, supply-chain role or commercial model changes. A consultant should therefore classify the facts before treating any certificate, laboratory report or supplier statement as sufficient.

Decision inputWhy it mattersEvidence to gather first
Product function and intended useDetermines the likely regulatory category and which requirements may overlap.Specification, user manual draft, intended-use statement, product photos.
Target countries and sales channelThe same product may need different approvals, responsible parties, language sets or filing steps in different markets.Country list, launch order, online/offline channel, importer/distributor structure.
User group and risk profileChildren, professional users, hazardous environments or safety-critical uses can trigger different rules or conformity routes.Age grading, foreseeable users, hazard analysis, operating environment.
Electrical, radio, battery, software or chemical featuresAdditional regulatory layers may apply even when the base product category is unchanged.BOM, radio module details, battery cell/pack data, software functions, material declarations.
Branding and economic-operator roleManufacturer, importer, distributor and private-label roles can carry different legal responsibilities.Entity map, contracts, label artwork, who places the product on each market.
Product changes and variantsA previous report may cease to cover a new variant if safety-relevant hardware, firmware, materials or intended use changed.Revision history, change log, old reports, component equivalence data.

How a consultant should select the route

A defensible strategy separates four questions that are often mixed together: what law applies, what technical requirements show conformity, what conformity-assessment procedure is required, and what evidence must exist at the moment of placing or making the product available on a market.

  1. Classify the product and transaction. Define the finished product, intended use, user, market, responsible economic operator and whether the item is new, modified, imported, private-labelled or supplied as a component.
  2. Map mandatory regimes before standards. Standards can support a legal requirement, but a standard number alone does not tell you which law applies or whether third-party assessment is mandatory.
  3. Choose the conformity route. Determine whether the applicable regime permits manufacturer self-assessment, requires an approved/notified/accredited third party, requires registration or filing, or combines several routes.
  4. Define the evidence package. Map each legal requirement to a document, analysis, test report, declaration, label or traceability record.
  5. Set hold points. Do not start irreversible testing, tooling, packaging print or filings until the classification assumptions that drive those purchases are confirmed.

Official guidance illustrates why this sequence matters. In the EU, not every product requires CE marking, more than one EU act can apply to the same product, and the need for a notified body depends on the applicable product legislation. In Great Britain, sector rules determine the conformity route and more than one regulation may apply. In the United States, different federal regimes can impose different authorization or certification mechanics—for example, CPSC certification rules for regulated consumer products and FCC equipment-authorization procedures for many RF devices. These examples are not interchangeable checklists; they show why classification must precede execution.

Run a gap analysis before ordering new tests

The practical question is not “Do we have certificates?” but “Which required propositions are already supported, which are unsupported, and which existing records can be reused without overstating their scope?” A useful gap analysis connects requirements to evidence and records the reason for each reuse decision.

Existing evidencePotential reuseConsultant check before relying on it
Test report for a previous modelPossible where the tested construction remains representative.Compare model identifiers, critical components, materials, firmware, ratings and test-standard editions.
Supplier certificate or declarationUseful as an input or supporting record.Confirm issuer, scope, product identity and whether the document satisfies the actual legal requirement.
CB Scheme or other international test evidenceMay reduce duplicated technical work in routes that accept or build on it.Check destination-country deviations, report validity/edition, product identity and local approval steps.
EU technical file / risk assessmentCan be a strong source for design evidence and hazard analysis.Do not assume it automatically satisfies another jurisdiction; remap evidence to that jurisdiction's requirements.
Component approvalsCan support the finished-product assessment.Verify installation conditions and whether finished-product testing is still required.

Evidence reuse is therefore a controlled equivalence exercise, not a promise that one certificate opens every market.

Set the strategy before testing or filing

A consultant should convert the gap analysis into a sequence of decisions. A practical order is: freeze the intended markets and product definition; confirm applicable regimes; resolve classification ambiguities; decide which evidence can be reused; identify missing design or documentation controls; then commission only the tests, assessments, registrations or filings that close the remaining gaps.

This sequencing also exposes commercial choices. A company may decide to postpone one market, split a product family into different configurations, replace a component that creates a difficult approval path, or launch with fewer variants so that the first evidence package is narrower and more stable. Those are strategy decisions; they should be made before an execution provider starts a large testing or filing programme.

Use market examples as route signals, not universal rules

  • EU: CE marking applies only where relevant EU harmonisation legislation requires it. The manufacturer is responsible for identifying applicable requirements, completing the required conformity assessment, preparing technical documentation and the declaration of conformity, and involving a notified body where the legislation requires one. Harmonised standards are generally voluntary but can provide a presumption of conformity where applicable.
  • Great Britain: product-specific regulations determine whether UKCA or recognised CE routes are available and whether self-declaration or third-party assessment is required. The government guidance expressly warns that multiple regulations can apply to one product.
  • United States: there is no single horizontal “US product certificate.” A regulated consumer product within CPSC rules may require a certificate based on applicable rules, while an RF device may fall under FCC certification or Supplier's Declaration of Conformity depending on the equipment and rule part.

The safe conclusion from a market example is therefore a question to verify, not a shortcut to a certificate.

Know where consulting ends and execution begins

This page owns classification, route selection, gap analysis, evidence reuse and sequencing. Once the route is fixed, execution belongs to the relevant workstream. Laboratory scope, samples and retest management are covered under product testing services. End-to-end implementation is covered under product compliance services. Formal certification execution belongs under product certification services. Multi-country rollout is covered under global market access services, while authority or portal submissions belong under product registration services.

A consultant should not imply that advice itself is an approval, laboratory accreditation, notified-body decision or regulator acceptance.

What to send a product compliance consultant

A useful first review normally starts with a compact evidence pack rather than a large unsorted document dump:

  • product name, model family and intended use;
  • target countries and launch priority;
  • photos, draft manual, label and packaging artwork;
  • technical specification, BOM and critical component list;
  • radio, battery, power-supply, software and material information where relevant;
  • existing test reports, certificates, declarations and registrations;
  • manufacturer/importer/distributor/private-label role map;
  • known variants, planned changes and launch date assumptions.

The next safe action should then be explicit: confirm a classification assumption, request one missing document, obtain a targeted technical opinion, or release a defined test/filing package. If a conclusion depends on facts not yet available, the consultant should identify the dependency rather than present a false yes/no answer.

Treat compliance as a change-controlled decision

A route decision is only as reliable as the product and regulatory assumptions behind it. Recheck the strategy when there is a material design change, new radio or battery configuration, new intended use, new target country, a change of manufacturer or responsible economic operator, a revised standard or legal requirement, or a change that may invalidate earlier test evidence. The purpose of change control is to decide whether existing evidence still supports the current product—not to retest everything automatically.

Official reference points

Frequently asked questions

Can a consultant tell me which certificates I need from only a product name?

Usually not reliably. The answer can depend on intended use, technical features, user group, target country, economic-operator role and the exact product configuration. A product name is a starting point, not a complete classification file.

Should I send a product to a laboratory before the compliance route is confirmed?

Only when the test purpose and applicable standard or regulatory requirement are already clear. Otherwise you risk buying a report that does not answer the legal question, uses the wrong configuration, or cannot be reused in the intended market.

Can existing CE, CB, FCC or supplier documents be reused for another market?

Sometimes, but reuse must be mapped requirement by requirement. A report can reduce duplicate work without automatically replacing local declarations, registrations, national deviations, responsible-party duties or additional tests.

What if two consultants propose different routes?

Ask each to state the product classification, applicable legal instrument or official rule, conformity route, evidence assumptions and unresolved facts. The disagreement can then be tested against primary sources instead of being treated as competing opinions.

When should the compliance strategy be reviewed again?

Review it when the product or intended use changes, a new market is added, a critical component or software function changes, a responsible party changes, or the applicable regulatory/standards baseline changes. The review should decide what remains valid and what must be updated.

Responsible for publication: Khachatrian Razmik

Last updated: 2026-10-16

Related guidance