Skip to main content
Factory DirectGlobal ShippingStrict QC
Tangma Craftsman | Body Kits, LED Headlights & Performance Auto Parts
EmailWhatsAppGet Quote

Tangma Automotive Compatibility Knowledge Graph V2

Last updated: July 28, 2026

Tangma Knowledge Center · Version 2

Automotive Compatibility Knowledge Graph

A VIN-first navigation system connecting vehicle generations, retrofit parts, OEM references, electronics, installation evidence and compatibility risks across five major brands.

5brand hubs
90published compatibility nodes
5system pathways
Tangma Compatibility CoreVIN · Production Date
OEM · Options · Market
Evidence · Coding

Brand Nodes

Start with the vehicle brand, then move from model generation to part system and workshop evidence.

20 nodes

BMW

Families: 3 Series G20 · 5 Series G30/G60 · X3 G01 · X5 G05 · X7 G07

Headlights, tail lights, body conversions, screens and coding

21 nodes

Mercedes-Benz

Families: C-Class W205/W206 · E-Class W213 · S-Class W222/W223 · GLE/GLS

Digital lighting, facelift conversions, ambient/electronic systems

22 nodes

Audi

Families: A4 B9 · A6 C7/C8 · Q5 FY · Q7 4M · Q8 4M8

LED/Matrix lighting, body upgrades, MMI and module matching

20 nodes

Porsche

Families: Cayenne 958/9Y0 · Macan 95B · Panamera 971 · 911 991/992

Lighting, PCM screens, bumper systems and sensor integration

7 nodes

Toyota

Families: Land Cruiser LC200/LC250/LC300 · Prado · Camry · RAV4

Headlights, body kits, multimedia and market-specific fitment

Universal Compatibility Decision Path

Identify
VIN, production month, market and body variant
Match
OEM references, option codes and revision suffixes
Map
Connectors, modules, brackets, sensors and harnesses
Prove
Installation photos, scans, video and packing evidence
Validate
Coding, calibration, beam/gap checks and road test

Cross-Brand Relationship Matrix

BrandModel-generation nodeTypical system edgesRequired verification
BMW3 Series G20 · 5 Series G30/G60 · X3 G01 · X5 G05 · X7 G07Headlights, tail lights, body conversions, screens and codingVIN + production date + OEM label + connector/module evidence + workshop validation
Mercedes-BenzC-Class W205/W206 · E-Class W213 · S-Class W222/W223 · GLE/GLSDigital lighting, facelift conversions, ambient/electronic systemsVIN + production date + OEM label + connector/module evidence + workshop validation
AudiA4 B9 · A6 C7/C8 · Q5 FY · Q7 4M · Q8 4M8LED/Matrix lighting, body upgrades, MMI and module matchingVIN + production date + OEM label + connector/module evidence + workshop validation
PorscheCayenne 958/9Y0 · Macan 95B · Panamera 971 · 911 991/992Lighting, PCM screens, bumper systems and sensor integrationVIN + production date + OEM label + connector/module evidence + workshop validation
ToyotaLand Cruiser LC200/LC250/LC300 · Prado · Camry · RAV4Headlights, body kits, multimedia and market-specific fitmentVIN + production date + OEM label + connector/module evidence + workshop validation

System Nodes

These pathways connect related retrofit problems across brands, so the same verification logic can be reused without assuming the parts themselves are interchangeable.

90 linked pages

Fitment & Workshop Evidence

VIN, OEM references, connectors, installation evidence, warnings and validation

All Published Vehicle Nodes

Open a brand to browse every compatibility guide currently connected to Knowledge Graph V2.

BMW — 20 compatibility nodes

Open BMW Compatibility Hub →

Mercedes-Benz — 21 compatibility nodes

Open Mercedes-Benz Compatibility Hub →

Audi — 22 compatibility nodes

Open Audi Compatibility Hub →

Porsche — 20 compatibility nodes

Open Porsche Compatibility Hub →

Toyota — 7 compatibility nodes

Open Toyota Compatibility Hub →

Evidence and Risk Edges

EdgeEvidence requiredFailure prevented
Vehicle → PartVIN, production date, body code, marketWrong generation or regional specification
Part → OEMFull label, suffix, supersession and left/right pairVisually similar but incompatible revision
Part → ElectronicsConnector pinout, modules, software and coding planFault messages or missing functions
Part → BodyMounts, brackets, gaps and adjacent-panel trial fitPoor alignment and irreversible paintwork
Installation → ValidationDiagnostic scan, calibration, beam/water/road testUnsafe or incomplete delivery
Compatibility warning: A relationship in this graph means the subjects share a verification pathway. It does not mean parts are interchangeable across brands, generations, markets or option packages.

V2 Entity Relationship Layers

V2 connects each vehicle node to four evidence entities. These links guide research and purchasing; they do not claim that a product fits without VIN-level verification.

Entity 01

Product Association

Connect the vehicle and retrofit system to candidate product records, revision notes, included components and written fitment confirmation.

Entity 02

OEM Reference

Connect original labels, part-number suffixes, supersession history, market specification and left/right matched sets.

Entity 03

Installation Evidence

Connect trial-fit photos, connector images, packing videos, workshop scans, measurements and calibration reports.

Entity 04

Diagnostic Validation

Connect coding, parameterization, fault scans, beam/gap checks, water tests, sleep current and road-test acceptance.

Brand-to-Product Association

Source entityRelationshipTarget entityRequired proof
Vehicle / VINhas candidateProduct revisionSupplier confirmation tied to production data
Product revisioncross-referencesOEM label / geometryFull number, suffix, market and physical interface
Product revisionsupported byInstallation evidenceSame-generation photos, video, scans and measurements
Installationvalidated byDiagnostic resultFault-free scan, coding/calibration and functional test

FAQ

What is the Tangma Automotive Compatibility Knowledge Graph?

It is a structured navigation layer connecting brands, vehicle generations, retrofit systems, OEM evidence and workshop validation steps.

Does the graph confirm that a product fits my vehicle?

No. It helps collect the evidence needed for a fitment decision; final confirmation must use the VIN, production data, option codes and physical/electronic checks.

Why connect different brands through system nodes?

Lighting, body conversion, infotainment and ADAS retrofits share verification methods even though the actual parts and coding are brand-specific.

How will V1 expand?

Future versions can add deeper model-year nodes, OEM-reference edges, product links, installation evidence and diagnostic relationships.

Product Association

This guide is linked to the vehicle product collection. A related listing is not automatic proof of fitment. Match the chassis, production date, original equipment, connectors, modules and included accessories before ordering.

Send vehicle evidence for product-level verification.

OEM Reference

Reference itemRequired evidence
Original part numberClear photo of the complete OEM label, including left/right suffix and revision.
Module or controllerModule label, software/hardware index and connector photo where applicable.
Vehicle production splitVIN or production month, market version and original option level.

Status: OEM numbers are verification inputs, not universal interchange promises. Do not order from a partial number or model name alone.

Installation Evidence

  • Before: photograph the vehicle, original part, labels, connectors, mounting points and dashboard warnings.
  • During: record dry-fit alignment, harness routing, adapter/module placement and any coding or calibration step.
  • After: provide installed photos plus a function video covering lighting, sensors, cameras, controls and warning messages.
  • Stop and re-check if a connector, bracket, gap, function or included accessory differs from the approved evidence.
Item added to cart.
0 items - $0.00