Fitment Sync
Setup, file formats, and answers to the questions that come up most. If something here does not cover your case, email us — a real person replies.
Open the app and press Sync. This reads your products so that part numbers in your fitment file can be matched to the right product. Run it again whenever you add or change products in bulk — individual changes are picked up automatically.
Go to Fitment import, choose your file, and press Preview. Nothing is written yet. You will see how many fitments will be added, how many updated, and which rows in the file could not be read and why. When it looks right, press Import.
In your theme editor, open the page where shoppers should pick their vehicle — your home page or a collection page works well — then choose Add block → Apps → Fitment Search and save.
Then open your product template and add Fitment Table as a block inside the product information section. This is what shows shoppers whether the part fits the vehicle they selected.
Nothing appears on the storefront? The vehicle dropdown only lists vehicles you actually have fitment data for. If you have not imported yet, the widget will say so rather than showing an empty list.
Column names are detected automatically. If a guess is wrong, you can correct it on the import screen before anything is written.
sku,year,make,model,submodel,brand,position,qty
BRM-ROTOR-F,2015-2019,Honda,Accord,EX-L,Brembo,Front,2
BIL-5100-FR,2020,Toyota,4Runner,TRD,Bilstein,Front,2| Column | Required | Notes |
|---|---|---|
sku | Yes | Also accepted: part number, part no, mpn, item |
make | Yes | Vehicle manufacturer |
model | Yes | |
year | Yes* | A single year, or a range such as 2015-2019 |
year_from / year_to | Yes* | Alternative to a single year column |
submodel | No | Trim or grade. Also accepted: trim, series |
engine | No | |
drive | No | 2WD, 4WD, AWD. Also accepted: drive type, drivetrain |
body | No | Crew Cab, 4-door. Also accepted: body type, body style, cab |
Parts that fit every vehicle — write ALL in year, make and model together, like OIL-5W30,ALL,ALL,ALL. Oil, wiper fluid, tools and cleaners then appear for every search. Leaving those columns blank is still an error, so a supplier file with a missing column cannot silently turn a part into a universal one. | ||
brand | No | Part brand. Needed for brand-scoped replacement |
position | No | Front, Rear, Left, Right |
qty | No | Defaults to 1 |
* Either a year column or a year_from / year_to pair.
Any other column is ignored — a supplier file with warehouse,
price or notes columns is read the same as one without
them. If a required column is missing from the file entirely, rows are not
silently dropped: Preview reports each one with the reason and
the line number, so you can see exactly what to fix.
A single import takes up to 20 MB and 500,000 fitments. Both are checked, and the one you reach first stops the import with a message telling you which it was.
A row with a year range counts once per model year. One line reading
2015-2019 becomes five fitments, so a file can hold far more
fitments than it has lines.
This is a limit per file, not per store. A full catalogue is imported as two or more files. Split by brand — that is how supplier files usually arrive anyway — and import the parts one after another. Each part is added to what you already have; nothing is replaced unless you choose one of the two replace modes below.
There is no limit on how many times you import, and no charge per import. What counts against your plan is how many fitments you are storing — the number you see on the home screen at any time.
That distinction matters. One fitment is one part on one vehicle in one position,
and a year range such as 2015-2019 becomes five fitments, so the
number of lines in a supplier file does not tell you how much of your plan it will
use. If a supplier widens the vehicle coverage of parts you already stock, your
usage goes up even though you added no products. Press Preview
before importing: it says how many fitments the file adds, and how many you would
be holding afterwards.
| Mode | What it does | Use it when |
|---|---|---|
| Add only | Adds new fitments. Existing fitments are left untouched. | Adding a new brand or a new product line. |
| Add and update | Adds new fitments and updates existing ones. Nothing is deleted. | A supplier sends corrections plus new applications. |
| Replace one brand | Deletes that brand's existing fitment, then imports the file. Every other brand is untouched. | A supplier reissues their whole catalog. |
| Replace the parts in this file | For every part number in the file, deletes that part's existing fitment, then imports the file. Parts not in the file are untouched, whatever brand they are. | A supplier corrects a few parts and sends the full vehicle list for each of them. Send the whole list, not a partial one — vehicles left out of the file are removed from those parts. |
There is deliberately no "replace everything" mode. A single mistaken import should never be able to erase fitment data you built up across many suppliers.
Most often the SKU in the file does not match any product in your store. Open the import screen and look at the rejected rows — each one shows its line number and the reason. Press Download these rows to keep them; they are shown rather than stored, and choosing the same file and pressing Preview reports them again without writing anything.
If the SKU is correct but was added to your store recently, press Sync once and import again.
The dropdown only lists vehicles that at least one of your products fits. If a
vehicle is missing, no imported row references it. Check the spelling of the make
and model in your file — Chevy and Chevrolet are treated
as different makes.
Yes, for the most recent one. Open Fitment data and press Undo. It puts back exactly what that import changed: rows it added are removed, rows it overwrote go back to their previous values, and rows it deleted come back. It is kept only for the last import, and only until you import, add or remove anything else — after that there is nothing to go back to.
One exception: a very large import does not keep an undo copy. If more than 200,000 rows would be added, changed or removed, the copy is skipped and the Undo button does not appear. Download a CSV of what is stored before a change that big.
Preview every import before accepting it as well. That screen exists precisely so mistakes are caught before anything is written.
If Undo is no longer available, Fitment data also lists what is stored, brand by brand, and lets you remove one brand — or everything — before importing again. Rows that arrived without a brand are listed there too, so a file with no brand column can still be taken back out.
The same screen downloads what is stored as a CSV, using the columns the import reads. Take a copy before a large change, edit it in a spreadsheet, or keep it if you ever stop using the app.
One thing to watch if you edit in Excel: a part number made only of digits,
such as 0912345, loses its leading zero when Excel saves the file.
Format that column as Text before saving. If it does happen,
the import will not match those rows to a product and will list them as rows
it could not read, so nothing is written incorrectly.
Your fitment data is never deleted, and your storefront keeps working — shoppers can still search and product pages still show fitment.
To switch back to Free from inside the app, you need to be within the free plan first. If you hold more than 1,000 fitments, the app tells you how many to remove and does not switch you until you have. That is deliberate: dropping you onto a plan you cannot import into would leave you stuck.
If a subscription lapses on Shopify's side instead — a card that stops working, say — nothing is removed and the storefront carries on exactly as before. You simply cannot import again until you are back under the limit or back on Pro.
Search results are returned from an index built for this purpose, so they stay responsive as your fitment catalog grows. The widget loads after your page content and does not block rendering.
Yes, and it happens automatically. Their selection is kept in their own browser, so on their next visit the vehicle is already chosen and product pages immediately show whether each part fits. The selection is sent to Fitment Sync while they use the picker — that is how the app looks up the makes for a year, the models for a make, and the parts that fit — but it is never stored in our database and never used for advertising, profiling or tracking.
Read access to your product catalog, and permission to set up an app proxy. Nothing else. The app cannot read orders, customers or payment information.
On the install screen Shopify describes the second one as
“View and edit store data → Edit Online Store”,
which sounds broader than it is. It is how Shopify labels the permission to
answer requests on one path under your own domain
(/apps/fitment) — that is what makes the vehicle search work
from your storefront instead of from someone else’s. It does not let the
app change your theme, your pages, your products, or anything else in your
store. Those need separate permissions, and this app does not ask for them.
See the privacy policy for the full detail.
One import takes up to 20 MB and 500,000 fitments. Split the file — by brand is easiest — and import each part in turn. Parts are added to what you already have, so the end result is the same as one large file.
Remember that a year range counts once per year: a line reading
2015-2019 is five fitments. A file with many ranges reaches that
limit while still looking small.
No, and that is deliberate. A download is written as it is read, so it never holds your whole catalogue in memory. The cost of that is that a download still in progress would stop at any rows removed while it runs, leaving you with a copy that looks complete but is not.
So while a download is being prepared, removing rows is refused with a message. Wait for the download to finish and try again. This matters most in the one case where it would hurt: taking a copy before clearing your data.
Email support@fitmentsync.com. Include your shop domain and, if the question is about an import, the file name — it makes the answer much faster.