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.
Automotive Aftermarket — DACH
Duplicates, missing OE links, half-filled attributes — gone. Your catalog cleaned, TecDoc-aligned, and queryable through one API.
Standards & catalogs we work with
Five pains we keep seeing
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.
Wasted inventory positions, search confusion, an inflated catalog. Same part exists three times under different SKUs because someone re-imported a supplier feed.
Workshop searches the part by KBA, finds nothing — and orders elsewhere. Your part exists, the link doesn't.
Filters miss your part. Wrong customer pick. Returns. The attribute table is half-empty.
A wrong cross-reference ships a wrong part. Returns, liability, lost trust. Manual cross-reference review doesn't scale past a few thousand SKUs.
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
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.
What it looks like
Once your catalog is in, partners and AI agents query it through the same governed surface — typed, audited, rate-limited, and policy-checked.
Plain HTTP under `/rest/v1`. Lowest-friction option for workshops, marketplaces, and dealer systems on legacy stacks.
bash
# 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}'Federated GraphQL across catalog, inventory, and service. Best when partners need precise field selection and typed cross-domain queries.
graphql
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
}
}
}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
{
"tool": "find_compatible_parts",
"arguments": {
"vehicleKba": "0588:595",
"category": "brake-pad",
"limit": 25
}
}Two sides, one platform
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.
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.
Aftermarket FAQ
DACH-first, Automechanika-ready
Email, contact form, or LinkedIn. We respond within one business day and won't waste your time with a generic deck.