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.

Architecture Principles of Oro Applications 

Symfony Role in OroPlatform 


We use Symfony Framework v. 5.4 LTS in Oro Applications v.5.x.

Symfony is the most mature PHP framework that provides a wide range of functions typical for any web application. Symfony takes care of numerous tasks, for instance:

  • Receiving a user request and transforming it into a response for the user’s browser

  • Organizing the source code in a conventional structure

  • Providing tools for continuous storage of application data, validation of income data against some set of rules

  • etc.

For more information on Symfony, its purpose and benefits, see the following articles on the Symfony website:

Using Symfony allows web applications to avoid the development of low-level components responsible for the application’s organization and focus on developing a functionality specific to a particular web application.

Oro applications have a lot in common with regular Symfony applications based on the 3rd version of the framework. So, if you are not familiar with Symfony yet - start your acquaintance with the Oro application from the Getting Started and Guides sections of the official Symfony documentation.

Many Symfony features substantially impacted the architecture of all Oro applications. Some are listed below with the description of how they were adjusted for Oro applications compared to other Symfony-based applications.

HTTP Request Application Flow 

Symfony framework (and its HttpKernel Component) determines the main flow of the Oro web application, i.e., the transformation of user requests into responses.

This flow in Oro applications is similar to the flows of other Symfony applications , in particular:

  1. A client sends an HTTP request to the application.

  2. The request is executed by the application’s front controller (index.php) file, which takes a request, boots the application, and passes the request information.

  3. Internally, the application uses registered routes, controllers, event dispatchers, and event subscribers to process the request and create a response object.

  4. The application turns the response object into the text headers and content, which are sent back to the client.

Oro HTTP Request Application Flow

This routine defines several important architectural features of Oro applications, such as using the Front Controller and MVC structural patterns and an Event system to organize the application functionality and manage the application flow.

Event System 

Oro applications actively use Symfony Event Dispatcher to create and use the points of functional extension and control of the application flow.

As illustrated throughout the Developer Guide, a significant part of the Oro application’s functionality allows you to adjust the application behavior by creating listeners or subscribers for system events.

Inversion of Control Principle 

The Inversion of Control principle is widely used in the architecture of Oro applications to loosen the coupling between classes and objects, facilitate extensibility and eliminate code duplication.

The principle is embodied in the | Symfony’s Service container| and the Dependency Injection Component used to create and manage all objects and organize their interaction in Oro applications.

Bundle System 

The bundle system is one of the main principles of feature and code organization in Oro applications. However, there are some differences in it between the Symfony framework and Oro applications.

At the beginning of Oro applications’ development, there were certain constraints with the Symfony bundle management system that we decided to address, namely:

  • Installing a bundle was too cumbersome

  • Removing a bundle was even more cumbersome

As a workaround, we changed the bundle registration system in Oro applications so that the bundles acquired the option of auto-registration in the application without needing to modify any of the application files.

For the bundle to be registered and enabled in Oro applications, it is sufficient to mention the bundle in its Resources/config/oro/bundles.yml file. You can activate any bundle in the application by putting its primary class name in the Resources/config/oro/bundles.yml of your bundle (keep in mind, though, that you must physically install the bundle with the help of Composer).

    - { name: Acme\Bundle\DemoBundle\AcmeDemoBundle, priority: 70 }


For more details on creating a bundle, please refer to the How to Create a New Bundle topic.

Application Directory Structure 

Oro applications follow Symfony’s recommendations to organize the structure of the application files and source code.

Please refer to the Architecture Guide for the detailed description of Oro application directory structure.

Application Configuration 

Oro widely uses Symfony conventions to configure the application and specific features in YAML configuration files.

On the application level (according to Symfony conventions), the configuration is divided into infrastructure-related (.env-app) and application-related (config/config.yml file).

On the bundle level, Oro applications have slight changes in the configuration technologies but a considerable shift in the role and purpose of the configuration files.

Simultaneously with bundle auto-registration in the Resources/config/oro/bundles.yml file, the policy of auto-registration of the feature’s configuration files that follow special naming conventions was enabled.

For example, the files called

  • Resource/config/oro/api.yml

  • Resource/config/oro/navigation.yml

  • Resource/config/oro/datagrids.yml

are auto-discovered and applied to the configuration of corresponding features.

The role of the configuration files underwent the most changes. In the Oro application, Yaml configuration files of many features are used not only to configure a feature but also to create parts of the application functionality.

For example, there are three ways in Oro applications to create navigation items in the UI:

  1. Use admin UI to manage the navigation items.

  2. Declare new navigation items in the DI service with a special dependency injection tag “oro_menu.builder”

  3. Add navigation item information to the Resources/config/oro/navigation.yml file of your bundle:

                label: New Menu Item
                route: acme_demo_new

                    new_menu_item: ~

Templating System 

Symfony Templating is widely extended in Oro Applications by the Layouts concept, which allows addressing Symfony’s limitations in UI extension and composition.

However, all features of the TWIG templating engine and Symfony Templating Component are widely used in Oro applications in UI building.

We recommend you get acquainted with the Symfony Templating documentation to work with Oro applications.

Security System (Data Access Management) 

Data Access Management in OroPlatform is based on the proprietary Role Based Access Control system as it is necessary for business applications.


More information on this is available in the next section of this guide which is dedicated to OroPlatform and its Security System.

However, this RBAC system of Oro applications widely uses Symfony Security Components. It is, therefore, vital that you familiarize yourself with them to be able to work with Oro applications.

Databases Management (Doctrine ORM) 

Oro applications support the storage of application data in relational databases, such as PostgreSQL, EnterpriseDB. Support for these databases is provided by the Doctrine layer.

Oro applications widely use all Doctrine features to manage the persistent data: Database Abstraction Layer, Object Relation Mapping, Event Manager, etc.

However, Doctrine Migrations, one of the most popular Doctrine projects, was entirely replaced by proprietary. It allows for versioning management of the database schema using specific migration classes on the bundle level, not the application level.

Because the Oro application functionality is constantly evolving, it was essential to be able to extend the Doctrine data types and DQL functions. As a result, the Oro Doctrine Extensions component was created.

CLI Application 

All Symfony-based applications come with a command line interface tool (bin/console) that helps you maintain your application. It provides commands that boost your productivity by automating tedious and repetitive tasks, such as clearing the application cache, debugging routing, viewing the list of registered commands, etc.

Oro application follows this convention and extends the set of the CLI tools by commands for:

  • Database migrations management (see Databases Management (Doctrine ORM) above)

  • Translations management

  • Application upgrading

  • Periodical task management

  • Unit tests generation

  • etc.

To see all Oro applications console commands, run the following command in the console:

php bin/console list oro

List of Symfony Components Used in Oro Applications 

Symfony is a set of program components and a web framework. Components represent separate independent parts of the functionality used to perform typical web programming tasks, while the framework is a functionality responsible for organizing the interaction of these independent components in a web application.

Description of Symfony’s contribution to the Oro applications architecture would not be complete without mentioning Symfony components that are actively used in the development of Oro applications:

You must be familiar with these components to work comfortably with Oro applications.