Blog · 18 November 2026 · Paulo Cordeiro

Auto parts master data cleansing: part numbers and cross-references

How to approach auto parts master data cleansing: separate the part from its codes, approve cross-references, link superseded numbers and move fitment out.

Auto parts master data cleansing starts by separating the physical item from the codes that point to it: the vehicle manufacturer's part number, the aftermarket manufacturer's code, each supplier's code and the internal code. Then cross-references become a table with a type and an approver, superseded part numbers stay linked to their replacements, and vehicle fitment moves out of the description into its own table.

At an auto parts distributor or retailer, it is common to see the same brake pad come up four times in an ERP search. One under the vehicle manufacturer's code, two under aftermarket manufacturers' codes and one that, on closer inspection, is a kit with a wear sensor. All four have stock, each has its own price, and every description tries to squeeze the car, the year and the engine into 40 characters.

The salesperson at the counter picks whichever appears first. Purchasing replenishes the one that ran out. The warehouse ends up with the same part sitting in three locations while the customer is told it is out of stock.

What is auto parts master data cleansing?

It is an item by item review of the parts master to remove duplicates, standardize descriptions, classify items and enrich attributes, before or during the load into the ERP. The foundation is the same as material master data cleansing. What changes with auto parts is the shape of the data: one physical item has several legitimate codes, relates to other items through interchange and supersession, and fits a list of vehicles that changes with every model year.

No public Brazilian standard for auto parts cataloging was consulted for this article. Everything below about the data model and method is a recommended practice for master data, not a regulatory requirement. The parts that depend on Brazilian law or regulation are identified with their source.

Why does one auto part end up with three or four codes?

Because every link in the chain has its own code, and all of them are correct. The vehicle manufacturer has the original part number. The aftermarket manufacturer has its own code for the same application. Each supplier or distributor may use a third code on the purchase order and invoice. And the company still creates its internal code.

The mistake is treating each code as a separate material. Someone receives an invoice with a code they cannot find in the search and creates a new item. Within a few years, the same physical part is spread across several records, with stock, cost and sales history split between them.

Terms such as "genuine", "original" and "aftermarket" are used in the market, but no regulatory definition of them was consulted. Instead of putting those words in the item name, the master record should store the source of each code in a dedicated field: vehicle manufacturer, aftermarket manufacturer, supplier or internal.

How do you separate the item from its codes?

1. Define what an item is

An item is a physical part with the same technical characteristics and the same interchangeability, regardless of who makes or sells it. If parts from two different manufacturers are accepted as interchangeable by the company's technical catalog team, the decision to keep them as one item or as two items linked by a cross-reference must be made once and written down as a rule. One alternative is to keep separate items per manufacturer, because price, warranty and supplier differ, and link them through the cross-reference table. What matters is that the rule applies to the whole master.

2. Create an item code table

Each code becomes a row related to the item, with: the code as received, the normalized code, the source (vehicle manufacturer, aftermarket manufacturer, supplier, internal), the name of the issuer and the status (active or superseded). The internal code remains the item key in the ERP.

3. Normalize before comparing

Part numbers arrive with hyphens, dots, slashes, spaces, lowercase letters and leading zeros that one system keeps and another drops. To compare them, create a normalized code: uppercase, no separators. Keep the original format as well, because that is what appears in the manufacturer's catalog and on the supplier's invoice.

Watch for the letter O used instead of zero and the letter I used instead of the number 1. A comparison that swaps those characters finds candidates, but merging only happens after checking the issuer's catalog. For some manufacturers, a leading zero is part of the code. The general signs of duplication and the false positives are covered in how to identify duplicate materials.

How do you build the cross-reference table without creating fitment errors?

An interchange is a relationship between two codes (or two items), not a line of text in the description. Writing "replaces X" in a notes field means nobody can query, filter or review it.

Types of interchange

  • Equal: both codes fit the same applications, with no conditions.
  • Replaces with conditions: it fits, but with a condition (for example, it needs another component, covers only part of the applications or changes the mounting position). The condition is written on the row.
  • Superseded: the issuer itself replaced the old code with a new one. It has a direction: the old code points to the new one.

Who approves

