EasyWebstore ↔ Sage 200 / Sage 50 Integration
EasyWebstoreEcommerce platformUK-hosted store platform for smaller Sage shops — orders into Sage 200/50, stock and prices pushed back, no re-keying between web and accounts.
EasyWebstore is a UK-hosted ecommerce platform aimed at smaller retailers and distributors — the same businesses that typically run Sage 50 or a single-entity Sage 200 install. There is no off-the-shelf Sage connector, so most EasyWebstore + Sage shops end up exporting orders to CSV and re-keying or importing them by hand. We build the missing layer: EasyWebstore orders land in Sage as proper sales orders (SOP in Sage 200, sales orders/invoices in Sage 50), stock and prices flow back to the store, and customer records are matched or created without duplicates. Because EasyWebstore's API surface is lighter than the big platforms, the integration is pragmatic — API where it exists, scheduled export/import where it doesn't — designed to be reliable rather than clever.
Data Flows
- 1
Orders → Sage
New EasyWebstore orders are pulled on a schedule and created as Sage sales orders — SOP in Sage 200, sales orders or invoices in Sage 50 — with the web order reference, payment status, delivery address and line-level detail intact. Paid orders post straight to the ledger; unpaid/phone-payment orders sit as open orders.
- 2
Customers
EasyWebstore customer accounts match to Sage customer records by email/company; new customers create a Sage account once. Guest checkouts post under a configurable 'web sales' umbrella account unless a match is found — no duplicate customer sprawl.
- 3
Stock & prices → store
Sage free-stock figures and sell prices push back to EasyWebstore on a schedule (or near-real-time where the platform allows). Price-band/customer-group pricing from Sage 200 maps to trade pricing on the store where both sides support it.
- 4
Despatch & tracking
Despatch in Sage marks the order fulfilled in EasyWebstore and triggers the platform's shipping-confirmation email; tracking numbers write back where the store supports them.
Where These Integrations Go Wrong
The failure modes we design around — most EasyWebstore ↔ Sage projects hit at least two of these.
Sage 50 vs Sage 200 are different jobs
Sage 50 has no SOP concept like 200 and no API in the same class — order creation, stock and pricing all work differently. The integration detects which product you run and uses the right path (SDO/file-based for 50, API/database for 200) rather than pretending they're the same.
API surface is thin
EasyWebstore isn't Shopify — not everything is exposed. Where an endpoint doesn't exist we fall back to scheduled exports, which means sync frequency is a design decision, not a given. We agree the acceptable lag per data type up front.
Guest checkout customers
B2C stores produce lots of one-off buyers. Creating a Sage customer per checkout pollutes the ledger — we use a matched-or-umbrella rule so repeat customers still reconcile but one-offs don't create accounts.
VAT and channel confusion
EasyWebstore order exports don't always carry a clean VAT breakdown per line. We validate the tax treatment against Sage's rules and flag mismatches (e.g. mixed-rate baskets) to a review queue instead of posting wrong VAT.
What's Included
- Order sync from EasyWebstore into Sage 200 SOP or Sage 50 sales orders
- Customer matching with umbrella-account fallback for guest checkouts
- Stock level and sell-price push from Sage to the store
- Despatch confirmation and tracking writeback
- Exception queue for VAT mismatches, unmapped products and failed orders
- Dual-version support — works on Sage 50 and Sage 200 installs
- UAT against a copy of your live Sage data before go-live
Who It's For
UK SMBs running EasyWebstore for their web shop while accounts and stock live in Sage 50 or Sage 200 — typically smaller distributors, parts suppliers and retailers who are re-keying orders or living with overnight CSV imports. It is not aimed at high-volume multichannel sellers; if you're shipping hundreds of orders a day across marketplaces, a platform with a bigger API surface (and an integration like our ChannelAdvisor or Shopify work) is the better fit.
FAQ
Does this work with Sage 50 as well as Sage 200?
Yes — the page covers both because the queries are mixed. Sage 50 integration uses its own access paths (the integration detects the product and uses the right mechanism), while Sage 200 uses SOP and the 200 data model. Pricing differs slightly because Sage 50 work involves different tooling.
How often do orders sync?
Configurable — typically every 5–15 minutes for orders. Stock and prices can run near-real-time where the platform permits, or on a schedule (hourly/daily) where it doesn't. We agree the lag you're comfortable with during scoping.
What about products that exist in the store but not in Sage?
Unmapped SKUs don't fail silently — the order goes to a review queue and the unmapped lines are flagged. You can then map the SKU to a Sage stock code or a default 'miscellaneous' item so the order completes.
Scope Your EasyWebstore Build
Fixed quote once we know your Sage version, the flows you need and the volumes.