EKM ↔ Sage 200 Integration
EKMEcommerce platformUK-hosted SaaS store platform with Sage 50/200 integration — order sync, stock/price, CSV/API hybrid for SMB retailers.
EKM is a UK-hosted ecommerce platform popular with SMB Sage 50/200 shops — it combines a user-friendly web store with a lightweight API surface that maps well to Sage's CSV export/import model. Unlike platforms that promise full API connectivity, EKM delivers a CSV/API hybrid: key operations (orders, stock, prices) sync via daily/periodic CSV uploads and occasional API calls for real-time stock/price checks. The challenge is the middle-mile: mapping EKM's native order types, payment statuses and customer data onto Sage 200's SOP model while keeping the channel-aware VAT treatment (UK VAT for B2B sales vs standard rates for B2C) clear. We bridge that gap with a Sage 200 layer that handles the CSV ingestion, validation and transformation, turning EKM's data into fully credited Sage orders with the right analysis codes, payment statuses and stock allocations. The platform also includes a lightweight 'stock refresh' API for live price/availability queries, so the store never promises what the warehouse can't ship.
Data Flows
- 1
Orders → SOP
Daily CSV batch from EKM export contains new/updated orders with customer, shipping, payment and order-state details — imported to Sage 200 SOP with channel and payment-type analysis codes.
- 2
Stock sync
Live stock figures from EKM via lightweight API (price/availability queries) ensure the store shows real inventory; background sync job nightly pulls full stock CSV for batch reconciliation.
- 3
Prices → EKM
Sage 200 master price list uploads via CSV nightly; new item/movement price changes propagated through a selective sync that only touches changed SKUs.
- 4
Exceptions & validation
Orders flagged by EKM for missing data, duplicate customer records, or mismatched Sage accounts end up in a review queue for manual fix.
Where These Integrations Go Wrong
The failure modes we design around — most EKM ↔ Sage projects hit at least two of these.
CSV format rigidity
EKM's export delimiter and header case lock you in — tweak any field mapping and the whole pipeline breaks. We treat it as a data contract, not an implementation.
Channel-aware VAT
EKM doesn't expose VAT rate in order export; we need channel source (Amazon, own site, etc.) to map to correct Sage tax codes — we hardcode the channel rule table.
Payment states drift
EKM's payment statuses (preorder, paid, failed) don't map directly to Sage's payment state. Our custom mapping ensures pending orders don't allocate stock and failed payments trigger a review queue.
Multi-location stock
Sage 200 sites run multiple warehouses/branches; EKM is a single store. We default from a warehouse rule table (all items from HQ vs branch-specific SKUs) rather than blocking on unknown location.
What's Included
- Daily CSV ingestion pipeline: new/updated orders with customer, shipping and payment mapping to Sage SOP
- Multi-channel VAT treatment: EKM order channels (Amazon, eBay, own site) mapped to Sage tax codes (0%/20%/Exempt)
- Live stock refresh API: near-real-time price/availability queries from EKM using the lightweight API surface
- Payment-state gating: EKM 'preorder' or 'pending' mapped to Sage 'awaiting payment' state, no stock allocation
- Customer matching: duplicate EKM emails to Sage accounts with fallback to 'EKM Sync' umbrella account
- Exception queue: orders flagged by EKM (missing fields, validation fails) reviewed and fixed manually
Who It's For
Sage 50/200 SMB users still using EKM as their store front — typical of small distributors, retailers and workshop businesses that run Sage for accounting and EKM for online sales. Where they want richer API connectivity, they'd migrate to a platform like Shopify, but while EKM works and the CSV hybrid fits, the goal is to turn EKM orders into Sage orders without manual entry. Also for shops already on Sage 200 that are migrating from QuickBooks/Excel-based order processing and don't want to build a custom API bridge.
FAQ
Does EKM have an official Sage 200 connector?
No — EKM's API surface is minimal and is designed for hosted SaaS: CSV export, basic callbacks and very limited customization. Their documentation hints at future API development but it's not there yet. This integration is bespoke, not a pre-packaged connector.
What if EKM changes their CSV headers?
EKM exports are versioned — if they change column names, we detect the break via the sync test run and pause everything, alerting you to the new mapping. The integration's documentation includes a dynamic mapping sheet you can update between releases.
Can customers pay by card on the web and post to Sage?
Yes — EKM supports card payments through its gateways; those transactions land in the 'paid' order state and create the cash book credit in Sage. The integration includes a daily bank reconciliation flow that matches Sage cash receipts with EKM payment confirmations, so the books stay balanced.
Scope Your EKM Build
Fixed quote once we know your Sage version, the flows you need and the volumes.