One: How does the catalogue work?

Think about product structure before product count. What are the variants, stock units, relationships and update frequency? Use representative items from the actual catalogue. A few examples can explain the need more clearly than a long wish list.

Two: What happens after an order?

Payment is not the end of the operational journey. Draw how the order reaches the team, where stock information comes from and how changes are handled. Make manual steps and information ownership visible.

Three and four: How will payments and content be managed?

Confirm the intended payment provider and compatibility with existing tools. Then consider who updates product descriptions, campaign pages and images, and how often. The administration experience is part of the store.

Five: Where is customization essential?

Not every difference requires custom software. But a critical business rule that does not fit the platform should be identified before choosing a theme. Separate business requirements, visual preferences and changes that can wait.

Six: How can you test the decision?

Walk a representative product through discovery, detail, basket and checkout. Discuss the operational journey at the same time. This is a decision method, rather than a promise of improved conversion.

What to bring to a discussion

An example catalogue, a list of existing tools, the order-handling process and first-phase boundaries form a useful starting point. Consider that context alongside the look of the storefront.