Should compatibility details live on every Shopify product page?
A shopper has found a product that looks right. They have one question left: will it work with what I already own?
If the answer only lives in a collection filter, they may never see it. They might arrive from search, a product link, an email, or a shopping assistant. They might also clear the filter before opening the product.
For parts, accessories, refill systems, cases, cables, and products with model-specific versions, compatibility belongs on the product page too.
The filter helps someone find a shortlist. The product page helps them decide whether to buy.
Filters narrow the catalogue. Product pages answer the decision.
Shopify describes filters as a way to narrow products on collection and search-result pages. Product metafields, on the other hand, can display product-specific details such as specifications, part numbers, and disclosures on the product page.
Those are different jobs.
Say you sell replacement water filters. A collection filter might let someone choose their appliance brand. That is useful when they have twenty products to sort through.
But once they open a product, they still need a plain answer:
- Fits AquaHome 200 and 300 models
- Does not fit AquaHome Mini
- Replace every six months
- Requires the standard cartridge housing
The shopper should not need to go back to the collection, remember which filter they chose, and infer the answer from a selected filter value.
Put the decisive fact where the purchase happens.
A filter is not a reliable place to keep essential information
Filters have limits by design. Shopify allows up to 25 storefront filters. Each filter can show up to 100 values to customers. Some metafield values can also be left out because of unique-value limits.
Shopify also hides filters for collections with more than 5,000 products and searches with more than 100,000 results.
This does not make filters bad. It means they are a discovery tool, not the only record of a product fact.
Shopify’s guidance on ecommerce filters makes a similar distinction: filters should reflect how shoppers make purchase decisions. A catalogue may contain many attributes that are useful internally but would make poor filters, such as SKU data, tags, or overly detailed specifications.
Compatibility often needs both forms:
- A simple filter for the broad buying choice, such as vehicle make or device family
- Clear product-page copy for the exact compatibility decision
Do not turn every model number into a filter value just because it exists in your product data.
Put the answer near the buying controls
The best placement depends on how risky a wrong purchase would be.
For a small, obvious compatibility rule, place a short statement near the product title, variant picker, or add-to-cart button.
For example:
Compatibility: Fits Model X and Model Y. Not compatible with Model Z.
For a longer list, show the summary near the buying controls and link to a fuller compatibility section or pop-up.
Shopify supports page-reference pop-ups and product disclosures for this sort of supporting content. They are useful when the product needs installation notes, a long supported-model list, or a warning that should not crowd the main purchase area.
Keep the first answer short. The buyer should not have to open a tab to learn whether the item fits.
A useful pattern is:
- Fits: the supported models or systems
- Does not fit: common near-misses
- You also need: adapters, housings, batteries, or other required parts
- Check before buying: the identifier the customer should compare, such as connector type or model year
The “does not fit” line can prevent more confusion than a long list of supported products. It names the mistake people are most likely to make.
Model compatibility at the right level
Do not store a product-level compatibility statement if the answer changes with the selected variant.
For example, a phone case product may have separate variants for different phone models. A cable may have USB-C and Lightning variants. A bike component may fit different axle standards depending on the selected size.
In those cases, the compatibility detail belongs at the variant level.
Shopify supports both product metafield filters and variant metafield filters. Its Liquid objects also expose both `product.metafields` and `variant.metafields` for storefront output.
That gives you a practical split:
- Use a product metafield when every variant fits the same thing.
- Use a variant metafield when a customer’s selected option changes the answer.
The page should then update the compatibility message when the shopper changes the variant. If that is not possible in your current theme, state the relationship directly in the option names and compatibility table.
A vague dropdown called “Size” is not enough if each size maps to a different machine or connector. Call the options what they are.
Use structured data as a check, not a substitute for copy
Google recommends product structured data on individual product pages, rather than product-list or category pages. Its product documentation describes detailed shopping information that can appear through product-page structured data, including price, availability, shipping, returns, reviews, and apparel sizing.
That is another reason to treat each product page as the home for product-specific facts.
But structured data is not a replacement for visible compatibility copy. A buyer needs to read the answer on the page. Your customer service team needs to find it. A shopping assistant or search system needs a clear page to read.
Keep the visible wording simple, then make sure your theme’s product data is accurate too.
Google also recommends combining product-page structured data with a Google Merchant Center feed for stronger product-data coverage. That is worth considering if you already maintain a feed. It does not remove the need for a readable product page.
Check one product in under a minute
Open a product page as if you have never seen the store before.
Then ask these questions:
- Can I tell what this product fits without returning to a collection?
- Can I see what it does not fit?
- If I change a variant, does the compatibility answer still make sense?
- Can I tell whether I need another part before buying?
- Is the answer visible before or close to the add-to-cart button?
If the answer is “the collection filter tells them,” the page needs work.
In Shopify admin, you can start by opening Settings → Custom data → Products and creating a compatibility metafield. Add a short, standardised value first. You can then connect that metafield to a theme block on the product template.
Use the same source of truth for the filter and the product-page display where you can. Otherwise, the filter may say one thing while the product copy says another.
Do not assume a catalogue read caught every product
We ran into a related problem while building our own `llms.txt` builder. Shopify’s `/products.json` endpoint returns no more than 250 products per page. A catalogue read can look complete while quietly missing the rest.
We handled pagination rather than treating the first page as the whole catalogue.
The same habit matters when you audit compatibility data. Do not spot-check ten popular products and conclude the job is done. Check whether your export, app, script, or internal process reaches every page of the catalogue.
Start with the product types where a wrong fit creates the most support work or returns. Then make the fields part of the product setup process for new items.
A collection filter can help shoppers find the right aisle. The product page should tell them whether the item in their hand is the right one.