Overview

The connector keeps Odoo and PrestaShop in sync over the official PrestaShop Webservice API. It covers:

• Products — import PrestaShop products (with variants and images) into Odoo product templates, optionally with stock and tax group, and export Odoo product changes back to the store.
• Customers — import PrestaShop customers (and their addresses) into Odoo contacts.
• Orders — import PrestaShop orders into Odoo sale orders, mapping each order's PrestaShop state id to a sale-order action (keep draft, confirm, cancel, or ignore).
• Refunds — optionally discover PrestaShop order slips (credit notes) attached to an order and create matching draft customer credit notes in Odoo.

Direction of sync: Odoo ↔ PrestaShop (import is the primary flow; product export and webhook-driven updates are supported). Multistore and multilanguage shops are supported via a shop id and a default language id on the instance.

Every remote call goes through a queue: nothing is written to Odoo until a job runs, jobs retry with back-off on transient failures, and a circuit breaker pauses an instance that keeps failing.

Requirements

• Odoo: 19.0, Community or Enterprise.
• PrestaShop: live-tested against PrestaShop 8.0, 8.1, 8.2 and 9.0. The shop must be reachable from the Odoo server and have the Webservice feature enabled.
• Python: no extra libraries beyond a standard Odoo 19 install.
• Odoo access: any internal user can use the connector screens. PrestaShop credentials are stored in system-only fields, so only the Settings / Administration user can read or change the API key and the webhook secret.
• Network: outbound HTTPS from Odoo to your shop. By default the connector refuses internal/loopback/private hosts as an SSRF safeguard (see Safety features).

Installation

1. Copy bambooforge_prestashop_connector into your Odoo addons path.
2. Restart the Odoo service.
3. Open Apps, click Update Apps List, search for PrestaShop, and press Activate / Install. Dependencies (Sales, Contacts, Invoicing) install automatically.

No PrestaShop store is required to evaluate the connector: a mock PrestaShop Webservice ships inside the module (served under /prestashop/mock_api/api), so you can install, explore and run the full import flow against sample data before pointing it at a real store.

Step 1 — Enable the PrestaShop Webservice & create an API key

PrestaShop talks over its built-in Webservice (a REST-style API). You enable it and mint a key in the PrestaShop back office.

1. Log in to the PrestaShop back office as an administrator.
2. Go to Advanced Parameters ▸ Webservice.
3. Set Enable PrestaShop's webservice to Yes and save. (If your store is behind a proxy that strips the HTTP Authorization header, also set Enable HTTP method override to Yes.)
4. Click Add new webservice key.
5. Leave Key to be generated automatically (or click Generate), and set a clear Key description, e.g. Odoo connector.
6. Set Status to Enabled.
7. Under Permissions, grant the resources the connector uses. For a full two-way sync, give View (GET), Add (POST), Modify (PUT) and (optionally) Delete on at least: products, combinations, images, stock_availables, customers, addresses, orders, order_states, order_details and order_slips. View (GET) alone is enough if you only import.
8. Save, then copy the generated Key — this long alphanumeric string is your API key.

The key is used as the HTTP Basic username with an empty password — exactly how the PrestaShop Webservice expects it. The connector handles that for you; you only paste the key.

Optional, for real-time updates, you will also configure a webhook later (see Automation).

Step 2 — Create the connection in Odoo

Open PrestaShop ▸ Configuration ▸ Instances and create a record.

Key fields:

Then click Test Connection. A green Connected state means the key and URL are correct, and the default order-state mapping is seeded automatically on first success. If it fails, the exact error is shown on the form and recorded in Logs (see Troubleshooting).

Tip: use Quick Setup (button on the instance) to pick a solution pack (Catalog Only, B2C Full Sync, B2B Order-First, Retail Starter), seed default field mappings and starter flows, and apply a recommended safety profile in one step.

Step 3 — First sync (dry-run, then live)

New instances start with Dry-run ON. In dry-run, import and delete jobs simulate writes: instead of changing data they produce Validation Results you can review under PrestaShop ▸ Operations ▸ Validation Results. This lets you confirm what would happen before anything is written.

To run a first import:

1. On the instance, click Import Products (and/or Import Customers, Import Orders). This enqueues jobs; it does not block the UI.
2. Jobs are processed by the PrestaShop Queue Processor scheduled action (every minute), or immediately if you open Operations ▸ Queue Jobs and run them.
3. Review Validation Results while still in dry-run.
4. When satisfied, open the instance, turn Dry-run OFF, and run the imports again to write the records for real.

Imported records land in the standard Odoo apps: Sales ▸ Products, Contacts, and Sales ▸ Orders (refunds appear as draft credit notes in Invoicing). Each carries its PrestaShop reference so re-imports update the same record instead of duplicating it.

Order status mapping

PrestaShop returns each order's state as a numeric id (its current_state), not a slug. Under Configuration ▸ Order State Mappings each instance gets a default table (seeded on first successful Test Connection) that decides what happens to the Odoo sale order when an order arrives in a given PrestaShop state:

Change any row to Ignore (do nothing), Keep draft, Confirm sale order or Cancel sale order. Unknown/custom state ids default to Ignore, so a state you have not mapped never triggers a destructive transition. Add a row for any custom state your shop introduces (use the exact PrestaShop numeric state id).

Field mapping & customization

• Field Mappings (Configuration) map PrestaShop fields to Odoo fields per model. Use Generate suggested mappings on the instance to seed the business-critical ones, then adjust. The mapping board flags fields that need attention.

• Schema Fields lists the discovered PrestaShop fields per resource. Run Schema Introspection on the instance to refresh it from your live store (or from the bundled mock when evaluating).

