How to Standardize Part Numbers Across Multiple Sites

Standardising part numbers across multiple sites means establishing a single, consistent naming and coding convention for every spare part and consumable in your maintenance inventory — so that the same component carries the same identifier whether it is stocked in Chennai, Dubai, or Singapore. Without this, multi-site organisations routinely hold the same physical part under three different codes at three different locations, purchase duplicates because the storeroom teams don't realise they are ordering the same item, and spend hours resolving discrepancies between site-level inventories and the central procurement system. According to the Society for Maintenance and Reliability Professionals (SMRP), uncoordinated MRO inventory across multi-site operations increases total parts spend by 15–30% compared with organisations running a unified master parts catalogue — the direct result of duplicated stock, missed redistribution opportunities, and fragmented supplier negotiations. This guide covers why part number chaos develops, how to build a standardisation framework, and how to implement it sustainably across your sites.

Key Takeaways

• Duplicate part numbers are the most expensive inventory problem most organisations don't measure: The same bearing held as CRG-201, BRG-SKF-201, and ITEM-0445 at three sites means three separate reorder cycles, three safety stock buffers, and zero visibility of combined demand for supplier negotiation.
• A master part number schema needs four fields minimum: Category prefix, manufacturer or supplier code, part descriptor, and a unique sequence number — applied consistently before any part enters the CMMS.
• Deduplication before migration is non-negotiable: Loading site inventories into a central CMMS without a deduplication pass first multiplies the duplicate problem rather than solving it.
• Governance prevents re-fragmentation: A standardised catalogue degrades back into inconsistency within 12–18 months without a defined process for adding new parts and a single owner responsible for catalogue integrity.

Why Part Number Inconsistency Develops Across Sites

Part number inconsistency is almost never the result of negligence. It is the natural outcome of sites operating independently over time, each solving the same problem with different tools and different naming instincts.

A site that opened in 2015 built its parts list in a spreadsheet, using whatever codes felt logical to the stores manager at the time. A second site that opened in 2018 used a different CMMS, which imposed its own auto-numbering. A third site inherited its parts catalogue from the previous occupant of the facility. By the time a group operations team tries to create a unified view of inventory across all three, they have three completely different coding structures for what might be 60–70% overlapping physical parts.

The problem compounds with every new part added. Without a central approval and coding process, a technician at Site A who orders a new seal variant adds it to the local system under whatever code is convenient. The same seal is independently added at Site B three months later under a different code. Now there are two records for the same physical item, and neither site knows the other holds stock. The next time one site faces a stockout and orders on emergency rates, the other site has four units sitting unused on the shelf.

The operational consequences are direct and measurable: duplicated safety stock across sites ties up working capital; fragmented demand prevents volume-based supplier negotiations; transfers between sites are impractical because storerooms can't reliably identify whether their stock matches another site's requirement; and MRO spend analysis at the group level is impossible when the same part appears under different codes in every site's data. According to Plant Maintenance Resource Center, organisations that implement a unified master parts catalogue typically recover 10–20% of their total MRO procurement spend within two years through consolidated supplier negotiations and elimination of duplicate safety stock.

Building a Multi-Site Part Number Schema

A part number schema is the naming convention that every part in your inventory must follow. Getting this right before any migration work begins is the most important investment in the standardisation project. A schema that is logical, scalable, and easy to apply consistently will outlast the implementation team. One that is too complex or too rigid will be bypassed within months.

A practical schema for most multi-site maintenance operations contains four elements:

• Category prefix (2–3 characters): A short code identifying the part's primary category — MEC for mechanical, ELE for electrical, HYD for hydraulic, FLT for filters, LUB for lubricants, SAF for safety consumables. Category prefixes make it immediately apparent what type of part a code refers to, without needing to open a description field. Use a flat, simple category list — ten to fifteen categories covers the vast majority of MRO inventories. Avoid creating twenty sub-categories that require detailed knowledge to apply correctly.
• Manufacturer or supplier code (3–4 characters): A short identifier for the primary manufacturer or authorised supplier — SKF, FAG, 3M, DOW, OEM. This element allows rapid filtering of all parts from a given supplier, supports supplier-level spend analysis, and clarifies interchangeability decisions (parts from different manufacturers with different codes that are functionally equivalent). Where a part has no distinguishable manufacturer, use GEN for generic or CSM for consumable.
• Part descriptor (4–6 characters): A short alphabetic descriptor of the specific component type — BRG for bearing, SL for seal, BLT for belt, VLV for valve, FILT for filter, O-RNG for O-ring. Keep these codes short and memorable. The goal is that a storeroom team can look at a code like MEC-SKF-BRG-0441 and immediately understand they are looking at a mechanical SKF bearing, number 0441 in the catalogue.
• Sequence number (4 digits): A zero-padded sequential number assigned by the central catalogue owner when the part is approved and added — 0001, 0042, 0441. Sequence numbers prevent duplicates because they are assigned centrally, never locally. A site cannot create a new part record without the central owner assigning the next available number.

