Sylius

Last reviewed Aug 26, 2026 · 778 words

Sylius is what you choose when your shop is a software project with a Git repository, a CI pipeline and at least one developer who writes Symfony for a living. It is not something you install and configure; it is something you build on. That single fact explains the "Hard" rating, the 2 GB memory floor and the 8,515 stars from people who would never touch WooCommerce. If your team does not fit that description, nothing else in this guide will make it fit.

Symfony all the way down

Sylius is a set of Symfony bundles plus a standard project skeleton. composer create-project sylius/sylius-standard myshop gives you a Symfony application, and from that point every customisation is a Symfony customisation: services, Doctrine entities, Twig templates, event subscribers. Resource models (products, orders, customers, promotions) are extended by subclassing them and telling the container, not by installing a plugin that patches behaviour at runtime. It has been built this way since 2011 and the payoff is a codebase that reads like the rest of a modern PHP application.

The tooling is standard too: Doctrine migrations, Symfony Messenger for async work, Webpack Encore for assets. That last one means a Node toolchain is a build dependency even though the runtime is pure PHP, which surprises people coming from Magento.

2 GB is the developer floor, not the production budget

The 2,048 MB minimum is honest for a single-process deployment with the database on the same box. A real store runs PHP-FPM workers, MySQL or PostgreSQL, Redis for sessions and cache, and a Messenger worker for emails and search indexing. Budget 4 GB if everything shares one host, or split the database out. Docker is the supported deployment shape and the standard project ships a Compose file, but for production treat it as a template rather than a finished stack: you will add a reverse proxy, a real database volume and a worker container.

API-first means the storefront is optional

Sylius exposes a Shop API and an Admin API through API Platform, under /api/v2, covering the full checkout flow and every admin resource. The bundled Twig storefront is usable and many stores ship it, but the architecture assumes you might replace it with a Next.js, Nuxt or native app. Headless is a first-class path rather than an afterthought, which is the strongest argument for Sylius over WooCommerce for anyone with a front-end team.

The plugin ecosystem and the Plus question

There is a curated plugin store: payment gateways (Stripe, Mollie, PayPal via Payum), CMS blocks, invoicing, wishlists, product reviews. It is a few dozen well-maintained plugins rather than WooCommerce's thousands, and each one is a Symfony bundle you can read and fork. The commercial edition, Sylius Plus, layers on multi-source inventory, returns management, advanced customer permissions and support. The MIT core is complete for a single-warehouse store; you buy Plus when the business grows into features it would cost more to write.

Testing is a habit you inherit

Sylius is developed behaviour-first with Behat scenarios describing every shop feature, backed by PHPSpec and PHPUnit. When you extend it, the scaffolding to write scenarios for your own changes is already there. The tax is CI time: a full suite takes a long while, and you will want to run only the relevant scenarios locally. The benefit is that upgrading between minor versions is reliably safe, which for an e-commerce platform is the thing that matters most.

Against the alternatives

Aimeos is the nearest comparison: Laravel instead of Symfony, lighter, faster on huge catalogues, and weaker on enterprise workflow. Choose by which framework your developers already write. WooCommerce wins when the person running the store is not a developer at all, and it should win those cases; Sylius has no equivalent of a non-technical admin installing a theme. Coming from Magento, Sylius is the modern replacement people mean when they say "Magento without the weight", and the Magento alternatives page sets out the trade. The wider e-commerce category covers the hosted-style options.

What I'd do

With a Symfony developer on staff and a catalogue that needs custom logic (configurable products, B2B pricing, integration with an ERP), I would start from sylius-standard, keep the default storefront for launch, split the database onto its own host, and add Redis and a Messenger worker before go-live. Without that developer, I would not start; run WooCommerce, or Aimeos if the team is Laravel. Sylius rewards engineering investment and punishes its absence, and it does both consistently.