# Bagisto SvelteKit Storefront — Svelte Commerce Connector

> Svelte Commerce on Bagisto: 22 of 43 services wired, with cart, checkout and sign-in; coupons, pages, payment methods and vendors are gaps. Setup and fixes.

- Canonical: https://kitcommerce.store/svelte-commerce/backends/bagisto/
- Last updated: 2026-09-25

---

Svelte Commerce × Bagisto

## Svelte Commerce on Bagisto

Solid core coverage: cart, checkout and sign-in are wired against Bagisto’s REST API. Bagisto chooses the channel by the request’s host, and takes locale and currency as headers.

- **22/43** services wired
- **@misiki/bagisto-connector** 0.4.0
- **Cart** wired
- **Checkout** wired
- **Sign-in (auth)** wired

### What works on Bagisto today

Cart, checkout and sign-in are wired; coupons, CMS pages, payment-method listing and vendors are not.

#### Cart

Wired: issues a real request to Bagisto.

#### Checkout

Wired: issues a real request to Bagisto.

#### Sign-in (auth)

Wired: issues a real request to Bagisto.

**Known gaps:** `coupon`, `page`, `payment-method`, `vendor` — each is explained under Limitations below.

22 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 Bagisto. You need Node.js and a Bagisto to point it at; the storefront holds no data of its own.

Clone it, choose the connector, point it at Bagisto

```
# 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/bagisto-connector

# 3 — point it at your Bagisto channel
echo PUBLIC_BAGISTO_API_URL=https://your-store.example.com >> .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 Bagisto*

| Variable | Required | What it does |
| --- | --- | --- |
| `PUBLIC_BAGISTO_API_URL` | Yes | Your Bagisto URL. Bagisto picks the channel by matching the request’s host, so point this at the channel’s hostname. Boot fails, naming this variable, if it is missing. |
| `PUBLIC_BAGISTO_ACCESS_TOKEN` | No | A Sanctum token, sent as a bearer token when set. |
| `PUBLIC_BAGISTO_LOCALE` | No | Sent as `x-locale`; an unknown value falls back to the channel default. |
| `PUBLIC_BAGISTO_CURRENCY` | No | Sent as `x-currency`; an unknown value falls back to the channel default. |
| `PUBLIC_CONNECTOR` | No | Only when more than one connector is installed: `@misiki/bagisto-connector` names the one this build runs on. |

`init.ts` hands the connector every `PUBLIC_BAGISTO_*` variable that is set, camel-cased. The guide also lists `PUBLIC_BAGISTO_STORE_ID` and `PUBLIC_BAGISTO_CHANNEL_ID`, which have no effect over Bagisto’s REST API — the channel comes from the host — and `PUBLIC_BAGISTO_API_KEY`, `PUBLIC_BAGISTO_API_SECRET` and `PUBLIC_BAGISTO_ACCESS_KEY`, which the connector’s source does not read.

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 Bagisto

- Point `PUBLIC_BAGISTO_API_URL` at the hostname of the channel you want to sell from: Bagisto matches the request’s host against its channels’ hostnames, falling back to the first channel.
- Let the storefront’s origin make cross-origin requests to Bagisto (CORS): in production the browser calls `PUBLIC_BAGISTO_API_URL` directly, not only the server.

### How the integration works

Bagisto has no channel header or parameter: it matches the request’s host against its channels’ hostnames. Locale and currency travel as the `x-locale` and `x-currency` headers, and signed-in shoppers carry a Sanctum bearer token. The storefront also ships a `/proxy/bagisto/*` route that forwards to `PUBLIC_BAGISTO_API_URL`.

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_BAGISTO_*` 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.
- CMS pages: not wired — legal and CMS pages render their layout with empty content.
- Payment-method listing: not wired.
- Vendors: not wired.
- Pages that depend on a service that is not wired render their empty state rather than failing.
- 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 Bagisto, and what fixes them*

| When you see | What to do |
| --- | --- |
| Boot fails with “the bagisto connector is active but PUBLIC_BAGISTO_API_URL is not set” | Add `PUBLIC_BAGISTO_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/bagisto-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. |
| `[bagisto] 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 Bagisto 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 Bagisto

**Can I run a Bagisto store on Svelte Commerce today?**

Cart, checkout and sign-in are wired; coupons, CMS pages, payment-method listing and vendors are not. Like every connector, it has not been run against a live production Bagisto store.

**How do I switch Svelte Commerce to Bagisto?**

Remove the connectors the storefront ships with, install @misiki/bagisto-connector, set PUBLIC_BAGISTO_API_URL in .env and start the dev server. vite.config.ts resolves whichever connector is installed, so no file in the storefront changes.

**How do I choose a Bagisto channel, locale or currency?**

The channel by host: point PUBLIC_BAGISTO_API_URL at the channel’s hostname. Locale and currency by variable: PUBLIC_BAGISTO_LOCALE and PUBLIC_BAGISTO_CURRENCY travel as the x-locale and x-currency headers, and unknown values fall back to the channel default.

**Has the Bagisto connector been run against a real Bagisto store?**

Not against a live production instance — no Svelte Commerce connector has been. It was written by reading Bagisto’s authoritative API source, and the Svelte Commerce maintainers ask Bagisto’s own maintainers for a sandbox to run it against.

### Sources

This page summarises BAGISTO.md in the Svelte Commerce repository and the Bagisto 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. Bagisto 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).

- [BAGISTO.md — the full guide for Bagisto](https://github.com/itswadesh/svelte-commerce/blob/main/docs/BAGISTO.md)
- [CONNECTORS.md — coverage for all 26 connectors](https://github.com/itswadesh/svelte-commerce/blob/main/docs/CONNECTORS.md)
- [@misiki/bagisto-connector on npm](https://www.npmjs.com/package/@misiki/bagisto-connector)
- [Bagisto](https://bagisto.com)

### Read the whole guide

The storefront is the same on every backend; the connector is what changes. BAGISTO.md has the Bagisto setup in full, beside the connector’s source.

[The Bagisto guide on GitHub](https://github.com/itswadesh/svelte-commerce/blob/main/docs/BAGISTO.md) · [All 26 backends](https://kitcommerce.store/svelte-commerce/backends/) · [KitCommerce vs Bagisto](https://kitcommerce.store/compare/kitcommerce-vs-bagisto/)