Products that need another product to work: purchase requirements and fewer returns

A customer buys the replacement head for a toothbrush they do not own. Another buys the expansion for a board game without the base game. A third signs up for the advanced course without having done the basic one. None of them does it in bad faith: they simply did not know they needed something else. And all three end up as a return, a support query or a negative review.

Stores usually try to solve this with a line in the description (“requires model X”). It half works: many customers do not read the whole description.

The kinds of requirement that exist in practice

• A specific product: the accessory only works with one model. The customer must have bought it before or have it in the cart.
• Any product from a category: an extended warranty valid for any phone, a case for any camera.
• A product from the same line: the accessory only makes sense with a product from its family.
• Customer group: professional lines, products for distributors, courses reserved for students.
• Minimum accumulated spend: products or benefits reserved for customers with a certain history.

What to do when it is not met: block, hide or warn

1. Block the purchase: the product is visible but cannot be added until the requirement is met. For spare parts that are useless without the machine.
2. Hide the product: it does not appear for those who do not qualify. For professional or reserved lines.
3. Allow with a warning: it can be bought, but there is a clear warning. For cases where the customer may have bought the base product elsewhere.

Do not lose the sale: “Add what is missing”

Simply blocking has a cost: the customer who does not qualify leaves. The alternative is to turn the block into a proposal: “This spare part needs model X. Shall we add it to your cart?”. With one click, the customer has what they need and carries on shopping.

This changes the approach: the requirement stops being a barrier and becomes a cross-sell with a clear reason. It works better than any generic recommendation, because the customer has already said they want the accessory.

The message: clear and in their language

• Say exactly what is missing, not “you do not meet the requirements”.
• If the customer may have bought it elsewhere, tell them what to do (get in touch, choose the option with a warning).
• If you sell in several languages, the warning should be too.
• It should not sound like a reproach: the customer wanted to buy something from you.

Cases where it matters most

• Spare parts and consumables: filters, cartridges, heads, batteries. A customer with the wrong model always returns them.
• Expansions: games, software with add-ons, modular systems.
• Incomplete kits: parts that only work with another (a mount without its adapter).
• Training: levels that require the previous one.
• Warranties and services: which only make sense with a product in the order.

How to know whether it pays off

Measure before and after: returns for “not compatible” or “does not fit my model”, support queries about compatibility and, if you offer “Add what is missing”, how many sales are completed thanks to it. Those are the sales you used to lose or that came back as returns.

Common mistakes

1. The requirement only in the product description.
2. Blocking on the product page but not in the cart.
3. Blocking without offering a way to meet the requirement.
4. Rules that are too strict and exclude those who bought the base product through another channel.
5. Not testing the rules before enabling them: a badly set requirement can block half the store.

Checklist

• A list of products that do not work on their own.
• The type of requirement for each one.
• Action: block, hide or warn.
• A clear message in every language.
• An option to add what is missing.
• A test with a customer who qualifies and one who does not.
• Measurement of returns before and after.

Frequently asked questions

What if the customer bought the base product in a physical shop or on another website? It is the most common complaint. For spare parts where this happens often, choose “allow with a warning” instead of blocking, or leave a way for them to contact you so you can enable the purchase. Blocking someone who does own the machine means losing a sale and a customer.

Does the requirement count old orders? It should, if they are valid orders: a customer who bought the machine two years ago is entitled to buy its spare part today. Check that cancelled or returned orders do not count as meeting the requirement.

Does hiding products affect SEO? Hiding them from those who do not qualify means search engines will not see them either unless they log in. For reserved products that is what you want; for spare parts people search for by reference, it is better to leave them visible and block or warn at purchase.

How many rules can I have? As many as you need, but start with the products that generate the most returns. A dozen well-set rules usually solve most of the problem.

How to handle it in PrestaShop

RKR Product Dependencies lets a product be bought only when the customer meets the conditions you set, with five types of requirement: a specific product (bought previously, in the cart or either, with combination and quantity), a product from a category, customer group, minimum spend or a product from the same category. For each rule you choose one of three actions: block the purchase, hide the product or allow it with a warning. The block is checked on the server, the warning is configured per language and the “Add what is missing” button puts what is needed into the cart with one click. It includes a simulator to test the rules and statistics on recovered sales.

If you also want to offer a complement at checkout, RKR Buy More Pro adds an offer that is accepted with one click.