Accessories and Kits in the Cart: Suggesting Compatible Products Without Confusing Customers
Design useful suggestions based on how the product is used and on verifiable rules.
SqualiOnline editorial team · 2026-09-07
Suggesting an accessory is useful when it removes a problem for the customer: the part needed for assembly, the material that gets used up, the spare part they'll need sooner or later. It becomes an annoyance when it's just one more sales attempt, put there because the feature existed. The difference isn't in the mechanism, but in the rule that decides what to show: and that rule needs to be written down, not inferred.
The worst risk isn't selling too little. It's that someone buys an incompatible accessory: it comes back together with the main product, and in between there are phone calls, shipments, and a customer who did exactly what the site suggested.
Three different suggestions that shouldn't be mixed
| Type | What it does for the customer | Where it's shown | Mistake to avoid |
|---|---|---|---|
| Necessary component | Without it, the product doesn't work or can't be installed | On the product page, together with the product | Hiding it to make the price look lower |
| Alternative | A different model instead of the one being viewed | On the product page, before the choice | Suggesting it after the choice: reopens a decision already made |
| Optional purchase | Something needed later, or that improves use | In the cart or after purchase | Placing it before the main choice, where it distracts |
The practical rule fits in one line: alternatives are shown before the choice, complements are shown after the choice. Reversing the order lengthens the path and sends back customers who had already decided.
Compatibility is a data point, not an opinion
A suggested pairing is a small technical promise: you're saying those two things work together. If the promise comes from a rule written on the product, it holds. If it comes from “customers who bought this also bought,” it holds until the first case that goes wrong.
- Compatibility must be recorded on the product — fitting, size, power, reference model — not decided at the moment of sale.
- A necessary but unavailable component shouldn't be presented as mandatory: you end up blocking the sale of the main product.
- Rules expire. When a model goes out of production, the pairings that reference it need to be reviewed, otherwise they stay there suggesting parts that no longer exist.
Example: a kit for replacing a pump
A hydraulic components retailer sells a pump. Around it is everything needed to install it, and not all of it carries the same weight.
- Necessary: the fitting set matching the chosen connection. Without it, the part can't be installed. It enters the cart together with the pump, with its price shown separately.
- Compatible and recommended: the expansion tank, which depends on the existing system. It's suggested with the condition stated next to it, not as a mandatory choice.
- Optional: the maintenance kit. It's shown afterward, in the cart or in the order confirmation.
- Excluded: accessories for a different fitting, which must not appear anywhere, not even under “similar products.”
In the cart, the kit should be shown broken out, line by line, with the option to remove whatever is optional. A kit presented as a single block at a single price only works when it truly is a block: if a part could be removed but can't be, the customer doesn't buy the kit, they leave.
What needs to be clear in the cart
- The contents: what's inside, not just the kit's name.
- The price of the individual items, or at least the difference between the kit and the same parts bought separately.
- What can be removed and what can't, with the reason next to it: “necessary for assembly” is an explanation, “mandatory” isn't.
- The effect of removal: if removing a piece changes the delivery time or voids a condition, it needs to be said at that moment, not on the general terms page.
Measuring margin and returns, not just cart value
Average order value is the easiest measure to push up and the easiest to misread. Accessories often carry a different margin than the main product, come back at different rates, and can cost more in support than they earn.
- The margin on the whole order, not the total collected.
- Returns broken down by reason: “not compatible” is a rules problem, “didn't need it” is a problem with how the suggestion was presented. These call for two different fixes.
- Support requests tied to pairings: if an accessory generates questions, the product page isn't explaining enough.
- Purchases abandoned on pages where the suggestion appears: if they increase after introducing it, the suggestion is getting in the way.
When it's better to suggest nothing
- When compatibility depends on information the customer doesn't have, like measurements to take or model numbers not readable on the part: a request to verify is better than a pairing based on a guess.
- When the main product is already a difficult decision: adding choices for someone undecided doesn't grow the order, it postpones it.
- When the accessory has much longer delivery times than the product: the whole order aligns to the slowest item, and the customer waits for something they didn't need right away.
What this guide doesn't cover
This guide covers the commercial rules for pairings: what to suggest, where, under what conditions, and how to measure the effect. Choices within a single product — sizes, colors, customizations, and allowed combinations — are modeled a different way and deserve a separate discussion. Reading the overall numbers of an online store, to understand whether it's working, is broader than this as well.
Frequently asked questions
Is it better to show accessories on the product page or in the cart?
It depends on the type of accessory. The one without which the product doesn't work belongs on the product page, because it's part of the decision and the real price. The optional one belongs in the cart or after purchase, when the main choice has already been made and one more suggestion doesn't get in its way.
Do automatic suggestions based on other customers' purchases work?
They're good for suggesting related items, not for guaranteeing that two products are compatible. They work fine for generic accessories, where a not-quite-relevant pairing only costs a bit of clutter. Where fittings, measurements, or models are involved, written rules are the only safe basis: a wrong suggestion there turns into a return.
Does a kit need to cost less than the sum of its parts?
Not necessarily. A kit can be worth it because it saves the customer the work of figuring out what's needed, and in that case the advantage is certainty, not a discount. What shouldn't happen is the opposite: the kit costing more than the parts bought separately on the same site, because whoever notices won't buy either one.
Let's evaluate useful kits and pairings for your catalog.
If you’d like to talk it through, the service that handles this is E-commerce.