TecDoc is one of the most important data resources in the independent automotive aftermarket. It is also frequently misunderstood.
Some businesses treat TecDoc as though it should contain everything required to run their e-commerce catalogue.
It shouldn’t.
What TecDoc is extremely good at
TecDoc provides standardised automotive aftermarket product and vehicle application information.
It can support areas such as:
- Article numbers
- Manufacturer information
- Generic article types
- Technical criteria
- OE references
- Vehicle relationships
- Product descriptions
- Images
- Cross references
This makes it enormously valuable for catalogue enrichment and fitment.
But TecDoc does not know everything about your business.
TecDoc does not know your commercial reality
Commercial data
Supplier cost, rebates, selling price, minimum margin and marketplace fees.
Stock data
Your actual availability, supplier stock, lead times and preferred sourcing rules.
Operational data
Warehouse location, parcel dimensions, dispatch method and carrier restrictions.
Channel strategy
Which products should be sold on which marketplace and under what commercial rules.
Those things belong in your own systems.
A better architecture
Manufacturer layer
What is the product?
Manufacturer, MPN, technical specifications, OE references, dimensions and imagery.
Vehicle layer
What does it fit?
Structured vehicle linkage and fitment data.
Supplier layer
How can we buy it?
Supplier, supplier SKU, purchase cost, stock, lead time and MOQ.
Commercial layer
How should we sell it?
Selling price, margin, marketplace fees, promotions and channel eligibility.
Operational layer
How do we fulfil it?
Warehouse bin, dropship flag, parcel size, carrier rules and shipping restrictions.
Channel layer
How should each marketplace receive it?
Titles, categories, item specifics, attributes and marketplace-specific content.
Why this distinction matters
Imagine a supplier changes a price.
That should not require somebody to manually edit eBay, Amazon, Shopify, Google and an internal spreadsheet.
The supplier cost should change once.
Your pricing logic should then decide what happens downstream.
Spreadsheets are not necessarily the problem
Spreadsheets are excellent for investigation, review, bulk editing and data cleansing.
The problem appears when the spreadsheet becomes the only place holding critical business logic.
If supplier stock = 0 → mark unavailable
If margin falls below threshold → flag for pricing review
If weight exceeds carrier limit → remove incompatible shipping method
If fitment changes → rebuild application data
Those rules should eventually become explicit system logic rather than something stored in someone’s memory.
TecDoc is part of the solution
TecDoc can be an extremely valuable part of an automotive e-commerce architecture.
But the strongest implementations combine it with the retailer’s own commercial, supplier and operational data.
What is this part, and what does it fit?
Your product master must also answer:
Should we sell it, at what price, through which channels, and how will we fulfil it?
Building a better automotive product architecture?
Sprint 7 Group helps businesses connect automotive catalogue data with pricing, stock, marketplaces and operations.
Talk to Sprint 7