Automotive Aftermarket — DACH

A clean catalog. TecDoc-linked. Ready for workshops, partners, and AI.

Duplicates, missing OE links, half-filled attributes — gone. Your catalog cleaned, TecDoc-aligned, and queryable through one API.

Standards & catalogs we work with

  • TecDoc
  • OE-Nrn.
  • KBA
  • EAN/GTIN
  • ETIM
  • GS1
  • OpenAPI

Five pains we keep seeing

The data problems behind most aftermarket frustrations.

Every wholesaler with 50,000+ SKUs we've talked to runs into some version of these five. They look like operational complaints; they're actually data problems.

Pain 1

Duplicate product records

Wasted inventory positions, search confusion, an inflated catalog. Same part exists three times under different SKUs because someone re-imported a supplier feed.

Pain 2

Missing TecDoc vehicle links

Workshop searches the part by KBA, finds nothing — and orders elsewhere. Your part exists, the link doesn't.

Pain 3

Incomplete product attributes

Filters miss your part. Wrong customer pick. Returns. The attribute table is half-empty.

Pain 4

OE-number errors

A wrong cross-reference ships a wrong part. Returns, liability, lost trust. Manual cross-reference review doesn't scale past a few thousand SKUs.

Pain 5

No API for partners or AI procurement

Workshops want real-time stock and prices. Buying groups want consistent feeds. AI procurement agents (the new buyer) need a clean, governed endpoint. Spreadsheets and FTP don't cut it anymore.

How it composes

From source data to a TecDoc-aligned API.

Meshbase runs alongside your ERP, PIM, warehouse, or custom catalog — no schema migration. It ingests your data, matches against TecDoc/OE, fills the gaps, and exposes the cleaned graph through one governed surface.

Sources
Import
Dedupe
TecDoc-match
Enrich
API

Sources → Import → Dedupe → TecDoc-match → Enrich → API.

What it looks like

TecDoc-aligned data, your governance.

Once your catalog is in, partners and AI agents query it through the same governed surface — typed, audited, rate-limited, and policy-checked.

01

REST

Plain HTTP under `/rest/v1`. Lowest-friction option for workshops, marketplaces, and dealer systems on legacy stacks.

bash

bashbash
# Find brake-pads compatible with a vehicle (KBA-Nr. 0588 / 595 — VW Golf VII)
curl -H "Authorization: Bearer $KEY" \
"https://api.meshbase.ai/rest/v1/parts?vehicleKba=0588:595&category=brake-pad" \
| jq '.data[] | {sku, oeRefs, brand, fitNotes}'
02

GraphQL

Federated GraphQL across catalog, inventory, and service. Best when partners need precise field selection and typed cross-domain queries.

graphql

graphqlgraphql
query CompatibleParts($vehicleKba: String!, $category: String!) {
parts(vehicleKba: $vehicleKba, category: $category, first: 25) {
  nodes {
    id
    sku
    oeRefs           # OE numbers (TecDoc cross-references)
    brand { name }
    tecdocId
    fitNotes         # vehicle-specific notes (engine code, year range)
    attributes       # cleaned, filled-in attributes
  }
}
}
03

MCP

Model Context Protocol — AI procurement agents call your catalog as a typed tool, under the same caller-governance and audit as a human partner.

json

jsonjson
{
"tool": "find_compatible_parts",
"arguments": {
  "vehicleKba": "0588:595",
  "category": "brake-pad",
  "limit": 25
}
}

Two sides, one platform

Whether you have parts data or need it.

Most aftermarket players are both. Meshbase splits providers and subscribers where it counts (governance, billing) and unites them where it helps (data model, API surface).

01 · If you have data

You're a wholesaler, distributor, or parts manufacturer. Your catalog is an asset — make it usable instead of a liability.

  • Connect ERP / PIM / warehouse exports / CSV / FTP / APIs
  • Dedup on SKU, EAN, MPN+brand with TecDoc validation
  • Match parts against TecDoc vehicles, KBA numbers, and OE cross-references
  • Govern partner and AI access via API plans, caller profiles, and audit
Pilot as a provider

02 · If you need data

You're a workshop platform, marketplace, dealer system, or AI procurement agent. Subscribe to verified provider data without scraping or bespoke integrations.

  • Marketplace of TecDoc-aligned providers
  • REST · SDK · CLI · MCP — pick what fits your stack
  • Streaming + webhook updates for catalog and price changes
  • One bill across multiple providers, governed quotas
Browse the catalog

Aftermarket FAQ

Industry-specific questions we hear most.

DACH-first, Automechanika-ready

Bring a sample. We'll show you the dedup result by next week.

Email, contact form, or LinkedIn. We respond within one business day and won't waste your time with a generic deck.