Svelte Commerce on CS-Cart

What works on CS-Cart today

Known gaps: auth, address, country, state, currency, coupon, wishlist — each is explained under Limitations below.

20 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 CS-Cart. You need Node.js and a CS-Cart 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/cs-cart-connector

# 3 — point it at your CS-Cart store
echo PUBLIC_CS_CART_API_URL=https://your-store.example.com >> .env
echo PUBLIC_CS_CART_API_KEY=admin@example.com >> .env
echo PUBLIC_CS_CART_API_SECRET=... >> .env

# 4 — run it
npm run dev

Environment variables

init.ts hands the connector every PUBLIC_CS_CART_* variable that is set, camel-cased. The guide also lists PUBLIC_CS_CART_ACCESS_TOKEN and PUBLIC_CS_CART_ACCESS_KEY; 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 CS-Cart

• Generate an API key for an admin in the CS-Cart admin panel — and read the limitations before putting it anywhere a browser can see.
• Let the storefront’s origin make cross-origin requests to CS-Cart (CORS): in production the browser calls PUBLIC_CS_CART_API_URL directly, not only the server.

How the integration works

CS-Cart has one REST surface under two version prefixes, authenticated with HTTP Basic: an admin’s e-mail as the username and their generated API key as the password. On CS-Cart Ultimate and Multi-Vendor many routes are company-scoped, and the connector reads the company ID from the store variable rather than assuming 1.

There is no checkout entity in the REST API: payment methods are configuration records, and the only call that places an order is POST /api/orders, which creates it unpaid. The connector puts that in orderService.codCheckout(), and leaves every capture unimplemented, because marking an order paid without verifying a payment provider’s signature would be a fraud hole.

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_CS_CART_* 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

• The storefront cannot complete an order. Its payment step calls one method per gateway, and on CS-Cart each throws NotSupportedError; the connector’s orderService.codCheckout(), which does create an order, is not called by the storefront yet.
• Sign-in (auth): throws NotSupportedError — CS-Cart has no core endpoint that returns a shopper session, and a stub that signed anyone in for any password would be an auth bypass, not a placeholder.
• Saved addresses: not wired.
• Countries: not wired.
• States and regions: not wired.
• Currencies: not wired.
• Coupons: not wired.
• Wishlist: not wired.
• Pages that depend on a service that is not wired render their empty state rather than failing.
• The connector signs every call with an admin’s e-mail and API key, taken from PUBLIC_CS_CART_API_KEY and PUBLIC_CS_CART_API_SECRET. SvelteKit sends PUBLIC_ variables to the browser, so every visitor to the store can read both and use that admin’s API access.
• 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