Skip to content
Interface language: English
Design / Signal

Will this accessory fit? Designing a product compatibility check

Design compatibility checks that identify both products, explain conditions and distinguish confirmed results from missing data.

Article language: English

Two people beside a table in front of a large circular structure overlooking a landscape.
In this article

In this purchase, the most important product is already on the customer's shelf. The shop is offering only an accessory. That changes the start of the journey: before choosing a colour, the customer must establish whether the item works with what they own. A beautiful photograph of a similar set cannot answer that question for them.

A compatibility check starts with two identifiable items and a defined relationship between them. One belongs to the customer; the other is in the catalogue. The design should show the basis for the result and any conditions limiting it. A green mark next to “fits” does not explain what was actually checked.

The owned model first, the accessory second

Imagine a fictional Port A4 photo album. The company sells extra pages and pockets for it. Older and newer series share the same trade name but have different fastening arrangements. The customer knows the name on the cover. Only the correct series marking identifies which pages can be offered.

Search should accept the information people actually have: a number on a label, a name from an order or a recognisable version marking. After selection, show the full name and distinguishing characteristic. If the system needs a particular series, do not treat “Port A4” alone as sufficient identification.

Apple identifies iPads by model number and a list of corresponding devices. Individual entries distinguish numbers and versions. This illustrates connecting a marking to a specific item; it does not prove that a general family name alone is enough to choose every accessory.

For the album, help could show where the marking is printed and a photograph of the distinguishing feature. Do not ask for the purchase year when you need the production year or series. An album bought in 2024 may have come from an earlier batch. The two questions look similar to a customer but supply different information for a compatibility result.

If the marking is illegible, retain a “model not recognised” result and offer a useful route to help. You can accept a label photograph if that is how the company works. Reporting a specific item for repair (in Polish) shows how to collect observations without demanding technical knowledge. Do not force someone to pick an arbitrary series just to continue.

Remembering a model between visits is a separate decision. A customer might have two albums from different series. Remembering the last selection is convenient if it remains visible which product is being checked and how to change it. Do not treat an old selection as indefinite confirmation of intent. When someone opens a link sent by another person, show whether the sender's model or the customer's saved choice was retained. If the two differ, ask for an explicit resolution before showing the result. Silently choosing one can provide a correct answer to the wrong question.

The customer's selected model should remain visible on the accessory page. A short catalogue strip might say “Checking for: Port A4, series P2” and offer a way to change it. It should not look like information about the item being purchased. Otherwise a reader might mistake the pocket's price for the price of the whole album or think they changed the offer's variant.

What the result means

Design states according to the information available in the catalogue. Four outcomes are useful in our example:

  • Confirmed compatible with the selected series. Page K2 is linked to album P2 in verified manufacturer data. The result should name both items and the scope of the match.
  • Conditionally compatible. The applicable manufacturer material specifies an additional component or particular version. Show the condition before purchase selection, together with whether the required component is included.
  • Incompatible. The data indicates that the selected page is not intended for this series. Explain the reason so the customer can change their choice, without a misleading attempt to force a match.
  • Not confirmed. The shop lacks sufficient data about this pair. Do not present this as confirmed incompatibility or as permission to buy qualified only by a small asterisk.

“Fits Port” is too broad if the brand or family includes several fastening arrangements. The result should say only what the source supports. If page dimensions were checked but the fastening method was not, the entire relationship cannot be called confirmed. The person responsible for the product establishes the technical basis; the designer translates it into understandable information.

Before a determination there may also be a loading state or a data retrieval error. Do not combine either with “not confirmed”, which describes catalogue knowledge. If the checking service does not respond, the shop does not yet know whether it has that relationship. Offer a retry and retain the selected pair. When someone quickly changes P1 to P2, an old response should not appear as the new result merely because it arrived later. During acceptance, check the order of visible responses with deliberately delayed retrieval.

Apple’s Pencil compatibility guide distinguishes accessory and device models. The Apple Pencil USB-C specifications give a system requirement, while Apple’s adapter description explains when an adapter is needed to pair and charge a first-generation Pencil. Your own catalogue likewise needs an explicit scope. We are not transferring its device list or recommendations to another product; we are using an example where compatibility is described for specific pairs.

A conditional result should not be a green confirmation with a hidden note. If a page requires a different insert, the customer should see that at the same place as the result. “You can use it after replacing the insert with W2; the insert is not included with this item” describes a different order from buying the page alone. Such a statement needs confirmation from the data owner, not a guess based on an illustration.

