Choosing Between Shopkeeper and miniShop for an Evolution CMS Store

Commerce questions in the Evolution ecosystem almost always return to the same strategic choice: keep the store lightweight with Shopkeeper, or move toward a heavier and more modular catalog architecture closer to miniShop-style thinking.

the discussion was not about one tiny bug. It was about long-term fit: product variants, stock logic, checkout behavior, maintainability, and how much complexity a project can absorb.

When Shopkeeper makes sense

• Catalog structure is moderate and predictable.
• You want a simpler order flow with less overhead.
• The project benefits from fast implementation more than deep catalog abstraction.

When a miniShop-style approach wins

• The catalog model is more complex.
• You need richer product logic, more structured extensions, or more scalable ecommerce architecture.
• The team is already comfortable with the extra operational weight.

The real lesson is not that one tool always beats the other. It is that store architecture should be chosen by catalog complexity and future workflow, not by habit.

Source: Shopkeeper package page on Extras.Evolution and miniShop2 documentation.