You handle part number and revision mismatches by treating them as controlled exceptions, not as routine data cleanup.
The practical rule is simple: the internal system of record for the item and its approved revision must win unless an approved change process says otherwise. If supplier data does not align, do not silently overwrite your ERP, PLM, MES, or quality records to make the transaction pass.
Identify which field is mismatched: customer part number, supplier part number, internal part number, drawing revision, specification revision, or document version.
Check the authoritative source for that item in your environment. In most plants this is split across PLM, ERP, document control, and supplier quality records.
Determine whether the mismatch is acceptable by rule, blocked by policy, or unknown. Not every revision difference means the same thing.
Hold or flag the affected receipt, ASN, PO line, inspection lot, or work order transaction until disposition is clear.
Approved cross-reference exists. If the supplier part number is an approved cross-reference to your internal part number, map it through controlled master data and preserve both values for traceability.
Equivalent revision is formally allowed. Some environments allow revision tolerance under defined conditions, but only if the governing documents, contracts, and quality rules permit it. That needs explicit evidence, not operator judgment.
Supplier used an obsolete or incorrect revision. This is usually a receiving, quality, and supplier coordination issue. The material may need segregation pending review, and the event may need an NCR or supplier corrective action depending on impact.
Your own master data is wrong or incomplete. This happens often in brownfield environments. Fixing the supplier record alone does not solve the root problem if ERP, PLM, document control, and purchasing are out of sync.
A governed part master with approved aliases, supplier cross-references, and effectivity where relevant
Revision and document control rules that define when a mismatch is blocking versus informational
Receiving and inspection workflows that can place transactions on hold without losing traceability
Exception queues with ownership across purchasing, engineering, quality, and supplier management
Audit trails showing who reviewed the mismatch, what evidence was used, and what disposition was applied
Do not let users free-type replacements into operational systems without change control.
Do not assume a revision mismatch is harmless because the item looks identical.
Do not rely on email-only approvals if your process requires controlled records.
Do not collapse supplier and internal numbering schemes into one field if both need to be retained for traceability.
In most regulated manufacturing environments, this is not solved by one application setting. Part and revision mismatches usually sit across ERP, PLM, MES, QMS, supplier portals, EDI messages, and document repositories. If those systems disagree on the authoritative value or update timing, mismatches will recur.
That is why full replacement is often a poor response. Replacing ERP, MES, or PLM just to fix supplier master data issues usually runs into qualification burden, validation effort, downtime risk, integration complexity, and long equipment and process lifecycles. A more realistic approach is to establish a canonical mapping model, tighten change control, and add exception handling around existing systems.
Strict blocking controls reduce the risk of building, receiving, or inspecting against the wrong revision, but they can slow receiving and increase shortages if master data is weak. Looser controls improve flow but increase the chance of traceability gaps, rework, and disputed accountability later. The right balance depends on product criticality, supplier maturity, contract terms, and how reliably your systems propagate revisions and document changes.
If mismatches are frequent, treat that as a data governance problem, not just a supplier behavior problem. You may need to clean up source ownership, synchronize change release timing, and formalize supplier-facing numbering and revision rules.
Whether you're managing 1 site or 100, C-981 adapts to your environment and scales with your needs—without the complexity of traditional systems.
