How to design an in-store product finder that helps Shoppers choose

An in-store Product Finder helps a Shopper narrow a range by asking relevant questions and explaining which Products fit their needs. Start with the decision they are trying to make, map answers to approved Product facts and show why each recommendation fits. Keep the result useful even when no suitable Product is available.

Define the decision before writing questions

A coffee-machine finder might distinguish drink preferences, cleaning routines and available space. A headphone finder might start with listening environment and fit. Do not ask a question unless the answer changes the recommendation or helps explain a genuine trade-off.

Agree the scope with the category specialist, Brand team, Retailer and Experience designer. Identify which Products are ranged, which are physically stocked and which are available through the Retailer’s other channels. Ranging and live stock are different inputs; a stock-check link is not a live inventory integration.

For worked category requirements, see smart home compatibility planning and laptop configuration planning.

Build a transparent decision matrix

The following example shows how to structure the logic. Replace the descriptions with approved attributes from the actual range.

| Shopper answer | Relevant Product attribute | Recommendation rule | Explanation to show | | --- | --- | --- | --- | | Mainly black coffee | Supported drinks | Prioritise suitable brewing options | Why these drinks are supported | | Milk drinks each day | Milk preparation and cleaning | Compare suitable milk systems | Daily preparation and care trade-off | | Limited worktop space | Dimensions and required clearance | Exclude models that do not fit | Space needed around the machine | | Fixed spending limit | Current approved pricing source | Respect the stated budget | What is included at this price | | No suitable model remains | Range limitations | Offer a clear no-match outcome | Which requirement could not be met |

Ask about everyday needs in language people understand. A technical question is appropriate when it is necessary for compatibility, but explain how to find the answer and provide “Not sure” where possible.

Design the questions and results together

Start with a short flow and test whether it reaches a reliable recommendation. Three questions can be a useful prototype; there is no universal optimum. Show progress without suggesting a precision the logic does not support. Allow people to go back, change an answer and start again.

On the result screen, explain the fit using the Shopper’s answers. Show important limitations, included items and relevant compatibility information. An alternative may be cheaper, simpler or more capable; include it when the difference helps the decision. A higher-priced model should not appear automatically.

If the range cannot meet a requirement, say so. Offer a useful next action, such as checking another option with a store colleague. Do not force an unsuitable result to avoid a “no match” screen.

Connect the result to the physical range

Use a clear Product image, model name and any approved shelf cue so the Shopper can identify the item. If a model is available only through the Retailer’s website, label it accordingly. Keep stock-dependent claims current through an agreed process, or link to the Retailer for availability.

On a shared Interactive Display, make a reset available and clear previous answers according to the approved implementation. On mobile, retain the recommendation during normal navigation without requiring registration to reveal it. Any save-to-phone handoff should be tested in the chosen configuration.

Test every outcome and important exception

Test each decision branch, conflicting answers, budget limits, unknown compatibility and discontinued Products. Check the logic with a category specialist, then observe first-time participants using it on the intended hardware. Include people with different reading, reach and accessibility needs.

Agree who updates the matrix when range or Product information changes. Keep a versioned copy so a recommendation can be traced to the rules active at the time. Where actual stock data is not connected, do not describe recommendations as guaranteed to be in stock.

Measure useful progress

Define finder starts and completions before reporting their ratio. Review question-level exits, “Not sure” choices, recommendation distribution and onward selections where those Events are supported. Exclude testing and automated traffic using the agreed rules.

An answer distribution describes people who used the finder, not every visitor to the aisle. A recommendation or click is a Product Interest Signal, not evidence of a purchase. Use repeated no-match outcomes to identify limitations in the range or question logic.

Product Finder checklist

• Every question changes or explains the recommendation
• Rules map to approved facts and the Retailer’s range
• Results explain fit, limits and relevant alternatives
• No-match and unknown-answer paths remain useful
• Accessibility, reset behaviour and every branch have been tested
• Range changes have an owner and measurement definitions are documented

Guide choice with MyFinder

MyFinder is MyPlayer’s guided selling capability. Bring your range and the decisions Shoppers find difficult so the Experience can be scoped with your category and retail teams. Discuss your Product Finder.