Write the claim a shopper can test
Compatibility is a match between two specific things. Start with the item you sell, then name the compatible model, generation, connector, size, or operating system you checked. Put known exclusions beside it. Use the manufacturer’s technical record for the thing your accessory connects to, and save its URL and check date.
| Weak copy | Useful copy |
|---|---|
| Fits the Atlas line | Fictional example: Fits Atlas 11 Model A24. Does not fit Atlas 11 Model A22. |
| Works with USB-C laptops | Requires USB-C DisplayPort Alt Mode. It does not add video output to a port without it. |
| Universal replacement part | Fits product codes AB-14 and AB-16 only. Measure the 14 mm opening before ordering. |
The Atlas and product-code examples show a writing pattern only; they are not claims about a product sold by Cuebase or a merchant.
Bounded real-world check
Connector labels alone do not establish a display promise. Apple’s technical specifications for MacBook Air (M1, 2020) say it supports one external display up to 6K at 60Hz. A USB-C accessory page therefore cannot promise that this model drives two native external displays solely because it has USB-C. Check the target device’s official specification, the accessory’s documented limits, and the exact configuration before making that claim.
Use a table, not a paragraph
Put the answer near the buy button and repeat it in the description. A table prevents the common mistake of mixing a compatible model with a nearby revision.
| Checked item | Result | Evidence | Checked |
|---|---|---|---|
| Exact model and generation | Compatible / not compatible / unknown | Manufacturer page or measured specification | YYYY-MM-DD |
| Port, mount, or physical dimension | State the required condition | Product specification | YYYY-MM-DD |
| Variant or region | Name the selected variant | Variant record or manual | YYYY-MM-DD |
“Unknown” is useful. It stops a sales claim from outrunning the evidence.
Use Catalog Readiness before publishing
In Cuebase, open a product in Catalog Readiness and review its rule breakdown and draft suggestions. Choose Generate improvements only when you want suggestions, then check every model, exclusion, and source against the official record. Nothing is written until you choose Apply all to Shopify. The review step is where a precise compatibility table belongs; Cuebase does not prove hardware compatibility for you.
Where Shopify helps, and where it does not
Shopify variants let a merchant represent product options, but a variant title does not prove compatibility. Put the supported-model list in page copy, a metafield, or a rendered specification. Keep the same model names on the product page and sales-channel feed. Google’s product structured-data guidance covers offer details such as price and availability; it cannot repair a vague compatibility table.
Publishing check
- Open the official manufacturer page for the target model.
- Record the model identifier, relevant dimensions or port, URL, and date.
- State the compatible case, then known exclusions.
- Open the storefront variant a shopper will buy and confirm the text is visible.
For a broader catalog review, start with Shopify product data for AI, then use a first AI visibility baseline and what to count in an AI answer to keep later checks comparable.
Download the worksheet
Use the blank worksheet to assign an owner, keep the proof link, and set a recheck date.
Download the compatibility worksheet (CSV). When the page, variant, and evidence agree, start your free catalog scan.