The full schema example: MEC-SKF-BRG-0441 — mechanical category, SKF manufacturer, bearing type, catalogue item 441.

Use the MRO inventory checklist as the baseline template for capturing the data fields you need to describe each part correctly when building the initial master catalogue.

Standardised vs. Non-Standardised Part Numbers: The Operational Difference

The inter-site transfer row deserves particular attention. When a critical asset fails at Site A and the required part is out of stock, the fastest resolution is often a same-day transfer from another site. With standardised part numbers, confirming availability and compatibility takes seconds — a search in the central CMMS inventory module returns stock levels at every site for that part number. Without standardisation, the storeroom team at Site A has to call each site individually, describe the part verbally, and wait for someone to physically check whether the part on their shelf matches the requirement.

The Four-Step Standardization Process

Executing a multi-site part number standardisation project in a structured sequence prevents the most common failure modes: starting migration before the schema is agreed, loading data before duplicates are resolved, and going live without governance in place.

• Step 1 — Export and consolidate all site inventories: Pull a complete export of every part record from every site — part number, description, manufacturer reference, unit of measure, current stock quantity, and last-used date. Combine these into a single working dataset. The raw combined list will almost certainly contain the same physical item under multiple codes — this is expected and addressed in Step 2.
• Step 2 — Deduplicate against manufacturer part numbers: Manufacturer part numbers (MPNs) are the ground truth for deduplication. Where two site records share the same MPN but different internal codes, they are the same part and must be consolidated under a single new master code. Where MPNs are absent or inconsistent, use physical specifications (dimensions, material, operating range) to identify matches. This step is typically the most labour-intensive part of the project — budget 2–4 weeks for a 2,000 SKU combined inventory, depending on data quality. The output is a deduplicated master parts list where each physical part appears exactly once.
• Step 3 — Apply the schema and build the master catalogue: Assign a new standardised part number to every item in the deduplicated list using the agreed schema. Map all existing site-specific codes to the new master code — this mapping table is essential for the migration phase, as it tells each site's CMMS or inventory system how to translate old records to new ones. Load the master catalogue into the central inventory management system and configure it as the authoritative reference that all sites pull from.
• Step 4 — Migrate sites sequentially with validation: Migrate one site at a time rather than all simultaneously. After each migration, run a validation check: confirm that every old site code has a corresponding new master code, that stock quantities match pre-migration levels, and that open work orders referencing old part numbers have been updated. Resolve any unmapped items before moving to the next site. Sequential migration gives you a clean rollback path if a site migration encounters unexpected data quality issues.

After migration, connect each site's spare parts inventory software to the master catalogue so that reorder requests, work order parts issues, and stock adjustments all reference the standardised part number automatically — with no manual translation required at the site level.

Governance: Keeping the Catalogue Clean Over Time

A standardised master catalogue that lacks governance will degrade back into inconsistency within 12–18 months. Sites will add new parts locally under ad hoc codes when the central approval process feels slow. Suppliers will introduce new part numbers that don't get mapped back to existing catalogue items. Equipment upgrades will add new components that nobody thinks to register centrally.

Effective governance requires three things:

• A single catalogue owner: One person — or one small team at group level — has sole authority to add new master part numbers. No site adds a part to the CMMS without a master code issued by the catalogue owner. This single control point prevents duplicate creation and ensures the schema is applied consistently. In practice, the catalogue owner reviews and approves new part requests within an agreed SLA (typically 24–48 hours) — fast enough that sites don't bypass the process.
• A new part request process: When a site needs to stock a part not in the master catalogue, they submit a standardised request form including the manufacturer part number, physical specifications, the asset it is required for, and the requesting site. The catalogue owner checks for existing equivalents (a different MPN that describes the same physical part already in the catalogue), approves or rejects the request, and issues the new master code if approved. This process prevents the most common re-fragmentation mechanism: independent site additions.
• Annual catalogue audit: Once per year, review every part in the master catalogue against consumption data from the maintenance costs reporting module. Parts with zero movement across all sites for 24+ months should be reviewed for removal or reclassification. New parts added during the year should be verified against the schema for consistency. This annual review keeps the catalogue lean and prevents the gradual accumulation of redundant entries.

