A product selection decision tree helps shoppers narrow an assortment when choices depend on a few meaningful constraints. It can also reveal the vocabulary customers use, which can improve category labels and product copy. Begin with the real purchase decision, not the catalogue fields available in the CMS.
How to make the decision
Use the following sequence for a UAE English-language business. Keep a copy of the inputs and the reason for each decision so a later reviewer can reproduce it. The right answer depends on the actual offer, audience and data available; the example is a planning exercise, not a claimed Megvi client outcome.
| Step | What to do |
|---|---|
| Find the constraints | Ask sales or support which questions reliably change the recommendation: use case, size, compatibility, delivery or budget. Remove questions that do not alter the next branch. |
| Limit each branch | Offer a small set of clear choices and an “I’m not sure” path. Show why a choice matters before asking for more detail. |
| Attach the right destination | Each outcome should point to a live category, filtered collection or product comparison with matching stock and claims. Avoid sending every branch to a generic shop page. |
| Learn from failures | Review no-result paths, abandoned branches and customer feedback. Update the tree when products or compatibility rules change. |
Worked example
Illustrative UAE office chair tree: first ask whether the chair is for a home desk or shared office; then ask for daily sitting time and size range. A “shared office, long shifts” answer goes to durable adjustable models, while “not sure” goes to a plain comparison of adjustment features. These are sample rules, not tested product recommendations.
Where this approach can fail
A decision tree can mislead if it acts like medical, safety or technical advice without verified product evidence. Mark assumptions and give customers a route to confirm compatibility with a human.
Review checklist
Test every branch on mobile, ensure no dead ends and check that destination pages reflect current inventory. Compare the tree’s questions with onsite search and support queries after launch.
Ask an owner to confirm the inputs and assumptions before using this method to change a live campaign, customer record or product recommendation. Keep the original version of any measurement or creative asset so the next review can separate what changed from what only appears to have changed.
What to do next
If the choices contain unfamiliar specifications, clarify them with When a Product Glossary Helps Shoppers and Search. If you need help applying the method to a live account or store, explore Megvi’s ecommerce SEO service and bring the current page, campaign or data flow plus the result you want to improve.