Oliver POS doesn't have a partnership with Sage 50. It supports Sage 50 the same way any WooCommerce store does — through the MyWorks Sync for Sage 50, which already syncs WooCommerce orders, customers, and refunds into Sage 50cloud in real time (or on the schedule you've configured). Once you understand that, the rest of this guide is mechanical: every sale Oliver rings on the counter writes a normal WooCommerce order, the Sage 50 connector posts it, and your in-store revenue lands on the same Sage 50cloud ledger as your online revenue. Sage 50cloud does the accounting. WooCommerce is the system of record. Oliver is the till on top.
What Sage 50cloud is, exactly
Sage 50cloud (Sage 50 Accounts in the UK, Sage 50 Accounting in CA/US — formerly Peachtree) is the desktop-anchored Sage SMB accounting platform with a cloud-sync layer. It has decades of installed base — small businesses run Sage 50 because they always have. The 50cloud layer adds cloud sync, remote access, and online connectors including WooCommerce.
For our purposes the important thing about Sage 50 isn't any specific feature — it's that the WooCommerce connector is mature, well-supported, and treats every WooCommerce order as a first-class transaction in Sage 50. Oliver POS doesn't add a second Sage 50 connector or modify the data path. It writes register sales into WooCommerce, and the existing Sage 50 connector picks them up.
How Oliver POS feeds in-store sales into Sage 50cloud
The Sage 50cloud WooCommerce POS flow inside Oliver is short and predictable:
- The cashier rings the sale on the Oliver register, scans or selects items, and taps Charge.
- Oliver prompts to attach a customer — by email lookup, phone-number lookup, or a fresh customer card.
- The cashier takes payment through whatever WooCommerce payment gateway the store uses.
- Oliver writes a standard WooCommerce order with the customer ID, line items, totals, VAT / GST / sales tax splits, and payment method.
- The MyWorks Sync for Sage 50 sees the new order through WooCommerce hooks within seconds.
- The connector posts a invoice to Sage 50cloud with the right VAT / GST / sales tax codes, customer, and revenue/payment-account mappings.
- Sage 50cloud's standard processing runs on the new document — journal entries, payment matching, VAT / GST / sales tax accruals, and any downstream automation you've set up.
End to end, the in-store sale arrives in Sage 50cloud before the customer has left the store (in per-order mode) or as part of the next end-of-day summary (in daily-summary mode). Either way, no manual entry is required.
The Sage 50cloud WooCommerce connector — what Oliver rides on
Oliver doesn't add a second Sage 50 connector or duplicate the sync. The plugin Oliver rides on is the standard MyWorks Sync for Sage 50, available at myworks.software/sage-50-woocommerce-sync. It's built specifically to handle the WooCommerce → Sage 50cloud data path, including VAT / GST / sales tax mapping, customer matching, refund handling, and the standard reporting flow.
Setup is identical to setup for any WooCommerce store: install the connector, connect to your Sage 50cloud account, map the chart of accounts and VAT / GST / sales tax codes, and let the initial sync run. Once that's done, every WooCommerce order — including every Oliver POS register sale — flows into Sage 50cloud on the same path.
Why pushing in-store sales into Sage 50cloud matters
Most retailers running Sage 50 on a WooCommerce store have an online-skewed ledger, because online is where the data has historically flowed automatically. The result is a Sage 50cloud ledger that knows everything about online orders and almost nothing about counter sales. The downstream consequences are real:
- Years of Sage history depend on consistency. A long-standing Sage 50 ledger has years of analytics, departments, and account structures built up. A POS that bypasses the ledger breaks the continuity.
- Accountant familiarity is worth keeping. The accountant has been on the same Sage 50 file for years. Manual end-of-day spreadsheets force them off-platform and onto reconciliations.
- Multi-outlet reporting in Sage 50 needs proper data. Sage 50 departments and analysis codes are powerful — but only if the POS feeds the right codes.
Push Oliver POS sales through the WooCommerce sync and all of those problems resolve at once. Sage 50cloud sees one revenue stream, one VAT / GST / sales tax-liability total, and one customer ledger across online and in-store activity. The bookkeeper's reconciliation against the bank stops being a forensic exercise. The advisor or accountant works from one source. The dashboard finally tells you what your business is really doing — online and in store combined.
What this is NOT
Oliver POS is not a Sage 50 partner. There is no co-marketing agreement, no revenue share, and no special Sage 50 pricing for Oliver merchants. Oliver does not insert itself between WooCommerce and Sage 50; the data path is exactly the same one any WooCommerce store uses. Oliver doesn't charge a markup, doesn't add a per-transaction fee on top, and doesn't take a cut of the Sage 50 subscription. Your Sage 50 account, ledger, and contract are entirely between you and Sage 50.
It's also worth saying that Oliver POS doesn't change the data ownership story. The WooCommerce orders table on your own WordPress install remains the source of truth. Oliver writes into it; Sage 50 reads from it through the connector. If you ever leave Sage 50, the data stays where it has always been — in WooCommerce.
Setup in 4 steps
- Install the MyWorks Sync for Sage 50 on your WordPress site and connect it to your Sage 50cloud account, mapping the WooCommerce sales, VAT / GST / sales tax, and payment-method accounts to your Sage 50 chart of accounts.
- Verify the initial sync completes and confirm a recent online order appears as the expected invoice in Sage 50.
- Install Oliver POS, sign in to the register on your counter tablet, and confirm the customer-capture prompt is enabled at checkout.
- Run a small live test sale at the counter, attach a customer, and confirm the invoice appears in Sage 50 with the right totals and VAT / GST / sales tax splits.
FAQ
Does Oliver POS require migrating off desktop Sage 50?
No. Sage 50cloud's cloud-sync layer is what the WooCommerce connector talks to. As long as you're on a 50cloud-enabled version of Sage 50, the connector posts WooCommerce orders into your existing ledger and Oliver POS sales follow the same path.
How are multi-outlet retailers handled in Sage 50?
WooCommerce orders from Oliver POS can carry an outlet identifier via custom fields, which the connector maps to a Sage 50 department or analysis code. Per-outlet reporting in Sage 50 works on those dimensions.
Does Oliver POS have a partnership with Sage 50?
No. Oliver doesn't partner with Sage 50 or any other accounting platform. We support Sage 50 because its WooCommerce connector already pulls orders, refunds, VAT / GST / sales tax, and customers from your store — and Oliver writes every in-store sale into WooCommerce as a standard order, so the same connector picks it up automatically. Your Sage 50 subscription, your ledger, and your contract stay between you and Sage 50.
Does Oliver charge extra to use Sage 50?
No. You pay Sage 50 directly on Sage 50's published pricing. Oliver's pricing is a flat monthly POS software fee that has nothing to do with the accounting platform you choose.
Will my in-store and online sales reconcile against one set of books in Sage 50?
Yes. Oliver POS writes register sales into the same WooCommerce store that powers your online checkout, so by the time orders reach the Sage 50 connector they're already a unified order stream. Sage 50 sees one revenue feed, one VAT / GST / sales tax-liability total, and one customer ledger — no manual reconciliation between an online and an in-store set of books.
Try Oliver POS free for 30 days at /demo/ — bring your existing WooCommerce store and your existing Sage 50cloud subscription and have your in-store revenue on the same Sage 50 ledger as your online orders within an hour. Built for established UK and North American SMB retailers but available wherever WooCommerce runs.