EAC Certification Scope for Product Families: Model Grouping and Evidence Coverage in the EAEU

The EAC certification scope on a Eurasian Conformity document can read broadly and still fail to cover the goods that arrive at the importer's warehouse. This happens when the commercial product family, the test evidence and the certificate scope are built from three different model lists. For manufacturers supplying machinery, low-voltage equipment and industrial electronics to the Eurasian Economic Union, the task is not to push more model numbers into an application — it is to demonstrate what those models represent, which differences matter for conformity assessment, and which products the final document can legitimately cover.

EAC model coverage fails because the family definition used by sales is not the family definition used by conformity assessment. A manufacturer may sell an industrial controller series under one catalogue name: one version has a larger power supply, another adds an output board, a third changes the enclosure, a fourth is produced under a new part number for a particular customer. To a sales team, they are all one family. For conformity assessment purposes, they may or may not be sufficiently similar to share the same evidence.

The answer depends on the applicable technical regulations, the conformity-assessment route, the differences between versions and the technical basis for grouping them. Under the EAEU framework, product identification and the applicable regulation come first. TR CU 004/2011 concerns the safety of specified low-voltage equipment; TR CU 020/2011 addresses electromagnetic compatibility of technical devices; TR CU 010/2011 covers the safety of machinery and equipment. These regulations do not automatically apply to every industrial product, and they do not make all variants interchangeable for assessment purposes.

The practical lesson is blunt: a common brand, product name or enclosure is not proof of common compliance coverage. An EAC certificate that does not cover all product variants is a customs and market-surveillance problem, not a paperwork preference.

The scale of the framework matters here. The EAEU system comprises a series of technical regulations covering product groups from railway vehicles and low-voltage equipment to machinery, explosive atmospheres, clothing and footwear, pressure equipment, chemicals and fire protection products. Products appearing in the unified list of products subject to mandatory conformity assessment may not be imported, sold or used in commercial service premises without the required certificate or declaration and the corresponding mark.

Scope control begins with a model matrix, not a certificate draft. Before requesting a certificate or declaration, the reviewer should see a matrix that places commercial identifiers alongside the technical differences that could affect requirements or testing.

At minimum, the working file should connect each model to its product function, ratings, supply configuration, critical components, interfaces, construction and relevant test evidence. For electrical and electronic products, the reviewer should identify potential differences in electrical safety and EMC performance. For machinery, the relevant hazards and the applicable technical-regulation scope can be different.

A clear matrix does two useful things. It exposes variants that were invisible in the initial sales list, and it gives the certification partner a defensible explanation of why certain models may be assessed together. The matrix is an engineering and document-control tool. By itself, it does not authorise grouping — the assessment decision under the applicable scheme does.

Because a laboratory report describes the sample that was tested, not every configuration that shares its name. Consider four versions of the same industrial control unit. Model A has the basic I/O configuration. Model B adds a switching output. Model C has a different power module. Model D includes an optional communications board.

A laboratory report for Model A may provide useful evidence for the family. It should not be treated as automatically covering Models B, C and D. A change in power electronics could alter heating, insulation or EMC behaviour. An added communications board could change emissions or immunity considerations. Some changes may be minor; others may require additional evidence or testing.

What matters is the documented technical justification and the assessment decision under the applicable scheme. The evidence must describe the product that will actually be manufactured and supplied, not a convenient representative from an earlier project.

The scope decision is driven by the technical regulation that applies to the product, and by the conformity-assessment scheme chosen under it. For electrical and electronic equipment placed on the EAEU market, the regulations most frequently engaged together are TR CU 004/2011 (safety of low-voltage equipment) and TR CU 020/2011 (electromagnetic compatibility of technical devices). Machinery falls under TR CU 010/2011. TR EAEU 037/2016 addresses the restriction of hazardous substances in electrical and radio-electronic products, and TR EAEU 048/2019 addresses energy efficiency requirements.

The EAEU technical regulations also determine who may act as applicant. Under the Belarusian national standardisation authority's guidance on mandatory certification, the specific range of applicants entitled to apply for certification within the framework of conformity assessment against the technical requirements of EAEU technical regulations is established by the EAEU technical regulations themselves. In other words, the applicant question is answered by the regulation, not by commercial convenience.

EAC certificates and EAC declarations issued in one EAEU member state have the same legal effect across all member states, and issued documents are registered in a unified EAEU register. That single register is why scope wording is unforgiving: what is registered is what customs and market surveillance will read.

For a product subject to both TR CU 004/2011 compliance and TR CU 020/2011 EMC requirements, the model list has to survive two different technical questions at once. A variant that is indistinguishable for electrical safety — same power module, same insulation system, same enclosure — may still differ for EMC because of an added interface or communications board. Grouping that is defensible under one regulation is not automatically defensible under the other.

This is the most common failure mode in a model matrix for EAC conformity assessment: the matrix is built from a safety perspective, the EMC differences are never tabulated, and the certificate scope inherits a grouping rationale that only half of the evidence supports.

The exposure sits with the importer and the manufacturer simultaneously, and it materialises at the point of shipment. Products listed in the unified list of products subject to mandatory conformity assessment cannot be imported, sold or used in commercial service premises without a valid certificate or declaration and the applied mark. A consignment containing a model designation that does not appear in the registered scope is, for practical purposes, a consignment without a document.

