In short: PrestaShop and NetSuite can be connected three ways: Celigo's PrestaShop connector, a custom build against the PrestaShop API and NetSuite's web services, or an existing PrestaShop module. Which one fits depends on your PrestaShop version and modules, your catalogue and number of combinations, how many shops you run and how finance wants orders and payments posted.
When PrestaShop and NetSuite live apart
It usually starts with a manual step that never goes away. You may recognise some of these:
- Orders are re-keyed into NetSuite, or exported from PrestaShop as a CSV file.
- Stock per combination (size, colour) is wrong on the web shop, so you oversell one variant and sit on another.
- Prices are maintained twice, once in NetSuite and once in the shop.
- A B2C shop and a B2B shop run different rules, and nobody owns the difference.
- Month-end means reconciling payments from Redsys, PayPal or Stripe by hand.
Getting orders in is the easy half; our piece on four ways to get ecommerce orders into your ERP covers the architecture behind it. Stock drift is rarely a speed problem either, as we explain in why stock drifts between channels.
Is there a native NetSuite connector for PrestaShop?
No. Oracle's NetSuite Connector documentation lists its supported storefronts as Amazon Seller Central, Amazon Vendor Central, BigCommerce, eBay, Magento 2, Shopify, Shopify POS, Walmart and WooCommerce, plus ShipStation among the 3PLs. PrestaShop is not on the list. We checked on 15 October 2026 (Oracle, NetSuite Connector: Supported Storefronts and 3PLs).
Celigo offers a prebuilt PrestaShop connector in integrator.io. It authenticates with a PrestaShop Webservice key and covers carts, customers, orders, products and stock, among others, with an HTTP mode for anything not in its prebuilt list. It is a connector to build flows on, so the mapping to NetSuite is still design work. PrestaShop modules that claim NetSuite connectivity also exist; assess each one on its own merits.
What we sync between PrestaShop and NetSuite
| Flow | Direction | What it covers |
|---|---|---|
| Orders | PrestaShop → NetSuite | Lines, carrier, payment method, discounts and vouchers |
| Customers and addresses | PrestaShop → NetSuite | Guest and registered buyers; B2B accounts can also flow NetSuite → PrestaShop |
| Products, combinations and prices | NetSuite → PrestaShop | When NetSuite is the item master |
| Stock | NetSuite → PrestaShop | By combination and by warehouse or location |
| Order status, fulfilment and tracking | NetSuite → PrestaShop | Shipment confirmation and tracking numbers back to the shop |
| Returns and refunds | PrestaShop → NetSuite | Credit slips and refunds matched to the original order; see returns, refunds and credit notes |
| Payments and payouts | Payment gateway → NetSuite | Settlement of Redsys, PayPal, Stripe and other payouts against the bank line |
If you also sell through marketplaces, payouts follow a different logic; see our marketplace settlements page.
Celigo or custom API: how we choose
| Route | Fits when | Watch out for | Who maintains it |
|---|---|---|---|
| Celigo integrator.io with the PrestaShop connector | You already use Celigo, or have several systems to connect and want one platform with a monitoring dashboard | The connector is a building block, not a finished PrestaShop–NetSuite app; the NetSuite side is still designed and configured | A managed platform, operated by us or by your team |
| Custom integration against the PrestaShop API and NetSuite (SuiteTalk REST, RESTlets) | Heavy customisation, a very large catalogue, unusual multistore logic, or no wish to license an iPaaS | You own the code, so it must be documented, tested and monitored | Us, or your team once trained |
| Existing PrestaShop module | Simple cases | Maintenance, supported PrestaShop versions and who owns the code | The module vendor, plus your agency |
The decision follows your PrestaShop version and modules, catalogue size and number of combinations, number of shops, order volume and peaks, the posting rules finance wants and any iPaaS you already pay for. We are not resellers, and we recommend the route that fits, not the one we sell most. For the wider trade-off, see iPaaS, point-to-point and middleware. We are a Celigo implementation partner, and we recommend it only when it fits.
PrestaShop-specific design decisions
This is where PrestaShop integrations succeed or fail. None of it comes out of a connector's default settings.
Combinations and NetSuite matrix items. The product maps to a matrix parent and each combination to a matrix child, with the attribute values mapped on both sides. The reference (SKU) of every combination must be unique and stable. Agree up front what happens when the agency adds a new attribute or value, because an unmapped combination is a product that silently stops selling.
Multistore. Several shops, whether by country or split into B2B and B2C, have to map to the right NetSuite subsidiary (OneWorld), price level, currency and location. Decide this per shop before building, not while debugging a wrong price.
Order states. Map each PrestaShop order state, including custom ones added by modules, to a NetSuite sales order, fulfilment or cancellation. Decide which state triggers the import; "payment accepted" is a common choice, and it keeps unpaid orders out of NetSuite.
Payment modules. Redsys, PayPal, Stripe, bank transfer and cash on delivery each become a customer deposit or payment in NetSuite in a different way, and each pays out on its own schedule. We design how every method is recorded and how its payout reconciles.
Who issues the legal invoice. PrestaShop can generate invoices, and so can NetSuite. Pick one issuer, never both. In Spain, the invoicing system has to comply with the SII and Verifactu rules, so agree the choice with your tax advisor before go-live. This is not tax advice.
Taxes. PrestaShop tax rules and NetSuite tax codes are two different models. Map them explicitly, including special cases such as the recargo de equivalencia on some Spanish B2B sales and EU OSS for cross-border B2C. Your advisor sets the rules; the integration carries them.
API and hosting. PrestaShop is usually self-hosted, so the API runs on your own server. Performance, caching, HTTPS and the scope of the API key all matter, and so do your agency's deployments. PrestaShop 9, released on 10 June 2025, adds an Admin API built on API Platform with OAuth authorisation, next to the legacy Webservice. Its coverage was still partial when it launched, so we choose the API per version and per endpoint after checking what your version actually exposes.
Upgrades and modules. A PrestaShop or module upgrade, or an override, can change data structures. Add integration tests to your agency's release routine so that an upgrade does not break the flows.
Real-time or batch. The Webservice is request and response, so a flow normally polls. Whether your setup can also push notifications depends on your version and modules, and we confirm it in discovery. Stock frequency follows how fast your catalogue turns over.
How a NetSuite–PrestaShop project runs
- Discovery with your PrestaShop agency. Version, modules, shops, combinations and payment modules.
- Mapping and sandbox build. With your real data, covering the edge cases: combinations, vouchers, refunds, several shops.
- Parallel run. On a subset of products or orders, compared with what you do today.
- Go-live and monitoring. We deploy, watch the first syncs closely and stay on.
The timeline depends on the route and your setup, and we fix scope and effort after discovery rather than guessing before it.
After go-live: monitoring, errors and ownership
Most integrations don't fail on day one. They fail on a busy week, silently, and someone notices at month-end. That is why error handling, retries and alerts ship with the integration. For PrestaShop, the alerts we typically set up cover failed order imports, unmapped combinations, stock feed errors and API authentication failures.
We agree with your PrestaShop agency who fixes what: shop-side changes belong to the agency, the integration to us or to you. You own what we build. We document the flows, and if you would rather run them yourselves, we train your team. Our piece on life after go-live explains why this phase decides whether an integration lasts.
Why Atypical Tech
- NetSuite depth, not just plumbing. We understand the records, the processes and the finance behind every flow.
- Senior engineers only. The people who scope your project are the ones who build it.
- Partner where it helps, independent where it counts. We are a Celigo implementation partner and a Stacksync partner, and we build directly against APIs when no platform fits.
- Based in Spain, working across Europe. In English, Spanish, Portuguese and Catalan. We already run Shopify, WooCommerce and Magento integrations; WooCommerce is the closest cousin, being open source and usually self-hosted. Selling B2B too? Read about B2B ecommerce for distributors. See all the systems we connect.
Sources
- Oracle NetSuite Help Center, NetSuite Connector: Supported Storefronts and 3PLs, checked 15 October 2026.
- Celigo, PrestaShop integrations, and Celigo Help Center, Set up a connection to PrestaShop and Available PrestaShop APIs, checked 15 October 2026.
- PrestaShop Project, PrestaShop 9.0 is available, and developer documentation for the Admin API and the Webservice, checked 15 October 2026.