# CS-Cart SvelteKit Storefront — Svelte Commerce Connector > Svelte Commerce on CS-Cart: 20 of 43 services wired. Browsing and cart work, but there is no shopper sign-in and the storefront cannot complete an order. - Canonical: https://kitcommerce.store/svelte-commerce/backends/cs-cart/ - Last updated: 2026-09-25 --- Svelte Commerce × CS-Cart ## Svelte Commerce on CS-Cart The CS-Cart connector covers browsing and the cart through CS-Cart’s REST API, which has no checkout resource and no shopper sign-in. It authenticates every call with an admin’s e-mail and API key. - **20/43** services wired - **@misiki/cs-cart-connector** 0.4.0 - **Cart** wired - **Checkout** wired - **Sign-in (auth)** no endpoint on the platform ### What works on CS-Cart today Shoppers can browse and fill a cart, but cannot sign in, and the storefront cannot complete an order. CS-Cart’s REST API has no checkout resource; the one call that creates an order sits in the connector’s `orderService.codCheckout()`, which the storefront’s payment step does not call, so every way it places an order throws `NotSupportedError`. #### Cart Wired: issues a real request to CS-Cart. #### Checkout Wired: issues a real request to CS-Cart. #### Sign-in (auth) No endpoint on CS-Cart: it throws NotSupportedError rather than pretend. **Known gaps:** `auth`, `address`, `country`, `state`, `currency`, `coupon`, `wishlist` — each is explained under Limitations below. 20 of 43 services wired, read from [CONNECTORS.md](https://github.com/itswadesh/svelte-commerce/blob/main/docs/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. Clone it, choose the connector, point it at CS-Cart ``` # 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 ``` The guide removes only `@misiki/litekart-connector`. A fresh clone’s `package.json` also lists `@misiki/vendure-connector`, and with two connectors installed and neither of them Litekart’s, the build stops and asks for `PUBLIC_CONNECTOR` — so this removes both. ### Environment variables *What Svelte Commerce reads to reach CS-Cart* | Variable | Required | What it does | | --- | --- | --- | | `PUBLIC_CS_CART_API_URL` | Yes | Your CS-Cart store’s URL. Boot fails, naming this variable, if it is missing. | | `PUBLIC_CS_CART_API_KEY` | No | Despite the name, an admin’s e-mail address — the HTTP Basic username. See the limitations. | | `PUBLIC_CS_CART_API_SECRET` | No | The API key generated for that admin in the CS-Cart admin panel — the HTTP Basic password. | | `PUBLIC_CS_CART_STORE_ID` | No | Company ID for company-scoped routes on CS-Cart Ultimate and Multi-Vendor, such as `/api/stores/{id}/orders`. `PUBLIC_CS_CART_CHANNEL_ID` is read if it is unset. | | `PUBLIC_CS_CART_CHANNEL_ID` | No | Read as the company ID when `PUBLIC_CS_CART_STORE_ID` is unset. | | `PUBLIC_CONNECTOR` | No | Only when more than one connector is installed: `@misiki/cs-cart-connector` names the one this build runs on. | `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 *Errors you may meet running Svelte Commerce on CS-Cart, and what fixes them* | When you see | What to do | | --- | --- | | Boot fails with “the cs-cart connector is active but PUBLIC_CS_CART_API_URL is not set” | Add `PUBLIC_CS_CART_API_URL` to `.env`. A production Node build and Docker read `PUBLIC_*` from the process environment rather than `.env`, so set it on your deploy platform too. | | The build stops with “Several commerce connectors are installed … Set PUBLIC_CONNECTOR to pick one” | More than one `@misiki/*-connector` is in `package.json` and none is Litekart’s. Uninstall the ones you do not run — a fresh clone also lists `@misiki/vendure-connector` — or set `PUBLIC_CONNECTOR='@misiki/cs-cart-connector'`. | | Boot fails with “PUBLIC\_…\_API_URL is set, but it configures a different backend than the one this build runs on” | Another backend’s variable is still set, usually left over from the one you switched from. Remove it, or install that backend’s connector. `PUBLIC_LITEKART_API_URL` is exempt: it only points the dev proxy. | | The store is called “Test”, or shows the wrong name and logo | Store identity is static on this backend. Set `name`, `logo`, `currencyCode` and the rest in the default export of `kitcommerce.config.ts`; `src/lib/core/connectors/default-store.json` lists every field. | | `[cs-cart] no native implementation for get /api/...` in the console | The connector’s REST guard caught a path inherited from Litekart and answered it empty instead of requesting it. Each path is reported once. Harmless if CS-Cart has no such feature; if it has one, the fix belongs in the connector’s matching service. | | `http proxy error: api/... ECONNREFUSED` in dev | A Litekart REST path was requested from outside the connector, so its guard never saw it. Vite proxies `/api` to `PUBLIC_LITEKART_API_URL`, or to `localhost:7000`. | | The build fails on `@misiki/litekart-connector` | `@misiki/kitcommerce-core` declares it as a peer, and `vite.config.ts` redirects that specifier to whichever connector is installed. Make sure exactly one `@misiki/*-connector` is listed in `package.json`. | ### Before you rely on it #### The one caveat that matters Read this before choosing Every connector was written by reading its platform’s authoritative source — an OpenAPI spec, a RAML file, a router registration or the controller source — rather than by running against a store. **No connector has been exercised against a live production instance of its platform.** [Offer a sandbox or a correction](https://github.com/itswadesh/svelte-commerce/discussions/new/choose) FAQ ### Questions about Svelte Commerce on CS-Cart **Can I run a CS-Cart store on Svelte Commerce today?** No. Shoppers can browse and fill a cart, but there is no shopper sign-in and the storefront cannot complete an order. The connector also authenticates with an admin’s credentials from PUBLIC\_ variables, which every visitor’s browser receives. **How do I switch Svelte Commerce to CS-Cart?** Remove the connectors the storefront ships with, install @misiki/cs-cart-connector, set PUBLIC_CS_CART_API_URL in .env and start the dev server. vite.config.ts resolves whichever connector is installed, so no file in the storefront changes. **Why can’t Svelte Commerce complete an order on CS-Cart?** CS-Cart’s REST API has no checkout resource. The only call that places an order, POST /api/orders, lives in the connector’s orderService.codCheckout(), and the storefront’s payment step calls per-gateway methods instead, which throw on CS-Cart. **Has the CS-Cart connector been run against a real CS-Cart store?** Not against a live production instance — no Svelte Commerce connector has been. It was written by reading CS-Cart’s authoritative API source, and the Svelte Commerce maintainers ask CS-Cart’s own maintainers for a sandbox to run it against. ### Sources This page summarises CS-CART.md in the Svelte Commerce repository and the CS-Cart connector’s source, read on 25 September 2026, and the coverage in CONNECTORS.md, read on 21 September 2026. Where they disagree with this page, they are right and this page is out of date. CS-Cart is a trademark of its owner, named here only to describe compatibility; no endorsement or affiliation is implied — see [trademarks](https://kitcommerce.store/about/#trademarks). - [CS-CART.md — the full guide for CS-Cart](https://github.com/itswadesh/svelte-commerce/blob/main/docs/CS-CART.md) - [CONNECTORS.md — coverage for all 26 connectors](https://github.com/itswadesh/svelte-commerce/blob/main/docs/CONNECTORS.md) - [@misiki/cs-cart-connector on npm](https://www.npmjs.com/package/@misiki/cs-cart-connector) - [CS-Cart](https://www.cs-cart.com) ### Read the whole guide The storefront is the same on every backend; the connector is what changes. CS-CART.md has the CS-Cart setup in full, beside the connector’s source. [The CS-Cart guide on GitHub](https://github.com/itswadesh/svelte-commerce/blob/main/docs/CS-CART.md) · [All 26 backends](https://kitcommerce.store/svelte-commerce/backends/)