eSellerPro ↔ Sage 200 Integration
eSellerProMultichannel order managementAmazon, eBay and web orders flowing into Sage 200 SOP — one stock figure, channel-aware pricing, no spreadsheet glue.
eSellerPro is the multichannel order-management layer: it aggregates marketplace orders (Amazon, eBay, your web stores), manages listings and pushes a consolidated stock figure back out to channels. Sage 200's job in that setup is to be the commercial system of record — stock, cost prices, nominal posting, customer accounts. The integration joins the two: channel orders import into Sage 200 as SOP entries with the right tax treatment per marketplace, Sage stock figures feed eSellerPro's channel sync, and despatch/tracking status travels back out so marketplaces see 'shipped' on time. The traps are all in the middle: marketplace VAT rules that don't match Sage's tax codes, returns flows that bypass normal despatch, and stock-oversell when channel allocations lag.
Data Flows
- 1
Channel orders → SOP
eSellerPro's aggregated orders land in Sage 200 as SOP with per-channel analysis codes — marketplace fees, channel, store and currency captured at entry, not reconstructed later in reports.
- 2
Tax per channel
Marketplace-collected VAT (Amazon/eBay collect-and-remit) posts at zero-rated/withheld, while direct-web orders post Sage's normal tax codes. The rule lives in a per-channel tax map — this is where most multichannel Sage builds go wrong.
- 3
Stock → channels
Free stock (minus allocations, minus safety buffers per channel) feeds eSellerPro's stock push. Fast SKUs get tight buffers; long-tail lines can sell to zero.
- 4
Despatch → shipped
Sage despatch + courier tracking pushes back to eSellerPro, which confirms shipment on each marketplace — keeping on-time-shipping metrics safe.
Where These Integrations Go Wrong
The failure modes we design around — most eSellerPro ↔ Sage projects hit at least two of these.
Marketplace VAT is your biggest accounting risk
Since 2021, Amazon/eBay collect and remit UK VAT on most marketplace sales — those transactions are zero-VAT on your side but NOT exempt; get the tax code wrong and your VAT return misstates. The channel tax map is the load-bearing wall of this integration.
Channel stock oversell
If channels pull stock faster than eSellerPro re-syncs, a sale can commit stock already allocated elsewhere. Fix it at the buffer level — hold back X units per channel — not by turning sync intervals down to unusable frequency.
Returns don't follow despatch
Marketplace returns (buyer returns, undelivered, damaged) land in eSellerPro's returns flow, often without a matching Sage despatch. Map them to Sage's returns/RMA entry rather than trying to reverse the despatch.
Multi-currency channels
EUR/USD marketplace orders need Sage multi-currency handling — not just 'convert at today's rate'. Bank fees and marketplace deductions mean the settlement value differs from the order value; account for it in the import.
What's Included
- Channel order import to Sage 200 SOP with per-channel analysis codes
- Channel-aware tax map (marketplace-collected vs direct-web VAT)
- Stock feed to eSellerPro with per-channel safety buffers
- Despatch/tracking writeback for marketplace 'shipped' confirmation
- Returns routing to Sage RMA entry
- Month-end reconciliation pack: channel fees vs settlement vs Sage postings
Who It's For
Sage 200 businesses selling through Amazon and eBay alongside their own web stores — where eSellerPro handles the channel plumbing and the pain point is getting those orders properly accounted in Sage without manual entry or dodgy VAT treatment.
FAQ
eSellerPro is older software — is it still supported?
eSellerPro (now under the Khaos/ACT Group umbrella) is still in service at a meaningful installed base; the API surfaces we integrate against are stable. If you're on it, we build around it; if you're choosing fresh, we'd scope the same flows against a modern multichannel tool.
How do channel fees reconcile in Sage?
Marketplace settlements arrive net of fees — the order value and settlement differ. We post the gross order, then match deductions (commission, FBA fees, advertising) as separate nominal entries per settlement, so your sales ledger and bank rec both balance.
Can channel orders create Sage customer accounts?
We generally don't create a Sage customer per marketplace buyer (volume and data-protection issues). Instead orders post under per-channel umbrella accounts with the buyer detail held on the SOP — cleaner ledger, full reporting by channel.
Scope Your eSellerPro Build
Fixed quote once we know your Sage version, the flows you need and the volumes.