When a restricted substance becomes a portfolio change

Turning a regulatory decision into a scoped, controlled change across formulas, products, and specifications
Table of Contents
5
min read
Diagram showing a regulated raw material connected through formulations and intermediate blends to affected finished products, specifications, and change-control records.

When a substance becomes restricted, the first job is not finding a replacement but finding every formula, intermediate blend, product, and specification that contains it. Regulatory experts decide how the rule applies; connected product lifecycle data, including where-used analysis, turns that decision into a scoped, controlled portfolio change.

A regulatory change rarely affects only one formula.

When an ingredient becomes restricted, receives a new classification, requires different communication, or creates a new customer requirement, the first operational challenge is usually not finding a replacement.

It is understanding the product impact.

Where is the substance used? Which formulas contain it? Which intermediate blends depend on it? Which finished products, specifications, labels, supplier records, customer commitments, and change requests may be affected?

For chemical and formulation-driven companies, that is a product-data question.

Regulatory experts determine how a requirement applies. Product, R&D, quality, and supply-chain teams need connected lifecycle data to turn that interpretation into portfolio action.

‍

Regulatory intelligence is not product impact

Regulatory intelligence and product impact are different questions. Regulatory intelligence answers questions about requirements, status, scope, and timing. It may come from internal experts, external counsel, regulatory-content providers, industry associations, and official sources.

Product impact answers a different set of questions:

  • Which materials are affected?
  • Where are those materials used?
  • Which product versions contain them?
  • Which products are sold into the relevant markets?
  • What evidence, specifications, and controlled changes need review?
  • Which reformulation or qualification projects should begin first?

These two capabilities need to work together, but they should not be confused.

Uncountable is not a legal-advice platform or a replacement for regulatory-content expertise. The value of connected lifecycle data is that it makes an expert conclusion actionable across the product portfolio.

‍

Where-used is the first required capability

When a substance is affected by a regulatory change, teams often begin with a manual search.

They pull ERP (enterprise resource planning) reports, search formula spreadsheets, review supplier documents, contact individual product teams, and compare local material names. This work can take time because the same ingredient may appear under multiple identifiers, in intermediate blends, across historical revisions, or in products managed by different sites.

A connected product record changes the starting point.

With structured relationships between raw materials, formulas, sub-recipes, products, and revisions, a team can use where-used analysis, a search that returns every formula, sub-recipe, product, and revision containing a given material, to identify the relevant portfolio. It can see which products contain the substance directly, which ones contain it through an intermediate blend, and which released or in-development revisions may need review.

That does not answer the regulatory question. It gives the organization the map needed to act on the answer.

‍

From restriction to product change

A connected workflow can support the path from regulatory interpretation to controlled product change, especially when regulatory checks sit alongside the formulation data.

First, the organization records the affected material and the relevant decision context: source, interpretation, scope, date, owner, and applicable markets. Regulatory experts should determine the appropriate content and approval requirements for that record.

Next, the team identifies product impact through the material-to-formulation relationships. It can group affected products, assess business priority, and determine which changes require R&D work, supplier engagement, specification review, or customer communication.

Then, formulation teams can evaluate alternatives. They can preserve the experiments, qualifications, tradeoffs, and selected replacement in the product history.

Finally, the approved revision can move through controlled change processes, with the associated specifications, quality evidence, and downstream operational handoffs visible as part of the change.

This does not remove the complexity of regulatory work. It removes avoidable uncertainty about where the affected substance appears and how a decision should flow through the portfolio.

‍

Specifications are part of regulatory readiness

A material change can affect more than the formula.

It can affect the specification used to verify the product, the methods used to test it, the documentation sent to customers, and the quality evidence required before release. If those records are disconnected, the company can complete a formulation update without fully assessing the downstream effects.

That is why regulatory change management should connect formulation data, specifications, quality records, and product revisions.

Read our guide on specification management across PLM and quality.

‍

Keep the decision attached to the product

A future team should be able to understand not only that a formula changed, but why it changed.

The change history should preserve the relevant decision context: the material involved, the product impact, the alternatives considered, the approval path, and the evidence supporting the released revision.

This is valuable when a customer asks about a product, a supplier changes again, an audit occurs, or a related restriction creates a similar portfolio question years later.

The product record becomes a reusable source of organizational knowledge rather than a series of disconnected change projects.

‍

A connected data layer makes experts more effective

Regulatory specialists should not spend their time manually reconstructing the portfolio impact of every material decision. Formulators should not need to search through old files to determine whether a replacement was already tested. Quality teams should not have to infer whether a formula revision changed the applicable release criteria.

Connected product lifecycle data gives each function a shared, governed view of the work while preserving its own responsibilities.

‍

How to prepare before the next restriction

The time to build the where-used map is before the next restriction arrives, not during it. A few preparatory steps make the next portfolio review much faster:

  1. Harmonize material identities. Link trade names, chemical names, internal codes, and site-specific names for the same substance, so one search finds every use.
  2. Record composition below the top level. Capture what is inside purchased raw materials and intermediate blends, not only the materials added directly to a formula.
  3. Link products to markets. Record which product versions are sold where, so a market-specific rule can be scoped to the right revisions.
  4. Connect specifications and quality records. Tie each product revision to its specification and test methods, so a formula change prompts a review of release criteria.
  5. Agree a triage template. Decide in advance which fields an impact assessment needs, such as product, market, business priority, owner, and next action.

For example, a coatings or adhesives team facing a new restriction on an additive might run a where-used query, filter the results by market, then rank affected products by volume and the effort a replacement is likely to need. Recent restrictions such as PFHxA show how quickly that scoping work becomes the bottleneck.

The most common mistake is treating each restriction as a separate project with its own spreadsheet. The mapping work is then repeated every time, and lessons from the last reformulation are hard to find.

Explore Product Lifecycle Management to see how formulas, material relationships, specifications, revisions, and controlled changes can remain connected across the product lifecycle.

FAQs

How does PLM support regulatory change management?

PLM supports regulatory change management by connecting materials, formulas, products, specifications, revisions, and change records. When regulatory experts identify an affected substance or requirement, teams use those relationships to find portfolio impact, prioritize and organize reformulation work, review specifications and quality evidence, and keep the history of the approved change attached to the product.

What is where-used analysis in formulation management?

Where-used analysis identifies every formula, sub-recipe, intermediate blend, finished product, and product revision that contains a selected material or component, whether directly or several levels down. It shows the potential scope of a raw-material, supply, cost, or regulatory change, so teams can prioritize the affected products instead of searching spreadsheets and ERP reports by hand.

Does PLM replace regulatory compliance software or legal advice?

No. Regulatory experts and specialized content sources determine legal requirements and how they apply. PLM makes those decisions operational by connecting the affected materials to the products, specifications, changes, and evidence across the portfolio, so the organization can see where a substance is used and route each product change through a controlled process.

How can chemical companies prepare for future restricted substance changes?

Chemical companies can prepare by harmonizing material identities across names and codes, recording composition inside raw materials and intermediate blends, linking product versions to the markets where they are sold, connecting specifications to product revisions, and agreeing a standard impact-assessment template. With that in place, a where-used search can scope the next restriction quickly.