Short answer
BOM-based compliance connects requirements and evidence from materials and components to the configuration actually sold. Correct roll-up needs identity, version control, the right calculation level, and visible data gaps; a green component status cannot be inherited uncritically by the finished product.
Key takeaways
- Distinguish material, homogeneous material, article, component, and complex product.
- Preserve supplier and revision lineage through the structure.
- Legal frameworks use different calculation levels and thresholds.
- Changed quantity, variant, or supplier must affect assessment.
This content is a practical overview, not legal advice. Always verify the current legislation and the requirements that apply to your product. Research uses official primary sources; competitor content is used only to identify questions and content gaps.
Build a compliance-ready BOM model
Each node needs stable identity, revision, quantity, unit, supplier, and validity. Materials and surface treatments should link to the article where they occur. Product variants need their own BOM or explicit configuration rules.
The right level for each rule
RoHS is assessed at homogeneous-material level. REACH Article 33 and SCIP use the article perspective in complex objects. Other rules apply to the whole product or packaging. The model must know both structure and legal calculation level; one product percentage is insufficient.
Connect evidence to node and revision
Declarations, reports, and certificates must link to the item or material revision they cover. Record scope, date, issuer, and review status. Where evidence covers a family, make the coverage rule explicit and verifiable.
Roll up conservatively with visible gaps
Differentiate approved data, explicit absence, below-threshold results, exemptions, and unknowns. Unknown child nodes must not disappear during aggregation. Show the node driving the result and any assumptions.
Change impact
A new supplier, material revision, substitute component, changed quantity, or variant can invalidate an earlier conclusion. Identify dependent products and reopen only assessments whose source changed. Retain history for the previous market version.
Release gates and data quality
Define minimum coverage and which unknown high-risk items block release. Separate technical data quality from the legal conclusion. Report coverage by BOM level and weighted risk so a high aggregate percentage cannot conceal one critical unknown component.
How Verca can support the process
Verca can connect BOMs, materials, substance profiles, supplier evidence, and product versions and expose gaps. It provides decision support; the customer owns data and final assessment.
Frequently asked questions
Can a component CE mark be inherited by the product?
No. The finished-product manufacturer must assess the complete product and all applicable rules.
Which BOM level applies to REACH?
Article 33 applies to each article retaining its identity in a complex object.
How should unknown nodes be treated?
As visible gaps with risk, owner, and action, never automatically compliant.
Does every variant need an assessment?
Every sold configuration must be covered, either separately or through documented family and worst-case rules.
Official sources
Primary sources used for this guide.