Product compliance: mapping which rule sets attach to what you make

Obligations arrive along several axes at once

Rules reach a product from different directions. Sector rules follow what the thing is: a machine, a toy, a pressure vessel, a diagnostic device. Horizontal rules follow what sits inside it or around it, covering substances, packaging, energy use, electromagnetic behaviour and end-of-life handling. Market-entry rules follow where it is sold, and customer contracts stack requirements on top that are not law but bite in much the same way. Several of these can land on one article simultaneously, and satisfying one says nothing whatever about the others. The useful scoping question is not which regulation covers us, singular, but which combination applies to this configuration in each territory on the sales plan.

Duties attach to a role, and roles change without anyone noticing

Most product regimes place their duties on whoever puts goods on a market rather than on whoever physically made them. A business importing finished stock generally inherits a heavier set of responsibilities than one reselling goods already circulating in that market, and putting your own brand on somebody else's product tends to move you into the maker's position entirely. Manufacturers meet this in private-label work, in kit assembly, and when a distributor asks for direct shipment into a new country. Before signing, establish on paper which party is treated as the responsible economic operator for each destination, because the commercial contract does not decide that question; the applicable law does.

The evidence is requested afterwards, which is why it has to exist beforehand

Nobody inspects a file before the goods ship. The demand arrives later, through a customer's onboarding questionnaire, a retailer's assurance team, a border check, or an officer following up a complaint. At that point the manufacturer is expected to produce the reasoning, the test results, the risk assessment and the supplier evidence behind the position taken. Reconstructing all that after a challenge is expensive and rarely convincing, because the documents will carry dates later than the question. Treating the evidence pack as a deliverable of the design project, owned by a named person and updated at each change, separates businesses that answer such requests in an afternoon from ones that lose weeks to it.

A design change can quietly reopen a settled position

Positions are taken against a specific bill of materials, a specific supplier and a specific set of instructions. Change the motor, move to a second-source connector, switch the plastic grade, alter a packaging claim or add a wireless module, and part of the earlier reasoning may no longer hold. Engineering change control is therefore the real control point, and it fails when substitutions are approved on cost and lead-time grounds by people who never see the regulatory file. One standing question in the change review, asking whether this touches anything the declaration relies on, catches most of it. Swapping a component because the original went obsolete is the most common route by which a compliant product stops being one.

Read the rule where it lives, not where it has been summarised

What applies differs between countries, between product families, and sometimes according to how the same article is presented to buyers, and the rules are revised more often than secondary summaries are refreshed. Guidance published by the responsible ministry, agency or commission is the authoritative statement. A consultancy article, a supplier's assurance, or a page such as this one offers orientation rather than legal, safety or engineering advice, and none of them can tell you what governs your particular product. Scope out which authorities are relevant, read what they themselves publish, and take advice from someone qualified in that jurisdiction before committing to a position you will later have to defend.

Frequently asked questions

Does a certificate from our component supplier make our product compliant?

It contributes evidence, but it rarely closes the question. A supplier certificate covers a component under the conditions that supplier tested, which may not match how the part behaves inside your assembly or how the finished article is used. Whoever places the finished product on a market normally has to reason about the whole thing rather than the sum of its parts. Treat supplier paperwork as an input, check the scope and issue date, and confirm it names the exact part you actually buy.

We only assemble components other firms make. Does that reduce our exposure?

Usually not, and sometimes it works the other way. Putting parts together generally creates a new product, and obligations follow the finished article rather than the pieces. The assembler decided how the components interact, wrote the instructions and chose the enclosure, so assessment of the whole lands there. Component suppliers can help with data and declarations for their own parts, but none of them is positioned to evaluate a combination they have never seen assembled.

How early can we work out which rules will apply?

Earlier than most teams attempt it. A rough scope can be drawn from intended function, energy source, user group, substances involved and target markets, all of which are normally settled at concept stage. Doing the work then changes design decisions cheaply; doing it after tooling means either an expensive change or defending a weak position. Where the scoping is genuinely ambiguous, that ambiguity is itself a finding, and it identifies exactly where specialist advice is worth paying for.