Each row needs the source of the information (manufacturer catalog, technical bulletin, internal test), a date and an approver. Approval belongs to the technical catalog or engineering team, never to someone in a hurry to close a sale. A wrong interchange becomes a returned part, a denied warranty claim or, worse, a part installed where it does not belong.

Which applications does the interchange cover?

Two parts can be equal for one engine and different for another. When the interchange does not cover every application of both items, it is a "replaces with conditions" type, and the condition states which applications are covered.

What do you do with a part number superseded by the manufacturer?

When the vehicle manufacturer or aftermarket manufacturer supersedes a code, the old code keeps showing up: in old stock, in customer orders, in repair shop quotes and on invoices from suppliers who have not updated yet. Creating a new standalone item for the new code is the fastest way to end up with two identical parts with separate stock.

The recommended handling is:

  • record the new code as a code of the item (or create a new item if the part actually changed);
  • mark the old code as superseded and link it to the new one with the "superseded" type;
  • block new purchases under the old code but keep it searchable, so the salesperson finds the current part;
  • decide with purchasing and sales what to do with the old stock: sell it down, transfer it or write it off.

Supersession chains (A became B, which became C) should point to the current code, without making the user follow the path by hand.

Where does vehicle fitment go?

In a table related to the item, one row per application: vehicle manufacturer, model, trim, start and end model year, engine and position, with a notes field for restrictions (for example, "from a given chassis number onward", when the manufacturer's catalog provides it).

Fitment inside the description creates three problems. It does not fit: an item that fits dozens of vehicles ends up with a truncated description. It does not filter: nobody can ask the system "which brake pads fit this car". And it cannot be maintained: when the manufacturer extends the fitment, someone has to rewrite the description, and the search changes with it. The same mistake shows up with other technical items, as described in the article on the mistake of putting the application in a bearing's name.

For the salesperson, the answer is a vehicle search that reads the fitment table. The description is there to identify the part.

Side, position, sets and kits: how should they be recorded?

Position and side as attributes

Front or rear, left or right, upper or lower, inner or outer. These values change the part: a front left shock absorber and a front right one may have different codes. That is why they become attributes with a closed list of values, not loose abbreviations at the end of the description. Each attribute definition follows the material attribute dictionary.

Set, pair and each

Brake pads are usually sold as a set, shock absorbers sometimes as a pair, bulbs individually. If the same code appears with one unit in purchasing and another in sales, price, stock and margin are wrong. Define the item's unit of measure and the quantity per package. If the company buys individually and sells in pairs, that is a recorded unit conversion, not two items with the same description.

A kit is a different item

Clutch kit, timing belt kit with tensioner, brake pads with wear sensor: the kit has its own code and a bill of components, each linked to its own item. It is not the single part with "w/ sensor" added at the end. This way you know which components exist on their own, which only come in the kit and when a kit can be assembled from stock.

Used parts and Inmetro registration: what changes in the master record?

Used parts from vehicle dismantling

In Brazil, Lei nº 12.977/2014 (Law No. 12,977/2014) regulates vehicle dismantling. Contran is Brazil's National Traffic Council. According to the text consulted:

  • after dismantling, the dismantling company records within 5 business days, in the database set up by the law, the parts that will be reused, with the information required by Contran (art. 9);
  • only used parts that meet Contran's technical requirements may go to the replacement market (art. 10, caput); Contran defines, among other points, the list of parts that cannot be used for replacement (art. 10, § 1, II); parts that do not meet the requirements go to scrap or another final disposal within 20 business days of dismantling (art. 10, § 2);
  • the dismantling company may not sell new parts (art. 10, § 4);
  • there is a national database of dismantled vehicles and of parts intended for replacement or scrap, managed by the federal traffic authority (art. 11);
  • the offer must give the buyer clear information about the origin and condition of the part (art. 12);
  • selling a part as a replacement part without the record required by art. 9, and failing to state clearly at the time of sale that the part is used, are serious infractions (art. 16, II and III).

The law applies to dismantling companies. For businesses that buy and resell used parts, the recommended master data practice is: a condition attribute (new or used), origin fields (the dismantling company and the part's record identifier, when received) and a separate code for the used part, distinct from the new one. That way the condition appears on the order, the invoice and the listing without relying on someone remembering to type it.

Components registered with Inmetro

Inmetro is Brazil's national metrology, quality and technology institute. It defines product registration as the act by which it authorizes placing a regulated product, input or service on the Brazilian market and the use of the conformity identification seal. The regulation cited on its page is Portaria Inmetro nº 258/2020 (Inmetro Ordinance No. 258/2020), and the same page points to the public lookup of registered products at registro.inmetro.gov.br/consulta.

Some auto parts fall into this category. Inmetro's report on motorcycle and similar vehicle components (Inmetro Ordinance No. 71/2022) mentions drive chains, sprocket sets and exhaust systems, states that obtaining registration is a condition for making these components available in the Brazilian market, and mentions complaints about imports and sales of transmission kits without the seal and without a registration number.

For the master record, this becomes an attribute: the Inmetro registration number, filled in for items whose regulation requires it and checked against the public lookup when the item is created and when the supplier changes. Which parts are covered must be checked in each product's regulation.

What about the description, NCM and other classification codes?

The description follows the PDM (Padrão Descritivo de Materiais, the Brazilian term for a descriptive material standard): noun, qualifier and attributes in the order defined for the family. Brand, part number and fitment stay out of the name, as explained in the guide on how to write material descriptions.

NCM classification (for materials and products), CEST and UNSPSC are item attributes to check during cleansing. NCM is the Mercosur Common Nomenclature, used in Brazil for goods; CEST is a Brazilian tax code; NBS is the Brazilian Nomenclature of Services. NCM and CEST are decided by the tax team, not by whoever creates the item, and the NCM review of the material master shows how to organize that check. An installation or engine reconditioning service belongs in the service master, classified under NBS, not as a material with a service description.

What you will find in the master and how to handle it

Situation found in the masterHow to identify itWhat to doBatch or decision (by whom)
Same part number stored with hyphens, dots, spaces, leading zeros or O instead of zeroCompare normalized codes (uppercase, no separators) and test O/0 and I/1 swapsMerge into one item after checking the issuer's catalog; keep the formats as item codesBatch to find; technical catalog decides the merge
One material per supplier code for the same partSame manufacturer and same technical attributes with different supplier codesKeep one item and link the supplier codes with source "supplier"Purchasing decides with the technical catalog team
Interchange written in the description or notesSearch for "similar", "equivalent", "fits", "replaces" in text fieldsMove to the cross-reference table with type, source and approverBatch to extract; technical catalog approves
Superseded part number created as a new unlinked itemTwo items with the same fitment, one with no recent purchasesLink old to new as "superseded", block purchases of the old one, keep it searchableTechnical catalog decides; purchasing and sales decide on stock
Vehicle fitment inside the descriptionDescriptions containing manufacturer, model, year or engineExtract into the fitment table and rewrite the description using the PDMBatch to extract; checked by technical catalog and sales
Side and position missing or abbreviated in textSide and position abbreviations at the end of descriptions; pairs with no distinctionCreate position and side attributes with a closed listBatch, with a sample checked by the technical catalog team
Set, pair and each mixed upSame item with different units in purchasing and sales; price inconsistent with quantityDefine the item unit, quantity per package and conversionPurchasing and sales decide
Kit created as a single partDescriptions with "kit", "w/ sensor", "complete set" and no component listCreate the kit as its own item with a list of linked componentsTechnical catalog decides
Used part sharing the new part's codeDismantling items with no condition or origin attributeSeparate code, condition attribute and origin fieldsSales decides with purchasing
Component subject to Inmetro registration with no number recordedFamilies named in the product regulation with the field emptyFill in the number and check it in Inmetro's public lookupPurchasing and quality decide, checked against the regulation

Hypothetical example: the brake pad recorded four times

Hypothetical example. Codes, brands, vehicle manufacturer and model are fictitious.

Before: four materials, all with stock.

  • 10234: "BRAKE PAD FRT ALFA 1.6 19/22 MTX45022AB1"
  • 10871: "BRK PAD FRONT ALFA/BETA FRX-7781"
  • 11502: "PAD FRT. ALFA BK3305 SIMILAR"
  • 11930: "BRAKE PAD FRT ALFA W/ SENSOR PST-K90"

After cleansing (applying the rule of one item per interchangeable part approved by the technical catalog team):

  • Item 10234: PAD, BRAKE, FRONT, with position (front), unit (set) and dimension attributes as defined in the attribute dictionary.
  • Codes linked to the item: MTX45022-AB1 (source: vehicle manufacturer), FRX-7781 (aftermarket manufacturer "Manufacturer X"), BK-3305 (aftermarket manufacturer "Manufacturer B"). Items 10871 and 11502 are blocked for purchasing, with their stock transferred to 10234.
  • Cross-reference table: FRX-7781 and BK-3305 recorded as "equal" to MTX45022-AB1, with source and approver.
  • Item 11930 becomes FRONT BRAKE PAD KIT WITH SENSOR, with a component list: 1 set of item 10234 and 1 wear sensor (its own item).
  • Fitment table for item 10234: Manufacturer A, Model Alfa, trims and model years 2019 to 2022, 1.6 engine, front position; plus the Model Beta rows confirmed by the manufacturer.

Now the salesperson searches by vehicle or by any of the three codes and finds the same item, with a single stock balance. Purchasing sees the real consumption of the part. And the kit is no longer confused with the single pad set.

Where to start

  1. Write the rules: what an item is, which interchange types exist, who approves each type and how superseded codes are handled.
  2. Build the structure before cleaning: item code table with source, cross-reference table, fitment table, and the position, side, condition and Inmetro registration attributes.
  3. Extract, in batch, the codes, interchanges and fitments currently sitting in descriptions and notes.
  4. Normalize the codes and generate the list of duplicate candidates; the technical catalog team decides on merges, starting with the highest turnover families.
  5. Rewrite descriptions using the PDM and complete the attributes by family.
  6. Send NCM, CEST and service items (NBS) to the tax team for review.
  7. Block the creation of new items without a prior search by normalized code and the item code table.

Frequently asked questions

Can I use the vehicle manufacturer's part number as the internal code?

It is not recommended. The part number belongs to its issuer and can be superseded, and the same part will have other codes from aftermarket manufacturers and suppliers. The internal code should be stable, and the part number goes in the item code table with source "vehicle manufacturer".

Does an interchange work both ways?

It depends on the type. An "equal" interchange works in both directions. "Replaces with conditions" and "superseded" have a direction: the new code covers the old one, but the old one may not cover every application of the new one. That is why each row records source code, target code and type.

What should I do when a supplier sends a code with different formatting?

Compare using the normalized code (uppercase, no hyphens, dots, slashes or spaces) and keep the received format as a supplier code linked to the item. If the match depends on swapping O for zero or removing leading zeros, check the manufacturer's catalog before linking.

Should vehicle fitment go in the description so salespeople can find the part?

No. Salespeople find the part through a vehicle search that reads the fitment table. In the description, fitment gets truncated, cannot be filtered and has to be rewritten every time the manufacturer extends the vehicle list.

Can a used part share the code of the new part?

The recommendation is no. With its own code and a condition attribute, the fact that the part is used appears on the order, the invoice and the offer. For dismantling companies in Brazil, Law No. 12,977/2014 requires stating clearly at the time of sale that the part is used and recording parts intended for replacement in the database set up by the law.

Do engine reconditioning or installation services belong in the material master?

No. They belong in the service master, with NBS classification and their own unit. Mixing services into the parts master disrupts inventory, tax and purchasing analysis.

How 4MDG can help

4MDG carries out master data cleansing by reviewing the catalog item by item: it removes duplicates using a similarity score and survivorship rules, with every merge recorded, standardizes descriptions using the PDM, classifies items under NCM and UNSPSC, normalizes units of measure and packaging, and enriches technical attributes before the ERP load. In its work with manufacturing companies, this includes family taxonomy, attribute templates, rule based descriptions and batch deduplication. If you want to see where your auto parts master stands, request a free catalog assessment or talk to the team.

Note: the sections on Brazilian Law No. 12,977/2014 and Inmetro registration are an operational reading for master data purposes, not legal advice. Check each product's regulation and, if in doubt, consult your company's legal or tax team.

Sources

Have a question or want to talk about this?

Talk to a 4MDG specialist — we reply through the channel you prefer.

The international code is added when you save.