Shopify Vehicle Parts Fitment Schema — Compatibility Structured Data for Auto Parts Stores

The Auto Parts AI Visibility Problem

Auto parts shopping generates some of the most precise, vehicle-specific queries in e-commerce: "front brake pads for 2018-2022 Honda Civic 1.5T FWD," "K&N air filter for 2020 Toyota Camry 2.5L LE," "OEM oil filter for 2022 Ford F-150 5.0 V8." These queries carry simultaneous filter requirements — year range, make, model, engine displacement, trim, and position — that are unresolvable without structured fitment data.

Schema.org has no dedicated "fitment" type, but its Product, Vehicle, and PropertyValue primitives are sufficient to express compatibility in a form AI agents can parse. The key is compatibleWith: a property on Product that accepts an array of Vehicle typed objects. Each Vehicle entry declares the year, make, model, trim, engine, fuel type, and drive configuration for a single compatible vehicle.

Without compatibleWith, an AI agent answering a fitment query has three options: refuse to confirm compatibility, caveat heavily ("check your vehicle manual"), or surface a competitor's listing that has structured fitment data. None of those outcomes benefit your store.

Auto parts query types requiring structured fitment data

Complete JSON-LD Example: Brake Pads with Three Compatible Vehicles

This is a realistic brake pad product (Brembo front brake pads) compatible with three Honda Civic configurations. Each compatibleWith entry is a fully specified Vehicle object. The additionalProperty block provides summary fitment attributes for agents that read property tables rather than traversing the full vehicle array:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Brembo P28056N Front Brake Pads — 2016-2021 Honda Civic",
  "description": "OE Replacement front disc brake pads for 2016-2021 Honda Civic 1.5T and 2.0L. Low-dust semi-metallic compound. Includes hardware kit.",
  "mpn": "P28056N",
  "gtin13": "0082736280567",
  "brand": {
    "@type": "Brand",
    "name": "Brembo"
  },
  "additionalProperty": [
    {
      "@type": "PropertyValue",
      "name": "Compatible Year Range",
      "value": "2016-2021"
    },
    {
      "@type": "PropertyValue",
      "name": "Compatible Make",
      "value": "Honda"
    },
    {
      "@type": "PropertyValue",
      "name": "Compatible Model",
      "value": "Civic"
    },
    {
      "@type": "PropertyValue",
      "name": "Compatible Engine",
      "value": "1.5L Turbocharged I4, 2.0L Naturally Aspirated I4"
    },
    {
      "@type": "PropertyValue",
      "name": "Compatible Trim",
      "value": "LX, Sport, EX, EX-L, Touring, Si"
    },
    {
      "@type": "PropertyValue",
      "name": "OEM Part Number",
      "value": "45022-TBA-A00"
    },
    {
      "@type": "PropertyValue",
      "name": "Position",
      "value": "Front"
    },
    {
      "@type": "PropertyValue",
      "name": "Drive Type",
      "value": "FWD"
    },
    {
      "@type": "PropertyValue",
      "name": "Part Type",
      "value": "Aftermarket"
    }
  ],
  "compatibleWith": [
    {
      "@type": "Vehicle",
      "name": "Honda Civic 2018 EX Sedan",
      "brand": { "@type": "Brand", "name": "Honda" },
      "model": "Civic",
      "vehicleModelDate": "2018",
      "vehicleConfiguration": "EX Sedan 1.5T",
      "driveWheelConfiguration": "https://schema.org/FrontWheelDriveConfiguration",
      "fuelType": "Gasoline",
      "vehicleTransmission": "CVT",
      "vehicleEngine": {
        "@type": "EngineSpecification",
        "engineDisplacement": {
          "@type": "QuantitativeValue",
          "value": 1.5,
          "unitCode": "LTR"
        },
        "engineType": "Turbocharged Inline-4",
        "fuelType": "Gasoline"
      }
    },
    {
      "@type": "Vehicle",
      "name": "Honda Civic 2019 Sport Hatchback",
      "brand": { "@type": "Brand", "name": "Honda" },
      "model": "Civic",
      "vehicleModelDate": "2019",
      "vehicleConfiguration": "Sport Hatchback 1.5T",
      "driveWheelConfiguration": "https://schema.org/FrontWheelDriveConfiguration",
      "fuelType": "Gasoline",
      "vehicleTransmission": "6-Speed Manual",
      "vehicleEngine": {
        "@type": "EngineSpecification",
        "engineDisplacement": {
          "@type": "QuantitativeValue",
          "value": 1.5,
          "unitCode": "LTR"
        },
        "engineType": "Turbocharged Inline-4",
        "fuelType": "Gasoline"
      }
    },
    {
      "@type": "Vehicle",
      "name": "Honda Civic 2021 LX Sedan",
      "brand": { "@type": "Brand", "name": "Honda" },
      "model": "Civic",
      "vehicleModelDate": "2021",
      "vehicleConfiguration": "LX Sedan 2.0",
      "driveWheelConfiguration": "https://schema.org/FrontWheelDriveConfiguration",
      "fuelType": "Gasoline",
      "vehicleTransmission": "CVT",
      "vehicleEngine": {
        "@type": "EngineSpecification",
        "engineDisplacement": {
          "@type": "QuantitativeValue",
          "value": 2.0,
          "unitCode": "LTR"
        },
        "engineType": "Naturally Aspirated Inline-4",
        "fuelType": "Gasoline"
      }
    }
  ],
  "offers": {
    "@type": "Offer",
    "price": "49.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition"
  }
}