• Stock / images / tax are opt-in toggles on the instance, all off by default; turn on only what you need:

  Toggle	What it does
  Sync Stock	Reads stock_available and writes the PrestaShop quantity on the product template.
  Sync Taxes	Resolves the PrestaShop tax_rules_group and stores it on the product (best effort).
  Auto-match Taxes on Import	With Sync Taxes, matches the PrestaShop tax group name to an existing Odoo sales tax in the same company. Never auto-creates taxes.
  Sync Images	Downloads the first PrestaShop image as the Odoo product cover image.
  Max Images	How many images to download per product (default 1; only the first becomes the cover, the rest go to product images).
  Upload Images on Export	When exporting a product, also uploads its images to PrestaShop.
  Sync Refunds	On order import, discovers attached order slips and creates a draft customer credit note.
  Auto-post Refund	Auto-validates the refund credit note instead of leaving it draft (off by default so accountants review first).

Automation (scheduled actions & webhooks)

The module ships these scheduled actions (Settings ▸ Technical ▸ Scheduled Actions):

Turn on Auto import / Auto reconcile per model on the instance to let the scheduled actions keep things in sync hands-free.

Real-time webhooks (optional): the connector exposes a single public route that accepts signed deliveries:

• Delivery URL: https://<your-odoo-domain>/prestashop/webhook
• Signature header: X-Prestashop-Signature — an HMAC-SHA256 hex digest of the raw request body, keyed with the instance Webhook Secret (admin-only field on the instance).

The shipped PHP companion module posts to this route with the correct signature. Odoo verifies the signature on every delivery, rejects stale or replayed requests, and enqueues a safe import. The route accepts product, customer, order and order_slip events, and you can target a specific instance with an instance_id (or base_url) query parameter. Without webhooks, the scheduled reconciliation still keeps data current.

Safety features

• Dry-run mode — simulate writes and review Validation Results before going live (field Dry-run, ON by default).
• Business validation profiles — Minimal / Standard / Strict gate risky writes (field Business Validation Profile).
• Safety profiles — Conservative / Balanced / Aggressive set sensible defaults for dry-run, delete strategy and batch size in one click.
• Resilient queue — every remote action is a job with retry and exponential back-off, and a dead-letter queue for exhausted jobs.
• Circuit breaker — after repeated failures (or an auth/config error) an instance auto-pauses (Tripped); the Auto Recover action reopens it once the store responds again, or click Resume.
• Rollback snapshots — when enabled, imports capture a snapshot so you can undo a batch from Operations ▸ Rollback Snapshots.
• SSRF guard — the connector refuses internal/loopback/private/reserved hosts; Base URL must be a public http(s) address.
• Signed webhooks with replay protection — deliveries must carry a valid HMAC-SHA256 signature and a fresh emitted_at; duplicates are rejected.

Troubleshooting

For anything else, Operations ▸ Logs records every API call, payload and error with a timestamp.

Frequently asked questions

Which versions are supported? Odoo 19.0 on the Odoo side. On the store side the connector was live-tested on PrestaShop 8.0, 8.1, 8.2 and 9.0 over the PrestaShop Webservice. Validate your exact build with the bundled mock first.

Do I need PrestaShop installed to evaluate it? No. A mock PrestaShop Webservice ships inside (served at /prestashop/mock_api/api), so you can install, explore and demo the full import flow before connecting a real store.

How does authentication work? You enable the Webservice and create a key under Advanced Parameters ▸ Webservice in the PrestaShop back office. Paste that key into the instance's API Key field. The connector sends it as the HTTP Basic username with an empty password — the standard PrestaShop scheme.

How does real-time sync work? The shipped PHP companion posts signed events to /prestashop/webhook with an HMAC-SHA256 X-Prestashop-Signature over the raw body, keyed with the instance webhook secret. Odoo verifies the signature, rejects stale/replayed requests, and enqueues a safe import. Without it, scheduled reconciliation keeps things in sync.

How are multistore and multiple languages handled? Set Shop ID to scope requests to one store (0 = all), and Default Language ID to choose which PrestaShop language is flattened into Odoo's single-language fields.

Is it safe to run against production data? Dry-run is ON by default, validation blocks risky writes, and rollback snapshots let you undo. You decide when to go live.

What support and refund policy do I get? Every request is answered within 24 hours, setup help included. If you report a bug within 2 months of purchase and it is not resolved within 15 days, you are entitled to a full money-back refund.

Data, privacy & limits

• The connector reads products, customers, orders and order slips from your store and writes the corresponding Odoo records. The API key and webhook secret are stored in admin-only fields.
• In scope today: product/customer/order import, product export, numeric order-state mapping, refund (order slip) discovery, multistore/multilang flattening, scheduled sync, signed webhooks.
• Out of scope / best-effort: tax auto-matching (off by default, name-based, never auto-creates taxes); multi-warehouse stock routing; subscription/booking order types.

Support & updates

• Support: bambooforge.labs@gmail.com — answered within 24 hours, setup help included.
• Refund: report a bug within 2 months of purchase; if unresolved within 15 days, full refund.
• Full source is included. Updates track the supported Odoo 19 / PrestaShop 8.0–9.0 line.

Upgrading & version compatibility

This build targets Odoo 19.0. Each Odoo major series (17.0, 18.0, 19.0) has its own dedicated build of this module — always install the build that matches your Odoo version. Mixing a build with a different Odoo series is not supported.

Uninstallation

You can remove this module at any time from Apps → (this module) → Uninstall, or from the command line. Uninstalling is clean and reversible by reinstalling — but note what is and is not deleted.

Changelog