Answers for connected product and trade work.

CommonShare is a connected evidence platform for mapping supply chain records, collaborating with partners, governing evidence, screening risk, managing cases and approvals, publishing Digital Product Passports, and preparing supported calculations and regulatory outputs.

Compliance, legal, sustainability, procurement, product, quality, trade, data, and partner teams can work from the same governed records while using views and workflows suited to their responsibilities.

Teams can send structured data and document requests through collaborative supplier portals, assign responsibilities, track responses, and route gaps into review or corrective-action workflows.

Yes. Governed records can be connected to more than one product, claim, program, or regulatory workflow when their scope, permissions, validity, and review status support that use.

Version history preserves the prior record, while alerts, cases, corrective actions, approvals, and escalation workflows help responsible teams review the change and decide what must be updated.

Role-based views and governed exchange policies help participants access the records and actions appropriate to their role without making every source record public.

No. CommonShare structures data, evidence, and workflows; accountable people and organizations remain responsible for legal interpretation, professional review, approvals, and final decisions.

The conversation starts with the products, partners, evidence, decisions, and outputs behind your priority workflow, then shows how the relevant live CommonShare capabilities can connect them.

Invite the people who own the business decision, source data, supplier relationship, evidence review, and technical environment relevant to the workflow you want to examine.

Yes. Start with the decision or obligation creating the most pressure, and CommonShare can demonstrate the connected records, participants, controls, and outputs relevant to that use case.

No. The workflow can be configured around the product, market, design gates, evidence owners, and applicable product-specific requirements.

Yes. Alternative materials, components, suppliers, and calculation versions can remain connected to the product structure and decision record.

No. Binding product requirements and transition timing come from the applicable delegated act or separate sector legislation.

Yes. Requirements, evidence, test coverage, certificates, and decisions can be connected to the product model, variant, component, facility, or batch they actually cover.

Watchlists, document status, cases, approvals, and escalation workflows can route the affected product record back to review.

No. It keeps the operational record connected while the appropriate experts perform testing, technical assessment, and legal interpretation.

Supplier mapping shows relationships. Transaction traceability connects the specific orders, lots, shipments, quantities, and transformations that moved through those relationships.

Yes. Inputs, outputs, quantities, lots, and facilities can be connected across the events that transform or redistribute materials.

Yes. Participants can contribute through collaborative portals and structured requests while system records can align through interoperability workflows.

Yes. Role-based views can separate public information from records intended for buyers, suppliers, repairers, recyclers, auditors, or authorities.

Yes. Product status, evidence versions, repair or ownership events, and other governed lifecycle information can update the connected record.

No. Product-specific delegated acts or separate sector legislation establish binding scope, fields, access, transition, and dates.

Yes. Collaborative requests and portals can collect structured facility, material, product, transport, and transaction data with supporting evidence.

Yes. Inputs, factors, assumptions, data quality, methodology, and results can remain versioned and connected to the relevant reporting or improvement period.

No. PEF is a multi-impact life-cycle methodology. Carbon is one impact dimension and may use a different goal, boundary, method, or reporting context.

Yes. When the underlying network is mapped, a supplier, facility, material, geography, or transaction signal can be connected to affected products and relationships.

Teams can open a case, request evidence, assign review, document mitigation or corrective action, approve a decision, and monitor follow-up.

No. A match is an investigation signal. Responsible teams validate identity, context, legal scope, and required action.

Organizations, facilities, identifiers, people, roles, ownership percentages, control relationships, documents, dates, transactions, products, watchlist signals, and review decisions.

Yes. Updated evidence, entity records, screening signals, or review dates can be routed into cases and approval workflows.

No. It organizes the identity, relationship, evidence, screening, and decision record used by authorized legal and compliance teams.

Yes. Role-based records can connect lifecycle status, service, repair, ownership, refurbishment, or recovery events to the persistent product identity.

Circular Products is the lifecycle operating workflow. A Digital Product Passport is one controlled way to publish information from that governed record.

Yes. Material choices, recycled content, repair or recovery scenarios, calculation inputs, results, and review evidence can remain linked and versioned.

Organizations, facilities, products, materials, claims, and transactions can receive a CommonID.

A CommonID Registrar can issue CommonIDs. Existing registrars authorize additional registrars under the network’s governance model.

No. CommonID is intended to provide a consistent reference across participating systems while organizations continue using their own operational software.

It is the ability for different software systems to align on common data standards and policies of exchange.

