Sylius B2B: company accounts, roles and permissions
For Sylius B2B ecommerce, company accounts, price lists and quick ordering come from the B2B Suite, quotes from the Request for Quote module, and admin permissions from a separate RBAC module, all of them commercial Sylius Plus modules. Public official material on these features is mostly product pages, with little technical documentation that I could find. So build your requirements list first, then have each line demonstrated.
I build Sylius shops for a living, so I have a stake in this subject. I present no B2B Suite project of my own here. I checked these pages on 1 November 2026, and the docs.sylius.com site did not open to me without signing in, which limits what I can state about the technical documentation.
Where company accounts, roles and permissions live
The main trap in any evaluation is the word "permissions", because it covers two different populations. One concerns your customer's employees: who may order, see invoices, manage colleagues. The other concerns your own staff in the admin panel. The two are handled in different places.
| Requirement | Where Sylius describes it | What to verify |
|---|---|---|
| Company accounts with several users | B2B Suite: organization management | Shared addresses, order history, billing data |
| Roles for buyers within a company | Elesto: different permission levels per user | Whether your exact roles exist or need development |
| Roles for your own staff | RBAC module, for the admin panel | Separate purchase, scope of restrictions |
| Customer specific pricing | Multiple pricing lists | Sync with your ERP as the price master |
| Quotes and negotiation | Request for Quote module | Interaction with your sales process and tax rules |
| Reordering | B2B Suite, Elesto | Behaviour when prices or stock changed |
| Formal approval workflow | Not described in the pages I read | Ask for a demonstration, budget custom work |
The B2B Suite listing describes organization management as company accounts whose users share addresses, order history and billing data. The Elesto article adds that users in an organization can hold different permission levels, that administrators can manage team members, and it points to RBAC for finer control. The Sylius Plus page lists advanced user permissions as a Plus feature.
Read that overlap carefully before you sign. If your scenario is "a buyer may order up to a limit and a manager approves above it", no page I read promises it. Elesto mentions shopping lists that let one team prepare, another approve the budget and another finalise, which describes a way of working with lists, and not necessarily an enforced rule.
Pricing, quotes and orders in the official material
Pricing is well covered in the descriptions. The B2B Suite offers lists for specific organizations or customer groups, and Elesto mentions percentage discounts by category and tier pricing by quantity. The question to ask is who owns the price. When your ERP holds the truth, the listing's import and export layer is described as custom data synchronisation, so plan for development work.
The Request for Quote module lets customers request a quote from the cart, gives sales teams an admin view to adjust pricing and terms, tracks the negotiation, and converts accepted offers into standard orders. Its listing shows version 3.1.1, updated on 1 June 2026.
On orders, one sentence deserves your attention. The Sylius Plus page says the Standard edition does not allow placing orders in the customer's name. It does not explicitly say that Plus does. If your sales reps order on behalf of clients, have this demonstrated.
Version and licence: the checks people skip
Compatibility needs a written answer. The B2B Suite listing shows Sylius "1.11 to 2.2" in one place and "1.11 and higher" in another. The RFQ listing shows 1.13 to 2.2, and Elesto shows 2.1 and higher. Yet Sylius 2.3 has been out since September 2026, and support for 2.2 ends on 31 March 2027. Ask Sylius or your integrator which module versions run on 2.3.
None of these listings publishes a price; each one leads to a quote form. The Plus page says pricing starts from 800 euros a year, based on online sales volume and modules. I cover the cost in more detail in my article on Sylius pricing.
When Sylius is not the right B2B choice
If your rules fit a standard pattern and you have no developer, a hosted platform with built-in B2B features may serve you better; compare it with what Shopify Plus offers for B2B before you decide. Sylius makes sense when your pricing, approval or ERP rules are specific enough to justify development and maintenance.
If you want to avoid the licence, you can build on Community Edition. Third party packages exist, such as a company accounts plugin for Sylius 2 under the MIT licence. It is not part of Sylius Plus, I have not audited it, and you would need to check who maintains it and for how long.
What to do next
Write your scenarios as sentences: who buys, who approves, who sees which price, who can see which invoice. Ask for a live demonstration, and Sylius offers a public demo to start with. Mark each line as covered, configurable or custom, then ask for the estimate on the last category.
If you want help with that table, see my e-commerce services or my Sylius developer page. My Sylius takeover reference, Coucouroucoucou, is a Belgian shop with about 15,000 orders retained, and it is not a B2B Suite project, so I would treat your requirements with the same scrutiny as above.