OEM Temperature Controller Compliance Planning: Build the Evidence Matrix

OEM temperature controller compliance requirements cannot be reduced to “CE needed” or “send a certificate.” Before hardware, firmware, enclosure, branding, or connectivity changes begin, the buyer and supplier need to agree what product will be sold, where it will be placed on the market, who takes each regulatory role, which requirements may apply, and what evidence must match the released configuration.

This guide shows how to build that compliance-planning package. It is a procurement and engineering framework, not a legal opinion or a certification decision. The applicable route must be confirmed for the actual product, intended use, target market, supply chain, and current rules.

Start with the product boundary, not a mark

A temperature controller may be sold as a finished stand-alone device, incorporated as a component in refrigeration equipment, supplied inside a control panel, or placed on the market as part of a complete machine. The same electronics can therefore sit inside different legal and technical product boundaries.

Write a one-sentence product definition before listing standards:

A panel-mounted electronic temperature controller, supplied as [a finished device / a component], powered by [defined supply], controlling [defined loads] through [defined interfaces], intended for [defined equipment and environment], sold in [markets] under [named brand].

Attach the block diagram, electrical diagram, I/O list, enclosure arrangement, intended-use statement, installation method, user group, and sales configuration. If the controller is embedded in another machine, identify which protective functions belong to the controller and which remain with the host equipment.

The current IEC 60730-2-9:2026 scope illustrates why classification matters. It covers defined categories of temperature-sensing controls, including controls associated with certain equipment and building automation, while also stating an exclusion for controls intended exclusively for industrial-process applications unless another relevant part or equipment standard brings them into scope. A familiar product name does not decide applicability; the actual intended use and product boundary do.

Name the economic operators and compliance owner

Do not leave responsibility hidden behind “OEM.” Record the legal manufacturer, brand owner, importer, distributor, authorised representative where relevant, applicant or certificate holder where the chosen route uses one, and the person who releases each market configuration.

For the EEA, the European Commission states that the manufacturer is responsible for identifying applicable requirements, performing the appropriate conformity assessment, preparing technical documentation, issuing the EU declaration of conformity, and applying CE marking. Its guidance also says that an importer or distributor marketing a product under its own name takes over manufacturer responsibilities (manufacturer guidance; importer and distributor guidance).

That does not mean every private-label arrangement is identical in every jurisdiction. It means the contract and project plan should explicitly answer:

• Whose name and address appear on the product and declaration?
• Who owns the technical file and can provide it to the relevant authority?
• Who approves the risk assessment, labels, instructions, and declaration?
• Who controls production changes and decides whether evidence remains valid?
• Who manages complaints, corrective action, withdrawal, or recall if required?

Build a market-and-requirements matrix

Create one row for every destination and sellable configuration. “Global version” is not a useful row.

The matrix is a controlled project record, not a one-time sales checklist. Date the legal and standards review, retain the source links, and name the qualified person or body that confirmed the route.

Treat each market as a scope decision

Different rules classify products by different criteria. For example, the official EAEU texts for TR CU 004/2011 on low-voltage equipment and TR CU 020/2011 on electromagnetic compatibility define different scopes, exclusions, roles, evidence, and conformity procedures. Whether either regulation applies—and which route applies—depends on the actual equipment and how it is placed on the market.

Use the same discipline for every destination:

1. Classify the sellable product and intended use.
2. Identify all potentially applicable rules, not only the best-known mark.
3. Check scope, exclusions, definitions, operator roles, and current amendments.
4. Determine whether the controller, host equipment, or both require assessment.
5. Record the assessment route and responsible party.
6. Convert every requirement into a design input, document, or verification task.

Do not copy a competitor’s marks, declaration, or standard list. A different supply voltage, enclosure, radio interface, installation category, end use, or economic operator can change the analysis.

Separate existing evidence from project evidence

A supplier’s previous report may be useful, but its title page is not enough. Build an applicability review around:

• exact model and hardware revision;
• PCB, power supply, relays, sensors, critical components, and approved alternatives;
• enclosure, terminals, cables, accessories, and installation configuration;
• firmware version, safety-related behavior, defaults, and communication options;
• test method, standard edition, deviations, sample identity, and operating modes;
• laboratory identity and the exact scope of its accreditation where accreditation is required;
• report holder, market route, validity conditions, and permitted use of marks; and
• differences between the tested sample and the product to be released.

ISO describes ISO/IEC 17025:2017 as the standard for laboratory competence, impartiality, and consistent operation. Even when a project requires an accredited test, verify that the laboratory’s accreditation scope covers the relevant method; a general claim of accreditation is not the same as scope for the needed test.

Classify evidence as directly applicable, supporting but requiring gap review, or not applicable. Record the reason and reviewer. Never turn a component report, an earlier model’s certificate, or a preliminary pre-compliance result into a finished-product claim without the assessment route allowing it.

Freeze the configuration before formal testing

Testing an unidentified “latest sample” creates expensive ambiguity. Before formal evaluation, issue a configuration record covering:

