Svelte Commerce on PrestaShop

What works on PrestaShop today

Known gaps: auth, review, wishlist, payment-method — each is explained under Limitations below.

24 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 PrestaShop. You need Node.js and a PrestaShop 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/prestashop-connector

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

# 4 — run it
npm run dev

Environment variables

init.ts hands the connector every PUBLIC_PRESTASHOP_* variable that is set, camel-cased. The guide also lists PUBLIC_PRESTASHOP_API_SECRET, PUBLIC_PRESTASHOP_ACCESS_TOKEN, PUBLIC_PRESTASHOP_ACCESS_KEY and PUBLIC_PRESTASHOP_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 PrestaShop

• Enable the webservice and create a key under Advanced Parameters › Webservice, with access to the resources the storefront reads — and read the limitations first.
• Let the storefront’s origin make cross-origin requests to PrestaShop (CORS): in production the browser calls PUBLIC_PRESTASHOP_API_URL directly, not only the server.

How the integration works

The webservice API is PrestaShop’s back-office API, not a storefront one: it has no customer login and no cart-to-order flow. The connector reads the catalogue and manages carts through it, and lists the shop’s active carriers as shipping options — without prices, because PrestaShop computes those outside the webservice.

Writes need care: translatable fields must be sent with <language> children, and echoing a display=full read straight back silently blanks them — a bug the connector hit and fixed.

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_PRESTASHOP_* 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 place an order. The webservice API has no checkout and no payment resource; placing an order is PaymentModule::validateOrder(), which only a front-office payment module can call. So cash on delivery, Razorpay, Stripe and every other way the storefront places an order are placeholders on PrestaShop.
• Sign-in (auth): throws NotSupportedError — PrestaShop 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.
• Reviews: not wired.
• Wishlist: not wired.
• Payment-method listing: not wired.
• Pages that depend on a service that is not wired render their empty state rather than failing.
• Shipping options come without prices: PrestaShop works them out from delivery ranges, zones and modules outside the webservice API.
• The webservice key the connector sends on every call comes from PUBLIC_PRESTASHOP_API_KEY. SvelteKit sends PUBLIC_ variables to the browser, so every visitor to the store can read it and use whatever permissions the key has.
• 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