Sylius B2B Suite features: buy it or build your own?
The Sylius B2B Suite is a commercial Sylius Plus module that adds company accounts, multiple price lists, quick ordering by SKU, reordering, multiple wishlists, an optional Elasticsearch search and an import and export layer. It saves development on standard B2B features and leaves your ERP integration and specific business rules to be built. The real decision is whether your needs match that list closely enough to justify a licence.
Disclosure: I earn my living on Sylius projects, whether they use custom development or integration, so read me with that interest in mind. Facts come from official Sylius pages read on 1 November 2026. I do not present any B2B Suite project of my own.
Official Sylius B2B Suite features, and what each one leaves you to do
The official listing shows version 4.0.0 under a proprietary licence, with more than 50,000 downloads stated. Here is its feature list, with the question I would raise on each one.
| 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 |
| Multiple wishlists | Lists for teams or departments | Little, unless approval rules attach to them |
| Import and export layer | Custom synchronisation with ERP or PIM | The integration itself |
Look at the last row again. "Custom data synchronisation" is an integration layer, and no specific connector is named. On most B2B projects, the ERP is where the budget goes, so do not assume the suite solves it.
Sylius claims on its Plus page that you can "save up to 40%" when implementing B2B systems. That is a vendor statement with no method given on the page. Your own saving depends on how many listed features you actually use.
The modules around it: quotes, permissions and Elesto
Some features people expect in the suite are described elsewhere. Request for Quote is a separate listing, and its page says it works with company accounts and other B2B purchasing features. Role-based access control for the admin panel is another module. Sylius's modular licence article lists B2B Suite and RBAC as separately purchasable modules. Clarify in your quote which ones are included, to avoid discovering a gap after signing.
Elesto is worth knowing about. Sylius presents it as a reference B2B project, delivered with source code you can study and adapt, combining B2B Suite, RFQ, RBAC, Advanced Multistore, Multisource Inventory and Product Configurator. The listing says it is available to teams adopting the B2B Suite, for Sylius 2.1 and higher. The Elesto article mentions catalogues above 200,000 products and a million variants, a vendor figure you should test against your own data rather than simply accept.
I would treat Elesto as a way to evaluate, and as a starting point for some projects. A demonstration of your own scenarios on it will tell you more than any feature table, and a reference project still needs someone to own the code you inherit from it.
Compatibility: check it against your Sylius version
The B2B Suite listing says "1.11 to 2.2" in its metadata and "1.11 and higher" in its requirements. Since Sylius 2.3 came out on 28 September 2026 and security support for 2.2 stops on 31 March 2027, ask Sylius which version of the suite runs on 2.3 before you plan your launch. If you still run 1.14, supported until 31 December 2026, the upgrade and the licence decision belong in the same conversation.
When the B2B Suite is overkill, and when it is not enough
It can be overkill if you sell to professionals with one price list, one user per company and invoices handled elsewhere. Customer groups and limited custom work on the free edition may be enough, and you could avoid a licence altogether. Check this before asking for a quote.
It may be insufficient if your differentiator is a process no catalogue module knows, such as multi-level approvals, contract prices that change by delivery site, or ordering through a procurement system. Then you are paying for a base and still funding substantial development. Compare that with custom development on the free edition, or with a hosted alternative such as Shopify Plus B2B or Adobe Commerce. Those can be the better choice if you have no technical partner.
How to decide without a long study
Score your requirements against the table: used as is, used with adaptation, not needed, or missing. If most of the value falls into the first two columns, request a quote. If most of it falls into "missing", a licence solves the wrong problem. Then ask three things in writing: the price and its renewal conditions, the supported Sylius versions, and what happens to your shop if the licence ends. That third answer rarely gets asked and it matters to anyone planning for several years.
If you want an independent reading of that table, my Sylius developer page and e-commerce services explain how I work. I can also audit an existing B2B shop before you commit. For a closer look at where each requirement sits, read company accounts, roles and permissions in Sylius.