No. Transport is only one part of exchange. Shared meaning, identity, permissions, and participation policy are also required for useful interoperability.

Not by definition. The architecture is designed to coordinate shared meaning and governed exchange while participants retain their operational systems.

It is a defined statement connected to its subject, scope, evidence, review activity, and responsible verification party.

The responsible testing, inspection, or certification organization retains professional oversight of the verification decision.

Yes. It is designed for digital verification services across scopes, standards, regulations, and emerging methodologies, with each implementation defining its specific requirements.

The architecture protects participant control over data ownership, permissions, agent execution, infrastructure, and model choice.

Yes. Deterministic automation improves process efficiency while exceptions, approvals, verification judgments, and consequential decisions remain human-supervised.

The architecture can involve standards organizations, certification bodies, buyers, suppliers, and other authorized stakeholders in the configured process.

No. Textile apparel is a priority in the ESPR working plan, but the delegated act must define the covered products, required data, transition period, and final compliance date.

Yes, the underlying product, material, facility, and document records can be reused. Each regulation and audience still needs its own scope, validation, access, and approval logic.

No. Footwear is under study for possible future ESPR work, but it is not in the adopted first priority set and no footwear-specific DPP act or compliance date has been established.

No. EUDR scope depends on the relevant commodity, the customs code of the product being placed on or exported from the EU market, the operator role, and the transaction. Material presence alone does not establish that every finished product is covered.

No. Beauty products may sit within ESPR’s broad physical-goods scope, but no beauty-specific delegated act, mandatory DPP data set, or compliance date is scheduled in the first working plan.

No. REACH and cosmetics rules interact, but the Cosmetics Regulation has its own product safety, information, notification, and responsible-person framework. Applicability must be assessed for the specific formula, substance, role, and market.

No. The toy passport comes from the separate EU Toy Safety Regulation. The new regime is due to replace the current directive on 1 August 2030; that date should not be presented as an ESPR deadline.

No. CPSIA and related CPSC requirements concern covered products for the US market. Product type, age grading, material, importer or manufacturer role, testing rules, and current CPSC requirements determine the specific obligation.

No. Sporting and leisure goods are not one scheduled ESPR product group. A specific product may fall within broad ESPR scope or later product measures, but no general sporting-goods DPP act or compliance date has been established.

No. GPSR is a general safety framework, while specific products can also be governed by sector legislation such as personal protective equipment rules. Classification, intended use, market, and the applicable sector act must be assessed first.

No. Consumer goods and housewares are not one ESPR product group. Requirements can only be stated once an applicable product-specific measure or separate sector act defines scope, data, transition, and timing.

No. GPSR provides a general safety framework, but sector legislation can establish more specific duties. The product, intended use, materials, market, and economic-operator role determine which rules apply.

No. The Construction Products Regulation establishes the system, while delegated acts and product-family rules define implementation and timing.

It is established under the Construction Products Regulation but must be compatible with and based on the ESPR DPP architecture while accounting for construction-specific requirements and BIM interoperability.

Not automatically. ICT and electronics work is in the current plan, but product-specific and horizontal acts must define scope, data, use of DPP or EPREL, transition, and dates.

CommonShare supports role-based views so approved public information can be separated from records intended for suppliers, customers, repairers, auditors, or authorities.

Food, feed, living plants, living animals, and microorganisms are excluded from ESPR. Packaging, equipment, processed non-food goods, and other sector laws can still create separate obligations.

No. EUDR covers cattle, cocoa, coffee, oil palm, rubber, soy, wood, and the products listed in its current Annex. Product classification and operator role must be checked.

Yes. Directive (EU) 2024/1760 entered into force in July 2024 and was subsequently amended. Member States must transpose the current rules by 26 July 2028; application begins from 26 July 2029.

The amended Directive generally targets EU companies with at least 5,000 employees and €1.5 billion in worldwide net turnover, and non-EU companies with at least €1.5 billion in EU net turnover. Consolidated groups, franchising, licensing, financial undertakings, and national implementation require closer analysis.

No. ESPR is a framework regulation. Concrete requirements arrive through product-specific delegated acts and other implementing measures.

A DPP is a structured set of product information connected to an identifier and made accessible according to rules defined for the product group.

The core commodities are cattle, cocoa, coffee, oil palm, rubber, soy, and wood, together with products listed in the Regulation’s annex.

The current EU timetable starts 30 December 2026 for large and medium operators and certain micro or small operators previously covered by the EUTR, and 30 June 2027 for other micro and small operators.

