A supplier site change needs a product impact decision

A supplier announces that future deliveries will come from another manufacturing site. The commercial contact, product name and price remain unchanged. Procurement updates the address, and the next shipment arrives before quality or regulatory affairs has assessed the consequences.

The problem is not that every site change has the same regulatory outcome. It is that the organisation has implemented a change before establishing its impact. A source change needs a controlled assessment tied to the materials and products that depend on that source.

For Indian operations, determine the applicable rules, licence and product commitments before deciding what evidence or permission is needed. A workflow can organise that assessment; it cannot decide that one filing category applies to every product and market.

Capture the change before changing the master data

Create a change record from the supplier notice. Preserve the notice and record what is proposed, when the supplier intends to implement it, and which materials or manufacturing activities are affected. Distinguish a change in manufacturing site from a commercial-office address change or a different distributor.

Those events may share a similar email subject but have different implications. Ask for missing information rather than filling gaps with assumptions. If the supplier has not stated whether the process, specifications, equipment or testing arrangements change, record those questions explicitly.

Procurement should identify open purchase orders and business deadlines. Supplier quality should establish the source assessment needed. Regulatory affairs should assess product and market commitments. Manufacturing or technical teams should evaluate process and material implications within their responsibilities.

For APIs, ICH Q7 section 13 addresses formal assessment of changes that can affect production and control. It also covers associated documentation and evaluation after implementation. Apply the relevant Indian requirements alongside the product's market-specific obligations.

Build a dependency map with usable identifiers

Start from the affected material and follow its actual uses. A bill of materials is a useful input, but it may not capture development batches, alternate formulations, customer-specific arrangements or stock held at another site.

The map should connect:

• Material code, grade and approved specification.
• Current and proposed manufacturer and site.
• Products or intermediates using the material.
• Manufacturing sites and processes receiving it.
• Relevant markets and product authorisations.
• Quality agreements, testing arrangements and controlled documents.
• Existing inventory, open orders and shipments in progress.

The purpose is to identify assessment work and prevent an unsupported implementation. Do not interpret every relationship as proof that the outcome will change. A product-market pair may be assessed and found unaffected, but that conclusion should be attributable and supported.

Keep the map reproducible. Store the versions of the source records used and a review date. If a new product starts using the material during the assessment, the change owner needs a way to detect that addition.

Work through a multi-product example

In an illustrative case, one API is used in four products sold in two markets. There are eight product-market combinations to consider. That does not mean eight identical submissions are needed. It means eight applicability decisions must be accounted for, with grouping where the responsible regulatory team considers it appropriate.

Suppose two product-market combinations can proceed after the required internal work, while others need an additional regulatory step. An organisation-wide “supplier approved” flag would obscure that difference. The implementation record needs to express the permitted product and market scope.

Existing stock also needs a deliberate treatment. Material from the current source does not become unacceptable merely because the supplier proposes another site. Conversely, a pending business decision does not authorise new-source stock for use. The relevant teams should document how each category is handled under the approved procedures.

Separate approvals from readiness

A change can be approved in principle while implementation prerequisites remain unfinished. The system should distinguish those states.

For example, the reviewers may approve the proposed plan, but the new supplier record, specification mapping, required testing, documents and training still need completion. If the application exposes “approved” to purchasing too early, users may interpret plan approval as permission to order or use the new source.

Define the meaning of each state in business terms. A suggested sequence is assessment, approved implementation plan, prerequisites complete, authorised activation and post-implementation review. Adapt it to the organisation's procedure and the actions each state permits.

Assign a named owner to each prerequisite and record its evidence. “Regulatory complete” should point to the applicable assessment or authorisation rather than an unexplained checkbox. The same applies to technical work: the system stores the conclusion and evidence reference; qualified specialists determine whether the evidence is adequate.

Make purchasing apply the exact activation decision

The activation record should say what changes, where it applies and when it becomes effective. It may identify approved material-site-product relationships and any transitional arrangements. Purchasing and receiving need the same interpretation.

An order created before activation may still arrive afterwards. A supplier may deliver the new source earlier than agreed. A changed order may retain an old default site. These are ordinary scenarios that should be included in the design, not handled by overwriting transaction history.

At receiving, compare the delivered source with the permitted scope. If the source differs, preserve the physical observations and route the discrepancy. Do not update the expected source solely because a delivery has already occurred.

Record whether the integration successfully published the new approval scope to dependent systems. Reconcile the enterprise resource planning (ERP), quality and supplier-portal systems after activation. If one system still uses the previous scope, the owner needs an explicit recovery task and a controlled temporary process.

Keep current rules and proposals separate

Regulatory research needs both a baseline and a change check. The CDSCO Gazette index lists final instruments and drafts. A proposal should be tracked as a possible future change, not applied as an operative requirement without confirming its status.

For each regulatory assessment, retain the jurisdiction, product context, instrument or approved commitment considered, assessment date, conclusion and reviewer. This makes the decision reviewable when the source or applicable framework changes again.

Avoid putting a universal “site-change approval takes X days” statement into a project plan. The required work depends on the change and product context. A useful schedule distinguishes internal tasks, external dependencies and uncertain completion dates, with the evidence supporting each assumption.

Test the workflow with changes that arrive out of order

Use a small group of affected materials for the pilot. Demonstrate a complete approved path and several exceptions:

1. A supplier notice lacks the proposed manufacturing-site details.
2. A product is added to the affected-material map after assessment begins.
3. One market has an unresolved prerequisite while another has completed its assessment.
4. A shipment from the new site arrives before authorised activation.
5. An old integration message tries to restore the previous scope.
6. Post-implementation review identifies a reason to restrict the new source.

For every scenario, inspect the business record and the operational response. It should be clear who owns the next decision, which activities are permitted and what evidence remains missing.

Measure unnoticed source changes, open assessments by age, transactions requiring correction and the time needed to reconstruct an activation decision. Fast approvals are useful only when the correct scope and prerequisites are preserved.

Summary and next actions

A supplier site change affects more than a vendor address when products, quality controls or registered commitments depend on the source. The right first step is an impact map, followed by scoped decisions and controlled activation.

• Choose one recent supplier change and connect the original notice to its affected materials, products and markets.
• Ask quality and regulatory owners to identify the decision and prerequisites for each affected use.
• Check whether purchasing activated only the approved scope after those prerequisites were met.
• Use any gaps to test a workflow that preserves different outcomes and their decision history.

Connect that work to supplier qualification, general change-control impact assessment and technology-transfer readiness. NextEdge Labs can help design the dependency model and system handovers around the decisions your quality and regulatory teams already own.