Svelte Commerce on Virto Commerce

What works on Virto Commerce today

Known gaps: none recorded.

28 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 Virto Commerce. You need Node.js and a Virto Commerce 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/virto-connector

# 3 — point it at your Virto Commerce platform
echo PUBLIC_VIRTO_COMMERCE_API_URL=https://your-store.example.com >> .env

# 4 — run it
npm run dev

Environment variables

init.ts hands the connector every PUBLIC_VIRTO_COMMERCE_* variable that is set, camel-cased — the prefix follows the product, not the package, which is virto-connector. The guide also lists PUBLIC_VIRTO_COMMERCE_API_KEY, PUBLIC_VIRTO_COMMERCE_API_SECRET, PUBLIC_VIRTO_COMMERCE_ACCESS_KEY and PUBLIC_VIRTO_COMMERCE_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 Virto Commerce

• Configure the payment methods you want shoppers to use on the Virto store itself: the connector places orders through cart.availablePaymentMethods, and refuses a gateway the store does not offer.
• Let the storefront’s origin make cross-origin requests to Virto Commerce (CORS): in production the browser calls PUBLIC_VIRTO_COMMERCE_API_URL directly, not only the server.

How the integration works

The connector speaks Virto Commerce’s GraphQL API, which wants culture, currency and catalogue as explicit arguments on most operations. Whatever you leave unset is read once from the store’s own record and remembered. Checkout places the order with a payment method the store exposes, matched by name — or, for cash on delivery, by a manual payment method.

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

• No gaps are recorded for Virto Commerce in CONNECTORS.md.
• 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