Import Fitment Data

You can bulk-import fitment data for multiple products at once by uploading a spreadsheet or an ACES XML file directly in the Convermax app.

Where to find the Import

In the Convermax app, open the Import Fitments page in one of these ways:

• In Fitment Editor, click the Import button in the Products section.
• In Integrations, open the Custom Fitment Data card and click Upload a file (shown when Convermax can add files to the source).

The page lists the columns your store’s fitment fields need and has a Download template button.

1. Destination: choose where the fitments go.
   • Product metafields or Convermax database, whichever storage your Fitment Editor uses, saves them as editor fitments that you can check and edit product by product in the Fitment Editor. Choose the import mode on this step too.
   • Fitment files saves the file as is and reads it again on every reindex, so use it for files you keep updating. A file with the same name replaces the earlier one; the Custom Fitment Data card lists the saved files. Rows match products by SKU or handle (or your store’s own key column, which the page names). On Shopify, use the first variant’s SKU unless your store has variant fitments; a product with fitments in its metafields ignores fitment files unless your store merges fitment sources, and Review warns about such products. A blank required vehicle column only warns here: after a filled vehicle field, a blank one fits every value, but a blank before any filled field (for example, a blank Year) makes the row match no vehicle.
2. Upload: choose a file, then click Review import. For Fitment files, you can also click Save without review to save the original file directly; the save is listed in History, and the file applies from the next reindex. For the Fitment Editor you can choose several .csv, .txt, .xlsx, or .xml files at once; they are reviewed and imported together. A file can be up to 100 MB with up to 5 million rows; split a larger file and import the parts one by one.
3. Review: the file is checked in the background, with its progress on the page; you can leave the page and come back. Review saves nothing. Check how many products and fitments were found, which columns are used and which are left out (fitment files do not read Brand, Excluded, or Fitment columns), vehicles missing from your vehicle list, and the rows that will be skipped (the page shows the first 10; download the CSV for all of them). Click Import (Save file for fitment files, Connect folder when you review a folder) to apply it.
4. Done: the import runs in the background too. See the results and which rows were skipped. Fitment files apply from the next reindex.

In Custom Fitment Data, click Review next to a file to check only that file from the connected source, or Review files to check the whole source. Individual file reviews are listed separately in History.

The History tab lists every file and folder reviewed or saved in the last 12 months: its status, destination, who reviewed and imported it, and the review and import results, including failed runs. Click View review to open a completed review and its available reports. Reports are kept for 12 months; uploaded files are kept for 21 days. Import is available only while the original file and the data needed for import are still available, and the file hasn’t already been imported.

File format

Supported formats: .csv, .txt, .xls, .xlsx, ACES .xml, and .zip archives of .csv, .txt, .xlsx, and .xml files (with lowercase extensions). Fitment files take the same formats except .xls.

Each row represents one fitment entry for one product. A product can have multiple rows — one per fitment. Column names are matched ignoring case, spaces, dashes, and underscores; columns the import doesn’t use are left out.

ACES files need no columns: each application’s part number is matched to a product SKU. In Fitment files, a part applies to a product whose SKU joins the AAIA brand ID and the part number ({BrandID}_{Part}, {BrandID}-{Part}, {BrandID}|{Part}, ds_{BrandID}_{Part}, or {BrandID}{Part}), or whose part number matches and whose brand is the part’s AAIA brand: on Shopify the SKU and the vendor, on BigCommerce the MPN and the brand.

Product identification

Each row must identify the product using one of the following:

Column	Description
sku (or Variant SKU, or Part number)	Product SKU.
handle	Shopify product handle. Used when sku is not provided.
id	Product ID, as in a Fitment Editor export. Used before sku and handle.
vendor or brand_name	Narrows down the match when multiple products share the same SKU or handle.

Note

id, sku, or handle must be present. sku takes precedence over handle, but when a row has a handle, a Variant SKU or Part number column is ignored, so products without a SKU still match by handle. Fitment files ignore id.

Fitment data

Typically the required vehicle columns are Year, Make, Model. Additional columns such as Submodel, Engine, Bed, Body, Drive, etc. may also be supported depending on your fitment configuration. Vehicle columns also accept VCdb-style names such as year_list, MakeName, ModelName, SubModelName, BodyTypeName, and EngineLiter. A blank optional column means the part fits every value of that field.

• Year accepts a year (2019), a range (2015-2020), an open range (2015-UP, 2015+, or 2015-), or a comma-separated list of these.
• Model can list several models separated by commas, not slashes (Civic, Accord); each becomes its own fitment.

Notes

You can attach a note to a fitment row by adding a Notes column with any text value. Notes are displayed alongside the fitment entry and can be used to provide additional context such as installation instructions, compatibility remarks, or part-specific details.

Example with notes:

sku	Year	Make	Model	Submodel	Notes
BRK-2200	2020	Ford	F-150	XLT	Front axle only
BRK-2200	2020	Ford	F-150	Lariat	Front axle only
BRK-2200	2021	Ford	F-150	XLT	Requires adapter kit AK-100
EXH-3400	2019	Chevrolet	Camaro	SS	Driver side; 3-inch piping
EXH-3400	2020	Chevrolet	Camaro	SS

Excluded fitment

To exclude a fitment or override an existing one, set the Excluded column to Yes, True, or 1 for that row. Fitment files ignore this column.

Exclude a fitment:

sku	Year	Make	Model	Excluded
BRK-2200	2020	Ford	F-150	True

Update a fitment (exclude the old entry, add a replacement with a Submodel):

sku	Year	Make	Model	Submodel	Excluded
BRK-2200	2020	Ford	F-150
BRK-2200	2020	Ford	F-150	XLT	True

Universal Fit

Some products are designed to fit all vehicles regardless of Year, Make, or Model. To mark a product as Universal Fit, add a row for that product with the Universal column set to Yes, True, or 1. Vehicle columns are not required for universal fit rows.

Universal and vehicle-specific products can be mixed in the same file. A single product can even have both universal and vehicle-specific fitment rows if needed.

Example file with universal and vehicle-specific products:

sku	Year	Make	Model	Submodel	Universal
BRK-2200	2020	Ford	F-150	XLT
BRK-2200	2021	Ford	F-150	XLT
BRK-2200	2022	Ford	F-150	Lariat
WHL-5500					Yes
EXH-3400	2019	Chevrolet	Camaro
EXH-3400	2020	Chevrolet	Camaro
CLN-7700					Yes
SUS-9100	2023	Toyota	Tacoma	SR5

In this example:

• BRK-2200, EXH-3400, and SUS-9100 have vehicle-specific fitments.
• WHL-5500 and CLN-7700 are marked as Universal Fit and will appear in search results for any vehicle.

Import mode

Pick how the import applies fitments. It only affects products listed in the file — other products are left untouched.

Mode	What it does
Add	Adds the imported fitments on top of the product’s current fitments. Nothing is removed.
Replace	Removes the product’s existing editor fitments, then adds the imported ones. Fitments from external sources are kept.
Replace and override external fitment	Same as Replace, and additionally excludes the product’s external fitments so they no longer apply. Use this when the imported fitments should fully replace the product’s existing ones.