Does Sylius Standard include company accounts?

Not as a dedicated feature in what I could verify. Sylius sells organisation accounts through the B2B Suite, and community plugins offer an alternative. Customer groups do exist as a condition for cart promotions.

Can Sylius manage customer specific prices?

Yes, with additional work. Standard prices are stored per channel, whereas price lists for specific organisations or customer groups come with the B2B Suite. A community plugin or custom code can also handle such rules.

Is a community plugin safe for a B2B shop?

It can be, but check who maintains it, how often it is released and what it leaves out. Have your developer read the code, since you take on the risk if the author moves on.

Does Sylius handle quotes?

The official Request for Quotation module lets customers submit a request from the cart, negotiate, and convert an accepted offer into an order. It is a paid module, and its listing names versions 1.13 to 2.2.

Sylius B2B ecommerce: three ways to build it in 2026

Sylius B2B ecommerce can be built in three ways in 2026: buy the official B2B Suite from Sylius Plus, add community plugins to the open source edition, or develop only what you need. The official documentation shows that company accounts, organisation price lists and quotes are not all part of the free core. The right route depends mainly on how your customers really buy, and on who will maintain the result.

What the official documentation covers in the free core

The open source edition is a solid base for B2B work, but you should know where it stops. Prices are saved per channel, in the base currency of each channel, so you can separate a trade shop from a public one. Cart promotions can be conditional on a customer group. That lets you handle simple cases, like a discount for a family of resellers, without any extra licence.

The limit appears when several people buy for one company, when a customer has their own negotiated price list, or when a purchase begins with a quote. In the features I could verify, those needs are served outside the free core. That is the point to clarify with your provider before you estimate anything.

The three routes compared

Need	Official B2B Suite and modules	Community plugin	Custom development
Company accounts	Organisation accounts with shared addresses, orders and billing data	tmonier company accounts, MIT, members with admin, buyer or approver roles	Exactly your model
Negotiated pricing	Price lists by organisation or group	tmonier tier pricing, rules per channel and customer group	Exactly your rules
Quotes	Request for Quotation module	Check availability for your version	Built to your sales process
Who answers if it breaks	Vendor, under commercial terms	Your developer	Your developer

On the official side, Sylius describes a demonstration project named Elesto, built on the B2B Suite, as an example of how customer catalogues, bulk ordering and multi buyer accounts fit together. It also covers category percentage discounts and quantity based tier pricing. Looking at this demo is a good way to compare what you imagine against what exists. Official pricing and contents are covered in my comparison of Sylius and Sylius Plus.

Read the limits before choosing a plugin

Community plugins look attractive because they are free and sometimes quite recent. The company accounts plugin mentioned above is a good example of why reading matters. Its page is honest about what it does not do in the current version: one company per customer, no subsidiaries, no invitations, no spending limits, no order approval, and no VIES check of the VAT number. It also requires Sylius 2.2.9 or 2.3. For one business, that is entirely sufficient. For another, the missing approval flow rules it out on day one. I have not audited this code and I am not recommending it over another: I cite it because its public documentation is precise.

Compatibility works the other way for the official modules. The B2B Suite page names versions 1.11 to 2.2, and the quote module 1.13 to 2.2. If you plan to launch on 2.3, get written confirmation from Sylius first.

Start from the buying process, not the feature list

The most useful B2B specification I can suggest fits on one page. Who places the order: one person or several? Does somebody need to approve above a certain amount? Where does the customer price come from: a list, a negotiation, or your ERP? Do customers reorder the same items, sometimes by reference? How is payment made: on order, or on invoice with terms? Which system holds the truth on stock and prices?

The answers decide most of the architecture. A customer who reorders 200 references every month needs a fast order form more than a beautiful catalogue. An ERP that holds the prices makes a synchronisation layer the central part of the project, whichever route you take. The B2B Suite does include an import and export layer for ERP or PIM connections, but the connection itself remains project work.

When Sylius is not the right choice for B2B

If your needs are standard, your team has no developer, and you prefer a vendor to carry the platform, a hosted solution will probably be simpler to live with. See my article on Shopify Plus B2B features as a point of comparison. If you have many internal teams and heavy procurement requirements, a larger agency may also be more appropriate than an independent developer like me. Sylius makes more sense when your commercial rules are your advantage and you want full control over them. I sell Sylius development, so please take that interest into account.

What to do next

Write your one page process, then test it against the Elesto demo and the plugin limits above. What remains is your real custom scope, and it is usually smaller than a first estimate suggests. You can send that page to me from my Sylius developer page. You will talk directly to the person who writes the code, and you will have a reply within 24 business hours.