Skip to main content

Connect your PrestaShop store to Clione

Plans: Starter ✓ · Growth ✓ · Pro ✓ · Agency ✓

You need: an administrator account in your PrestaShop back office, and your shop served over https.

A PrestaShop store connects with one thing: a Webservice key you create in your back office. Clione uses it to read your catalog — products with their combinations, categories and CMS pages, in every language your shop has installed.

What Clione does and does not do with a PrestaShop store today​

Read this before you connect, because PrestaShop support is not yet at the same stage as the other platforms:

Reads your catalog✅ Products, combinations, categories, CMS pages, all languages
Enriches with AI✅ The same pipeline as every other platform
Writes signals back to your shop❌ Not yet.

Nothing Clione generates reaches your storefront yet. Writing signals to PrestaShop needs a Clione module for your shop, which is being built; until it exists, Clione reads your catalog and will not write a single field back. You can connect, sync and enrich now, and see what Clione produces — it stays in Clione until the module ships.

We say this plainly rather than let you discover it: if what you need today is signals on the page, BigCommerce, Shopify and WooCommerce do that now. See Connect BigCommerce, Connect Shopify or Connect WooCommerce.

Step 1 — Create a Webservice key​

  1. In your back office, go to Advanced Parameters → Webservice.
  2. Set Enable PrestaShop's webservice to Yes and save.
  3. Click Add new webservice key.
  4. Leave the key as PrestaShop generates it, and give it a Key description you will recognise later, such as Clione.
  5. Set Status to Enabled.
  6. In the permissions table, tick View (GET) on these five resources and nothing else:
    • products
    • combinations
    • categories
    • content_management_system
    • languages
  7. Save, and copy the key.

View is all Clione needs, and all you should grant. It cannot add, change or delete anything in your shop with a View-only key — not by accident, and not if someone else got hold of the key.

Why combinations is separate

In PrestaShop a product's variants (combinations) are their own resource rather than part of the product, so Clione needs View on both or your products arrive without their sizes, colours and per-variant prices.

Why languages

Your language IDs are specific to your shop — ID 1 is whichever language was installed first, which is not necessarily English. Clione reads the list so it knows which language is your main one, instead of guessing and reading a secondary translation as if it were your primary text.

Step 2 — Add the store in Clione​

  1. In Clione, go to Add store and choose PrestaShop.
  2. Give the store a name, and enter your shop URL — the home page of your shop, over https (for example https://shop.example.com).
  3. Paste the Webservice key.
  4. Save.

Clione checks the key immediately by reading your language list. If that fails, the error says which part failed rather than just "could not connect".

Step 3 — Sync your catalog​

Run Sync from the store's page. Clione reads your products with their combinations, your categories and your CMS pages.

Two things you will notice, and both are deliberate:

  • Your "Root" and "Home" categories do not appear. Every PrestaShop install has them above your real categories; no shopper ever lands on them, so Clione skips them rather than spend an enrichment on a page nobody sees.
  • A sync never runs the AI. Syncing is free and reads your shop; enriching costs credits and only ever happens when you ask for it.

Step 4 — Install the Clione module (for when signals go live)​

The module is what prints Clione's structured data into your pages. It does nothing yet: Clione does not write to PrestaShop storefronts at the moment (see the table at the top). Install it now if you want to be ready, or wait.

  1. Download clione-<version>.zip from your Clione dashboard.
  2. In your back office, go to Modules → Module Manager → Upload a module and drop the zip in.
  3. Open its Configure screen and paste the four values your Clione dashboard shows: the API URL, the API key, the organisation ID and the store ID.
  4. Save.

Why four values and not one: the module ships with no URL and no key in it. That is deliberate — a module with our endpoint baked in cannot be pointed at a test environment, and a key inside a file that gets distributed is a key in everybody's hands. You are pasting your own.

What the module does to your shop: it adds one table for the signals Clione sends, and it reads that table when a page is built. It does not change your products, your categories, your pages or your theme. Uninstalling removes its table and its settings and leaves everything else untouched.

Which permissions it needs: none beyond the Webservice key from step 1. Clione writes the signals through the same Webservice, as the module's own resource, so you can revoke our write access from the same screen without touching anything else.

Requirements and limits​

  • https is required. The Webservice key is sent as the username of an HTTP Basic auth header, so over plain http anyone on the network path could read it. Clione refuses an http:// shop URL rather than send your key in the clear.
  • Your shop must answer JSON. Clione asks the Webservice for JSON. If your PrestaShop version replies in XML instead, Clione tells you so by name and syncs nothing, rather than importing a catalog of nameless products.
  • Clione reads gently. Two requests per second at most. A full catalog takes a few minutes rather than a few seconds, on purpose: the Webservice loads your whole shop for each request, and a fast import is an import that slows your checkout down.
  • Multi-shop installations are not supported yet.

Troubleshooting​

"Could not connect" straight after saving the key. Check, in this order: the webservice is enabled (step 1.3), the key's status is Enabled, the key has View on languages, and your shop URL is the https home page with no path after it.

Products arrive with no variants. The key is missing View on combinations. Add it and sync again.

CMS pages are missing. The key is missing View on content_management_system.

Products arrive in the wrong language. Clione uses whichever language your shop lists first among its active languages. Check International → Localization → Languages: the order and the Enabled column there decide which language Clione treats as your main one.

A product has no name. That is the symptom of a shop whose Webservice is answering XML rather than JSON. Clione normally refuses the sync outright for this reason; if you see it, tell support and include your PrestaShop version.