No. The definitive regime began on 1 January 2026, with authorization, declarations, and certificate obligations now applying under the current rules.

CBAM covers specified goods in cement, iron and steel, aluminium, fertilizers, electricity, and hydrogen. Scope is determined by the legal annexes and customs classification.

The Act generally applies to companies with a head office, principal place of business, administrative headquarters, statutory seat, or branch in Germany and at least 1,000 employees, subject to the Act’s counting rules.

The LkSG remains in force. Germany has announced a transition toward a law implementing the amended CSDDD, but the timing, final text, reporting relief, and enforcement position must be checked against current legislation and BAFA guidance.

No. It can affect manufacturers, importers, downstream users, distributors, and suppliers of articles across many industries.

Inclusion can trigger immediate legal obligations for suppliers, producers, and importers of articles, including communication and potentially notification duties.

Covered goods are presumed prohibited under 19 U.S.C. 1307 unless the importer establishes that the presumption does not apply or satisfies the demanding requirements for an exception.

No. The presumption can apply when any part of a good was mined, produced, or manufactured wholly or in part in Xinjiang or by an Entity List party.

CPSC generally defines it as a consumer product designed or intended primarily for children 12 years of age or younger, using statutory factors and agency guidance.

A Children’s Product Certificate supports covered children’s products and relies on required third-party testing; a General Certificate of Conformity applies to certain non-children’s products subject to CPSC rules.

No. PEF is an EU methodology, not a standalone binding regulation. It can, however, be referenced by policies, schemes, contracts, or market initiatives.

PEF is LCA-based but provides harmonized EU rules intended to improve consistency, comparability, reproducibility, and verifiability.

From 18 February 2027, each light means of transport battery, each electric-vehicle battery, and each industrial battery with a capacity above 2 kWh placed on the market or put into service must have an electronic battery passport.

Regulation (EU) 2025/1561 postponed the application of the Chapter VII battery due-diligence duties to 18 August 2027. Detailed scope, turnover exclusions, raw materials, and operator roles still require legal analysis.

The Regulation entered into force on 13 December 2024. Its principal product-prohibition and investigation provisions apply from 14 December 2027, while specified institutional provisions applied earlier.

No. It covers products placed or made available on the EU market and products exported from the EU, whether manufactured in the EU or elsewhere.

Regulation (EU) 2025/40 entered into force on 11 February 2025 and generally applies from 12 August 2026. Numerous operational requirements have later dates or depend on delegated and implementing acts.

No. It applies broadly to packaging placed on the EU market and packaging waste, including primary, grouped, transport, e-commerce, and other formats subject to the Regulation’s definitions and exclusions.

Regulation (EU) 2023/988 has applied since 13 December 2024. Products placed on the market before that date receive the Regulation’s stated transitional treatment if they complied with the previous General Product Safety Directive.

It acts as a general safety framework. Its requirements apply to non-food consumer products except where sector-specific EU law contains provisions with the same safety objective; exact overlap requires product-specific analysis.

It covers specified forms of tin, tantalum, tungsten, and gold—often called 3TG—listed in Annex I, including ores, concentrates, and certain processed metals.

No. The mandatory due-diligence duties directly target EU importers of Annex I minerals and metals whose annual import volumes exceed the stated thresholds. Downstream customers may still receive data requests or have duties under other laws.

The duty generally concerns articles placed on the EU market that contain a REACH Candidate List substance above 0.1% weight by weight, when supplied by an actor within the Waste Framework Directive’s scope.

SCIP is established under the Waste Framework Directive, but its trigger depends on substances on the REACH Candidate List. The product and substance evidence therefore overlaps heavily with REACH Article 33 work.

No. Its chain-of-activities concept can extend beyond tier-one relationships, although the exact duties depend on the activity, relationship, risk, and legal text.

Operators need the geolocation of all plots where relevant commodities were produced. The required form depends in part on plot size and commodity context.

Start with product identifiers, bills of materials, supplier and facility relationships, substances, recycled content, durability evidence, and footprint data relevant to priority product groups.

It is a sector-specific passport established directly by the Batteries Regulation. It shares digital-product-passport principles with ESPR but has its own categories, data, access, and lifecycle requirements.

The GPSR requires specified manufacturer or responsible-person identification, product identification including an image, and warning or safety information, subject to the detailed legal text and operator role.

A Product Environmental Footprint Category Rule provides more specific modeling and reporting rules for a defined product category.