Your cart
There are no more items in your cart
Integrations
Connect PrestaShop to the ERP that already runs your business
Sage, Business Central, a3ERP, Odoo, Holded, SAP… and also a CRM like Salesforce, a monday.com board or that database only your IT person understands. We are not a partner of any of them, and we do not need to be: we know how information gets in and out of each one, and we build the PrestaShop side, which is the part that almost always fails.
The ERP runs the business; the store runs the sale
The first thing to decide in an integration, before writing a single line, is who owns each piece of data. Once that is clear, the rest is plumbing. When it is not, the store and the ERP end up arguing, and they always argue on your busiest day.
The ERP owns price and stock
Which items are for sale, at what price, how many are left in each warehouse and which ones are on offer. None of that is touched from the store.
The best catalogue owns the product page
Trade name, description, photos, barcode, brand and minimum order quantity. From the ERP itself, from a PIM or from your buying group’s database.
The store owns the sale
The home page, campaigns, your own copy, shipping and the way you treat your customers. What is not in the ERP because it is not the ERP’s job.
- Orders go back on their ownWith their lines, both addresses and the payment method translated into the one the ERP understands. Nobody types them in again.
- What is written by hand is never overwrittenAn improved description or a better photo survives the next sync. Without this rule, nobody ever touches a product page again.
- You can see whether it got throughOn the order page, in the back office, you can see whether it reached the ERP, when and under which number. And if something failed, one button sends it again.
Four routes, and there is always one
Your ERP does not have to be modern or in the cloud. The data only has to come out somewhere, and it always comes out through one of these four.
REST or SOAP API
The direct route: the store asks and the ERP answers there and then, with nobody in between.
- Business Central
- Odoo
- Holded
- Sage 200, 300 and X3
- SAP B1
- Salesforce
- monday.com
Webhooks
The system announces when something changes —a price, a stock level, a status— and the store reacts without waiting for the next run.
- Odoo
- Holded
- Salesforce
- monday.com
Database
When the ERP lives on the server in your office. Only what is needed is read, with a read-only user and without touching its tables.
- SQL Server
- MySQL
- Oracle
- ODBC
- Sage 50 and 300
- a3ERP
- Navision
Files
CSV, XML or Excel files that the ERP drops into a folder, onto an SFTP server or into an email. It is how many long-standing installations work and, properly scheduled, it runs just as smoothly.
- CSV
- XML
- Excel
- SFTP
- In batches, and it picks up where it stoppedA 30,000-item catalogue is processed in blocks and, if it is interrupted, it carries on where it left off. The store never closes “for maintenance” or ends up half updated.
- Inside your storeThe integration runs in your PrestaShop: no middleman service with a monthly fee, no third party your data passes through and no cost per volume.
Systems we work with
We do not work for these brands or resell them. What we have is experience in how each one opens up its data, which is all it takes to connect it. If yours is not on the list, ask: it almost certainly comes in through one of the four doors.
ERP
The system that runs the business: items, price lists, stock and orders.
Sage 50, 200, 300 and X3
- REST API
- GraphQL
- SQL Server
- Files
From the Sage 50 in the office to the X3 of a large company: API, database or files, depending on the version.
How each Sage connectsDynamics NAV and Business Central
- REST API
- OData
- SQL Server
REST API and OData in Business Central; on a classic Navision, its web services or straight into its SQL Server.
a3ERP
- API
- SQL Server
The Wolters Kluwer ERP used by a great many Spanish SMEs: it connects through its API and through its SQL Server database.
Odoo
- XML-RPC
- JSON-RPC
- Webhooks
A full API in both directions: products, price lists, stock, orders and customers.
Holded
- REST API
- Webhooks
In the cloud: catalogue, contacts, orders and invoices, with no server in between and nothing to install at the office.
SAP Business One
- Service Layer
- DI API
Warehouses, customer price lists and orders that come in with the business logic SAP requires of them.
CRM and work tools
They do not run the warehouse, but that is where customers are followed up and the day-to-day is organised. The store tells them what happens.
Salesforce
- REST API
- Webhooks
Every customer and every order from the store shows up in the CRM, in the right account and with their sales rep. And the B2B accounts opened in Salesforce come into the store with their prices.
monday.com
- GraphQL
- Webhooks
Every order, incident or return comes in as an item on the board you choose, with its data in columns. What changes on the board can go back to the store.
Your own data
When what you have is not a program with a name, but a database someone looks after.
External database
- MySQL
- SQL Server
- Oracle
- ODBC
The store reads the catalogue and stock straight from where they are, with a read-only user.
Sage, Microsoft Dynamics, a3ERP, Odoo, Holded, SAP, Salesforce and monday.com are trademarks of their respective owners. We have no commercial relationship with any of them: we are not a partner, distributor or implementer. We know their systems because we have connected stores to them.
How we do it
Four steps. The second one lets you see the result with your real catalogue before you commit to anything.
- Step 1
Data map
Half a day with whoever runs your ERP: which field comes from where, which system owns each piece of data and what must never travel.
- Step 2
A first test run
On a copy of your store and with your real catalogue. You see your products, your prices and your stock inside PrestaShop before deciding anything.
- Step 3
Orders going back, and the odd cases
Payment methods, shipping, discounts, new customers, duplicate references, items without a photo. None of that is unusual and none of it stops you going live.
- Step 4
Live and monitored
Every sync leaves a log, a failure sends an alert, and whatever needs resending is resent from the order page.
A real case: Go!Manage and Aunabase
- Almost 30,000 items in the ERP
- 16,700 for sale
- Order in the ERP on payment
An electrical supplies distributor with Telematel’s ERP and the good product data in its buying group’s database. Today the store shows the warehouse price and stock, discontinued items disappear on their own, offers place themselves, and the warehouse sees web orders where it sees all the others.
How it was built, step by step
Frequently asked questions
Are you a Sage, SAP or Odoo partner…?
No, and you do not need us to be. A partner sells you the ERP and implements it; we make your store talk to it. If you already have a partner, we work with them: they know how your ERP is set up and we know what PrestaShop needs.
Do you need to know my ERP inside out?
We need its documentation and a connection user; the rest is known by whoever maintains it for you. Our part is the store: the catalogue coming in properly, each customer seeing their price and the order going out complete. That is where most integrations fail.
What if my ERP has no API?
Then it has a database or it exports files, and either of them can be connected. It happens more often than you would think, and it changes nothing of what you end up seeing in the store.
How often does it sync?
Price and stock, every few minutes, or instantly if the ERP sends a webhook. The full catalogue, overnight. The order, the moment the customer pays.
What happens if the ERP goes down?
The store keeps selling with the last good data, and orders wait in a queue and are sent when it is back. Everything is logged and nothing has to be rebuilt by hand.
I already have a connector that half works
That is the most common case. We look at what is there, tell you what is worth keeping and what is better rebuilt, and leave it documented so that you do not depend on us.
How much does it cost and how long does it take?
It depends on how many things travel and in how many directions. After the data map you get a fixed quote with a price and a date; a typical integration is up and running in three to six weeks.
Which versions of PrestaShop?
1.7, 8 and 9, multistore included, and with several languages and currencies. If the store is still to be built, it is built already connected.
Which ERP do you use, and what would you like to travel?
Write to us and we will tell you what can be connected, how and in what order. No commitment and no salespeople in between: you hear back from the person who will do the work.