Important

You are browsing documentation for version 5.1 of OroCommerce, supported until March 2026. Read the documentation for version 6.0 (the latest LTS version) to get up-to-date information.

See our Release Process documentation for more information on the currently supported and upcoming releases.

Application Architecture

What is Oro Application

Oro application is a PHP web application that uses the Symfony framework. It provides the following benefits:

• Runs on any OS, although Linux is recommended. See system requirements for more information.

• Scalable - Oro application can be easily scaled up and down to meet your company needs (message queue, indexes, search).

• Extendable - Oro application can be extended via the packages from the Oro Extensions Store designed by Oro, Oro partners, or the Oro community. Also, you can design your own packages to implement additional functionality.

• Customizable - The Oro application inherits most of the development techniques enabled by the Symfony framework and extends them. It helps quickly customize the Oro application for any business needs.

With these out-of-the-box benefits, developers can focus on implementing their unique business logic and build Oro-based applications in less time.

Oro Licensing

Community versions of Oro applications are distributed under the OSL-3.0 license. The community edition of OroPlatform is distributed under the MIT license. Enterprise editions of Oro applications are distributed under a custom End User License Agreement.

Architecture Overview

• Technology Stack
  • Client Side
    • Web Browser
    • API Client
  • Server Side
    • Oro PHP Application
    • Web Server and PHP
    • Database and RDBMS
    • File Storage
    • Session Storage
    • Message Queue
    • Search Engine
    • Notes on Deployment Options
• Application Structure
  • Source Code Repositories
  • Distribution Model
  • File System Structure
    • Oro PHP Application File System Structure
    • Oro Package File System Structure
• Application Framework
  • How It Works
  • Getting Started
    • Prepare Your Custom Application
    • Create a New Functionality
    • Change an Existing Functionality
    • Create and Publish an Extension
  • Related Cookbook Articles
    • Architecture Principles of Oro Applications
• Application Customization
  • Customize the Source Code
    • Prepare for Source Code Customization
    • Implement the Customization
    • Publish Your Complete Customization as a Package on the Oro Extensions Store
  • Customize via UI
  • Related Articles
• Differences to Common Symfony Applications
  • The Application Kernel
  • Routing Configuration
  • Access Control Lists
  • Extension Management
  • Related Articles
• Custom Oro Application
  • Application Repository and Installation
  • Application Custom Code
  • Application Deployment
  • Related Articles
• Bundle-less Structure
  • Application-level Structure Changes
  • Moving Existing Bundle to Bundle-less Structure
    • Migrations
    • Fixtures
    • Entity
    • Controllers
    • Views
    • Translations
    • Gridview
    • Search
    • Navigation
    • Entity
    • ACLS
    • API
    • Channels
    • Charts
    • Workflows
    • Processes
    • ACL Categories
    • Address Format
    • API Frontend
    • Application Base Configuration
    • Configurable Permissions
    • Dashboards
    • Entity Extend
    • Entity Hidden Fields
    • Locale Data
    • Naming Format
    • Permissions
    • Placeholders
    • System Configurations
    • Cache Metadata
  • Moving Extension and Configuration
  • Themes & Layouts
    • Asset Handling in Application Development
    • Overriding SASS Variables
    • Referencing Assets Using the asset() Function in Twig
    • JS Modules
    • Admin Theme Configuration
  • Tests

Business Tip

Are you in the process of selecting the best eCommerce platform for B2B? Evaluate nine alternatives on our B2B comparison page.