Skip to main content
GullySystem
A practical guide

Why accessory orders come back as not compatible

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 5 min read

In this guide 6 sections
The short answer

Accessory orders come back as not compatible when fit lives only in the product title, where shoppers skim and filters cannot read. Store fit as a table of model numbers. Then ask for the shopper’s device on the product page and show a clear fits or does not fit message before checkout.

What do the returned parcels have in common?

Start with last quarter’s return reasons. Pull every parcel tagged not compatible, wrong fit or does not charge, then sort them by product type and by the device the shopper owned.

A pattern shows up within a day. Cases come back because the camera bump differs between two siblings of one phone line, and cables come back with the wrong connector on one end. Chargers fail on wattage, because the laptop wanted more than the brick could give, and sleeves fail on the diagonal, which was close but not close enough.

Recode a sample by hand first if the return reasons are free text, because typed notes hide the pattern behind a dozen spellings of the same complaint. Do it before touching the catalogue.

A title cannot carry compatibility

A title that reads case for eleven phone models is only text, and text cannot be filtered or checked against a shopper’s device. Worse, marketplaces shorten long titles and phone screens shorten them again, so the line that decides the fit often never appears.

Marketing names mislead as well. One name can cover two regional model numbers with different radio bands, and neighbouring sizes in one range can differ by a millimetre at the cutout. Shoppers guess from the name.

Descriptions repeat the trouble at greater length.

Build one compatibility table per product

Give every accessory its own table. Each row lists one device with its brand, model number, marketing name and a fit status of fits, fits with a note or does not fit. Notes cover quirks such as needs an adapter.

Each accessory type adds its own columns. Cables need the connector at each end and a flag for data or charge only, while chargers need maximum output and the profiles they speak. Sleeves need the screen diagonal and the thickness of the machine inside.

Fill the table from the brand’s own compatibility page or a sample on the bench, never from a rival’s listing, because copied errors travel with the copy. Then test one fit by hand.

  • Case: model number, camera cutout and button layout
  • Cable: connector at each end, charge only or data
  • Charger: maximum output and supported profiles
  • Sleeve: screen diagonal and chassis thickness
  • Screen protector: model number and edge shape

Ask for the device on the product page

Put a device selector above the buy button. The shopper picks a brand and a model, the page answers in green or red, and a red answer offers the three nearest products that do fit.

Save the choice for the session. Category pages then hide accessories that do not fit, and search results carry a small label that reads fits your phone. A shopper with two devices must be able to switch.

Plan for the unknown case. If a model is missing from the list, show a contact option and log the model, instead of allowing a silent add to cart.

  • Selector placed above the buy button
  • Green fits or red does not fit answer
  • Device remembered for the whole session
  • Category pages that hide items which do not fit
  • Fallback message when the model is unlisted

Keep the tables alive after launch

Every new handset launch brings a new cutout. Add the model to the table before launch week and not after the first angry review lands in your inbox.

Tag every return with a coded reason and the shopper’s device. Review the not compatible tag each Monday. A repeated mismatch points to one missing row or one wrong row.

This week, export last quarter’s returns, rank products by mismatches, take the worst ten and rebuild their tables before you add a single new accessory to the shop.

Compatibility table template

A one page worksheet. Each line pairs one accessory with one device, and the columns hold product code, device brand, model number, marketing name, fit status, note, checker and date checked. A block at the foot lists the extra columns by accessory type: connector ends for cables, output for chargers and diagonal for sleeves.

Open a blank worksheet to print

Questions owners ask

Is a compatible with list in the description enough?

No, because a list in the description cannot be filtered, cannot drive a fit check and gets cut short in marketplace feeds. Keep the data in a table. The page can still print it as text.

How do we handle a new phone launch?

Add the rows before launch week. Cases and screen protectors depend on exact cutouts, so wait for the supplier’s drawing or a sample unit before you mark any product as fits.

What about universal accessories?

Universal is a claim, not a fact. Even a universal mount has limits, such as the widest handset it grips or a ring that blocks wireless charging. Record those limits in the note column.

Can a small shop do this without a developer?

Yes, for a start. A spreadsheet with one line per product and device pair imports into most catalogue tools, and the device selector can follow once the table is clean.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements