English简体中文
Talk to us
Data service

Auto parts data as a service

Data domains

What the catalogue contains

Six master data domains, all normalised and cross-linked to each other.

Vehicle data

Brand hierarchy, series, model, model year, displacement, version, engine, body and emission fields.

  • car_brand / parent_id / level
  • car_series · car_model_name · model_year
  • engine_description · fuel_type · body_form

Parts master data

Part number, part name, standard name, category, vehicle brand and parts brand in one record.

  • parts_no · parts_name
  • standard_name_id · category_id
  • brand_id · car_brand_id · unit

OE & interchange codes

Multiple OE numbers per part, optionally scoped to a vehicle brand or a parts brand.

  • general_code
  • Scope: car_brand_id
  • Scope: brand_id

Fitment

Applicability stored per vehicle model with an optional sales area, keeping fitment precise.

  • parts_id ↔ car_model_id
  • area_id (sales region)
  • remark · isEnabled

Category taxonomy

A maintained tree that spans automotive systems and part families, available for both store and parts catalogues.

  • name · name_en
  • parent_id · sort
  • type: group / engine / OEM

Standard names & aliases

A normalised naming layer so the same physical part is not described five different ways.

  • standard_name · unit
  • alias_name
  • category_id
Coverage

Current coverage

Read live from the production parts data service.

Counts are read live from the parts data service of the current tenant.

Delivery

How you receive the data

Start with the website, graduate to the API, scale with file feeds.

Web lookup

The pages on this site — vehicle, parts and OE search with fitment detail.

REST API

JSON endpoints for direct integration into your own catalogue or ERP.

File export

One-off or scheduled CSV / Excel exports for the exact scope you need.

Managed feed

A recurring delivery over SFTP or object storage, with change tracking.

Governance

How the data is kept reliable

Every record carries enabled / disabled state and soft-delete auditing, and is continuously maintained.

Enabled / disabled state

Records can be retired without losing history; disabled records never surface publicly.

Soft delete auditing

Deletions keep timestamps, so a remover can be traced and undone.

Consistent references

Foreign keys between part, vehicle, fitment and code are enforced in the model.

Continuous maintenance

The catalogue is extended and corrected as new vehicles and part families are onboarded.

Tell us what you need

Share the scope — vehicle set, part families, languages and delivery format — and we will size it for you.

Browse the endpointsContact sales