WooCommerce & Sage integration, including Sage 200 Evolution
Connect WooCommerce to Sage so orders, customers, stock and refunds reach the right accounting records without anyone retyping them. We start with your exact Sage product and edition, because Sage 200 Evolution, Sage Business Cloud Accounting and Sage 50/Pastel are very different environments to integrate with.
Connect the order to the right accounting record
WooCommerce is where we build most of our stores, and Sage is where many South African businesses keep their books. The two don’t talk out of the box, so someone ends up copying every order across, fixing stock by hand and reconciling at month-end.
The first question isn’t technical. It’s what each order should become in Sage, and which system is in charge of customers, products, prices and stock.
Every handover needs a way back.
An illustrative planning pattern. Your actual systems and rules determine the implementation.
Normal delivery
- Store order event
- Validate & match
- Accounting document
- Reconciliation
Keep the source reference and make the receiving result visible.
When something fails
- Keep the original event
- Show a pending state
- Retry the same reference
- Review the exception
A lost acknowledgement must not silently become a duplicate record. Assign recovery to an authorised owner.
“Sage” covers several very different products
Plenty of plugins say “Sage integration”. The question is which Sage. How we connect, what can sync and what it costs all depend on the answer.
| Sage product | Where it runs | How WooCommerce connects | What to check first |
|---|---|---|---|
| Sage 200 Evolution (formerly Pastel Evolution) | Your server or a hosted server, on SQL Server | A connector service beside your Evolution database, using the Evolution SDK | Your Evolution version, the modules you use (inventory, order entry, multi-warehouse) and SDK licensing with your Sage business partner |
| Sage Business Cloud Accounting (formerly Sage One) | Sage’s cloud | Sage’s web API, directly from the store or a small middleware | Your subscription level and which records the API exposes for it |
| Sage 50 / Pastel Partner | A desktop or local network | A connector on the machine or network running Pastel | Version, where the company data lives and who has access to it |
| Sage 300 and Sage X3 | ERP on your server or hosted | Through the ERP’s integration layer, scoped as an ERP project | Which ERP modules own stock, pricing and fulfilment |
One trap to look out for: “Sage 200” means different products in South Africa and the UK. Most UK plugins and guides are written for the UK product, not Sage 200 Evolution. If a vendor quotes you for “Sage 200”, ask which one.
How a Sage 200 Evolution integration runs
Evolution usually sits on a server inside your business, not on the internet. We don’t open your SQL Server to the web to make an integration work. Instead:
- A small connector runs on your network, next to Evolution, and talks to it through the SDK.
- The connector calls out to WooCommerce over HTTPS for new paid orders, refunds and customer changes. Nothing reaches in.
- Each order is written to Evolution as the document your accounts team expects: a sales order for picking, or a tax invoice when it’s already paid and fulfilled.
- Stock and prices flow back to the store on a schedule, per warehouse if you run more than one.
- Every transfer is logged with its WooCommerce order number, so a retry never creates a second invoice and you can always see what’s waiting.
Sage Business Cloud is simpler, because its API is already online. Pastel follows the same connector pattern as Evolution.
What syncs between WooCommerce and Sage
- Orders to sales orders or tax invoices, with lines, shipping, discounts and the 15% VAT treated the way your accountant wants.
- Customers to customer (debtor) accounts: guest orders go to a cash-sale account or a new account, and B2B buyers match their existing account.
- Products matched by SKU or item code, with Sage as the master for price, description and tax type if you want it that way.
- Stock on hand from Sage to WooCommerce, per warehouse, so the store stops selling what isn’t there.
- Price lists for trade and B2B customers, so logged-in buyers see their own pricing.
- Payments and refunds as receipts and credit notes, matched to the original invoice.
Decide which system owns each record
| Workflow | Decision before implementation |
|---|---|
| Orders | Which paid or approved event creates a sales order or invoice? |
| Customers | How are guest orders and existing account customers matched? |
| Products | Which system owns SKU, price and tax category? |
| Stock | Which location supplies availability, in which direction and how often? |
| Discounts and shipping | How do order-level and line-level adjustments reconcile? |
| Refunds | Does the event need a credit note, payment reversal or operator review? |
| Duplicates | Which stable order reference prevents a second accounting record? |
We agree these with the person who runs the store and the person who reconciles the accounts. Stock usually starts one-way and on a clear schedule before any two-way sync.
Prove the exceptions before going live
- Ordinary order. Customer, lines, tax and shipping all land correctly.
- Discounted order. Order-level and line-level discounts reconcile.
- Partial refund with shipping. The credit matches what your accounts team expects.
- Sage unavailable. The order waits with a visible status and retries safely.
- Replay. Sending the same event again creates nothing new.
Plugin or custom integration?
If you run Sage Business Cloud with a simple catalogue, an off-the-shelf connector may be enough, and we’ll tell you so. A custom integration earns its cost when you run Sage 200 Evolution or Pastel on your own server, have several warehouses, B2B price lists or account customers, or have already tried a plugin that keeps creating duplicates or failing silently.
Stores we’ve built
eCommerceGrand Timepiece
eCommerceVassco
Send us your Sage and WooCommerce details
The Sage product and version, where it runs, and what you copy across by hand today. We’ll confirm the connection route before quoting.
- Name the systemsWhere leads or orders start, and where they have to end up.
- We check the routeAPI, import, portal or connector: we confirm what each system supports.
- You get a scopeSized to the connection you need, not a whole platform.
- Orders → Sage 200 Evolution
- Stock → WooCommerce
- Price lists → B2B store
- Refunds → credit notes
Questions about WooCommerce and Sage
A few useful answers before you decide.
Do you integrate WooCommerce with Sage 200 Evolution?
Do I need an SDK licence for Sage Evolution?
Which other Sage editions do you support?
Can stock sync both ways?
Can B2B customers see their own Sage pricing in the store?
Can you import historical orders?
Assess your setup
Send us the Sage product and edition, the event that should create the accounting record and the fields you copy by hand today. For a full custom platform, the web application calculator gives a first estimate; most single Sage connections are smaller than that, so use the form above for a scoped quote.
Keep the right things connected.
E-commerce and Accounting Integrations
Connect online orders to accounting workflows with explicit record mapping, reconciliation, exception recovery and integration monitoring.

Integrating E-commerce Orders With Accounting Systems
What must be agreed before an order can become an accounting record? Review ownership, mapping, duplicate prevention and reconciliation.
eCommerce development, from WooCommerce stores to bespoke B2B ordering
WooCommerce stores, custom checkout logic, PayFast and Shopify integrations, and bespoke B2B ordering platforms built for large catalogues.
Web application pricing calculator
Portals, internal systems, automation and API integrations.
Start a conversation
Tell us what you are working towards. We’ll help you find a practical next step.