Español
English
Twitter
LinkedIn
YouTube
  • NEO code®
  • SOLUTIONS
    • Improve assortment
    • Improve search engine
    • Improve product data
    • Consultancy
  • PRICES
  • ABOUT US
    • About Us
    • Team
    • Blog
    • Partners
    • Contact
BLOG-FD - 1000 million cross

More than 1 billion equivalences!

4 de June de 2024adminfactorydataFactory Data

All manufacturers and distributors who have their own brand need to create equivalences between their products and part numbers of their competitors, suppliers or major brands. For this reason, they usually create and maintain huge matrices of equivalences of this type in spreadsheets:

 

xRef matrix

If we take into account that there are brands with extensive ranges with more than 20,000 numbers, that there are hundreds of brands on the market, and that in addition, there are OE, OEM part numbers, commercial part numbers, different ranges (premium range, rebuilt, etc.), different formats for writing the part number (beginning with or without 0), etc. etc., How many equivalences do we need to define to express all these relationships that exist in the market between part numbers?

So let’s simplify the data that actually exists in reality, to try to quickly calculate an approximate figure of the equivalences that should be defined:

  • 200 main parts types (alternators, turbochargers, brake discs…) x 1000 part numbers in each range x 10 OE part numbers x 2 (commercial codifications, ranges, etc.) x 35 brands, we have: 200 x 1000 x 2 x 35 x (2 x 35) = 980,000,000 IAM equivalences and 200 x 1000 x 2 x 35 x 10 OEs = 140,000,000 OE equivalences

  • 3000 types of NON-main parts (Depressor rotor, Steering shaft, Oil pressure sensor…) x 200 part numbers in the range x 5 OE part numbers x 1.2 (commercial codifications, ranges, etc.) x 15 brands, we have: 3000 x 200 x 1.2 x 15 x (1.2 x 15) = 194,400,000 IAM equivalences and 3000 x 200 x 1.2 x 15 x 5 OEs = 54,000,000 OE equivalences

  • 8000 types of secondary parts (Reflector for rear/clearance light, Fog light bracket, Oil filler pipe, …) x 50 part numbers in the range x 2 OE part numbers x 1 (commercial codifications, ranges, etc.) x 5 brands, we have: 8000 x 50 x 1.0 x 5 x (1.0 x 5) = 10,000,000 IAM equivalences and 8000 x 50 x 1.0 x 5 x 2 OEs = 4,000,000 OE equivalences

Even if we make a very low estimate, in total we would be talking about handling: 1,382,400,000 equivalences (1,184,400,000 IAM-IAM and 198,000,000 IAM-OE). Can anyone imagine what this volume of equivalences represents to store it, detect errors but, above all, perform continuous maintenance?

However, if we had a universal code, such as NEO code®, which relates all the part numbers on the market to each other using a main code, all these equivalence relationships would be simplified to only 32,600,000 equivalences, 42 times less than trying to define equivalences between all the part number on the market!

Graph all vs all

What we should ask ourselves is: Do we really want or will we be able to manage and minimize the potential errors in the millions of equivalences that must be generated to relate all the existing part numbers between all the products and brands on the market?

Well, if you feel that the path the industry is taking is not the right one, and you want a much simpler solution to analyse the aftermarket and/or manage your product data, please contact us and we will help you.

 

By Joan Cabós
CEO & founder

Tags: Auto parts data, Automotive aftermarket, Clusterization, cross-list, NEO code

Related Articles

The challenge of the century!

18 de May de 2022adminfactorydata

What do you need to set up your own B2B store?

3 de February de 2023adminfactorydata

More solutions than in any catalogue!

17 de December de 2024adminfactorydata
  • English
    • Español

Recent Posts

  • Real-time strategies to minimize lost sales
  • Your potential sales
  • GAPs discovery
  • Products of the year 2024
  • Lost sales

Recent Comments

    Archives

    • May 2025
    • April 2025
    • March 2025
    • February 2025
    • January 2025
    • December 2024
    • October 2024
    • September 2024
    • August 2024
    • July 2024
    • June 2024
    • May 2024
    • April 2024
    • March 2024
    • February 2024
    • January 2024
    • November 2023
    • October 2023
    • September 2023
    • June 2023
    • May 2023
    • April 2023
    • March 2023
    • February 2023
    • January 2023
    • November 2022
    • October 2022
    • September 2022
    • August 2022
    • June 2022
    • May 2022
    • March 2022
    • February 2022
    • December 2021
    • November 2021
    • October 2021
    • September 2021
    • July 2021
    • June 2021
    • May 2021
    • April 2021
    • March 2021
    • February 2021
    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • July 2020
    • May 2020
    • April 2020
    • February 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • June 2019
    • May 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • July 2018
    • May 2018
    • April 2018
    • March 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017

    Categories

    • Factory Data
    • NEO
    • PFcode
    • Web Services

    SOLUTIONS

    • Improve assortment
    • Improve search engine
    • Improve product data

    PRICES

    ABOUT US

    • About us
    • Team
    • Blog
    • Contact
    • Partners

    Subscribe to our Newsletter!

    @2025 Factory Data. All rights reserved    |    Notice of Privacy  |  Terms of use