A kit configurator can start with a product or a use case. The best entry point depends on what the customer already knows. An experienced buyer may recognise the correct base product. A new customer may mainly be able to describe what they want to achieve. Choose an entry point that uses that knowledge and fills the gaps, so the first step does not become an unnecessary barrier.
Investigate the buyer’s starting point
Listen to the first question in advisory conversations. Does the customer name a model or describe a situation? That difference provides direction. Someone who has already chosen a base product wants to see suitable components quickly. Someone unfamiliar with the products first needs help with the application and starting assumptions. A configurator that asks everyone the same technical opening question may unnecessarily slow one group down.
In a fictional lighting store, an installer is looking for accessories for a familiar track system. A consumer is looking for light for a home workspace. The first can start with the product; the second benefits more from a use-case question. The two routes can meet later at the same components. The product model needs to maintain the same meaning throughout.
Keep applications specific enough. Indoors or outdoors may be relevant, but may say little about the actual use. Write out a few recognisable scenarios and check with advisers which information is needed to select products. A use-case entry point works only if the answers actually influence a suitable combination.
Prevent the entry point from becoming an unclear promise
A configurator that opens with “tell us what you need” may suggest fully personalised advice. Define which assessment actually takes place and explain its boundaries clearly. A route that identifies a suitable product family differs from a complete room design. The customer needs to know which assumptions they still have to check themselves.
For the product experience this promise should be reflected in the summary. Show which application was chosen and which components follow from it. The customer can then assess whether the outcome still fits their situation. A product list alone does not explain why the route produced that combination.
A product entry point needs context too. A familiar model may serve different applications. Where necessary, let the customer indicate how the product will be used before choosing additional components. This is therefore about the order that gives the intended audience the most clarity, rather than an absolute choice between application and product.
Test both entry points with different knowledge levels
Build two small trial routes with fictional products. Let an experienced buyer and a new customer assemble a comparable kit. Ask where they feel certain and where they have to guess. If the experienced buyer has to answer many general questions, a faster product route may help. If the beginner must choose model names immediately, a meaningful entry point is missing.
Then check that both routes arrive at the same relevant product rules. An extra entry point must not create a different version of product facts. The content source and final combination must remain consistent. This is especially important as the range grows and different teams work on explanations or rules.
For Yindle Kit Configurator, the desired opening question can be explored with a specific product family. For unusual application logic, targeted development may be needed. The best entry point fits what the customer already understands and makes the next choice easier, with a clear explanation of the resulting kit.