Govern item masters so duplicate parts do not break factory planning

Why text deduplication alone either strands inventory or creates wrong-spec kitting risk

When multi-plant manufacturers search for item master data management or clean up duplicate part numbers before an ERP migration, existing guides—such as Claro's item master data management guide covering supplier aliases, packaging units, plant extensions and approval workflows, Verdantis' overview of item master data models and governance, ETH Zurich's OPESS teaching notes on separating technical, stockkeeping and cost views in the item master and Vesonix's manufacturing BOM change and impact guide—already describe structured naming conventions, taxonomy fields and multi-department stewardship.

In daily plant operations, however, master-data cleanup projects fail when teams treat deduplication as a purely clerical text-matching exercise rather than a cross-functional engineering, inventory and financial transaction control:

1. Pack-unit duplicates that create phantom MRP shortages: A buyer creates a new item code for a vendor's 10-piece box (UoM = BOX) because the existing engineering part was set up in individual pieces (UoM = EA). Even though 18 boxes (180 pieces) sit in stores, MRP sees zero stock under the engineering part number and triggers an unnecessary material request (ERPNext material request documentation, S05).
2. False duplicates where a critical clearance or seal suffix is ignored: Automated text matching scores BRG-6205-2RS (Spec A) and BRG-6205-2Z-C3 (Spec B) at over 90% similarity because both share 6205 boundary dimensions (25 mm × 52 mm × 15 mm). As technical bearing literature explains, C3 designates a greater-than-normal radial internal-clearance class rather than a standalone temperature rating or guarantee against bearing seizure, and seal/shield suffixes (2RS contact seals vs 2Z non-contact shields) alter speed and retention characteristics (SKF guide to rolling bearings and seals in electric motors and generators). Automatically merging them commingles distinct engineering specifications and creates potential wrong-spec kitting risk.
3. Revision clones created instead of controlled engineering changes: Planners clone a new item number whenever a drawing tolerance changes, rather than managing product versions and transaction effectivity through structured engineering change controls (Microsoft Dynamics 365 engineering change management, S03; Microsoft engineering change management FAQ, S22).

Govern item masters so duplicate parts do not break factory planning — reporting workflow

Follow the workflow below, or open its complete text version.

Read the complete workflow as text

1. Flag candidate duplicate cluster via attribute and alias scan → Verify form-fit-function equivalence with engineering owner
2. Verify form-fit-function equivalence with engineering owner → Convert pack units and re-index open POs, BOMs and bins
3. Convert pack units and re-index open POs, BOMs and bins → Reconcile combined moving-average inventory valuation with finance
4. Reconcile combined moving-average inventory valuation with finance → Execute controlled merge or lock distinct attribute boundary

Four-owner governance contract for manufacturing item masters

Consistent with the separation of technical, stockkeeping and accounting data taught in ETH Zurich's item master architecture and enterprise engineering-change controls (S03, S22), no single department should have unrestricted write access to create, merge or obsolete an active manufacturing part record. Enforce a four-stage ownership gate:

As explained in the Microsoft Dynamics 365 engineering change management FAQ (S22), plants must decide when a change remains a tracked version of the same item versus when it requires a distinct item identifier. When two records are genuinely identical in form, fit and function, merging them requires migrating open material requests (S05), purchase orders and bin balances without losing audit traceability.

Worked example: resolving a 4-record 6205 bearing duplicate cluster (Batch IM-GOV-2026-10)

Scope note: All item IDs, fictional specification codes (Spec A, Spec B), vendor catalogue aliases (VND-6205-2RS-BOX10), bin quantities, rupee valuations and order numbers below are purely synthetic illustrative records constructed to demonstrate manufacturing item-master governance. They are not bearing design or operating advice; in practice, bearing selection and interchangeability require qualified engineering review of manufacturer datasheets and application conditions (SKF rolling bearings and seals guide).

Consider synthetic industrial gearbox plant CHN-GBX-01, which is preparing its October MRP run for 600 gearboxes across two engineering-approved assembly BOMs that specify non-interchangeable 6205 bearing records after qualified engineering and manufacturer datasheet review:

