Svelte Commerce on Shuup

What works on Shuup today

Known gaps: coupon, review, page, country, state, wishlist — each is explained under Limitations below.

19 of 43 services wired, read from CONNECTORS.md on 21 September 2026, where the package version is recorded too; npm may carry a newer patch. 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. Some services are Litekart-native concepts with no equivalent elsewhere (reels, deals, chat, gallery, popularity, demo-request, feedback, plugins, banner). They stay documented placeholders on every connector and are excluded from known gaps.

Quick start

From nothing to a Svelte Commerce storefront reading Shuup. You need Node.js and a Shuup to point it at; the storefront holds no data of its own.

# 1 — get the storefront
git clone https://github.com/itswadesh/svelte-commerce
cd svelte-commerce

# 2 — one connector at a time: remove the two the storefront ships with, add this one
npm uninstall @misiki/litekart-connector @misiki/vendure-connector
npm i @misiki/shuup-connector

# 3 — point it at your Shuup shop
echo PUBLIC_SHUUP_API_URL=https://your-store.example.com >> .env

# 4 — run it
npm run dev

Environment variables

init.ts hands the connector every PUBLIC_SHUUP_* variable that is set, camel-cased. The guide also lists PUBLIC_SHUUP_ACCESS_KEY, PUBLIC_SHUUP_STORE_ID and PUBLIC_SHUUP_CHANNEL_ID; the connector’s source does not read them.

Every variable here begins PUBLIC_, and SvelteKit sends PUBLIC_ variables to the browser: treat each value you set as published.

What to set up on Shuup

• Let the storefront’s origin make cross-origin requests to Shuup (CORS): in production the browser calls PUBLIC_SHUUP_API_URL directly, not only the server.

How the integration works

Shuup’s REST API accepts HTTP Basic, session and JWT authentication. The connector sends a JWT as Authorization: JWT <token> — the header prefix Shuup’s JWT library expects — and falls back to HTTP Basic when it has a username and password instead.

Installing the package is the whole switch. vite.config.ts resolves whichever @misiki/*-connector is installed, and src/lib/core/connectors/init.ts hands it every PUBLIC_SHUUP_* variable that is set, camel-cased, at boot — in the server hook for server rendering and in the client hook for the browser, which must reach the same URL in production.

There is no Litekart API behind the storefront here, so store identity — name, logo, currency, menus, plugin toggles, theme colours — comes from src/lib/core/connectors/default-store.json merged under the default export of kitcommerce.config.ts. Until you override it, the store is called “Test”. Any Litekart REST path the connector still inherits is answered from that local data, or resolved empty, rather than requested.

Limitations

• Coupons: not wired.
• Reviews: not wired.
• CMS pages: not wired — legal and CMS pages render their layout with empty content.
• Countries: not wired.
• States and regions: not wired.
• Wishlist: not wired.
• Pages that depend on a service that is not wired render their empty state rather than failing.
• If you set PUBLIC_SHUUP_API_KEY and PUBLIC_SHUUP_API_SECRET for HTTP Basic, those credentials reach every visitor: SvelteKit sends PUBLIC_ variables to the browser.
• Homepage sections other than the live product list come from the active theme’s static content — the standing rule for themes.
• The Conversational Shopping assistant is Litekart-only; its widget stays hidden when another connector is active.

Troubleshooting

Before you rely on it