Blog Sections Open
Shopkeeper vs miniShop2 for Large Catalog Projects
The bigger the catalog gets, the less helpful a purely “which plugin is better” debate becomes.
The source discussion framed a familiar choice: should a larger catalog stay on Shopkeeper, or is it time to move toward miniShop2?
What changes when the catalog grows
- variant logic gets heavier
- stock and pricing rules get less template-friendly
- catalog import and synchronization matter more
- editorial product management starts to overlap with operational commerce data
Shopkeeper is often a good fit when the store is still closely tied to the content tree and the project values Evo-native simplicity. miniShop2 becomes more attractive when the project starts behaving like a real commerce system first and a CMS-driven catalog second.
Useful way to decide
Do not choose only by feature lists. Choose by data shape, catalog scale, and how much business logic the store must carry over the next year.
Source: original community announcement. Related docs: modern Evolution commerce docs.
Building a Custom Checkbox TV Input in Evolution CMS
How a custom checkbox-style TV input can be added to Evolution CMS when the standard checkbox field is too limited for the project’s needs.
Planning a Revo Commerce Stack with miniShop2 and mSklad
A historical ecosystem note on combining MODX Revo, miniShop2, and external inventory systems such as mSklad for more serious commerce projects.