Too many products, too little guidance? How a product advisor leads to the right item

A product advisor reduces choice overload through guided questions, weightings and instant updates to the results. For shop operators with a large range, this means fewer wrong purchases and faster buying decisions. This practical description shows how the plugin works in Shopware and when it makes sense.

If your shop carries many similar items, customers quickly lose their bearings. An interactive product advisor for Shopware leads them to the right product with just a few questions, gives technical priorities precedence over nice-to-have criteria and updates the matches live. In this article we describe typical use cases, how the advisor logic works, which requirements apply and where the plugin is not a good fit.

When customers get stuck in the range: the problem and its consequences

Customers are slowed down by very broad ranges: too many variants, unclear priorities and uncertainty lead to longer sessions or abandonment.

From a professional perspective, this is a classic case of decision overload: if users cannot quickly see which features narrow down the choice, the cognitive load rises. The result is behaviour such as aimless browsing, frequent switching between product pages or leaving the shop early. On the technical side, unstructured product data and missing or inconsistently maintained attributes make the problem worse, because search and filters do not work reliably.

In practice, this shows not only in lower order numbers but also in more returns, because buyers choose products that do not meet their needs. Asking specifically about buying criteria (for example use case, connection preferences, wearing comfort) reduces the search effort and makes decision aids visible. It is important that the questions do not just narrow things down but reflect the priorities of the customer group: technical functionality, budget or design can be weighted differently depending on the context.

Common pitfalls are too many or overly technical questions at the start, questions with unclear answer options, no live feedback after a selection and ignoring variant attributes. To counter this, an iterative approach is recommended: analyse user behaviour, identify core criteria, test prototypes and optimise the order of questions based on real sessions. Also make sure your product data follows clear labelling standards, otherwise weighted answers will be mapped to the wrong products.

What you can replace: manual advice vs. automated recommendations

Without a plugin, you have to use filter lists, extensive landing pages or personal support to guide customers; that is labour-intensive and scales poorly.

Manual tools such as extensive filter pages, content-based buying guides or live chat do offer depth, but they require constant maintenance and produce inconsistent answers across channels. A product advisor standardises decision knowledge: it encapsulates rules, makes priorities reproducible and gives every user a consistent, guided experience. Technically it does not replace people, it scales the decisions that sales advisors typically make.

When introducing it, you should decide where to use it along the customer journey: for entry and category stages, short, targeted question trees make sense; in buying contexts that need a lot of advice, an advisor can act as a pre-selection and then hand over to live advice. Use dynamic product groups to restrict the list of matches in advance (for example to products in stock or certain manufacturers). This reduces irrelevant results and the effort of maintaining landing pages.

Typical wrong decisions are over-automation (no human escalation path), overloading the question tree with irrelevant details and neglecting the maintenance of attribute mappings. The deciding factors for or against automated advice are how predictable the buying criteria are, how standardisable the product features are and the size of the range. If many cases are highly individual or complex pricing rules apply, a hybrid solution with human support makes sense.

Product advisor plugin in Shopware: view from the product documentation

How the product advisor works in practice

At its core is a weighted question-and-answer workflow: questions are given individual weightings, answers influence product relevance and the list of matches updates live after every answer.

Technically, the system is built on several elements: a question controller that manages answer paths and conditional logic; a relevance layer that translates answers into weightings; and a matching engine that ranks products according to these weightings. Different question types matter for usability: buttons for quick, binary decisions, dropdowns for many alternatives, range selection for scalable attributes (such as size ranges) and text input when users should enter free information. The choice of question type affects conversion and abandonment rates; short, visually supported answers usually work better than open text.

Variant handling is important: variant attributes must either be mapped to the main product entity or evaluated per variant. Decide whether the advisor aggregates variants (product family as a match) or rates variants individually; both have pros and cons for user guidance and for follow-up work in the shop back end. Equally central is the consistency of attribute names and values across the range; inconsistencies lead to missing matches or wrong prioritisation.

For integration, use the CMS block provided in Shopping Experiences. Think about tracking too: record question paths, drop-off points and follow-up actions in order to optimise the question tree. Testing in several languages and with variant visibility is essential when multilingual support and variant support are active. Typical implementation errors are missing indexing of relevant attributes, incomplete translations and overly rigid product groups that artificially restrict valid matches.

Compatibility, limits and when the plugin is not a good fit

The plugin requires Shopware 6.5.0 to 6.8.0 and PHP 8.1 or higher. It is suitable for shops with a broad range and clear, answerable selection criteria; it is not suitable for highly configurable product configurators or B2B workflows with complex pricing rules.

Technically, this means: make sure your shop and server environment meet the version requirements and that product data is maintained with meaningful, consistent attributes. Also check whether existing extensions or customisations interfere with embedding the CMS block or mapping attributes. For high-load scenarios you should test the caching and indexing behaviour of the matching engine to avoid performance bottlenecks.

The plugin is not the right choice if your products mostly have to be configured individually, if pricing depends heavily on the customer or account, or if there is a lack of standardisable properties. Common implementation errors are expecting the plugin to replace a full configurator, neglecting data quality and missing governance for attribute maintenance. Plan time for modelling the questions, mapping them to the product data and testing in real user flows.

You can send support and integration questions by email to [email protected]. For more information on Shopware-specific topics, see our knowledge section and the practical notes on Shopware plugins. Use these resources to compare technical requirements, best practices for data modelling and experience from similar integrations.

Frequently asked questions

Which Shopware and PHP versions are supported?

According to the plugin documentation, compatibility is stated for Shopware versions 6.5.0 to 6.8.0; PHP must be at least version 8.1. Check your environment before installing.

Can the advisor be run in several languages?

Yes. The documentation lists multilingual support as a built-in feature, so questions and answers within an advisor can be translated and no separate advisor is needed per language.

Can the advisor be limited to certain product groups?

Yes. The plugin supports “dynamic product groups”, which let you define in advance which products feed into the recommendations (for example only items in stock or by manufacturer).

How do I embed the product advisor in the storefront?

It is embedded via a CMS block in Shopping Experiences. The quickstart instructions in the documentation say: create the advisor and then add it to a layout under ‘Content → Shopping Experiences’.

Conclusion

The product advisor is a pragmatic solution if your range is hard to navigate and the selection criteria can be standardised. It works with weighted questions, live updates and dynamic product groups. Requirements: Shopware 6.5.0 to 6.8.0, PHP 8.1 or higher. View the plugin in the Shopware Store.