Supplier qualification that controls what purchasing can buy

A buyer selects a familiar supplier. The purchase order passes the normal commercial approvals, and the material arrives on time. Receiving then discovers that the manufacturer has supplied it from a different site. The vendor is approved in the enterprise resource planning (ERP) system, but the site-material combination has never been assessed for the intended use.

The useful control is an approval with a defined scope. Purchasing needs to know which source is acceptable for which material and use, under which conditions, at the time the order is placed. A single green flag against a vendor cannot express that decision reliably.

For Indian pharmaceutical operations, start from the applicable requirements and approved quality procedures. Revised Schedule M includes supplier evaluation and approved-source controls. Its requirements differ across relevant parts, so the assessment must identify the applicable provision rather than applying one generic checklist everywhere. Part I section 10.8 assigns supplier approval to the person responsible for quality control together with relevant departments; reflect that applicable authority in the workflow. See Schedule M, including Part I section 10.8 and API materials controls.

Define the object being approved

Commercial supplier, original manufacturer and manufacturing site may be different entities. A distributor can supply materials from several manufacturers. A manufacturer can operate multiple sites. The same site can make several grades of a material, with different specifications and intended uses.

Represent those relationships explicitly. The commercial supplier remains the entity against which purchasing and payment occur. The manufacturing source identifies where the material originates. The approval connects the source to the material or approved material family and its permitted use.

This is an engineering model to support the organisation's quality decision. The responsible quality function should determine the necessary granularity from the material, process and regulatory context. Do not create thousands of unnecessary approval combinations simply because the software can store them. Equally, do not compress materially different sources into one code merely to make data entry easier.

For API operations, ICH Q7 materials-management guidance, section 7, is a useful reference for supplier evaluation and source controls. It is API guidance; its scope should remain visible when a team uses it alongside Indian requirements.

Work through the approval combinations

Consider an illustrative business buying three materials from one supplier. The supplier uses two manufacturing sites. This produces six possible site-material combinations, but the quality team has approved only two.

The supplier's commercial status does not resolve the four missing combinations. Neither does a purchase order below a financial approval threshold. The system should explain the specific gap: “Site B is not approved for Material X under this specification,” rather than displaying an unhelpful “vendor blocked” message.

Suppose Site A later loses approval for Material X. That change should trigger assessment of relevant open orders and incoming shipments. It should not silently erase the earlier approval or rewrite the history of previous purchases. The organisation needs to reconstruct what was known and authorised at each decision point.

Give the qualification record a usable lifecycle

Start with the request to qualify a source. Record the business need, proposed material, source identity, specification and responsible quality owner. Procurement supplies commercial and logistical information; quality determines the evidence and assessment needed for the proposed use.

A practical workflow distinguishes at least these business states:

1. Requested: the source is proposed and the reason is recorded.
2. Assessment in progress: evidence and identified gaps are being reviewed.
3. Approved within scope: the authorised decision and its conditions are recorded.
4. Restricted or suspended: a defined limitation prevents some or all use.
5. Closed or superseded: the record is retained but no longer governs new activity.

These are suggested system states, not a mandatory regulatory vocabulary. Match them to the approved procedure. If conditional approval exists in that procedure, record the exact condition and permitted activity. A label called “conditional” is unsafe as a business control when users cannot tell whether it permits ordering, receipt, testing or production use.

Retain the evidence reviewed, the decision maker, approval date, effective date, scope and any review trigger. A scheduled review date and an approval expiry date are different concepts. Do not automatically suspend a valid source merely because an informational reminder is late unless the approved procedure requires that outcome.

Collect the fields needed for a purchase decision

The following record is a starting point for a design workshop:

Use controlled identifiers where records must join across systems. Keep supplier aliases available for searching, but do not let a similar company name establish that two sources are identical. Where legacy data is incomplete, show the missing field and its owner. Replacing an unknown site with the supplier's head-office address creates false certainty.

Connect the decision to purchasing and receiving

A useful purchasing check runs against the actual order line. It compares the requested material, specification and source with the effective approval scope. If the source is not yet known, the order should follow a defined exception path rather than assuming the vendor's default site.

Repeat the relevant check at receiving. An order can be correct while the delivered source differs. Receiving should capture the source information available on the documents and labels and route discrepancies to the responsible team. It should not edit source identity simply to make the receipt match the order.

Decide which system owns approval. Often the quality workflow holds the authoritative decision while ERP consumes a controlled status or approval reference. The integration needs a version or effective timestamp, an acknowledgement and a reconciliation queue. A failed update must be visible; otherwise purchasing may continue using yesterday's status.

Keep commercial approval separate. Procurement can approve price and delivery terms while the designated quality owner retains the source qualification decision. Both decisions may be necessary, but neither substitutes for the other. The purchase-approval guide develops that distinction.

Test the exceptions before expanding the scope

Pilot one material family with enough variation to exercise the real process. Include an approved manufacturer supplied through a distributor, a second manufacturing site, a changed specification and an order created before a suspension.

Ask the team to demonstrate these outcomes:

• An approved combination is accepted for the permitted activity.
• An unsupported combination is stopped or routed according to procedure, with a specific reason.
• A later source restriction identifies relevant open transactions for assessment.
• A stale integration message cannot overwrite a newer approval decision.
• Receiving can report a source mismatch without changing the original order history.
• An authorised reviewer can reconstruct the evidence and approval effective at purchase time.

Measure the number of unresolved source combinations, time spent obtaining missing evidence and purchases requiring rework. Do not evaluate the project solely by the percentage of automatically approved orders. A system that routes genuine uncertainty correctly can be more useful than one that reports a high pass rate by ignoring missing data.

AI can help classify documents, extract proposed identifiers or identify a possible inconsistency. The extracted information should remain linked to its source and enter a reviewed workflow. A model-generated supplier score is not a qualification decision.

Summary and next actions

Supplier qualification becomes operationally useful when purchasing and receiving can apply its exact scope. Preserve the relationship between commercial supplier, original manufacturer, site, material and approved use.

Start with three actions:

• Select recent receipts and test whether each can be linked to the approval that governed its source.
• Assign owners to missing or ambiguous site-material records before introducing automated checks.
• Pilot the purchase-to-receipt workflow, including a source change and failed status update.

Then connect the controls to COA verification and supplier change control. A focused NextEdge Labs discovery can turn that sample into a record model, integration boundary and acceptance plan for your existing systems.