The product certification process, from scoping to a market-ready mark

Step one: scope the schemes and standards

Everything starts with knowing precisely what the product is and where it will be sold. You classify the product by its function and features, every radio, every electrical characteristic, its intended use and users, then determine which mandatory schemes apply in each target market and which technical standards those schemes call up. This is the single most important step, because a missed requirement discovered late can force re-testing or block a launch. Getting the scope right means listing, for each country, the safety, electromagnetic-compatibility, radio, and any category-specific requirements your product triggers.

Scoping is also where you find efficiencies. Many schemes reference the same international standards, so a thoughtfully planned test campaign can produce evidence usable across several markets. Scoping decides what to test, against which standard versions, and in what order, and it flags any market that needs in-country testing, a local representative, or a license holder. A clear scope is the foundation the rest of the process is built on.

Step two: test at an accredited laboratory

Testing is the evidence-gathering core of certification. Representative samples of the product go to an accredited test laboratory, which runs the product against the applicable standards: electromagnetic-compatibility tests to confirm it does not emit harmful interference and tolerates normal interference, electrical and product-safety tests to confirm it will not shock or overheat, and radio tests for any wireless function to confirm it uses the spectrum lawfully. Other categories may add specific tests, for example for batteries or energy efficiency.

Two practical points matter here. First, accreditation matters: schemes generally require testing by a laboratory accredited and, for some schemes, specifically recognized for that scheme, or the results will not be accepted. Second, design fixes are common: products frequently fail an early test, and the fastest path is pre-compliance checking before formal testing so issues are found and fixed cheaply rather than after a failed official run. Good preparation here protects both the timeline and the budget.

Step three: compile the technical documentation

Certification is as much about documentation as it is about testing. Most schemes require a technical file, sometimes called a technical construction file or technical documentation, that demonstrates the product meets the requirements. It typically gathers the test reports, a description of the product and its design, schematics and key component information, risk assessments, the list of standards applied, user instructions and labeling, and the conformity declaration or certificate. This file is the evidence a regulator or certification body relies on, and in many markets the manufacturer must keep it available for years after the product is on sale.

The quality of this documentation directly affects how smoothly approval goes and how well you withstand later scrutiny. A complete, well-organized technical file speeds review, supports declarations of conformity, and protects you if a market authority asks questions after launch. A thin or disorganized file is a frequent cause of delay and of trouble during market surveillance, so it deserves real attention rather than being treated as a formality.

Step four: certify, mark, and label

How approval is finalized depends on the scheme. Some markets operate on supplier self-declaration: once testing and the technical file support it, the manufacturer signs a declaration of conformity and applies the mark, taking legal responsibility. Others require a third-party certificate issued by a recognized certification body before the product can be sold, and some require registration with, or a license from, a government authority. Knowing which model each market uses is part of scoping, and it changes who must hold the approval and what evidence is filed.

Then comes marking and labeling, which is more consequential than it looks. Each scheme specifies its mark, where and how it must appear, and what information must accompany it, the manufacturer or importer details, model identifiers, certificate or registration numbers, and required warnings. Incorrect or missing marking is a common reason products are stopped at customs or flagged in market surveillance, even when the underlying testing was fine. Getting the labels right for every market is the final, easily-overlooked gate before shipping.

Step five: maintain the approval over time

Certification is not a one-time event. Approvals must be maintained as the product, the standards, and the rules evolve. A design change, a new radio module, a different power supply, or a component swap can invalidate an existing approval and require re-testing or an updated certificate. Standards are revised on their own schedules, and a market can tighten requirements or change a scheme, so a product compliant at launch can drift out of compliance if nobody is watching. Some schemes also require periodic factory audits or surveillance to keep a certificate live.

Practically, this means tracking which approvals you hold, their validity and renewal dates, the standard versions they rest on, and any change-control process so engineering changes trigger a compliance review. For manufacturers selling across many markets, this ongoing maintenance is a real operational task, and it is exactly the kind of thing a market-access partner monitors so an approval does not lapse quietly and put sales at risk. Build maintenance into the plan from the start rather than rediscovering it after a lapse.