• hardware and PCB revision;
• firmware build and checksum or controlled identifier;
• bill of materials and critical-component list;
• enclosure, terminals, sensor, cable, and accessories;
• default parameters and enabled functions;
• radio or communication modules and antennas, if any;
• labels, rating information, instructions, and packaging content; and
• drawings, risk assessment, and standards list used for the review.

The EU Blue Guide 2022 explains that modifications affecting applicable requirements can require technical documentation updates and reassessment; substantial physical or software changes may make the modified product a new product for conformity purposes. The practical lesson is broader than one market: every released change needs a documented compliance impact review.

Connect this review to the project’s firmware change-control process. A screen edit may be low impact; changes to supply circuits, relay loads, protective behavior, sensor interpretation, communication, intended use, enclosure, or critical suppliers may require wider analysis or retesting.

Plan evidence by design stage

Keep development evidence separate from market-release evidence:

1. Requirements review: confirm product definition, markets, roles, rules, standards, and acceptance criteria.
2. Design review: check schematics, layout, critical components, enclosure, risk controls, firmware architecture, labels, and instructions.
3. Pre-compliance: find likely failures on a controlled engineering build; do not present the result as final certification.
4. Formal evaluation: test the frozen representative configuration through the confirmed route.
5. Production release: align drawings, BOM, programming files, labels, manuals, inspection, and end-of-line tests with the evaluated configuration.
6. Surveillance and change review: maintain records, monitor standard or component changes, and reassess deviations before shipment.

Link test samples and results to the prototype validation plan. Functional acceptance proves that agreed behavior works; conformity evidence addresses the requirements of the selected market route. A project may need both, and one does not automatically replace the other.

What to send in a compliance-ready OEM enquiry

Send the following with the OEM controller RFQ:

• target countries, launch channels, brand, and responsible legal entities;
• finished-product or component status and host-equipment description;
• intended use, users, environment, installation, and foreseeable service conditions;
• power, load, electrical diagram, I/O, sensors, communications, panel, and enclosure;
• certification or declaration objectives already confirmed by a qualified adviser;
• existing reports and certificates with full model, revision, standard edition, and owner;
• required documents, languages, labels, traceability, and retention expectations;
• prototype, formal-test, pilot, and production configurations;
• estimated quantities for planning, without treating them as proof of feasibility; and
• change-notification, approval, retest, and renewal responsibilities.

Ask the supplier to mark every requested item as standard, published option confirmed for the selected model, or project-evaluated customization. Then request a gap list rather than a simple “compliant” answer.

Standard, optional, or project-evaluated at Beamform

Beamform’s product pages describe published standard controller families and model-specific functions. Only the documented functions of the selected model should be treated as standard. A published option still requires written confirmation for the exact model and project.

Changes to PCB, relay arrangement, sensor interface, power supply, firmware, HMI, communication, enclosure, labels, documentation, or packaging are project-evaluated customization. Existing evidence cannot be assumed to cover a change until its scope and configuration have been reviewed.

Final feasibility, applicable requirements, assessment route, sample plan, laboratory work, documentation, cost, MOQ, tooling, and schedule can be determined only after the product definition and compliance matrix are confirmed. Contact Beamform with the target markets, legal entities, application, electrical diagram, I/O list, panel dimensions, environment, expected quantities, proposed standards, evidence already available, and required launch configuration.

Frequently asked questions

Does a CE mark from the base controller automatically cover my private-label product?

Do not assume so. Confirm the product identity, brand and economic-operator roles, applicable legislation, declaration owner, technical documentation, and whether branding or design changes affect the assessed configuration.

Can a component test report certify the finished machine?

Not by itself. It may support the finished-product assessment if its scope, sample, standard, conditions, and route allow it. The responsible party must document the gap between the component and the complete equipment.

Should we choose standards before the controller architecture?

Start early, but classify the product and intended use first. Standards become design inputs only after their relevance, edition, adoption, and relationship to applicable requirements have been checked.

Does a firmware-only change need compliance review?

Yes. The review may conclude that no retest is needed, but that conclusion should be recorded. Changes to protective logic, operating sequence, limits, diagnostics, communications, updates, or intended functions can affect the assessment.

What is the most useful first deliverable from the supplier?

A model-specific gap report: what is standard, what existing evidence covers, what differences remain, which decisions belong to the buyer or finished-equipment manufacturer, and what must be designed, tested, documented, or confirmed before release.

Sources

• European Commission — CE marking responsibilities for manufacturers
• European Commission — responsibilities of importers and distributors
• EUR-Lex — The Blue Guide on the implementation of EU product rules 2022
• IEC — IEC 60730-2-9:2026, particular requirements for temperature-sensing controls
• Eurasian Economic Commission — TR CU 004/2011 on low-voltage equipment
• Eurasian Economic Commission — TR CU 020/2011 on electromagnetic compatibility
• ISO — ISO/IEC 17025:2017 for testing and calibration laboratories