If you sell replacement parts on Shopify, you’ve probably hit the same wall every parts merchant eventually hits: your product catalog is organized by SKU, but your shoppers are organized by what they own. They don’t know they need a “HPA300-CMB filter.” They know they have a Honeywell HPA300 air purifier, and something in it is making noise.
Compatibility data — the mapping between a part and the equipment models it fits — is what closes that gap. Done right, it’s the difference between a shopper confidently adding to cart and a shopper closing the tab. Done wrong, it’s a spreadsheet that no one can keep up to date.
This guide covers the practical side of setting it up: how to structure the data, how to load it into Shopify, and how to use it on the storefront to actually move the needle on conversion.
What “compatibility data” actually means
Compatibility data is a structured record that says “this part fits this equipment.” At minimum, each record has:
- A part identifier (SKU, product ID, or handle)
- A brand (Honeywell, Whirlpool, Stihl, John Deere)
- A model (HPA300, WRF555SDFZ, MS 271, 5075E)
That’s the skeleton. Good compatibility data adds more — category tags, model aliases, confidence scores, product images, direct variant links — but you can start with just part + brand + model and get most of the value.
A practical example. A single filter part with SKU HPA300-CMB might fit 14 different Honeywell purifier models. In a well-structured compatibility dataset, that’s 14 separate records — one per compatible model. The part stays the same; each row links it to a different brand/model combination.
Why separate rows? Because shoppers don’t search “HPA300 or HPA200 or HPA100” — they search their specific model. You need to match each model independently, and that only works if each model is its own row.
What compatibility data isn’t
Not the same as Shopify product variants. Variants are for attributes of the same product (color, size, pack count). Compatibility data is about which external equipment a product fits. You need both. A single variant can be compatible with hundreds of models.
Not a category taxonomy. “HEPA filters” is a category. “Fits Honeywell HPA300” is compatibility. Both are useful, but compatibility is what actually answers a shopper’s question.
Three places compatibility data earns its keep
Compatibility data by itself is just a database. What makes it valuable is surfacing it where shoppers make decisions. There are three places that matter.
1. On the product page
When a shopper lands on a specific part, the question they’re asking is “does this fit my equipment?” A compatibility checker on the product page — where they enter their brand and model and see a verified fit — is the single highest-leverage surface. It converts browsers into buyers at exactly the moment they’re deciding.
2. On a dedicated finder page
Some shoppers don’t start on a product page. They start with “what do I need for my Honeywell HPA300?” A finder page lets them enter their equipment and see every compatible part in your catalog. This is how you sell adjacent parts — not just the filter they came for, but the pre-filter, the belt, the consumables.
3. On collection pages
When a shopper lands on your “All Filters” collection, they see 300 products. If they’ve already told you their model (via a cookie or a saved setting), the collection can filter to just what fits. Instead of “300 filters, pick one,” they see “12 filters for your machine.”
The data itself isn’t the product. The surfaces where shoppers use it are the product.
Setting up the data structure
Before you load anything into Shopify, you need to decide on a data structure. Here’s the minimum viable schema:
- SKU — the part identifier in your Shopify catalog
- Part name — a human-readable description
- Category — “Filter,” “Belt,” “Pump,” etc.
- Brand — the equipment manufacturer
- Model — the specific equipment model
- Model alias (optional) — alternate names/codes for the same model
One row per part + brand + model combination.
Optional but recommended if you can swing it:
- Product variant ID — the exact Shopify variant this compatibility row points to (enables direct add-to-cart)
- Confidence level — “Verified” (you’ve confirmed it fits), “Likely” (probable based on specs), “Unverified” (user-submitted, not confirmed)
- Notes — any caveat (“fits but requires adapter X”)
A compatibility record for a single part that fits 10 equipment models = 10 rows. A catalog of 500 parts with average 20 compatible models each = 10,000 rows. You can see how this scales fast — which is why you need software to manage it.
How to actually get the data into Shopify
There are three paths to loading compatibility data, each with tradeoffs.
Path 1 — CSV upload
Works if you already have the data in a spreadsheet. Every compatibility tool worth installing supports CSV import. The key is matching your column headers to the tool’s expected schema. If you’re starting from a manufacturer spec sheet (PDF) or a catalog you’ve been maintaining manually, CSV export is your starting point.
Path 2 — Manual entry
Works for small catalogs or when you’re adding one-off records. Time-consuming for anything serious, but essential for filling gaps. Every tool should support manual entry — avoid any tool that forces you to re-import a full CSV just to add one record.
Path 3 — AI-assisted mapping
A newer option. Some tools (including ModelMatch) can read your existing Shopify product catalog and infer compatibility from product names, descriptions, and variants. You review each suggestion before it saves, which keeps quality up while cutting manual work dramatically. This is the fastest path if you have a catalog that already describes compatibility in product titles or descriptions.
Which path to use
Honestly, most merchants end up using all three. CSV for the bulk historical load, AI for filling gaps on existing products, manual for the handful of one-offs that don’t fit either workflow.
Data quality matters more than data quantity
It’s tempting to load everything you can find — every spec sheet, every catalog PDF, every forum post — and call it compatibility data. Don’t. A smaller, verified dataset beats a larger unverified one, because shoppers lose trust the moment they buy a “compatible” part that doesn’t fit. Start with what you know is right. Expand from there.
The merchant experience
Once the data is in, the question is how you manage it. This is where most compatibility tools fail — they nail the storefront side and ship a merchant admin that looks like it was built in 2015.
A serious merchant admin should give you:
- Search and filter across all records by any field
- Bulk edit so you can fix whole categories at once
- Duplicate detection so you’re not maintaining two records for the same part-model combination
- Coverage insights that show which parts are under-mapped
- No-match tracking so you see what shoppers searched for that didn’t find anything
That last one — no-match tracking — is the most underrated. Your shoppers tell you exactly what compatibility records you’re missing, just by searching. A good tool captures those searches and turns them into a prioritized list of records to add.
The storefront experience
Three things to get right on the storefront.
Speed. Compatibility lookups need to return in under a second. Anything slower and shoppers abandon. Every tool worth using runs against a real database — not a JSON file embedded in your theme.
Clarity. The verdict needs to be obvious. Verified fit? Show a clear green checkmark. Likely fit? Show a softer badge with an explanation. No fit? Show it clearly and suggest what does fit. Ambiguity kills conversion.
Context. If a shopper has told you their model once, every product they visit should already know it. Collection pages should auto-filter. Product pages should auto-check. The shopper shouldn’t have to re-enter their model on every page.
What not to do
A few patterns I see merchants get wrong.
Don’t hide compatibility in the product description. Buried text doesn’t convert. If a shopper has to read 400 words to figure out if it fits, they’ve already left.
Don’t only show compatibility after add-to-cart. By then the decision is made. The compatibility check needs to live before the add-to-cart button, in an obvious place on the page.
Don’t treat compatibility as a static document. Your catalog changes. Your shoppers’ models change. If your compatibility data is a CSV you re-upload every six months, you’re always behind. Use tools that sync continuously.
FAQ
Can I use Shopify metafields for compatibility data?
Technically yes. Practically no. Metafields don’t scale to tens of thousands of cross-references, they’re painful to manage, and they don’t surface cleanly on the storefront without custom theme work. Every serious compatibility tool uses its own data layer precisely because metafields hit these limits fast.
Do I need compatibility data if I only sell 100 products?
If those 100 products each fit multiple equipment models, yes. Compatibility data isn’t about catalog size — it’s about shopper confidence. A 50-product catalog with strong compatibility data outconverts a 500-product catalog with none.
How long does it take to set up?
Depends entirely on where your data lives now. If it’s in a manufacturer’s spec sheet or an existing spreadsheet, expect a few hours to structure and import. If you’re starting from scratch, budget a week or two to build a meaningful initial dataset. AI-assisted mapping can cut this significantly.
What if a part is compatible with a specific range of years of a model?
Add each year as a separate row, or use model aliases (HPA300-2018, HPA300-2019, etc.). Range expressions in compatibility data tend to break shopper search — most shoppers search by a single year, not a range.
Closing
Compatibility data is one of those operational details that quietly determines whether your parts store thrives or leaks sales. The merchants who get it right aren’t the ones with the biggest budgets — they’re the ones who treat compatibility as a product surface, not a database export.
Start with a clear data structure. Load from your best-available source. Put the data in front of shoppers on product pages, in a finder, and on collections. Keep it updated.
And if you’d rather not build all of this yourself — well, that’s why ModelMatch exists.