Sylius ecommerce platform in 2026: editions and features

The Sylius ecommerce platform in 2026 is an open source framework built on Symfony, with a REST API, multi store channels and two editions: a free MIT core and the commercial Sylius Plus. It is a good solution when your shop has rules that packaged software handles badly and you can pay a developer to own the code. It is a poor one when you want a store running next week without any technical partner.

What Sylius is, in plain terms

Sylius is not a subscription you switch on. Its public repository describes a headless open source platform on top of PHP, Symfony and API Platform. "Headless" means the storefront can be separate from the engine, so a website, a mobile app or a kiosk can all talk to the same back end through an API. Symfony is a widely used PHP framework, which matters to a buyer for a simple reason: the code follows conventions that other developers already know, so you are less tied to one supplier.

The price of that freedom is that nothing arrives finished. You get a solid base and an admin panel, then someone adapts it to your business. I earn my living from this kind of work, so read my opinion knowing that I have an interest in the subject. The sources below let you check every factual claim yourself.

Sylius editions in 2026: Standard, Plus and the prebuilt setups

The vendor's Plus page compares two levels. The free one, called Sylius Standard there and Community Edition in the documentation, is under the MIT licence with community support and no guaranteed response time. Plus is commercial, with contractual support and a stated one day response time. The same page says pricing "starts from 800€ / year" and depends on online sales volume and on the modules chosen, and that modules can be bought one at a time. Treat that figure as an entry point, and ask for a written quote based on your own sales.

The vendor's site also lists Elesto, a preconfigured B2B setup for manufacturers and wholesalers, and Dafre, a setup with multi-vendor logic for marketplaces. These are starting points for specific business models, and you should ask the vendor what licence each one requires.

Symfony, documentation and API: what a technical reviewer will check

Version 2.3, released on 28 September 2026, requires PHP 8.3 and accepts Symfony 6.4, 7.4 or 8, plus API Platform 4.3 or 5. The Payment Request API, which handles communication with payment providers, is no longer experimental. The release also adds per channel promotion rules, a dark mode for the admin and locking that prevents a coupon from being redeemed too many times. These are useful details, and they show that the project keeps moving.

The documentation has one trap for evaluators. Getting started pages are public, while The Book, the complete reference, requires a login. Your developer should create an account before forming a view of the depth of the docs. A separate article covers how to read the architecture and API documentation.

Channels and multi store: the feature people misread

The basic configuration guide defines a channel as a single storefront, holding its hostname, locales, currencies, billing details and tax configuration. It adds that each channel has one base currency, used to store prices internally, while other currencies are displayed through exchange rates. That base currency deserves a real decision before products are created, because the guide tells you to set it first.

So one free installation can already serve a French site and a Belgian site from one back office. What Plus adds is an organisational layer: a multi-store module that assigns channels to business units, for companies operating across several legal entities. If you are one company with two domains, you may never need it.

Support dates you should put in your calendar

According to endoflife.date, security support for Sylius 1.14 ends on 31 December 2026 and for 2.2 on 31 March 2027, while 2.1 ended on 30 September 2026. Security fixes do land regularly: the October 2026 release covered 1.14.21, 2.1.17, 2.2.12 and 2.3.2. A Sylius shop therefore has a recurring cost that a hosted subscription hides inside its monthly fee: someone must apply these updates and test them against your custom code.

When Sylius is not the right choice

If your catalogue is simple and your process is standard, Sylius will cost you more than it returns. A hosted platform gives you a working store faster, and the money saved can go into marketing. The same applies when no one will own the code after launch: a custom shop without a maintenance plan ages badly, and the risk is an unpatched store taking payments. There is also a case against me specifically. If your board requires a supplier listed by the vendor, or a team able to absorb several parallel projects, start with the partner directory, because I work alone.

Sylius earns its place when you have unusual pricing, complex checkout rules, several integrations with an ERP (the software that runs stock and accounting), or a shop that has outgrown its current tool. Before you commit, ask any supplier three questions: who owns the code and the servers, which version will the shop launch on, and who applies security releases and at what cost.

A simple next step

I build, take over, audit and maintain Sylius shops, and you talk directly to the person writing the code. One example is Coucouroucoucou, a Belgian Sylius store taken over with about 15,000 orders, along with customers and invoices, without interrupting sales. If you are still unsure whether the platform fits, send me your constraints through the Sylius developer page: you will get a straight answer, and it may be that you need something simpler.