PrestaShop

Read PrestaShop products, combinations, stock, customers, addresses, orders, carts, categories and manufacturers; create and update products, stock, addresses, order status and tracking.

Connect a self-hosted PrestaShop store to ERP, warehouse and CRM flows for catalogue, stock and order processing.

Build a flow with PrestaShop Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

addresses

Create address
Destination
Not retried automatically
Approval before production
Add an address to a customer.
addresses.create
List addresses
Source
Incremental
Customer addresses, optionally for one customer or updated since a date.
addresses.list

carts

List carts
Source
Incremental
Carts (including abandoned ones) updated since a date, with rows.
carts.list

categories

List categories
Source
Catalogue categories with parent and depth.
categories.list

combinations

List combinations
Source
Product variants (combinations) with reference, EAN and price impact.
combinations.list

customers

Get customer
Source
One customer with consent flags.
customers.get
List customers
Source
Incremental
Customers, optionally updated since a date or by email.
customers.list
Update customer
Destination
Provider duplicate protection
Approval before production
Patch a customer's name, email, company, consent or active flag.
customers.update

manufacturers

List manufacturers
Source
Brands (manufacturers).
manufacturers.list

order carriers

List order carriers
Source
Carrier, weight, shipping cost and tracking number per order.
order_carriers.list
Set tracking number
Destination
Provider duplicate protection
Approval before production
Set the tracking number on an order carrier record.
order_carriers.update

order histories

Change order status
Destination
Not retried automatically
Approval before production
Move an order to an explicit state ID, optionally emailing the customer.
order_histories.create

order states

List order states
Source
Order state IDs with names and paid, shipped and delivered flags.
order_states.list

orders

Get order
Source
One order with lines and totals.
orders.get
List orders
Source
Incremental
Orders updated since a date with lines, totals and current state.
orders.list

products

Create product
Destination
Not retried automatically
Approval before production
Create a product with name, explicit price, default category and reference.
products.create
Get product
Source
One product with categories, combinations and stock associations.
products.get
List products
Source
Incremental
Products, optionally updated since a date or by reference.
products.list
Update product
Destination
Provider duplicate protection
Approval before production
Patch mapped product fields; price only when mapped.
products.update

stock availables

List stock
Source
Stock quantities per product and combination.
stock_availables.list
Set stock quantity
Destination
Provider duplicate protection
Approval before production
Set the quantity on a stock record (product or combination).
stock_availables.update

Authentication

Webservice key (HTTP Basic username, empty password)

Plans and access

PrestaShop 8.0 or later (open source, self-hosted) with the webservice enabled. Each webservice key is granted GET, POST, PATCH and PUT per resource in Advanced Parameters → Webservice.

Test environment

Use a staging PrestaShop installation.

Rate limits

No built-in rate limit; throughput depends on the shop's hosting.

Pagination

limit=offset,count with display=full; a short page ends paging.

Provider events

Module hooks (no native webhooks). Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

Requires PrestaShop 8.0+ (PATCH and JSON output); the shop must be installed at the domain root.
Writes are sent as XML because the webservice does not accept JSON input; responses are read as JSON.
Order status changes use order_histories; order state IDs are shop-specific and payment modules may react to states such as Refunded or Canceled, so map only states your process allows.
Customer creation (requires a password), order creation, deletes and refunds are not implemented.
Date filters use the shop's local time zone.
PrestaShop documents no idempotency key; creates and status changes are not repeated automatically when uncertain.

Developer reference

Create the PrestaShop credentials described above with the narrowest permissions your flows need.
In Nexra, open Connect, then Connections, then New connection, choose PrestaShop, enter its settings and credentials, and tick only the write actions you need. Connection guide
Test the connection, then use its actions as flow sources and destinations. Flow guide

PrestaShop docsAPI reference PrestaShop docsAuthentication PrestaShop docsRate limits PrestaShop docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/prestashop and the Connections API.