The product groups most affected by family-scope problems are those with high configuration variance: machinery and equipment, electrical engineering, industrial electronics, pressure equipment, and vehicles and components. These are precisely the categories where customer-specific part numbers, optional boards and alternative power modules proliferate between the time the application is filed and the time the goods ship.

Market surveillance applies to EAC-marked products, and certificates are subject to inspection control during their validity period. Certificate validity can run up to five years for series production, which means a scope defined once can govern four more years of shipments — including shipments of configurations that did not exist when the certificate was issued.

Series production and batch assessment are different scope decisions, not interchangeable paperwork options. Two shipments can contain identical-looking products while needing different documentary treatment because the supply arrangement is different.

For series production, the assessment is directed at an identifiable product range produced under the relevant scheme and manufacturing arrangements. A batch assessment is tied to a defined supply of products. The exact choices and evidence depend on the applicable EAEU technical regulation and scheme.

The EAEU scheme families reflect this split. Certificate of conformity schemes 1c, 2c, 5c, 7c and 8c apply to serial (mass) production, while schemes 3c, 4c and 9c apply to batch production; schemes 10c and 11c cover vehicle component certification. On the declaration side, schemes 1d, 3d, 5d and 6d apply to serial production and schemes 2d and 4d to batch production. The EAC declaration of conformity scope is therefore subject to the same series-versus-batch logic as the certificate.

The model list must be read together with the production or batch scope, the declared manufacturer and production sites, and the supporting documentation. A certificate issued for one defined batch should not be represented to a buyer as open-ended authorisation for every future shipment.

EAC certification is carried out on the analytical basis of technical documents and records, internal company test protocols, test protocols from accredited testing laboratories, and, where required, an EAC production audit. The process runs through application, document review, product classification, sample selection, testing and analysis, production audit, certificate issuance, product supervision and inspection control. Sample testing is required and factory inspection applies conditionally, depending on the scheme.

Product classification is the step where a sloppy model list does the most damage. If the classification is built from the commercial family rather than the technical one, every downstream step — sample selection, test protocol coverage, certificate wording — inherits the error.

A scope problem surfaces at import clearance or during inspection control, not at issuance. That is the uncomfortable timing: the document is already registered in the unified EAEU register, the importer has already placed orders, and the discrepancy is discovered when a model designation on the commercial invoice does not match the registered scope.

Agree in advance how later design changes will be screened. Adding a new model after issue is not automatically an administrative edit — the applicable rules and the effect on existing evidence must be reviewed. Treating a post-issue model addition as a clerical amendment is the assumption that most often produces an unusable certificate.

I am not aware of published EAEU-wide enforcement statistics on scope-related rejections, and I will not estimate them. What is documented is that market surveillance applies and that inspection control forms part of the certification lifecycle.

Yes — EAC certificates of conformity issued by the individual EAEU member states have the same legal effect in all member states of the Eurasian Economic Union, and once conformity with the technical regulation requirements has been confirmed, the products can be sold throughout the customs territory of all member states. Issued EAC certificates and declarations are registered in a unified online EAEU register.

The variation sits at the applicant and certification-body level rather than in the recognition of the document. National authorities, such as the Belarusian State Committee for Standardisation, administer the accredited certification bodies conducting mandatory certification within the framework of conformity assessment against EAEU technical regulation requirements, and the range of eligible applicants is set by the applicable EAEU technical regulation. Products outside the scope of an EAEU technical regulation remain subject to the national standards of the respective member state.

A final scope review works only when the reviewer opens several files side by side rather than reading the certificate in isolation. Run these five checks before signing off.

First, compare the model designations in the application, the draft conformity document, the product labels and the commercial invoice. Watch for missing suffixes and customer-specific part numbers — these are the designations that never reach the certification file because nobody in engineering regards them as a different product.

Second, compare the model list against the technical documentation and the actual released configurations. For each model, decide whether it is supported by direct test evidence, by a justified group rationale, or whether additional work is required. Record which of the three applies; an undocumented assumption is the same as no coverage.

Third, reconcile the manufacturer and production-site information. This is a separate issue from model-family coverage, and a correct model matrix cannot cure an incorrect factory record.

Fourth, confirm that the chosen certificate or declaration route fits the applicable regulation, the product category and the supply scheme — specifically, whether the scheme selected is a serial-production scheme or a batch scheme, and whether the intended shipments match that choice.

Fifth, agree the change-screening process now. Define which component or configuration changes trigger a review of existing evidence before a purchase order creates an unplanned compliance problem.

A small discrepancy found at this stage is cheaper to resolve than an argument over model coverage while goods are sitting at the border.

The useful output is not the longest model list. It is a consistent chain connecting the product actually sold, the models identified in the conformity document, the technical basis for grouping and the approved supply arrangement.

That chain lets commercial, quality and logistics teams make the same decision from the same document. It also lets engineering flag a relevant component change before it becomes a scope defect.

The next thing to put in the calendar is not a regulatory deadline — it is your own certificate expiry and the review point before it. Certificate validity runs up to five years; schedule the model-matrix reconciliation at least one quarter before any planned product-line extension, and re-run the five cross-checks whenever a new power module, interface board or customer-specific part number enters the released configuration list.

Note on sourcing: the scheme numbering (1c–11c, 1d–6d), the five-year maximum certificate validity and the certification process sequence described above are drawn from conformity-assessment body documentation describing EAEU practice rather than from the primary EAEU legal texts. Verify the applicable scheme against the specific technical regulation annex for your product before relying on it.