Which backends Svelte Commerce speaks to, and how completely
Svelte Commerce talks to a backend through a connector: a package that maps one platform’s API onto a shared 43-service surface. Nothing in the storefront imports a connector by name, so installing a different package runs the same storefront on a different backend.
- 26 connectors
- 43 services in the surface
- 2 at 39/43
- 0 hand-asserted numbers
Coverage, measured
Coverage is not claimed, it is traced: a script follows each connector’s own request helpers and counts a service as wired only if it genuinely reaches the HTTP layer. Sort order is coverage, highest first.
- Wired — issues a real request
- No endpoint on the platform — throws rather than faking a session
- Not yet wired
Read from svelte-commerce/docs/CONNECTORS.md on . Coverage is traced by a script in the Svelte Commerce repository: a service counts as wired only if it transitively issues an HTTP request, or delegates to one that does. It is not hand-asserted.
| Platform | Coverage | Cart | Checkout | Auth | Known gaps |
|---|---|---|---|---|---|
| Litekart ↗ | wired | wired | wired | reference implementation | |
| Vendure ↗ | wired | wired | wired | none | |
| Medusa ↗ | not yet wired | wired | not yet wired | auth, cart, product, category, search, address, user, payment-method | |
| Broadleaf ↗ | wired | wired | wired | none | |
| Saleor ↗ | not yet wired | not yet wired | not yet wired | auth, cart, checkout, order, category, coupon, search, address, user, page, payment-method | |
| Shopware ↗ | wired | wired | wired | coupon | |
| Virto Commerce ↗ | wired | wired | wired | none | |
| WooCommerce ↗ | wired | wired | no endpoint on the platform | auth (no core endpoint), wishlist | |
| Magento ↗ | wired | wired | wired | review, wishlist | |
| Spree ↗ | wired | wired | wired | review | |
| X-Cart ↗ | wired | wired | wired | vendor | |
| Shopify ↗ | wired | wired | wired | review, wishlist, vendor, page, profile, country | |
| EverShop ↗ | wired | wired | wired | review, wishlist, vendor | |
| Spryker ↗ | wired | wired | wired | coupon | |
| nopCommerce ↗ | wired | wired | wired | coupon, currency | |
| PrestaShop ↗ | wired | wired | no endpoint on the platform | auth, review, wishlist, payment-method | |
| Sylius ↗ | wired | wired | wired | wishlist, vendor, page | |
| Swell ↗ | wired | wired | wired | review, wishlist, vendor, state | |
| Bagisto ↗ | wired | wired | wired | coupon, page, payment-method, vendor | |
| commercetools ↗ | wired | wired | wired | country, currency, page, vendor | |
| OroCommerce ↗ | wired | wired | wired | review, wishlist, currency, vendor | |
| Sharetribe ↗ | not yet wired | wired | wired | cart, coupon, address, country, state, wishlist | |
| CS-Cart ↗ | wired | wired | no endpoint on the platform | auth, address, country, state, currency, coupon, wishlist | |
| Shuup ↗ | wired | wired | wired | coupon, review, page, country, state, wishlist | |
| Django Oscar ↗ | wired | wired | wired | coupon, review, search, page, payment-method, currency, state, wishlist, vendor | |
| OpenCart ↗ | wired | wired | no endpoint on the platform | catalogue, search, auth, address, user, profile, coupon, page, wishlist, vendor | |
| GoCommerce | — | wired | wired | not yet wired | early connector, 0.1.0 — not measured by the coverage script; no customer accounts or search index |
How to read it
A low score is often correct
OpenCart core ships exactly ten API controllers and no product, category or search controller at all. Its 9/43 is the honest ceiling for that API, not a to-do list.
“No endpoint” is not a gap
Where a platform has no real customer-auth endpoint, auth throws rather than minting a session. A stub that logs anyone in for any password is an auth bypass, not a placeholder.
Some services count for nobody
Reels, deals, chat, gallery, popularity and a few others are Litekart-native concepts with no equivalent elsewhere. They stay documented placeholders and are excluded from the gaps column.
The one caveat that matters
Read this before choosing
Every connector was written by reading its platform’s authoritative source — the OpenAPI spec, the RAML, the router registration, or the controller source. No endpoint was guessed, and where a route could not be verified it was left an explicit placeholder rather than shipped as a plausible path that 404s in a merchant’s store.
But reading a spec is not running against a real store. None of these connectors has been exercised against a live production instance of its platform. That is the single biggest gap in this table, and it is the thing platform maintainers can help with that we cannot do alone.
Offer a sandbox or a correctionFAQ
Questions about backends
How many backends does Svelte Commerce support?
26 connectors exist today, covering Litekart, Vendure, Medusa, Broadleaf, Saleor, Shopware, Virto Commerce, WooCommerce, Magento, Spree, X-Cart, EverShop, Spryker, nopCommerce, PrestaShop, Sylius, Swell, Bagisto, commercetools, OroCommerce, Sharetribe, CS-Cart, Shuup, Shopify, Django Oscar and OpenCart. They differ a great deal in how complete they are, which is what the coverage column on this page is for.
Which connectors are the most complete?
Litekart and Vendure, both at 39 of 43 services, with cart, checkout and auth all wired. Litekart is the reference implementation and Vendure’s GraphQL Shop API covers essentially the whole surface.
Is the coverage number reliable?
It is measured rather than asserted. A script traces which service methods transitively reach the HTTP layer, following each connector’s own request helpers, and a service counts as wired only if it genuinely issues a request or delegates to one that does. What the number does not tell you is whether the connector has been run against a live store, because none of them has.
Can I use Svelte Commerce with GoCommerce?
Yes, through an early connector: @misiki/gocommerce-connector 0.1.0, on npm, covers catalogue, cart, checkout and order lookup, but not customer accounts or a search index. It sits at the bottom of this table, outside the 26, because the script behind the coverage column has not measured it; the connector status page describes what it does instead.
What if my platform is not listed?
Then there is no adapter for it yet. A connector is a TypeScript package mapping one platform’s API onto the shared service surface, so adding one does not require changing the storefront. The existing 26 are the pattern to follow.
Pick a backend, or help fix one
The storefront is the same either way. The connector is what changes.