Aeneia conceptual photography

A result without data can lead to an enquiry that preserves both selected items. The employee should receive a question about page K2 and album P1, not a general “Does it fit?” The customer should not have to retype the markings. If the company confirms compatibility, establish how the catalogue will be updated so the next person does not have to ask the same question from the beginning.

“You may also like” supports a different decision from checking compatibility. A shared colour or frequent purchase in the same order does not confirm a technical relationship. Separate such recommendations from a list of items intended for the owned model. One card layout can support both tasks, but should clearly identify their basis.

Schema.org defines isAccessoryOrSparePartFor as a reference to a product for which the item is an accessory or spare part. This describes a relationship in data. The property records a declared relationship; its correctness requires a basis in confirmed product documentation. The data entry itself is not the result of a fit test.

Schema.org's isRelatedTo describes a general connection to another product or service. That broader relationship alone should not be labelled “fits”. The distinction is useful even without implementing structured data: a “related” field in an editorial panel does not necessarily mean “compatible with”.

A similar issue appears in visual product search (in Polish). An image can help identify candidates for checking, but cannot confirm a feature invisible in the photograph. If a function recognises an album by its cover, it may still need the series marking before confirming the result.

In Aeneia Design's product-information work, these relationships can be separated and communicated clearly. The design needs actual examples of pairs: compatible, conditional and lacking data. This lets a mock-up show a difficult result before it is populated with the full catalogue.

A changed selection must reach the cart

Checking the owned album is not the same as choosing a variant of the product being purchased (in Polish). If the customer changes a pocket's colour, compatibility may stay the same. If they change its fastening, the result may need to be checked again. Establish which characteristics actually affect the relationship and which concern appearance only.

In your own configurator, the customer builds a result through several choices. A guide to option dependencies in configurators (in Polish) discusses designing such a tool. Here the product already owned is an additional input condition. Do not remove it from the summary when moving to another accessory. If the new item does not fit the remembered series, the previous green mark cannot remain on screen while a new result loads.

The cart should make it possible to recognise what was actually ordered. When compatibility depends on an additional insert, check whether it is included. Do not add it without an explicit user decision. A customer who already owns the component may need only the page. Communicating a condition and automatically selling a whole set are different actions.

Aeneia Design Connect identification of the owned model with a clear compatibility result and the correct order item. Prepare confirmed product relationships and examples of exceptions so the design also covers missing data. Discuss accessory compatibility information

Who maintains the answer “fits”?

A relationship has an owner and a source. It may come from manufacturer documentation or an approved company catalogue. Record who confirms changes and how new series are identified. An identical trade name should not automatically inherit every compatibility from an earlier edition. That is why our example uses an album whose name has not changed.

Confirmation should have a change history in the catalogue back office. If a manufacturer corrects its application list, the person responsible for content should be able to find the affected pairs rather than manually inspect every description. When two materials conflict, do not automatically choose the more favourable result. Record the conflict for the data owner to resolve. Meanwhile the site can limit the scope of confirmation or direct the question to support. The appropriate path depends on the company's process, not on a component's default green label.

When a spreadsheet supplies the catalogue, take care with column mapping and a data import trial (in Polish). The accessory identifier and owned-model identifier must reach the right fields. Swapping one column can produce a credible-looking list of pairs that were never confirmed.

For acceptance, prepare the same accessory for two similarly named series and an item without data. Test changing the model, returning from the cart and opening a saved address. The expected outcome is preservation of the correct pair or an explicit request to select again. A user should not receive default confirmation for the last model used in a different task.

For a fictional prototype, a small reference set can state: K1 fits P1, K1 does not fit P2, K2 fits P2, and there is no data for K3 and P1. These are assumptions for the example, not a verified product specification. Working through these pairs shows whether the screen actually retrieves a result for both identifiers. Also change only K1's colour if the assumed rules say it does not affect fastening. The compatibility result should then stay the same even though the photograph of the page being purchased changes. The acceptance record should include both identifiers, the catalogue data version and the visible result. This helps distinguish a screen error from a later correction to the application list. Without that information, reopening the same address may show different, properly updated data.

If a customer can identify their album and understand why a page fits, why it does not or what remains unconfirmed, the interface gives them a basis for a decision. For acceptance, choose a pair that is easy to confuse and carry it through to the correct order item. Then the extra pages have a better chance of reaching the album instead of starting their own collection on the next shelf.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear