WheelFitmentDB logo WheelFitmentDB
Developer Guide

Production SQL Schema for Automotive Wheel Fitment Data

Drop WheelFitmentDB directly into PostgreSQL or MySQL with clean column types, composite Year-Make-Model indexes, and an instant SQL query for cross-brand wheel interchange matching.

1. PostgreSQL DDL & Bulk Import (< 1 Second)

All 12 columns are UTF-8 encoded with zero null placeholders in core fitment fields:

CREATE TABLE vehicle_fitment (
  year             SMALLINT NOT NULL,
  make             VARCHAR(64) NOT NULL,
  model            VARCHAR(128) NOT NULL,
  trim             VARCHAR(64),
  pcd              VARCHAR(32) NOT NULL,
  center_bore      VARCHAR(32) NOT NULL,
  "offset"         VARCHAR(32),
  thread_size      VARCHAR(32),
  seat_type        VARCHAR(32) NOT NULL,
  hex_size         VARCHAR(16),
  confidence_level VARCHAR(16),
  last_updated     DATE
);

CREATE INDEX idx_fitment_ymm ON vehicle_fitment (year, make, model);
CREATE INDEX idx_fitment_pcd ON vehicle_fitment (pcd);

\copy vehicle_fitment FROM 'WheelFitmentDB_Master_2026_11.csv' WITH (FORMAT csv, HEADER true);
Ready to put this blueprint into production?
Download Production CSV & JSON ($47 / $89) →
POWERED BY WHEELFITMENTDB v2.6 · ONE-TIME OWNERSHIP

Building a wheel store, YMM filter, or automotive SaaS?

This page is powered by the WheelFitmentDB v2.6 Master Dataset — 12,902 OEM-verified vehicles (1992–2026, incl. 553 MY2026 models) in clean CSV & JSON. One-time purchase, zero API rate limits.