eCommerce Architecture: Layers, Approaches, and Deployment Models Explained
The right ecommerce architecture decides how easily your online business can change, yet it is often overlooked when choosing a platform. This guide explains the layers an ecommerce platform is built from, compares the monolithic and headless approaches and the main deployment models, and shows how to choose the model that fits your business.
If you are selecting a new vendor or considering replatforming, it also covers how to approach that decision.
Contents
- WHAT IS ECOMMERCE ARCHITECTURE?
- WHAT IS A WEB-BASED COMMERCE ARCHITECTURE?
- THE FIVE-LAYER ECOMMERCE ARCHITECTURE FRAMEWORK
- WHAT ARE THE TWO FUNDAMENTAL ECOMMERCE ARCHITECTURE APPROACHES?
- WHAT ARE THE MAIN ECOMMERCE ARCHITECTURE MODELS?
- CHALLENGES AND ADVANTAGES OF EACH MODEL
- HOW VIRTO COMMERCE APPLIES THIS ARCHITECTURE
- CONCLUSION
What Is eCommerce Architecture?
eCommerce architecture is the way an online platform’s technical components are organized into layers and subsystems, and how those parts work together to let customers buy and businesses sell online. The term covers everything from the frontend user interface to the backend server infrastructure.
An ecommerce architecture is usually described by three attributes:
🔘 eCommerce architecture framework (e.g., two-layer, three-layer, five-layer): how the system is split into layers.
🔘 eCommerce architecture approach (e.g., monolithic, headless): how the components interact.
🔘 eCommerce architecture model (e.g., SaaS, vendor-managed, or self-managed): how the system is deployed and who runs it.
The attributes combine freely. For example, a Software-as-a-Service (SaaS) ecommerce platform can be monolithic or headless, with two or three layers.
What Is a Web-Based Commerce Architecture?
While ‘ecommerce architecture’ is a broader term, web-based commerce architecture refers specifically to ecommerce systems that operate through web technologies, typically hosted on the cloud or web servers.
A web-based commerce architecture is closely tied to the web interface of the ecommerce website and can be split into two basic layers: client-side (frontend) and server-side (backend).
eCommerce architecture framework: How many layers are enough?
The common rule is that an ecommerce framework has at least two layers or tiers, the two main components of an ecommerce software architecture: frontend and backend. Such a simple architecture framework is somewhat outdated, as it cannot support modern API-driven omnichannel capabilities. Today, a three-layer architecture framework is considered a basic standard for an ecommerce platform.
1. Presentation layer
This user-facing layer includes the website, layout, user interface, personal account portal, and any other part of the system end users can reach.
2. Application layer
The application layer handles the business logic and internal processes, including product catalog management, shopping carts, payment processing, and order tools.
3. Data layer
This layer stores product information, customer data, order history, and other data the system needs.
A three-layer ecommerce architecture
While a three-layer framework is used in the majority of monolithic and SaaS platforms, more modular ecommerce platforms usually use a five-layer framework.
How to choose the right ecommerce platform?
Read guide for expert insights!
The Five-Layer eCommerce Architecture Framework
The five-layer framework is more modular, separating UI, business logic, data, integration, and infrastructure. We use the architecture of the Virto Commerce Commerce Innovation Platform as the example for each layer.
Five-layer ecommerce architecture: Virto Commerce example
1. Presentation Layer
This layer consists of all frontend applications that interact with end users, such as websites, mobile apps, customer portals, and IoT interfaces. It doesn’t contain business logic or unnecessary backend data, which keeps the frontend lightweight and easy to adapt to each business.
2. Business Logic Layer
This level contains business logic and processes requests from the frontend, controls commerce modules, and organizes data and integrations. It is split into independent logic blocks for different industries and is accessible only to developers.
3. Commerce Modules Layer
Built on Atomic Architecture™, this layer consists of commerce modules, each serving one purpose (for example, catalog, pricing, marketing, or inventory). Each module is linked to other modules and tiers through APIs, so it can be changed, upgraded, or scaled up and down without affecting the rest.
4. Best-in-Breed Applications Layer
While not part of the core ecommerce platform, these tools determine performance, scalability, and security. This layer includes infrastructure components such as databases (a wider version of the Data layer in the three-layer model), search, storage, cache, and more. The core of the ecommerce system connects to this layer through APIs, so any of these tools can be replaced.
5. Third-Party Apps Layer
The Third-Party Apps Layer connects the platform to the external systems it depends on, such as CRM and ERP systems and payment providers. Like the Presentation Layer, it talks to the core through APIs, but the applications in it are not built on the platform.
Download architectural guidelines for Virto’s Commerce Innovation Platform
What Are the Two Fundamental eCommerce Architecture Approaches?
A framework sets out the layers. An approach defines how the components in those layers interact, and there are two main options.
Monolithic Approach
Monolithic architecture is a legacy approach where all components of a webstore are tightly connected, so any backend change affects the entire solution. As a result, even a minor change means rebuilding the entire ecommerce system.
Headless Approach
With a headless architecture approach, the frontend is completely decoupled from the backend logic. The backend and frontend communicate through APIs. This lets a business run several channels, devices, or frontends on one platform while keeping product presentation and user experience consistent.
“Headless” and “composable” are often used interchangeably, but they describe different things. Headless separates the frontend from the backend, so you can build and change customer experiences without rebuilding the commerce platform. Composable goes further: each capability is a component you can replace on its own. A platform can be headless without being composable.
What Are the Main eCommerce Architecture Models?
SaaS for Businesses with Standard Processes
In a Software-as-a-Service model, the vendor deploys and maintains the application. That is the main reason small and mid-sized businesses with limited resources choose SaaS: they can launch faster.
The main difference between SaaS and a platform you can extend is who decides what the backend can do. In SaaS, the backend is out of reach and can’t be modified. Google Workspace is a familiar example: a good set of collaboration tools as is, but it can’t be changed to fit how a large enterprise works. SaaS ecommerce works the same way, so companies with contract pricing, approval flows, or several entities end up adapting their processes to the platform.
Extensible Platforms for B2B Enterprises
An extensible platform gives your team access to the backend, so the software adapts to your business processes instead of the other way round. What you choose next is who operates it. In a vendor-managed model, the vendor hosts, scales and upgrades the platform. In a self-managed deployment, your team runs it on its own cloud, a private cloud or on-premises, and applies the vendor’s releases itself. This suits medium and large B2B companies whose sales do not fit a standard SaaS product: contract pricing, approval flows, several entities or routes to market.
Multi-tenant SaaS fixes one data model and one upgrade path for every tenant on it. Virto Commerce is source-available: you extend the core without forking it and replace one capability at a time, and upgrades follow your LTS schedule, not a vendor’s release date. Virto Cloud runs the hosting and the platform lifecycle, so that freedom does not arrive as an operations burden.
Self-Managed Deployment for Residency and Compliance Needs
In a self-managed deployment, the company, not the vendor, runs the platform: on its own cloud, a private cloud or on-premises.
B2B companies considering on-premises deployment often assume it means installing the platform by following the vendor’s instructions. In practice, a modern B2B ecommerce solution includes several separate software products: search, PIM, CMS or CRM systems, and more.
Each of them has to be installed and licensed separately, which usually costs more than the same set bought as a package from a cloud vendor.
In our experience, companies choose self-managed deployment mostly because of data residency, sovereignty, or strict compliance requirements. Pharmaceutical and biotechnology companies are a typical case: data privacy law can require them to keep full control over sensitive information and over who can access it and when.
Challenges and Advantages of Each Model
|
Criterion
|
SaaS
|
Extensible platform, vendor-managed
|
Extensible platform, self-managed
|
|---|---|---|---|
|
Who runs the platform
|
The vendor, for all tenants
|
The vendor hosts, scales and upgrades it
|
Your team, on its own cloud, a private cloud or on-premises
|
|
Backend changes
|
Configuration within the vendor’s limits
|
Your team extends the backend
|
Your team extends the backend
|
|
Upgrades
|
On the vendor’s release schedule
|
Applied by the vendor
|
Applied by your team from the vendor’s releases
|
|
Integrations
|
Mainly the connectors the vendor supports
|
Any system through APIs
|
Any system through APIs
|
|
Typical fit
|
Smaller businesses with standard processes
|
Mid-size and large B2B companies with their own sales processes
|
Companies with data residency or compliance requirements
|
|
Main trade-off
|
Your processes adapt to the platform
|
Needs a capable technical team or partner
|
Your team also owns infrastructure, scaling and monitoring
|
SaaS Model
Pros:
1. Ready-to-use
A SaaS solution comes with out-of-the-box features you can use right away.
2. Automatic centralized updates
The provider is responsible for centralized platform updates, but it cannot adapt them to your needs.
Cons:
1. Vendor-dependent
To maintain the software and keep it available, you need to fully rely on a provider, even if the provider fails to upgrade some parts or takes too long to implement changes.
2. Not adaptable
With a static SaaS platform license, you get a set of ready-to-use features that are the same for all users of this solution. If you need a unique feature, you have to persuade your SaaS vendor to build it or go through an expensive replatforming.
3. Integration challenges
SaaS solutions can only integrate with the third-party tools they are initially built for. Integrating other tools is often difficult.
Does your platform’s TCO hold you back?
Ask your vendor these questions to find out.
Extensible Platform Model
Pros:
1. Flexibility & Adaptability
The modular architecture lets you customize both frontend and backend and integrate other systems.
2. Cost-effectiveness
Extensible platforms are often priced per order or by GMV, with transparent pricing. Adaptable platforms keep costs predictable as market conditions and business scenarios change.
3. Easy integrations
With an API-first approach, every piece of business data and function is accessible via API, so the platform can be integrated with any third-party solution or service.
Limitations:
1. The complexity of the architecture
An extensible platform requires a capable technical team to bring ideas to life. Vendors with an active developer community, detailed documentation and a self-service knowledge base give that team strong support.
2. Limited frontend theme variations
Extensible platforms usually come with a ready-to-use frontend that supports white-labelling, branding, and a few prebuilt themes. A unique design needs additional development. SaaS solutions often offer more themes but limit how far you can customize them.
How Virto Commerce Applies This Architecture
Virto Commerce is a digital commerce platform built on the five-layer model described above. Its Commerce Innovation Platform is cloud-native, API-first and headless, and Virto Atomic Architecture™ lets teams change one capability without touching the rest. Run it on Virto Cloud, where we host, operate and upgrade the platform for you, or as a self-managed deployment on your own infrastructure when residency or policy require it.
☑️ Extensibility
Built on Atomic Architecture™, the platform is extensible by design, from quick prototyping to fully custom solutions.
☑️ Continuous Platform Updates
Customers of the Commerce Innovation Platform can immediately use new features and centralized improvements without worrying about compatibility issues.
☑️ Backend Available in 10 Languages
Virto Commerce Engine, the backend of the platform, has been available in 10 languages since October 2024 (English, German, French, Spanish, Portuguese, Polish, Italian, Chinese, Japanese, and Russian), so international teams can work in their own language.
☑️ Multi-Regional Support
On the customer side, the platform supports multi-regional, multi-language, and multi-currency settings, custom pipelines, compliance and verification methods, and the permission assignments that multi-vendor marketplaces need.
Conclusion
For large B2B ecommerce, we recommend a five-layer, headless, API-first platform your team can extend, run by the vendor or by your own team.
HEINEKEN, Bosch, De Klok Dranken and Standaard Boekhandel run their B2B commerce on Virto Commerce; their results are in our case studies. To go deeper, download our Architectural Guidelines or talk to our team.