Vehicle Schema Properties Reference

The Vehicle type (a subtype of Product in schema.org) provides structured fields for every dimension of fitment data that auto parts queries require. Use these on each object in your compatibleWith array:

driveWheelConfiguration enum values

EngineSpecification pattern

Use vehicleEngine with a nested EngineSpecification object whenever engine displacement is a fitment dimension — which it is for most filters, fuel systems, and intake/exhaust parts:

"vehicleEngine": {
  "@type": "EngineSpecification",
  "engineDisplacement": {
    "@type": "QuantitativeValue",
    "value": 2.5,
    "unitCode": "LTR"
  },
  "engineType": "Naturally Aspirated Inline-4",
  "fuelType": "Gasoline"
}

For diesel engines, set both fuelType: "Diesel" on the EngineSpecification and on the parent Vehicle object. For hybrid powertrains, use fuelType: "Hybrid" and add a separate vehicleEngine describing the combustion component if relevant to the part's fitment.

additionalProperty Fitment Reference Table

The additionalProperty array on the Product object carries summary-level fitment attributes. These complement the detailed Vehicle objects in compatibleWith — AI agents that read property tables rather than traversing nested arrays use these values to answer year/make/model summary queries rapidly:

Shopify Metafield Namespace for Fitment Data

Store fitment attributes in a dedicated fitment namespace. Use JSON list metafield types for multi-value attributes (makes, models) and single-line text for scalar values (position, OEM part number). Loop over compatible vehicles from a fitment.compatible_vehicles JSON list metafield — one object per vehicle:

Shopify Liquid template — full fitment JSON-LD

Gate on a product tag (auto-part) to avoid injecting Vehicle fitment schema on non-parts products. Loop over the fitment.compatible_vehicles JSON list to build the compatibleWith array. Handle the driveWheelConfiguration mapping from text shorthand to schema.org enum URLs within the loop:

{% if product.tags contains 'auto-part' %}
{% assign fitment = product.metafields.fitment %}
{% assign vehicles = fitment.compatible_vehicles.value %}

{% endif %}

Common Mistakes

1. Not including compatibleWith at all

The most damaging omission. Without compatibleWith, an AI agent answering "will these brake pads fit my 2019 Honda Civic EX?" has no machine-readable fitment signal to work with. Your part appears identical to a universal-fit product — or to a competitor's part that happens to be mentioned alongside a Civic in a review. Every auto parts product page that has fitment data must output that data in compatibleWith. Encoding it only in the product title ("2016-2022 Honda Civic Brake Pads") leaves AI agents unable to resolve structured fitment queries.

2. Using plain text in name instead of structured compatibleWith + additionalProperty

Titles like "Fits 2016-2022 Honda Civic / 2017-2021 Acura ILX Front Brake Pads" contain fitment information, but it is packed into an unstructured string with forward-slashes, em-dashes, and inconsistent delimiters that AI agents and parsers cannot reliably decompose. Structured data works precisely because the year is in vehicleModelDate, the make is in brand.name, and the model is in model — each in a declared typed field that requires no NLP to interpret.

3. Using vehicleModelDate as an integer instead of a string

Schema.org specifies vehicleModelDate as a Text value. The year must be a quoted string — "vehicleModelDate": "2019" — not an integer "vehicleModelDate": 2019. Structured data validators flag the integer form as a type error. For year ranges, use "2016-2021" as a single string value rather than separate minYear/maxYear fields, which are not part of the Vehicle schema.

4. Setting brand to the vehicle brand instead of the parts brand

The brand property on the root Product object belongs to the parts manufacturer — Brembo, ACDelco, K&N, Bosch, NGK. The vehicle manufacturer's brand (Honda, Toyota, Ford) belongs inside each Vehicle object in the compatibleWith array. Setting brand: Honda on an aftermarket brake pad signals that the part is a genuine Honda OEM part, misleading both AI agents and shoppers comparing OEM versus aftermarket options.

5. Omitting mpn

MPN (manufacturer part number) is the primary cross-store comparison key for auto parts. When a shopper asks an AI agent "compare prices for Brembo P28056N," the agent looks for mpn: "P28056N" to identify which product listings are the same part. Without mpn, your listing is invisible in part-number comparison queries — one of the highest-intent query types in auto parts shopping. SKU is insufficient; SKUs are store-specific and non-transferable. MPN is universally recognized across stores, catalogs, and fitment databases.

Common Mistakes — Quick Reference

Related Resources

• Shopify Schema Markup — Complete Guide
• E-commerce Product Schema Markup
• Product Weight & Dimensions Schema
• Shopify Product Specifications Schema
• CatalogScan Blog — AI Shopping Optimization