- TecDoc
- TecDoc is a data standard and catalogue for the independent aftermarket, operated by TecAlliance. It links vehicle types, parts manufacturers, articles, article types and cross references in one model — fed by the data the parts manufacturers themselves supply.
Why the standard exists
Hundreds of parts makers, thousands of distributors and tens of thousands of workshops work on the same vehicles. Without a shared description, every relationship between vehicle and part would have to be negotiated individually. The standard performs that translation and is therefore the infrastructure on which parts catalogues, workshop systems and online shops are built.
The building blocks
| Element | Meaning |
|---|---|
| Vehicle type (K-type) | A vehicle type with build period, engine and technical data |
| Parts manufacturer | The brand under which an article is offered |
| Article | The specific article of a parts maker with its article number |
| Article type | What kind of part it is — brand independent |
| Criteria | Technical attributes per article type, such as diameter or connector type |
| Linkage | Which article fits which vehicle type |
| Cross references | The associated OE numbers and other suppliers' numbers |
For a dismantler the last two elements matter most: through cross references an OE number leads to the article type and the vehicle application — exactly the data that makes a used-part listing findable.
Where the limits are
- It is supplier data, not OEM data. The content arises from what parts makers enter. What nobody supplies is not there.
- Coverage is uneven. Common wear parts are described very well, rare body and electronic parts considerably less so.
- Older vehicles thin out. The older the model line, the patchier the linkages — even though that is exactly where used parts are worth most.
- An assignment is a statement, not proof. A cross reference in one source is that source's claim. Only agreement across sources makes it dependable.
For businesses that want to connect
Anyone handing stock to marketplaces or workshop systems will sooner or later be asked for article type, criteria and vehicle application — precisely these fields. Holding them in your own stock is therefore not optional polish but the entry ticket. The technical side is covered in Connecting an API: when it pays off for dismantlers, how the fields get into stock in Part identification: from removed component to sellable record.
Operating case: bring OE stock into one shared data language
User story: As a new-parts wholesaler or dismantler, I want supplier lists and removed stock in the same search. An OE number should lead to article type, maker, supersessions, fitments and alternative manufacturer references, with visible gaps rather than invented links.
| Step | Response | Benefit |
|---|---|---|
| Cross-check OE | GET /parts/oe/{oeNumber} returns the normalised number, tapiGenArt, VDI identifiers and available part, fitment and supersession data | ERP and shop gain structured search and mapping fields |
| Find IAM alternatives | GET /parts/oe/{oeNumber}/aftermarket-references returns known maker and part-number pairs | Alternative new stock appears beside OE and used offers |
| Connect a catalogue | Your licensed TecDoc access or connector maps the TecDoc keys and content you require | Usage rights and data responsibility stay separate |
| Handle a gap | Empty or ambiguous responses become a review queue | No pretend-perfect vehicle linkage |
Measure it: Track hit rate by source, unclassified items, manual mapping time, time to publish and returns caused by a wrong reference. This shows where another catalogue licence pays and where the OE cross-check is sufficient.
Sources and legal references
Frequently asked
Is TecDoc the same as a vehicle manufacturer's catalogue?
No. It is a data model of the free market, fed by parts makers. The vehicle makers' catalogues are a separate, separately licensed world — see OEM: vehicle makers, suppliers and original-equipment quality.
What is a K-type number?
The identifier of a vehicle type in the data model. It describes a type with build period and engine, not an individual vehicle like the VIN.
Why is there no assignment for my older vehicle?
Because coverage decreases with the age of the model line. For such cases, assignment via the OE number across several sources is the better route.