Docs Navigation Open
Commerce Sites
Use Evolution CMS as a content-first foundation for catalogs, stores, and business-facing project flows.
Commerce in Evolution CMS has two main generations: the classic ecosystem built around Commerce, DocLister, and FormLister, and the newer Evo 3 package layer built around sCommerce and related packages.
Modern Commerce Layer
- sCommerce — main commerce suite for Evo 3 projects.
- sOffers — offer and record handling in manager workflows.
- multiCurrency — currency support when one project serves multiple currencies.
- sMailer — transactional mail around order and customer events.
Classic Commerce Layer
- Commerce — classic addon with a plugin, order manager module, cart/order snippets, price conversion, and currency tools.
- Shopkeeper — older commerce solution still found on long-running projects.
- eFilter — catalog filtering and sorting layer.
Classic Commerce Building Blocks
- Cart — cart rendering
- Order — checkout form
- Comparison and Wishlist — compare and favorites flows
- PriceConvert and PriceFormat — currency and price display helpers
- CurrencySelect — currency switcher
How the Classic Stack Usually Works
Product resources carry the product data. DocLister renders category or catalog pages. Cart and Order snippets handle basket and checkout flows. The manager module tracks created orders and statuses.
Practical Rule
Use sCommerce for new Evo 3 builds. Keep Commerce or Shopkeeper when you are maintaining an older working stack and migration is not yet justified.
See also Commerce & Business and Lists, Forms, and Search.
Multilingual and Multisite
Plan language and multisite structure early so URLs, ownership, and maintenance do not become fragile later.
Frontend and Layouts
Keep frontend implementation clean by separating content structure, reusable presentation, and runtime logic.