Skip to main content
The Solution Architecture guide offers a thorough overview of the application concepts, architectural framework, and key integration points that are essential for the successful deployment and integration of the OroCommerce application. It explores the necessary cloud services and infrastructure components needed for a smooth and efficient implementation process.

Concepts

Key features distinguishing back-office and storefront, access control, product catalog, pricing, inventory, customer handling, sales flow, multi-website support, and versioning.

Integration Points

OroCommerce integration capabilities, available interfaces, common use cases, real-world examples, and their impact on user experience.

Cloud and Infrastructure

Deployment architecture, infrastructure services, environment types, network segmentation, security measures, and support options.

Key Concepts Overview

OroCommerce provides two distinct scopes of access:Back-Office is designed for organizational users — administrators, sales representatives, marketers, and content managers — responsible for managing the application’s configurations and data.Storefront is tailored for buyers, allowing them to browse the product catalog, access account information, request quotes, and submit orders.
AspectBack-OfficeStorefront
Primary rolesAdministrator, Seller, Sales Representative, Marketing ManagerBuyer
User entityUserCustomer User
Company entityBusiness UnitCustomer
Organization entityOrganizationWebsite
TemplatingTwig templatesLayout engine + Twig templates
ThemeBasic styling customizationFull styling customization

Multi-Level Configuration

OroCommerce allows setting values for system configuration options on multiple levels. Each higher level may override values from the lower level. For example, a website-level configuration overrides the same values from the organization or global levels.
  1. Global — system-wide defaults applying to all organizations and websites
  2. Organization — overrides global settings for a specific organization
  3. Website — overrides organization settings for a specific storefront website
  4. Customer Group — overrides website settings for a group of customers
  5. Customer — overrides customer group settings for a specific customer
Many deployments require multiple storefronts (websites). Each website has its own set of configuration options and enabled features. Websites are identified by domain, cookie value, or environment variable.Key per-website configurable features include:
  • Routing — domain name, canonical URLs, web catalog, navigation menu, guest access
  • Localization — default and enabled localizations
  • Design — theme, page template, menu template
  • Sales Flow — shopping list options, checkout options, RFQ, quotes, order history
  • Search — search terms, saved search, fuzzy search, synonyms, stopwords
Every website must belong to one organization. To share a data set (master catalog, products, pricing, customers) across websites, place those websites under the same organization.

Build docs developers (and LLMs) love