PrestaShop and Sage integration: what syncs with Sage 50, 200 or X3

Yes, you can integrate PrestaShop with Sage: products, price lists and stock flow into the store on their own, and every order goes into Sage as a sales order, without anyone keying it in. It works with Sage 50, Sage 200, Sage 300, Sage X3 and the cloud Sage products. What changes from one to another is how it connects, not what travels.

If your store’s stock is updated from a spreadsheet uploaded on Mondays, you know what happens: an order comes in for twelve units of something that went out yesterday, and someone has to call a customer who has already paid. That is what stops.

What syncs between Sage and PrestaShop?

From Sage to the store goes what you already have set up, and it keeps itself up to date:

• Products and product groups. Each Sage product group becomes a store category, or is regrouped the way you sell, which is not always the way you buy.
• Price lists. The standard price for the public and the customer or group price lists for trade buyers: each one logs in and sees their own price. How to show the catalogue only to approved customers is explained in the trade-only PrestaShop store.
• Stock per warehouse. All warehouses added up, just one, or with allocated stock deducted. Out of stock, the item is still shown, but it cannot be bought until it is back.
• Variants. If you handle sizes and colours in Sage, each item becomes a product with combinations in the store, each with its own stock and barcode.
• VAT. Each item’s VAT code and each customer’s VAT treatment are respected, on the price and on the invoice.
• Offers and discontinued items. What goes on offer in Sage shows up in the offers category; what you discontinue stops being sold without anyone having to remember.

And the order comes back. When your customer pays, it goes into Sage with the Sage product codes, the price applied and the discount. The customer is found by account reference or VAT number and, if they are new, an account is created with their addresses and payment terms. Carriage goes in as a line, and you set the warehouse and order settings once.

Then the road continues: when you despatch the order in Sage, the store tells the customer; and if Sage issues the invoice, the PDF shows up in the customer’s account. On the order page of your store you can see whether it reached Sage, when and with which number, and a button sends it again.

The store is not another place to keep the catalogue. It is the shop window for what is already in Sage.

Does it work with my Sage?

Yes, with the ones in use today. It is the first thing we will ask, because each one connects differently. You do not need to know it by heart: whoever maintains it for you does.

• Sage 50 Accounts, on an office PC or server. Sage gives registered developers a way in, and scheduled file imports and exports cover the rest, so nobody has to press a button. In the United States, Sage 50 is the former Peachtree, with its own way in.
• Sage 200, Professional on your own server or Standard in the cloud. Both have a direct connection: in Standard it is on from day one; in Professional your Sage partner switches it on, without opening your server to the internet. The UK Sage 200 is not the Spanish or South African one, which is why we ask which one you have.
• Sage 300, the former Accpac. It has its own direct connection, and its data can always be read with a user who can only look.
• Sage X3, for companies with several entities and warehouses. It has a modern connection for orders and files for large loads, which is the combination Sage itself recommends for online stores. There is usually a team behind it, and with them everything is settled in one meeting.
• Sage Intacct and Sage Accounting, the cloud ones. They connect directly, with no server in the office.

A ready-made connector or a custom integration?

There are several Sage–PrestaShop connectors, and custom integrations too. What separates a good one from a troublesome one does not show on the day it is switched on, but six months later. Look at these four things:

1. Price and stock are changed in one place only: in Sage. If they can also be changed by hand in the store, the two end up arguing, always on the busiest day.
2. What you improve in the store is never overwritten. A better product name, a rewritten description or a new photo survive the next update.
3. The store never closes “for maintenance”. A large catalogue is updated in batches and, if it is interrupted, it carries on where it left off.
4. If something fails, you find out. Every order is logged and a failure sends an alert. What you cannot see, you cannot fix.

It is the same split as in the GoManage and Aunabase case: the ERP owns price and stock, the store owns the sale, and the order goes back on its own.

What will we ask you for to get started?

• Which Sage you have, which version, and who maintains it for you.
• Access for the store, the kind that fits your Sage: we tell you which one and your partner sets it up.
• What you want to travel and in which direction: catalogue, price lists, stock, orders, invoices.
• Whether you sell to trade customers with fixed prices, to the public, or both.

With that, we set up a first test run on a copy of your store, and you see your real catalogue inside PrestaShop before deciding anything else.

Frequently asked questions

Can Sage 50 be integrated with PrestaShop?

Yes. Sage 50 can be read through the tools Sage gives developers, and what is not read is exchanged with scheduled files. It is the most common case in a small business.

Can I sell to trade customers with their Sage prices?

Yes. Each trade customer logs into the store and sees their Sage price list. Everyone else sees the standard price, or no prices at all, as you prefer.

Are you a Sage partner?

No. A partner implements and maintains the ERP; we build the store side. If you already have one, we work with them without stepping on each other’s toes.

For your technical team

Sage 50 Accounts (UK) opens its data through Sage Data Objects, the SDK for registered developers, and its ODBC driver, plus scheduled CSV files; Sage 50 in the US has its own .NET SDK. Sage 200 Professional and Standard share a REST API with Sage ID sign-in; in Professional it reaches the store through a Microsoft connector installed on the Sage server, with no inbound ports. Sage 300 has an OData-based Web API since the 2016 updates and runs on SQL Server only. Sage X3 connects mainly through its GraphQL API, on-premise too, plus import templates and SOAP web services. Sage Intacct has a REST API alongside its XML API; Sage Accounting, a REST API.

Running Sage alongside a PrestaShop store? Tell us which version you use and what you would like to travel, and we will tell you how it connects and in what order. The other systems we connect are on the PrestaShop ERP integration page.

Talk to us

Sage, Sage 50, Sage 200, Sage 300, Sage X3 and Sage Intacct are trademarks of The Sage Group plc or its licensors. We are not a Sage partner or reseller: we connect PrestaShop stores to its ERPs.