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 - Tecdoc cross

Tecdoc, more equivalences? No thanks!

8 de June de 2021adminfactorydataFactory Data

Getting equivalences between any existing reference number on the market and the reference number associated with the products of our supplier(s) has been and continues to be a highly prized target in the auto parts sector.

The existence of distinct codifications created by the thousands of suppliers and manufacturers who act in the market is making it ever more necessary to define more and more equivalences, so our products can be located in whatever way possible.

The maximum exponent of this madness can be found in Tecdoc, the most frequently used electronic catalogue in the market. It uses a database which combines the catalogue information from multiple manufacturers in the sector, all (most) with the intention of adding and adding more and more equivalences.

DB_mess_graph

In Tecdoc, when we open the product sheet to view the defined equivalences, only the equivalences against vehicle manufacturers are shown, but internally there are dozens more equivalences defined against aftermarket reference numbers.

Thanks to these other internal equivalences, we can find, for example, results between two IAM reference numbers, but paying a high price, imprecision.

Because, what is the point of finding a result between one aftermarket reference nubmer, which could be associated with more than 10 different OE/OEM reference numbers, with another aftermarket reference number which could also be associated with multiple OE/OEM reference numbers? The probability of error multiplies when, in the search, we use IAM reference numbers to find IAM reference numbers.

DB_mess_table

But even while being aware of this big problem, the market pushes everyone to establish these equivalences between aftermarket reference numbers, to add and add more and more equivalences, the whole world wants more equivalences, all the electronic catalogues highlight the millions of equivalences they have, the more, the better!

So we, at Factory Data, say: The fewer, the better!

DB_mess_disruptive-ENG

At Factory Data we also access these millions of equivalences, but we only consider the ones which are accurate. We are continually decoding the information from the market to learn what each reference number corresponds to, what exact product(s) on the market each reference number is associated with.

Thanks to our data clusterization technology, we are capable of proposing equivalences between any two suppliers, with no need to explicitly define the equivalence between them.

For us, most of the equivalences defined in the market, are really just noise generating imprecision in the data!

If you want to get away from the noise of the market, we put our technological platform at your disposal, to help you face the challenges of data with the most advanced technology.

 

By Joan Cabós
CEO & founder

Tags: Clusterization, cross-list, Electronic Catalogues, Interoperability, Parts catalogs, Tecdoc

Related Articles

Limitations of the TecDoc ktype

6 de September de 2021adminfactorydata

On-line shops: Performance optimization

19 de November de 2018adminfactorydata

Data interoperability

18 de April de 2023adminfactorydata
  • 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