GoCommerce ↔ Svelte Commerce connector

Status: early (0.16.0). Published on npm as @misiki/gocommerce-connector.

In a test on 28 October 2026 with version 0.14.0, catalogue, cart, cash-on-delivery checkout and order lookup worked end to end. Sign-in, the address book and order history need GoCommerce’s identity module. No store is known to run Svelte Commerce on GoCommerce in production.

This page exists so the answer is one link rather than an inference: what the connector does, what it does not, and how to try it.

Install it

In a Svelte Commerce checkout, with a GoCommerce instance running somewhere the storefront can reach.

Swap the connector, point it at GoCommerce

# one connector at a time — remove the two Svelte Commerce ships with
npm uninstall @misiki/litekart-connector @misiki/vendure-connector
npm i @misiki/gocommerce-connector

# tell the storefront where GoCommerce answers
echo PUBLIC_GOCOMMERCE_API_URL=http://127.0.0.1:8080 >> .env

Install one connector at a time: the backend is whichever @misiki/*-connector package.json has, and two would fight over the same alias. The package’s README is the authority on its details; the package itself is on npm.

Current architecture

Both halves exist and are solid. The piece between them exists too, and it is the early one.

Svelte Commerce

Calls a connector package. Imports none by name — $connector resolves from package.json.

@misiki/gocommerce-connector 0.16.0 — early

GoCommerce

Serves 550 documented operations over REST, published as OpenAPI.

Svelte Commerce reaches every backend through a connector implementing a shared 43-service surface — product, cart, checkout, order, auth, address and the rest. The backends page measures 26 of them; the GoCommerce connector is not in that set. It implements the commerce path and refuses the rest by name. The two halves are described on the architecture page.

What exists, what does not

  • Works: Published to npm — @misiki/gocommerce-connector 0.16.0, first published on 2 September 2026. The source is in its own repository, misiki-in/gocommerce-connector.

  • Works: Catalogue — productService lists, filters, sorts and paginates, and fetches by slug, id or SKU, with variants. categoryService serves the tree and category pages; collectionService serves curated lists and a collection page.

  • Works: Cart — open, add, change quantity, remove, apply a discount code, set the email.

  • Works: Checkout — cash on delivery, Razorpay and the store’s first hosted-page gateway (Adyen, Paddle, Lemon Squeezy, Creem, Hyperswitch or RevenueCat), shipping rates, and placing the order. Cash on delivery worked end to end in a test on 28 October 2026 with version 0.14.0.

  • Works: Order lookup — one order, by its number and the access token checkout returned. In the same test the order-success page showed the full order.

  • Works: Money and missing fields — prices are converted from the engine’s minor units per currency, not by a constant 100. Fields the engine lacks are not invented: with no popularity score, “most popular” sorts nothing, and mrp equals the price.

  • Early: Production use — none known. No store is known to run Svelte Commerce on GoCommerce in production; the tests run against a real engine, not a real shop.

  • Early: Shopper accounts — sign-in by email and password or by a code texted to a phone, the address book and order history, through GoCommerce’s identity module. They did not work in the test stack, which ran without it.

  • Early: Guest orders — opening an order with its number and the email or phone on it, with a 4-digit code sent to either, or from the link in its emails. Not yet tested end to end here.

  • Early: Pages and theme — the home page, the product and collection templates, the header, the footer and the theme settings a shop sets in GoCommerce’s Themes, with the editor’s live preview; the store’s own logo, dark logo and icon; its address, map and opening hours on the contact page. Not yet tested end to end here.

  • Early: Basket and product page extras — add-ons, suggestions, the codes a shop lists, the free-delivery bar, highlights, a free gift, product videos, the sold count and PIN code autofill. Not yet tested end to end here.

  • Early: Search, pictures and the storefront modules — search through Meilisearch when the store switches it on, and the database when it cannot answer; pictures resized by the engine to the width shown; reviews, wishlists, content pages, menus, FAQ, newsletter and contact through the matching GoCommerce modules. Not yet tested end to end here.

  • Not covered: What it does not map — account deletion, blogs, banners, reels, chat, warranties, deals and uploads. Their lists answer empty, and anything that writes or opens one record throws, naming the service.

  • Not covered: Other payment methods — the storefront’s checkout offers no Stripe, Cashfree, Clover or Helcim, nor a second hosted-page gateway, and its Stripe and Cashfree flows throw, naming the service. checkoutService.checkout(code) reaches every method the engine has switched on, for a storefront that draws its own payment step.

Which release brought each page and theme setting, and which Svelte Commerce branch draws it, is on storefront and themes.

Known limitations

What is true of 0.16.0 as published.

A stable contract, not a proven one

GoCommerce is 1.0, so the API the connector binds to will not move without a major version. What that does not supply is production mileage: no store is known to run GoCommerce in production yet, let alone the pair, so the connector will meet whatever the first real catalogue exposes.

Partial, and loud about it

The connector refuses what the engine does not do with an error that names the service, rather than returning empty. It has no score on the backends page, because the script that measures the 26 has not measured it, so its coverage is described here rather than numbered.

No benchmarks either way

Nothing has been published about GoCommerce’s performance, so nothing can honestly be said about the pair’s. That stays true until somebody measures it.

How to help

  • Run it against a real store. Put it in front of a real GoCommerce catalogue and report what breaks. The standing weakness of every Svelte Commerce connector is that none has been run against a live production store; being the first would matter more than new code.
  • Start from the tests. They run against a running GoCommerce, not a mock, and skip loudly when there is nothing to talk to. A mock would test the connector against an idea of the engine rather than the engine.
  • Keep refusals loud. A service the connector does not map throws UnsupportedByGoCommerce. Making one return an empty list instead turns a missing feature into a heading with nothing under it.
  • Do not stub auth. The convention across every connector is to throw rather than mint a session — a stub that logs anyone in is an auth bypass, not a placeholder.

The backend carries over 2,000 tests and a documented contract for every route, so the connector has something precise to build against.

GoCommerce issues Svelte Commerce discussions Discord

FAQ

Connector questions

Can I connect Svelte Commerce to GoCommerce today?

Yes, through an early connector. @misiki/gocommerce-connector 0.16.0 is on npm, first published on 2 September 2026. Install it in a Svelte Commerce checkout, set PUBLIC_GOCOMMERCE_API_URL to your GoCommerce instance, and the storefront can browse the catalogue, fill a cart, check out and look up an order. Sign-in, the address book and order history need GoCommerce’s identity module, and no store is known to run the pair in production.

What does “early” mean here?

It is 0.16.0, first published on 2 September 2026. The path from a shelf to a placed order works, and its tests run against a real GoCommerce engine rather than a mock. What it lacks is production mileage: no store is known to run Svelte Commerce on GoCommerce in production, so nothing has yet met a real catalogue or real shoppers. Build on it deliberately, and place test orders before real ones.

What does it not do?

Shopper sign-in, the address book and order history go through GoCommerce’s identity module; without it, as in a test stack on 28 October 2026 with version 0.14.0, they do not work, and an order is read back with the access token checkout returned. Account deletion, blogs, banners, reels, chat, warranties, deals and uploads are not mapped: a list of them answers empty, and a write or a single record throws, naming the service. At checkout it offers cash on delivery, Razorpay and the store’s first hosted-page gateway.

How do I install it?

Run npm i @misiki/gocommerce-connector in your Svelte Commerce checkout and set PUBLIC_GOCOMMERCE_API_URL to where GoCommerce answers, for example http://127.0.0.1:8080. Install one connector at a time: the backend is whichever @misiki/*-connector package.json has, so remove the Litekart and Vendure connectors Svelte Commerce ships with.

Is GoCommerce one of the 26 backends?

No. The 26 are the connectors whose coverage the backends page measures with a script, and the GoCommerce connector is not in that set. It lives in its own repository, misiki-in/gocommerce-connector, and this page describes it instead.

Does this mean the two packages are now one wired stack?

They are two packages of one platform with an early connector between them. Both are still useful on their own — GoCommerce behind any client, Svelte Commerce in front of 26 other backends — and the connector is the newest and least proven of the three.

Either package is useful on its own

The connector is early, and this page says what it does not do. GoCommerce and Svelte Commerce are each useful without it.

Explore GoCommerce Explore Svelte Commerce See the other 26 backends
Chat on WhatsApp