• 400 Assembly Series A Gearboxes (Model GBX-SER-A): Require 2 bearings / gearbox = 800 EA of fictional approved Spec A (BRG-6205-2RS-C0, CN/C0 normal radial internal clearance with 2RS contact seals).
• 200 Assembly Series B Gearboxes (Model GBX-SER-B): Require 2 bearings / gearbox = 400 EA of fictional approved Spec B (BRG-6205-2Z-C3, C3 greater-than-normal radial internal clearance with 2Z non-contact shields, designated by engineering as non-interchangeable with Spec A).

Ahead of the MRP run, an automated master-data similarity scan flags four active 6205 (25 mm × 52 mm × 15 mm) item records in Batch IM-GOV-2026-10:

Reconciling physical stock, moving-average valuation and MRP net requirements after governance

When Engineering, Stores, Purchasing and Finance execute the controlled decisions in Batch IM-GOV-2026-10, every physical bearing, rupee of inventory value and MRP shortage reconciles across the three distinct post-governance states (merged master, distinct specification, and superseded revision record):

Notice why both under-merging and over-merging would have damaged planning and inventory integrity:

1. Why leaving ITM-28904 unmerged distorted MRP: Because 18 BOX (180 EA) sat under a separate vendor-catalogue code (VND-6205-2RS-BOX10), ITM-10412 showed only 420 EA on hand + 200 EA on PO-7810 = 620 EA against 800 EA demand. That 180 EA phantom deficit caused a planner to raise MR-4402 (S05) for 20 BOX (200 EA at ₹1,850/BOX = ₹37,000 of planned purchase exposure). Normalising 18 BOX × 10 EA/BOX = 180 EA into ITM-10412 brings total available supply to 800 EA, cancelling the unapproved purchase request before PO release and preserving exact general-ledger value (₹75,600 + ₹33,300 = ₹1,08,900, or ₹181.50 / EA).
2. Why auto-merging ITM-31108 (91% text similarity) would have created potential wrong-spec kitting risk and costing distortion: Because C3 is an internal-clearance class (Spec B, paired here with 2Z non-contact shields) that engineering approved specifically for GBX-SER-B rather than an interchangeable substitute for Spec A (CN/C0, 2RS), an automated script merging all 6205 records into a single pool (750 EA on hand + 300 EA on PO = 1,050 EA against 1,200 EA combined demand) would have blended the moving-average cost to ₹1,47,900 ÷ 750 = ₹197.20 / EA (distorting product margins; see how we make the plant margin report show decisions rather than conflicting totals) and exposed assembly kitting to issuing Spec A stock against Spec B work orders.
3. Why superseding ITM-39055 via controlled version effectivity differs from a duplicate merge: Unlike ITM-28904 (which represented the exact same Spec A revision stored under a box UoM), ITM-39055 was an earlier Rev A engineering definition. Rather than merging its identity away, engineering change controls (S03, S22) retain ITM-39055 in closed/superseded status for historical service traceability while updating active BOM effectivity dates—aligning system write boundaries as detailed in our guide to deciding which manufacturing decisions belong in ERP, MES, QMS and PLM and piloting ERP and shop-floor integration exceptions.

Run a 50-part duplicate triage pilot before freezing master-data rules

Before launching a plant-wide item-master cleansing programme, test this four-step governance loop on one high-value component family (such as bearings, fasteners, seals or electrical contactors):

1. Extract candidate clusters with open balances: Group active items by geometry or supplier reference, together with current bin quantities, base UoMs, moving-average unit costs, open purchase orders and active BOM references.
2. Require explicit engineering disposition (Merge Duplicate, Keep Distinct Spec, or Supersede via ECN): Never permit a bulk spreadsheet upload to deactivate or merge parts without qualified engineering review of manufacturer datasheets confirming whether internal clearance, seal configuration, material grade or revision effectivity differ.
3. Execute UoM conversion and financial value reconciliation before closing a true duplicate code: Convert secondary pack quantities (BOX, SET) into the master base UoM (EA) and verify that post-merge physical piece counts and ledger rupee totals match the pre-merge sum to the last unit and rupee.
4. Audit post-governance BOM effectivity, open purchase orders and MRP net requirements: Confirm that supplier pack aliases are mapped in the Approved Manufacturer List, superseded revision codes are blocked from new purchasing under controlled effectivity (S03, S22), and the next MRP run generates shortage requests only for genuine net deficits.