Sylius Plus B2B features: accounts, roles and quotes
The official Sylius Plus B2B features are organisation accounts, multiple pricing lists, quick ordering, multiple wishlists and Elasticsearch search in the B2B Suite, with quotes and back office roles as separate modules. No price is published for these modules: Plus starts from 800 euros a year, then it is a quote. Before buying, check two things that are easy to confuse or overlook: which kind of roles you need, and whether the modules support your Sylius version.
The official Sylius Plus B2B features, module by module
This table summarises the vendor's listings as I read them on 1 November 2026. It describes claims from Sylius, not tests that I ran.
| Module | What it provides | Listed Sylius versions |
|---|---|---|
| B2B Suite | Company accounts, price lists, quick ordering by SKU, reordering, wishlists, Elasticsearch search, ERP or PIM import and export layer | 1.11 to 2.2 |
| Request for Quotation | Quote request from the cart, admin panel, negotiation, conversion into an order | 1.13 to 2.2 |
| RBAC | Back office roles, permission tree, limits by channel or catalogue section | 1.11 to 2.2 |
The last column deserves attention: Sylius 2.3 came out in September 2026, and these listings do not name it. They may simply be lagging, as the same pages also say "1.11 and higher". Since security support for 2.2 ends on 31 March 2027, ask for a written answer on this point.
Company accounts: what is shared
The B2B Suite groups several users under one company account. They share addresses, order history and billing data. The Sylius overview describes this as one master account. For a customer whose buying is decentralised, this removes the familiar workaround of a single login passed around the office.
Sharing also raises a question to check with your customers: should a buyer in one department see all the company's orders and invoices? The Elesto page says that order history, invoices and billing data stay visible to the whole organisation, and that users can have different permission levels. Ask to see in the demo how far those levels go.
Roles: two different subjects
The search term "roles" hides a common misunderstanding. RBAC, or role based access control, deals with your staff. The module lets you create roles, define permissions, and limit an admin to certain channels or catalogue sections. Its listing focuses on back office access. It does not tell you what one of your customer's buyers can do on the shop.
Permissions on the buyer side form a separate need. The B2B Suite overview I read does not mention approval workflows, and its listing does not describe roles in detail. If your customers need a junior buyer to submit an order for approval by a manager, treat this as an open question. It may be part of what you have to build, whichever edition you choose.
Pricing: the features and the licence
As a feature, pricing lists let you set dedicated prices for an organisation or a customer group. The Elesto page adds category wide percentage discounts and quantity based tiers. For many wholesale businesses, this is the most valuable item, unless your prices already live in an ERP. In that case, the question becomes how they get synchronised and how often.
As a cost, the module pages publish no price. The Plus page gives only the entry point and says that pricing depends on your online sales and the modules you choose. It also claims that the B2B Suite can save up to 40% on implementation. That is a vendor's figure with no method given on that page, so ask how it was calculated. For context on what the licence covers overall, see my comparison of Sylius and Sylius Plus. None of these figures reflects my own rates.
Quotes: useful, but check the process
The Request for Quotation module lets a customer submit their cart as a request. Your sales team then prepares an offer and adjusts prices, quantities or conditions, and an accepted offer converts into a standard order. Comments and attachments are part of the exchange. This suits businesses that negotiate on each order. If your quotes are built in a CRM or an ERP, the real question is how the two systems will avoid duplicate work, and the module page does not settle it for you.
Questions the listings do not answer
Bring these to your vendor call. Which module versions support the Sylius version I will run in production? How far do buyer permissions go, and is approval included? Can my developer read and extend the code? The listings mention extension through Symfony services, events and Doctrine entities, but confirm the terms under the proprietary licence. What happens if I stop paying? What would my price be if my sales double? Is implementation support included or billed apart?
When Plus is not the right purchase
If you only need a few customer groups with a discount, the other routes to Sylius B2B may be sufficient, including community plugins and limited custom work. Conversely, if your needs match these modules closely and you want a vendor commitment, paying for them is likely to be more sensible than asking someone like me to rebuild them. I am an independent developer, not a Sylius partner, and I can also implement these modules for a fee, so I do have an interest in the outcome.
Next step
Request a demo, and use your own real order as the test scenario rather than the standard presentation. If you want someone technical at your side to prepare that call or to review the answers, you can contact me through my Sylius developer page.