Skip to main content
IntegrationsPrestaShop
PrestaShop · production

The PrestaShop procurement agent, end to end.

Stokis is built around PrestaShop as a first-class citizen — because PrestaShop is dominant in EU and Eastern European B2B e-commerce, the market the big procurement vendors ignore. Versions 1.7 through 9, in production with paying customers since the start. Setup takes about ten minutes, doesn’t touch your theme, your modules, or your customer data — and is read-only until you flip on stock write-back.

Versions

One adapter, three major versions.

PrestaShop powers more than 250,000 stores worldwide and is dominant in Southern Europe e-commerce. The adapter handles every supported major version transparently — you don’t upgrade your store to use Stokis.

1.7

PrestaShop 1.7

Full support. The adapter handles 1.7’s older webservice quirks transparently — you don’t need to upgrade to use Stokis.

8.x

PrestaShop 8

Full support. Works with the new Symfony-based back office. Multi-shop installations supported per workspace.

9.x

PrestaShop 9

Full support. We track 9.x development and ship adapter updates within a sprint of major releases.

Read, write, never touch

Trust starts with knowing what’s connected.

Most “integrations” are a black box: connect, hope, debug. Stokis publishes the full read/write surface up front. If a row isn’t on this list, the agent doesn’t see it and can’t change it.

DataDirectionFrequencyNotes
Products & variantsReadHourlyPrestaShop reference → Stokis SKU
Stock on handReadHourlystock_availables per product · per warehouse
Orders & line itemsReadHourlyLast 90 days at sign-up; rolling thereafter
Categories & taxReadDailyFor grouping and supplier matching
Supplier email repliesRead (BYO mailbox)ContinuousIMAP or forwarder · raw mail preserved
Stock adjustment on PO receiveWriteOn receiveOff by default · explicit opt-in per workspace
Supplier list, payment terms, lead timesLocal to StokisNever written back to your store
Customer data (names, addresses, emails)Never readStokis only needs aggregate sales, not customers
Setup, in four steps

Ten minutes, no module install.

  1. 01

    Generate a webservice key

    In PrestaShop back office: Advanced Parameters → Webservice → Add new key. Tick read access for products, stock_availables, orders, categories, taxes. Tick write only for stock_availables when you’re ready to push received stock back.

  2. 02

    Paste the key into Stokis

    Workspace settings → Integrations → PrestaShop. We test the connection on save. If a permission is missing, we name it exactly so you know what to tick. No copy-paste guesswork.

  3. 03

    Watch the first sync

    The first pull imports your full catalogue, current stock, and the last ninety days of orders. A 5,000-SKU store typically completes in under three minutes. You see the progress per resource — products, stock, orders — and any rows the adapter couldn’t match.

  4. 04

    Trigger your first agent run

    Add at least one supplier (manual entry or CSV import), set your auto-send cap, and click “Run agent”. The first run is draft-only — nothing leaves Stokis. You watch the agent work for a week before flipping auto-send on.

Built for the realities

Multi-currency, multi-shop, multi-warehouse — native.

Real PrestaShop stores aren’t single-currency, single-shop, single-warehouse. The adapter handles every combination without making you flatten your data first.

Multi-currency

If your supplier invoices in GBP and your store sells in EUR, Stokis keeps both. POs stay in the supplier’s currency end to end. Workspace KPIs convert at the latest ECB rate, with the rate stamped on the page. We never destructively convert.

Multi-shop

One PrestaShop multi-shop install can map to one or many Stokis workspaces. Most operators run one workspace and let the agent group POs across shops by supplier. Some prefer a workspace per shop. Either works.

Multi-warehouse

If you run advanced stock management with multiple warehouses, Stokis reads the per-warehouse stock and uses it in the forecast. Reorder points are per warehouse where it matters and rolled up where it doesn’t.

Forked installs

If your PrestaShop is heavily customised — non-standard product fields, modified webservice, override modules — we’ll do a sandbox connect first and tell you what works. No surprises after sign-up.

PrestaShop questions

Setup, security, what gets touched.

1.7, 8.x, and 9.x — all on the same adapter. We test the integration weekly against a 1.7 reference store and an 8.x reference store. If you’re on a heavily forked PrestaShop, we’ll do a sandbox connect first to confirm.
Generate a webservice key in PrestaShop’s back office (Advanced Parameters → Webservice). Paste it into Stokis. We test the connection on save — if it fails, we tell you exactly which permission is missing. No module to install, no theme code to change.
Products, stock_availables, and orders — pulled hourly via PrestaShop’s REST webservice. Categories and tax classes are pulled daily. We only fetch deltas after the first sync, so the load on your store stays minimal even with a 50,000-SKU catalogue.
By default, no. We’re read-only until you flip on stock write-back. When you do, the only thing we touch is stock_availables — incrementing on hand quantities when a PO is received. We never edit prices, descriptions, categories, customers, or orders.
The agent fails safe. If a sync fails, the next run skips that workspace and emails you within fifteen minutes. No drafted POs disappear; nothing is sent on stale data. When the store comes back, the next hourly run picks up where it left off.
Yes — that’s the design. Procurement runs in Stokis; everything else stays where it is. Customer service, returns, the storefront itself — none of it changes. Your team can keep using PrestaShop’s BO; Stokis just stops them having to draft POs by hand.
Live in production

Connect PrestaShop, watch a real run.

No card. The agent stays read-only until you turn on auto-send. Cancel anytime. Operators on PrestaShop 1.7 through 9 are running on it today.