How Cryotos CMMS Supports Multi-Site Part Number Standardisation

Managing a multi-site master parts catalogue in a spreadsheet reaches its limits quickly. When part records need to be visible and searchable across sites, linked to work orders in real time, and updated simultaneously when a storeroom issues a part — a spreadsheet cannot deliver that without manual synchronisation that introduces errors and delays at every step.

Cryotos's CMMS manages the master parts catalogue centrally while giving each site full visibility and operational access. The central catalogue holds the master part number, description, manufacturer reference, unit of measure, and technical specifications. Each site's inventory record references the master part number and tracks its own stock level, reorder threshold, and consumption history against that shared identifier.

When a technician at Site A issues a part against a work order, the consumption is recorded against the master part number — not a local code. When a manager at group level pulls a parts consumption report, every site's usage is aggregated under the correct master code automatically. When procurement negotiates with a bearing supplier, the combined demand across all sites for every SKF bearing in the catalogue is visible in a single query — no manual consolidation from site-level exports required.

The warehouse management module provides the inter-site stock visibility that makes transfer decisions immediate. When a critical part is at zero stock at Site A and has four units at Site B, the work order at Site A surfaces that availability automatically — so the storeroom manager can initiate a transfer rather than placing an emergency purchase order. This single capability recovers the most directly measurable cost from part number standardisation. According to Reliable Plant's MRO inventory analysis, organisations that centralise their parts catalogue under a unified CMMS reduce total MRO procurement costs by 10–20% within two years, primarily through consolidated supplier negotiations and elimination of emergency purchases driven by inter-site stock invisibility.

Frequently Asked Questions

What is a master parts catalogue and why do multi-site operations need one?

A master parts catalogue is a central, authoritative list of every spare part and consumable used across all sites, each identified by a single standardised part number. Multi-site operations need one because independent site catalogues inevitably diverge — the same physical part accumulates different codes at different sites, making group-level inventory visibility, inter-site transfers, and consolidated supplier negotiation impossible without manual cross-referencing that is slow, error-prone, and does not scale.

How long does a multi-site part number standardisation project take?

Timeline depends on the number of sites, the size of each site's inventory, and the quality of existing data. A three-site operation with 1,500 total SKUs and reasonably clean manufacturer reference data can complete the deduplication, schema application, and migration in six to ten weeks. A ten-site operation with 8,000 SKUs and poor MPN coverage may take four to six months. The deduplication step is consistently the longest — budget more time here than feels necessary, as data quality problems discovered mid-deduplication are more expensive to resolve than time invested upfront in a thorough data quality assessment.

What is the most common cause of part number standardisation failure?

The most common failure is going live without governance in place. The catalogue is clean and standardised on migration day, but within months, sites begin adding new parts locally under ad hoc codes because the central approval process is unclear, slow, or unknown to the storeroom team. The fix is to establish the catalogue owner role, the new part request process, and the SLA for approvals before migration begins — not as an afterthought after go-live.

Can a CMMS enforce standardised part numbers automatically?

Yes, when the CMMS is configured with the master catalogue as the only source of parts that can be referenced in work orders and purchase requests. In Cryotos, the central parts catalogue is the authoritative reference — sites cannot create local part records that do not reference a master catalogue entry. New part additions require master catalogue approval before the part becomes selectable in work orders or purchase requests, enforcing the governance process through the system rather than relying on procedural compliance alone.

A standardised parts catalogue is one of the highest-return investments a multi-site maintenance operation can make — it eliminates duplicate purchasing, enables inter-site transfers, supports group-level supplier negotiation, and makes MRO spend analysis meaningful. Cryotos gives you the central catalogue management, multi-site inventory visibility, and governance controls to build and maintain that standardisation at scale. Schedule a free demo to see how leading multi-site operations teams use Cryotos to unify their parts inventory and cut MRO procurement costs.