Sylius official features: multi-channel and B2B in 2026
The official features of the Sylius ecommerce platform fall into two groups in 2026. The free Symfony core offers channels, promotions, catalogue, API and admin. Multi-store management across business units, the B2B Suite, returns and multi-source inventory come with the commercial Plus offer. If you are comparing with Magento, that split is the first thing to check, as it decides what you pay for and what you build.
Feature inventory: free core versus Plus
The vendor's comparison page lists these under Plus: B2B Suite, Marketplace Suite, advanced multi-store, advanced user permissions, returns management, multi-source inventory, partial order fulfilment, admins per channel, a loyalty system, multiple pricing lists, advanced search and one page checkout. Modules can be bought individually, and pricing depends on online sales and on the modules chosen. The free edition stays under MIT.
| Need | Free core | Sylius Plus | Adobe Commerce |
|---|---|---|---|
| Several storefronts | Yes, channels | Yes, plus business units | Yes, websites, stores, store views |
| Company accounts | Not as listed | B2B Suite | B2B extension |
| Customer price lists | Not as listed | B2B Suite | Shared catalogues |
| Negotiated quotes | Not as listed | Quote module | Negotiable quotes |
| Purchase order approval | Not as listed | Ask the vendor | Purchase orders |
"Not as listed" means the official sources I read do not present it as a core feature. It does not mean it is impossible: on Sylius, a missing feature can be developed, and the decision is whether that costs less than the module.
Multi-channel: what is native and what is not
A channel, in the words of the official guide, represents a single storefront, with its own hostname, locales, currencies, billing details and tax configuration. Every product, order and customer belongs to one. In version 2.3, promotions gain per channel rules and actions, which helps when a discount must apply in one country only.
For most mid sized merchants, channels will be enough. The Plus multi-store module targets companies working across legal entities or business units, and "admins per channel" matters once separate teams must not see each other's orders. Magento takes a different approach with its three level hierarchy of websites, stores and store views. It is more elaborate out of the box, and that is both its strength and the source of its complexity.
B2B on Sylius: what the official sources say
The B2B Suite listing describes company accounts in which several users share addresses, order history and billing data, multiple price lists, quick ordering by SKU, multiple wishlists and a layer for data exchange with ERP or PIM systems (software that holds your stock and product data). Quotes are in a separate module: the buyer asks from the cart, the seller makes an offer, and the buyer accepts or replies until both agree.
Sylius's Elesto article presents a preconfigured B2B example for manufacturers and wholesalers and says the module was tested with over 200,000 products and one million variants. Take that as a vendor claim. A deeper look is in the article on accounts, roles and pricing.
Sylius or Magento: the honest differences
Adobe Commerce's B2B documentation describes company accounts with roles and divisions, shared catalogues, requisition lists, negotiable quotes, purchase orders with approval rules and payment on account. On paper, that is broader than the Sylius listings. If those functions match how your buyers already work, Adobe gets you closer to the goal without custom development, and it is the better choice, provided you can fund the people who know it.
Sylius has the advantage on code clarity and on custom logic. It runs on Symfony, with version 2.3 requiring PHP 8.3 and accepting Symfony 6.4, 7.4 or 8, so common Symfony skills apply directly. Magento uses its own conventions, which require specific experience. That is my professional view, and I work on Sylius rather than on Magento, so weigh it accordingly.
On timing, both keep shipping. Magento 2.4.9 arrived on 12 May 2026, and Sylius 1.14 leaves security support on 31 December 2026. If you run either, an upgrade plan belongs in your budget.
A compatibility check to do before signing
Here is a concrete detail buyers miss. When I read them, the B2B Suite and quote module listings showed a Sylius version range ending at 2.2, while 2.3 had been out since 28 September 2026. The pages may lag behind reality, or the module may need time to catch up. Either way, it affects your launch version, and 2.2 security support ends on 31 March 2027. Ask the vendor for written confirmation of the exact compatible versions.
When neither is the right answer
If you are a small B2B seller with a few customer groups, Shopify's B2B features may be enough at a much lower running cost. Before any platform decision, write down how a real order moves through your company, from request to invoice. This document costs nothing, and it reveals most of the true requirements.
Next step
I develop and maintain Sylius shops and custom applications, working alone and answering directly. If your requirements are written down, even roughly, send them through the Sylius developer page. You will get a clear opinion on what the platform does natively, what needs development, and whether Magento would serve you better.
