A company often thinks it knows in one sentence what it sells. For legislation, a more precise question counts: does the product or service fall under a category to which separate obligations are attached. Textiles, batteries, packaging, financial products and certain raw materials each have their own regulations, alongside broader sustainability reporting. Which category applies depends on the composition, the application and sometimes the market in which the product is placed. The same machine can count as an end product or as a component, and that distinction changes which rules apply to it.
The classification of a product determines not only whether a rule applies, but also who in the chain is responsible for the proof. A producer has different obligations than an importer, and an importer again different ones than a distributor who resells the product unchanged. If a company processes, combines or repackages a product, it may end up in a different role as a result, with a different documentation obligation. This kind of shift often only becomes visible during an audit or when a customer asks a question, not at the moment the product itself changes.
Product documentation does not stand on its own. It works together with the question of how your sector partly determines which ESG rules apply, because the same product can fall under a stricter regime in one sector than in another. It is also connected to the question of how your size partly determines which ESG rules apply, because thresholds for reporting obligations are often applied at company level, not at product level. And as soon as a product crosses a border, the question returns of how you document the countries in which you are active so that it holds up afterwards, because national add-ons to European rules can impose slightly different requirements on product documentation.
Documenting is not the same as writing an internal memo. It concerns a structure in which, per product, it is clear: under which category it falls, on the basis of which characteristics that classification was made, who within the organization carried out that assessment, and which document or file substantiates that choice. Without that structure, a classification exists only in someone's head, and that does not hold up during an inspection or when a regulator asks a question. The documentation must also remain up to date: a product change, a new application or a new sales market can tip the classification, and that requires a moment at which that documentation is reviewed again.
This page does not describe which thresholds, article numbers or deadlines apply to a specific product. Those are laid down in the applicable regulations and directives, and the current text of these can be found at the source itself. What counts here is the demonstrability layer: can the organization show how the classification came about, and who was responsible for it. That connects to the broader question of what counts as proof for an obligation, which describes what a file must satisfy in order to count as substantiation. In larger organizations, moreover, that information is rarely found in one place: the technical specification sits with R&D, the trade documentation with procurement, the sustainability claim with marketing. How that falls apart and why that forms a risk is described on the page about where proof becomes scattered within an organization.
A board that wants to demonstrate it is in control needs not only a correct product classification, but also the trail along which that classification was established. That trail consists of an owner per product category, the proof that substantiates the classification, and a control that records at which moment that classification is tested again. Without that trail, a correct classification is a matter of chance; with that trail, it is demonstrable, even when the question comes from outside.
Mapping and keeping these product classifications up to date is exactly the kind of repeatable, rule-based work in which people spend time looking up, comparing and documenting categories, while the assessment itself often relies on patterns. The work scan of FTE TO AI calculates per task which part of that work, from working out a classification to maintaining the evidence file, can be taken over by AI, so that it becomes clear where people remain necessary for judgment and where the legwork can be automated.
Vraag maar welke verplichting op u van toepassing is, en waaraan u dat kunt aantonen.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.