> For the complete documentation index, see [llms.txt](https://docs.globo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.globo.io/vehicle-finder/import-vehicle-data.md).

# Import vehicle data

Upload a spreadsheet mapping vehicles to the products and variants that fit them, so the Vehicle Finder form can match shoppers to the right products.

## What this does

The Vehicle Finder form only knows which products fit which vehicles because of the data you import here — without it, the form has nothing to match against, no matter how well it's configured. For example, a spreadsheet row mapping "2019 Honda Civic" to product "Brake Pad Set - Front" is what lets a shopper who selects 2019 / Honda / Civic in the form see that brake pad set (and only vehicle-compatible products) in their results, instead of your full unfiltered catalog.

Each import is additive by default: uploading a file with new or updated vehicle mappings adds to what's already on your products without wiping out vehicle data that was already there, so you can grow your fitment data incrementally as your catalog changes. If you'd rather have a new file take over completely, you can choose to replace earlier file imports instead.

## Prerequisites

* [Vehicle Finder form](/vehicle-finder/set-up-vehicle-finder-form.md) is set up, or you're following its setup guide.

You can also drive fitment from **product metafields** (parallel `custom.vehicles_*` lists). That workflow is still supported — see [Configure YMM metafield values](/vehicle-finder/configure-ymm-metafield-values.md). To add or fix a few vehicles by hand instead of uploading a file, use [Vehicle Manager](/vehicle-finder/manage-vehicles.md).

## Steps

1. In the app, go to **Vehicle Finder**.
2. Click **Upload file** — in the **Vehicle Manager** section, or in step 1 of the setup guide. The **Import vehicles** dialog opens.
3. Click **Download sample Excel** to get a template showing the expected columns: the Product ID, SKU or Variant ID, plus Year, Make, and Model. Extra columns become vehicle attributes you can turn into [form fields](/vehicle-finder/configure-vehicle-finder-fields.md).
4. Fill in your vehicle data based on the sample. You can also upload a TecDoc-style sheet (for example `Marke`, `Modell`, `Motor`, `Jahr ab`) — those headers map to Make, Model, Engine, and Year. **Product Ids** may be Shopify product ids, variant ids, or SKUs. Put **one id per row** (repeat the vehicle), or list several in one cell — each on its own line, or separated by `~`.
5. Drag your file into the upload area, or click it to choose a file. Only **.xlsx** and **.csv** files are accepted, up to **100 MB** — split a larger file into smaller ones and upload them one after another. To pick a different file, click **Replace file**.
6. Decide how the new file combines with earlier uploads:
   * Leave **Replace previous file import data** unchecked (default) to **merge** — the new rows are added to the fitments from earlier uploads.
   * Check it to **replace** — fitments from earlier file imports are removed before this file is imported. Vehicles and fitments you added manually in Vehicle Manager are kept either way.
7. Click **Upload file** at the bottom of the dialog to start. A message confirms the file was uploaded and the import has been queued.

![Vehicle Finder — Import vehicles dialog](https://2009335375-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKmtdB4I84W3J8hc91H4S%2Fuploads%2Fgit-blob-a0712bf88d4f5e3adc720a635f26a486dc89b2cb%2Fymm-upload-modal.png?alt=media)

The app imports the vehicles in the background and adds them to the matching products and variants. When it's done, the vehicles appear in [Vehicle Manager](/vehicle-finder/manage-vehicles.md), where the **Vehicles**, **Fitments**, and **Products covered** counts show what was imported.

## Remove all vehicle data

To start over, click **Clear all vehicles** in the **Vehicle Manager** section (or in step 1 of the setup guide) and confirm. This removes every vehicle and product fitment from Vehicle Manager and clears vehicle compatibility data on those products in search. It can't be undone.

To remove only some vehicles, delete them in [Vehicle Manager](/vehicle-finder/manage-vehicles.md#delete-vehicles) instead.

## Product metafield (combined) — optional

You can also store multiple fitment rows in **one product or variant metafield** as JSON. This is an **extra** option alongside:

* Parallel `custom.vehicles_*` lists — [Configure YMM metafield values](/vehicle-finder/configure-ymm-metafield-values.md)
* Spreadsheet import on this page

It does not replace those methods. When several sources exist on the same product, the app merges and deduplicates fitment rows.

### Supported metafield keys

Any namespace, with one of these keys (case-insensitive): `vehicles`, `vehicle_fitments`, `ymm`, `ymm_vehicles`, `fitments`.

Example: `custom.vehicles`.

### JSON

Metafield type **JSON** (or multi-line text containing a JSON array of objects). Keys on each object become vehicle attributes (dynamic — not limited to year/make/model):

```json
[
  {"year":"2025","make":"Toyota","model":"Camry"},
  {"year":"2025","make":"Toyota","model":"Vios","engine":"1.5"}
]
```

After you save the metafield in Shopify, re-sync products (or wait for the product update webhook) so Vehicle Finder can use the new rows.

## Related pages

* [Set up Vehicle Finder form](/vehicle-finder/set-up-vehicle-finder-form.md)
* [Manage vehicles in Vehicle Manager](/vehicle-finder/manage-vehicles.md)
* [Configure Vehicle Finder fields](/vehicle-finder/configure-vehicle-finder-fields.md)