Panel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Sylius · sylius.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Sylius at a glance
- Vendor
- Sylius
- Headquarters
- Incorporated in Poland source, captured 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Sylius 3/5, the mean of 6 judges. Sylius is an open-source e-commerce framework on Symfony, and the bench scores it highest where the documentation runs deepest. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Sylius is an open-source e-commerce framework on Symfony, and the bench scores it highest where the documentation runs deepest. Extensibility sits at 9-10: an MIT-licensed core installed via Composer, a headless REST API built with API Platform, 500+ indexed marketplace plugins and PHPUnit/Behat testing. Data control and exit follows at 7-8, with self-hosting on a VPS, Docker or Kubernetes keeping data in the merchant's own stack. Tax and legal stands at 0 — the captured pages show nothing on VAT determination, OSS, reverse charge, invoicing or German checkout requirements. Catalog and checkout holds at 4: named providers include a vendor-maintained PayPal plugin, Stripe, Mollie, Adyen, PayPlug, Tpay, while variants, discounts, vouchers and guest checkout stay unproven. Operations scores 5-6, its returns handling and multi-source inventory inside the paid edition. Pricing transparency lands at 3-4: the core is stated free under MIT, and no price appears for Sylius Plus. Sovereignty scores 4-6, resting on a Polish entity under Polish law and a no-third-country-transfer clause in the terms, with vendor-run residency unknown. Score spreads stay within two points; no genuine split emerged.
Speaks for it
- MIT-licensed core installs via Composer as a standard Symfony application, which the vendor describes as safe and easy to customize and upgrade
- Headless REST API built with API Platform is documented to work with any frontend or microservice architecture
- Marketplace lists 500+ indexed plugins, with further extensions available on Packagist
- Runs self-hosted on a VPS, Docker or Kubernetes, keeping catalogue, customer and order data in the merchant's own stack
- Checkout runs through named providers, including an official PayPal plugin maintained by the vendor's core team and Mollie marked preferred for Germany, installed over 6000 times
Held against it
- We found no public information on VAT determination, OSS, reverse charge, invoicing or German checkout requirements on any captured page
- We found no public information on product variants, discounts, vouchers, guest checkout or abandoned-cart recovery
- We found no public information on prices for Sylius Plus, the commercial edition carrying the one-page checkout, B2B suite and multi-source inventory, so an annual cost is not computable from what is public
- We found no public information on carrier and label-printing integrations or maintained interfaces to ERP and accounting systems such as DATEV
- We found no public information on a data processing agreement, a subprocessor list, documented export tooling or a migration path in and out
Best for
- You have a Symfony or PHP development team and want to own and reshape the commerce stack rather than rent it
- You need headless commerce, driving your own frontend or microservices from the REST API
- Data control matters most and you can self-host on your own VPS, Docker or Kubernetes
- You want to start on the completely free MIT-licensed core and add capability through plugins or the paid edition later
Avoid if
- You need a published, computable annual cost before committing — the edition carrying the operations modules states no price, so budgeting starts as a sales conversation
- You run a German-facing shop and need tax and checkout-law handling documented up front — the judges advise verifying VAT, OSS, reverse-charge and invoicing behaviour elsewhere before committing
- You depend on native carrier, label-printing or DATEV-style ERP and accounting interfaces from day one
- You want turnkey merchandising out of the box — variants, discounts, vouchers and guest checkout are unproven on the captured pages
The scores
| Criterion | Panel median |
|---|---|
| Catalogue & checkout | 2 of 5 |
| Extensibility & developer surface | 4.5 of 5 |
| Order operations & back office | 3 of 5 |
| Data ownership & exit | 4 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 1.5 of 5 |
Catalogue & checkout
Show reasoningHide reasoning
How this is scored
Products, variants, pricing rules and the path to payment — the part that either converts or does not.
0 — Not a shop: no product catalogue and no checkout of its own.
3 — A product catalogue with categories and a checkout that takes payment through at least one provider.
5 — Products with variants, discounts or vouchers, guest checkout, and several payment methods including those German buyers expect (PayPal, invoice or direct debit) through named providers.
8 — Tiered and customer-group pricing, bundles or configurable products, rule-based promotions, per-channel or per-market pricing, abandoned-cart recovery, a checkout customisable without a rebuild, and buy-now-pay-later where offered.
10 — Merchandising and checkout are the product: rule-driven pricing and promotions, A/B-testable checkout, multi-currency and multi-language as standard, and conversion features (abandoned cart, one-page checkout) shipped rather than bolted on.
The Merchant
This is a real shop platform — ten thousand-plus online stores and B2C/B2B positioning — with a payment rail I can sell on: an official PayPal plugin maintained by the vendor's own team, Mollie named preferred provider for Germany, plus Stripe, Adyen, PayPlug and Tpay. But we found no public information on product variants, vouchers or discounts, guest checkout or abandoned-cart recovery, and the one-page checkout module sits in the commercial Sylius Plus edition, so the merchandising side of conversion stays unproven to me. 3 6 1 1
The B2B Seller
Payments are the documented strength: an official PayPal plugin maintained by the vendor's own team, Mollie named as the preferred provider for Germany and Benelux with over 6,000 installations, plus Stripe, Adyen, PayPlug and Tpay. The paid edition lists a one-page checkout module and a B2B suite, but we found no public information on product variants, discount or voucher rules, guest checkout, or the contents of that B2B suite, so I cannot see customer-specific net pricing or payment on account described on the captured pages. 3 6 6 1
The Developer
This is a full open-source commerce framework and the payment side is documented through named providers — an official PayPal plugin maintained by the core team, plus Stripe, Mollie marked preferred for Germany, Adyen, PayPlug and Tpay — with a one-page checkout module in the commercial edition. We found no public information on product variants, promotions, vouchers or guest checkout in the captured pages, so I score just above the basic catalogue-and-payment mark. 3 6 6 1
The Operations Lead
The payment-partner capture is the strongest evidence: PayPal via an official plugin the core team maintains, Mollie named preferred for Germany, plus Stripe, Adyen, PayPlug and Tpay, and a one-page checkout as a module of the commercial Sylius Plus edition. We found no public information on variants, promotions, guest checkout or per-channel pricing, so the documented level sits between the basic and mid anchors. 3 6 6 1
The Data Protection Officer
The payment partners page evidences a genuinely broad checkout: an official PayPal Commerce Platform plugin developed and maintained by the core team, plus Mollie, Stripe, Adyen, PayPlug and Tpay as named providers, with Mollie marked preferred for Germany and installed over 6000 times. One-page checkout is documented, but as a module of the commercial Plus edition, and I found no public information on variants, discounts, vouchers, guest checkout or abandoned-cart recovery on the captured pages. 3 6 6 1
The Skeptic
The captured payment-partners page names real providers — PayPal via a vendor-maintained official plugin, plus Stripe, Mollie, Adyen, PayPlug and Tpay — and the commercial edition adds a one-page checkout, which clears a working checkout through named providers. But the captured pages show nothing on variants, discounts, vouchers or guest checkout, so the conversion machinery past the payment step stays unproven to me. 3 6 6
Tax & German legal correctness
n/r
n/r
n/r
n/r
n/r
n/r
Show reasoningHide reasoning
How this is scored
VAT determination, OSS, B2B reverse charge, invoicing, and the checkout requirements German law imposes (Button-Lösung, Widerrufsrecht, Preisangabenverordnung) — judged on what the platform documents it does or ships as a maintained extension.
0 — No tax handling at all; prices carry no VAT logic and the merchant calculates tax outside the platform.
3 — VAT rates configurable per country or product, with prices shown gross or net and legal texts placed as pages in the checkout.
5 — VAT by destination country with gross and net display per customer group, B2B with VAT ID and reverse charge, and the German checkout requirements (order button wording, withdrawal policy, price indications) handled by the platform or a named official extension.
8 — VIES validation of VAT IDs, OSS thresholds tracked or OSS reporting data provided, invoices issued from orders with correct content per case including reverse-charge notes, small-business and third-country handling, and e-invoicing (XRechnung/ZUGFeRD) for B2B orders.
10 — Tax and legal correctness are maintained by the vendor rather than the merchant: rates and thresholds updated as the law moves, OSS reporting produced, every invoice case correct out of the box, and documented conformity a lawyer could review.
The Merchant not rated — no public information
We found no public information on VAT determination, OSS, B2B reverse charge, invoicing, or the German checkout requirements such as order-button wording, withdrawal policy and price indications on any page we captured — the payment-partner page, the homepage and the terms of service address none of it. For a German-facing shop this would all have to be verified elsewhere before committing. 3 2 1
The B2B Seller not rated — no public information
We found no public information on VAT determination, VAT-ID validation, reverse charge, OSS, invoicing or the German checkout requirements; the payment-partner and homepage captures carry no tax detail, and the terms govern the vendor's own commercial services under Polish law rather than the shop platform's tax behaviour. Reverse charge with a validated VAT-ID at checkout is what a trade buyer needs first, and the captured pages give nothing on it. 3 2 1 1
The Developer not rated — no public information
I found no public information on VAT determination, OSS reporting, invoicing and e-invoicing, or the German checkout requirements such as order-button wording and price indication rules. The homepage captures, the terms of service and the payment partner pages cover privacy, liability and providers, and none of them touches tax or German checkout law. 1 2 3 2
The Operations Lead not rated — no public information
We found no public information on VAT determination, OSS, reverse charge, invoicing or the German checkout requirements (order button wording, withdrawal policy, price indications) on any captured page; the B2B suite named for Sylius Plus is a commerce feature and says nothing about tax handling. Reported as unevidenced, so it does not count toward the verdict. 3 6 1
The Data Protection Officer not rated — no public information
I found no public information on VAT determination, OSS, B2B reverse charge, invoicing or the German checkout requirements (order button wording, withdrawal policy, price indications) on any page I read — the homepage captures, the payment partners page and the terms of service are all silent on tax and legal conformity of the shop itself. 1 3 2 1
The Skeptic not rated — no public information
We found no public information on VAT determination, OSS, reverse charge, invoicing or the German checkout requirements on any page we read — the terms cover entity, liability and complaint handling, and the homepage and payment-partners pages cover marketing and integrations, but nothing on tax or German legal correctness appears in the captures. 2 3 1
Extensibility & developer surface
Show reasoningHide reasoning
How this is scored
Themes, apps, APIs and headless — whether the shop can be shaped to the business, and at what cost in lock-in.
0 — A closed shop builder: no themes to edit, no apps or plugins and no API.
3 — Themes adjustable in an editor and a set of apps or plugins to add features.
5 — Custom themes with a template language or code access, an app or plugin ecosystem, and a documented API with webhooks for order events.
8 — A storefront API for headless builds, an extension framework with its own lifecycle, staging or development environments, version control for themes, and documented rate limits.
10 — A platform a team can own: headless-first APIs, open-source or source-available core, plugin architecture with a real dependency model, local development and CI supported, and upgrade paths that do not orphan customisations.
The Merchant
An MIT-licensed core, a REST API built on API Platform with headless and PWA positioning, an Addons Marketplace of 500-plus indexed plugins plus Packagist, and a Composer architecture where the shop is a standard Symfony application with the core as a dependency, described as safe and easy to customize and upgrade. That is a checkout a team can reshape without a rebuild — my kind of platform — though the captured pages give no rate limits or staging environments. 5 6 6 1
The B2B Seller
The core is MIT-licensed and installs as a standard Symfony application with the platform as a Composer dependency, described as safe and easy to customise and upgrade, with a headless REST API built on API Platform, a marketplace of more than 500 plugins, Docker installation and full-stack behaviour-driven testing with PHPUnit and Behat. This is a platform a development team can own rather than rent, short of the top level only on undocumented rate limits and webhooks. 5 6 6 1
The Developer
This is the platform a team can actually own: an MIT-licensed Symfony core installed as a Composer dependency that the vendor says makes customising and upgrading safe, headless-first APIs built on API Platform, plugins distributed as Composer packages through a marketplace of over 500 indexed extensions, Docker installation with a development repository on GitHub, and behaviour-driven testing with PHPUnit and Behat as a stated culture. Every element I look for in a five-year maintainable stack is documented on the captured pages. 5 6 6 1
The Operations Lead
An MIT-licensed open-source core, a headless REST API built on API Platform, plugins via Composer with a marketplace of over 500 indexed extensions, Docker installation and a GitHub repository with 41,527 commits and 711 contributors — this is a platform a team can own. It installs as a standard Symfony application with the core as a dependency, which the vendor says makes customisation safe and easy to upgrade. I stop short of the top because the commercial Plus edition runs under a separate licence from the open-source core. 5 6 6 1
The Data Protection Officer
A REST API built on API Platform documented to work with any frontend or microservice architecture, an MIT-licensed core with 8,600 stars, 343 releases and 711 contributors, Composer dependency management with 500-plus indexed marketplace plugins, Docker installation and a PHPUnit/Behat testing culture give a team full ownership of the code. Self-hosting as a standard Symfony application is documented as safe and easy to customise and upgrade, which is the upgrade path a custom build needs. 5 6 6 1
The Skeptic
This is the part a team can own: an MIT-licensed core installed with Composer as a standard Symfony application, headless by design on a REST API built with API Platform, a marketplace with 500+ indexed plugins plus Packagist, Docker-based setup, and the core itself ships with PHPUnit and Behat test suites. The only gaps I can see are that the captured pages document no webhooks for order events and no API rate limits. 5 6 6 1
Order operations & back office
Show reasoningHide reasoning
How this is scored
What happens after checkout: order management, stock, returns, shipping, and the link to ERP or accounting.
0 — No order handling in the product; orders leave as emails or exports to be processed elsewhere.
3 — An order list with statuses, stock counts per product, and shipping rates set up in the shop.
5 — Order management with status emails, stock tracking, named carrier integrations or label printing, and refunds or returns handled in the system.
8 — Partial shipments and partial refunds, multi-warehouse or multi-location stock, multi-channel or marketplace order intake, fulfilment routing, dropshipping, and maintained interfaces to named ERP and accounting systems (DATEV among them for German merchants).
10 — The shop is the front of an operation: real-time stock across channels and warehouses, returns and refunds fully worked including partials, ERP integration the vendor maintains, and operational reporting a merchant runs the business from.
The Merchant
The commercial Sylius Plus edition documents partial order fulfillment, smooth returns handling and multi-source inventory, which covers the returns-and-stock half of back-office work. We found no public information on carrier integrations or label printing, refunds, multi-channel order intake, or maintained interfaces to named ERP and accounting systems such as DATEV — and note the modules that do exist sit behind the paid edition. 6 6
The B2B Seller
The commercial edition documents returns handling, multi-source inventory, partial order fulfilment and multi-store management, which is real back-office substance. But we found no public information on carrier or label integrations, marketplace order intake, or maintained ERP and accounting interfaces; DATEV connectivity is the first thing my German trade buyers ask for after checkout, and we found no public information on it. 6 6
The Developer
The commercial edition documents partial order fulfilment, smooth returns handling and multi-source inventory, which is advanced-grade capability shipped as maintained modules. We found no public information on carrier or label integrations, refund workflows, or interfaces to named ERP and accounting systems such as DATEV, so I place it between the middle and advanced marks. 6 6
The Operations Lead
The vendor's own page lists partial order fulfilment, returns handling, multi-source inventory and multi-store management as modules of the commercial Sylius Plus edition — real operations capability, but behind an edition with no stated price. We found no public information on carrier integrations with label printing, ERP or accounting interfaces such as DATEV, partial refunds or operational reporting, and an ERP link the vendor maintains is exactly what I look for. 6 6 1
The Data Protection Officer
The commercial Plus edition documents partial order fulfilment, returns handling and multi-source inventory, which covers the partial-shipment and multi-location side of back-office work alongside multi-store management. I found no public information on carrier or label-printing integrations, status emails, marketplace order intake or maintained interfaces to ERP and accounting systems, DATEV among them, on the captured pages. 6 6
The Skeptic
The commercial edition lists partial order fulfilment, returns handling, multi-source inventory and a B2B suite — returns and partials handled in-system, which is real back office. But we found no public information on carrier integrations, label printing, or interfaces to ERP and accounting systems such as DATEV, and note that the operational modules beyond basics sit behind the commercial licence rather than the free core. 6 6
Data ownership & exit
Show reasoningHide reasoning
How this is scored
Whether the catalogue, customers and order history remain the merchant's: export completeness, hosting choice, and what leaving actually costs.
0 — The terms state that the merchant's data cannot be exported or is not returned on cancellation.
3 — CSV export of products and customers, or of orders, from the admin.
5 — Export of catalogue, customers and orders documented (CSV, API or dump), with data deletion or return on cancellation stated in the terms or help centre.
8 — Full-fidelity export including media and order documents, a documented migration path in and out, self-hosting or a choice of hosting partner, and no metering that prices a migration out of reach.
10 — Ownership is structural rather than promised: open-source or source-available platform the merchant can run anywhere, database-level access, documented migration in both directions, and contractual data return.
The Merchant
Ownership here is structural rather than promised: the platform is open source under the MIT licence and self-hostable on a VPS, Docker or Kubernetes, so catalogue, customers and order history live in the merchant's own installation and leaving is a matter of moving it. We found no public information on documented export tooling or a migration path in and out, which is what keeps it short of the top for me. 5 6 1
The B2B Seller
Ownership is structural: an MIT-licensed, self-hostable platform that runs on a standard VPS or under Docker and Kubernetes, so the catalogue, customers and order history sit in the merchant's own database by construction. We found no public information on export tooling, a documented migration path, or a contractual data-return commitment for the commercial edition, which keeps this short of the top level. 5 6 1
The Developer
Ownership here is structural rather than promised: the platform is released under the MIT licence and runs on the merchant's own VPS, Docker or Kubernetes, so the catalogue and order data sit on infrastructure the merchant controls from day one. We found no public information on export formats, a documented migration path in and out, or contractual data return on cancellation, which is what holds this below the top marks. 5 6 1
The Operations Lead
Ownership is close to structural: the platform is MIT-licensed and self-hostable on a VPS, Docker or Kubernetes, so the merchant runs their own instance with no metering that could price an exit. We found no public information on export tooling or on what the terms say about returning merchant data when commercial services end. 5 6 1
The Data Protection Officer
Ownership is structural rather than promised: an MIT-licensed platform installable via Composer or Docker onto the merchant's own VPS or Kubernetes cluster, so customers, addresses and order history live in a database the merchant holds, and leaving is carrying the application and data out. What the captured pages do not show is documented export formats and completeness, a stated migration path in either direction, or a contractual data-return commitment on cancellation of the commercial services. 5 6 6 1
The Skeptic
Ownership here is structural rather than promised: the platform is MIT-licensed, installable via Composer and Docker, and runs on the merchant's own VPS or Kubernetes cluster, so the data sits in the merchant's own stack and leaving costs nothing at the licence level. We found no public information on a documented migration path in or out or a contractual data-return commitment, and the commercial edition is offered under a separate licence from the MIT core. 5 6 6 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where customer and order data live, who the contracting entity is, and which subprocessors sit in the checkout path. Independently sourced by the sovereignty pipeline. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain (CDN, analytics, payment routing, support tooling) is unstated or partly non-EU.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published with locations, any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a self-hosted option that puts the shop entirely under the merchant's control.
The Merchant
The contracting entity is Sylius sp. z o.o. in Poland, under Polish law and Polish courts, with the Polish data protection authority named in the terms, which also state that client personal data is not transferred to a recipient in a third country. Self-hosting puts the shop entirely under the merchant's control, but we found no public information on a published data processing agreement, a subprocessor list, or where vendor-hosted data resides. 2 2 5 1
The B2B Seller
Sylius sp. z o.o. in Poland is the contracting entity, Polish law and Polish courts govern, the terms state that clients' personal data is not transferred to a third-country recipient, and the platform can be self-hosted entirely under the merchant's control. Data residency as offered by the vendor, a published data-processing agreement and a subprocessor list are unknown on the captured pages, so the chain is only partly proven. 2 5 6
The Developer
The contracting entity is Sylius sp. z o.o. in Poland under Polish law with Polish courts for disputes, the terms state client personal data is not transferred to a third-country recipient, and the self-hosting option puts the whole stack under the merchant's control. We found no public information on hosting residency for vendor-run services, a published subprocessor list, or a data processing agreement, which keeps this below the higher marks. 2 2 5
The Operations Lead
The vendor is European and proven: Sylius sp. z o.o. in Poland, Polish law and Polish courts, the Polish data protection authority named for complaints, and the terms state personal data is not transferred to a recipient in a third country; a self-hosted option puts a shop under the merchant's control. Hosting locations for the vendor's own services, a data processing agreement and the subprocessor chain are unknown from the captured pages, so this lands between the lower and middle anchors. 2 2 5 1
The Data Protection Officer
The contracting entity is European and proven in detail — Sylius sp. z o.o. in Poland with Polish governing law, Polish courts and complaint rights before the Polish data protection authority — and the terms state clients' personal data shall not be transferred to a recipient in a third country, with self-hosting leaving infrastructure choice to the merchant. But I could not find a published data processing agreement, a data-residency statement on the vendor's own pages, or a subprocessor list with locations, so where the CDN, analytics and payment routing actually process customer data is unstated. 2 2 5 1
The Skeptic
The contracting entity is Sylius sp. z o.o. in Poland under Polish law, the terms state client personal data is not transferred to a third-country recipient, and self-hosting puts shop data in the merchant's own infrastructure. We found no public information on a data-processing agreement or a subprocessor list with locations, and the commercial edition's separate licence sits outside the MIT core. 2 2 5
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a merchant can compute the real annual cost — licence, transaction fees, apps, hosting — from public pages alone. The category where the headline price is least often the invoice.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one priced tier.
5 — Prices for the main tiers public with the billing period stated and the main inclusions per tier listed.
8 — Every tier priced publicly including transaction or revenue-share rates, order or GMV limits, and the cost of the extensions most shops need; VAT treatment and minimum term stated.
10 — Complete price computability: annual cost derivable for a given order volume and GMV including licence, transaction fees, hosting and typical extensions — and for open-source platforms, an honest statement that the licence is free and where the money actually goes.
The Merchant
The framework is stated as "completely free and released under the MIT License", an honest free headline, but the commercial Sylius Plus edition — which carries the one-page checkout, returns handling and multi-source inventory a real shop needs — shows no prices, and the terms say only that fees "shall be specified on the Website". I judge price against contribution: the free tier is real, yet I cannot compute what the converting configuration actually costs me per year from these pages. 2 6 1
The B2B Seller
The open-source licence is stated plainly as completely free under MIT, which is honest about where the money goes for self-hosters. But the commercial Sylius Plus edition — the one carrying the B2B suite, one-page checkout and multi-source inventory — states no prices on the captured page, and while the terms say fees for the Commercial Services are specified on the website, no figures appear in what was captured, so no buyer can compute the real annual cost of the edition a trade shop actually needs. 2 6 1
The Developer
The open-source edition is priced with unusual honesty — "Sylius is completely free and released under the MIT License" — so a developer-run deployment carries zero licence cost plus my own hosting. The commercial edition's product tour page states no prices, and the terms say only that service fees are specified on the website, so an annual cost for the paid edition is not computable from the captures. 2 6 1
The Operations Lead
The framework itself is publicly priced at free under the MIT licence, stated plainly. The commercial Sylius Plus edition — where the operations modules live — has no price stated on the captured page, and the terms only say fees for commercial services are specified on the website without figures, so the annual cost of the edition a merchant would actually run cannot be computed. 2 5 6 1
The Data Protection Officer
The licence is honestly stated as completely free under the MIT Licence, and hosting runs on the merchant's own infrastructure, so there is no vendor hosting fee to guess at. But the commercial Sylius Plus edition — where the one-page checkout, B2B suite, returns handling and SLA-backed support live — carries no price on the captured pages, and the terms only say that fees for commercial services are specified on the website. 2 6 1
The Skeptic
The core licence price is public and honest — "Sylius is completely free and released under the MIT License" — but that is the only figure on the table: the captured pages state no prices for the Sylius Plus edition, and the terms say commercial-service fees "shall be specified on the Website" while the captures show none. A merchant who needs the one-page checkout, B2B suite or multi-source inventory cannot compute an annual cost from anything published here; that part is a sales conversation. 2 6 6 1
European sovereignty — proven facts
3 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in PL | 2/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options | Self-hostable | 1/1 pts | 5 Report an error |
| Open source |
Open source (permissive)
unverified
Why unverified?The MIT licence covers the open-source framework; the commercial Sylius Plus edition is offered under a separate licence. |
1/1 pts | 6 Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
Questions about Sylius
Is Sylius European?
Not determined: the vendor’s pages as captured do not say where Sylius is based. Its vendor, Sylius, is incorporated in Poland, per the vendor’s page captured 16 Nov 2026.
Where does Sylius store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Sylius have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Sylius?
As of 18 Nov 2026, the panel rates JTL-Shop (3.5/5), Saleor (3/5) and Shopware (3/5) highest among the other 28 E-Commerce Platforms & Shop Systems products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is JTL-Shop (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Sylius alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Transfer impact assessment, Hosting location. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Open source. The MIT licence covers the open-source framework; the commercial Sylius Plus edition is offered under a separate licence.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 5 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (6)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page sylius.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 22 Sep 2026 Details →
- 2 Terms of service — found from the homepage sylius.com Checked 16 Nov 2026 +1 earlier capture: 30 Sep 2026 Details →
- 3 Catalogue & checkout — found from sitemap sylius.com Checked 16 Nov 2026 Details →
- 4 Extensibility & developer surface — found from sitemap sylius.com Checked 16 Nov 2026 Details →
- 5 Self-hosting / on-premises installation docs — found from the homepage sylius.com Checked 16 Nov 2026 Details →
- 6 Code repository (open-source licence) — found from the homepage github.com Checked 16 Nov 2026 +1 earlier capture: 1 Nov 2026 Details →