Sylius B2B features: accounts, roles, pricing, quotes
The official Sylius B2B features are mostly found in the B2B Suite, a proprietary Sylius Plus module: company accounts with shared data, price lists for each organisation, quick ordering and an ERP data layer. Roles and permissions exist at organisation level, quotes sit in a separate module, and API access is documented for price lists. The free MIT core does not present these as standard features, so a B2B project on Sylius begins with a licensing decision.
Company accounts: what is shared and what is not
The B2B Suite listing describes organisation management as company accounts holding several users who share addresses, order history and billing data. Sylius's module overview adds the idea of a single master account serving a whole organisation.
This suits most wholesale relationships, where an office manager and a warehouse lead must see the same history. It raises a question for groups, though. If a client has several subsidiaries that must not see each other's orders or invoices, you need to test how far the shared model goes. Shared data is a feature until the day it reveals the wrong invoice to the wrong person.
Roles and permissions: two different things
People often confuse two systems here. The first is on the buyer side: Sylius's Elesto article says several users can belong to one organisation with different permission levels, with admins managing members and access. The second is on your side: RBAC (role based access control) restricts what your own employees can do in the admin panel, depending on their job. They solve different problems, so name both in your specification.
I did not find a public, detailed list of the buyer side permissions, and the earlier module overview does not describe them. Purchase order approval is also not presented as a standard feature in the pages I read, although Elesto's shopping lists are described as useful for project purchasing and budget approval. If your clients' purchasing rules include "above this amount, a manager must approve", ask for a live demo of that exact case. If the answer is custom development, price it now.
Pricing and catalog: the strongest part of the offer
This is where the suite is most specific. According to the Elesto article, the pricing engine supports price lists per organisation, percentage discounts by category and tier pricing based on quantity. The pricing engine documentation, which requires a login, also covers assigning lists to customer groups or organisations, along with API operations to create, update, assign and delete them. That API matters if your ERP is the source of truth for prices, because your developer can sync the two without manual entry.
On catalog handling, the listing mentions SKU based quick ordering, Elasticsearch integration for large catalogs and an import and export layer for ERP or PIM systems. Elesto adds file import for quick orders and a claim of testing with over 200,000 products and one million variants. That is a vendor figure, so check it on your hosting with your data. A buyer's real test is simple: can your most demanding customer place their usual 80 line order in a minute?
Quotes: a separate module
Quotes are not in the base suite. The RFQ module (request for quotation) lets a customer ask for a quote from the cart. Your sales team then prepares an offer with adjusted prices, quantities, notes and attachments in the admin. The buyer accepts, which creates an order, or replies to keep negotiating, and the history stays in the admin. The module is proprietary and works with company accounts.
| Need | Official source | Status to verify |
|---|---|---|
| Company accounts | B2B Suite | Separation between subsidiaries |
| Buyer permissions | Elesto article | Exact list, ask for a demo |
| Staff permissions | RBAC, Sylius Plus | Licensed separately? |
| Customer prices | Pricing engine | Sync direction with your ERP |
| Quotes | RFQ module | Additional licence cost |
| Formal approval | Not found as standard | Likely custom work |
What the B2B Suite leaves you to do
The listing reads like a finished product, so here is the question I would raise on each line. "Custom data synchronisation" is an integration layer, and no specific connector is named: on most B2B projects the ERP is where the budget goes.
| Feature | What Sylius describes | What usually remains |
|---|---|---|
| Organization management | Company accounts, shared addresses, order history, billing data | Your onboarding and validation of new companies |
| Multiple pricing lists | Prices for organizations or customer groups | Price sync if your ERP is the master |
| Quick shopping | SKU search and a dedicated interface for large orders | Adapting the screen to how your buyers really order |
| Order management | Create, customise, reorder | Rules when products were withdrawn or repriced |
| Enhanced search | Elasticsearch, for larger catalogues | Hosting and tuning one more service |
| Import and export layer | Custom synchronisation with ERP or PIM | The integration itself |
It can be overkill if you sell to professionals with one price list, one user per company and invoices handled elsewhere. Sylius's modular licence article lists B2B Suite and RBAC as separately purchasable modules, so clarify in your quote which ones are included. Elesto, a reference B2B project delivered with source code, is a useful way to evaluate them: a demonstration of your own scenarios will tell you more than any feature table.
One sentence on the Sylius Plus page also deserves attention: it says the Standard edition does not allow placing orders in the customer's name, without explicitly saying that Plus does. If your sales reps order on behalf of clients, have this demonstrated. Then bring these questions to your vendor call: can my developer read and extend the code under the proprietary licence, what happens if I stop paying, what would my price be if my sales double, and is implementation support included?
API, architecture and version compatibility
The suite is designed to be extended using Symfony services and events, Doctrine entities and Twig templates, so a Symfony developer can add your rules with familiar tools. Here is my main caution for November 2026: the suite's version field showed 1.11 to 2.2, and the quote module's showed 1.13 to 2.2, whereas Sylius 2.3 came out on 28 September 2026. Listings can trail releases, so ask the vendor for written confirmation. It matters since 2.2 security support ends on 31 March 2027.
On cost, the listing has no price, only a quote form. The Plus page states a start from €800 a year and says the price is based on online sales and on the modules chosen, and that it can save up to 40% on implementing B2B systems. That percentage is the vendor's own marketing claim.
When Sylius B2B is the wrong choice
If your flow is simple, with a few customer groups, net terms and quantity rules, Shopify's B2B tools may do the job for less. If you need deep native approval chains, credit lines and role hierarchies, Adobe Commerce documents more of these out of the box. Sylius B2B makes sense when your pricing or ordering rules are specific enough that you will be writing code in any case, and you want that code on a clean Symfony base.
A sensible next step
Write out one real order, from the buyer's request to the invoice, including the exceptions. I work on Sylius projects, so I have an interest in the outcome, but that scenario will show you the truth about any platform. Send it through the Sylius developer page and I will tell you what fits as is, what needs development and what should stay outside the shop.