The problem, in plain English
You have 100 units of SKU A. You list them on eBay (100) and Amazon (100). A customer buys 1 on Amazon. Your actual stock is now 99, but eBay still shows 100. A customer buys 1 on eBay. Your platform thinks you have 99. You're now at 98 actual with 99 listed — two people shopping, two listings, 20-30 second sync lag, and the race is on.
Scale that to 50 SKUs and 500 orders a day and the maths says you oversell. Every time. The only question is how often and how painfully. Amazon penalises consistently; eBay cancels, refunds, and dings your seller rating. The cost compounds.
The architecture that actually works
Four components, non-negotiable:
- One source of truth. Your inventory platform owns the stock count. Never edit stock directly on Amazon or eBay — that breaks sync and creates phantom stock.
- Real-time API sync in both directions. Orders flow in, stock updates flow out, under 60 seconds end-to-end. Under 15 seconds is meaningfully better.
- Per-channel stock buffers.Don't list your full stock on every channel. Reserve 5-10 units per channel as buffer to absorb API lag.
- Oversell prevention logic. If two channels both try to sell the last unit, the platform holds the second order rather than confirming both.
Architectures that will oversell you
- CSV upload batch sync.Whatever the vendor promises, if the underlying architecture is daily or hourly CSV upload, you will oversell. The eBay and Amazon APIs both support real-time push — there's no reason to use CSV in 2026.
- Zapier / Make / IFTTT daisy-chains.Fine for low-volume, fragile at scale. Sync breaks silently, you don't notice until orders start being cancelled.
- Shopify-as-master-inventory.Shopify's multi-channel app pushes stock to Amazon and eBay, but it's one-way (Shopify → channels). If someone buys on eBay first, Shopify doesn't know until the next sync cycle.
- Manual spreadsheets with daily reconciliation.Works up to about 150-200 orders/month if you're disciplined. Above that, you oversell. Every time.
Step-by-step: connecting eBay and Amazon to a sync platform
- Don't relist. Your existing eBay and Amazon listings have history, reviews, and search ranking. Never re-create them. Connect the inventory platform to pull existing listings via API.
- Map SKUs.Match each listing to an internal SKU in your inventory platform. This takes 1-3 hours for 500 SKUs if they're well-named, longer if inconsistent.
- Set stock buffers per channel. Start conservative: Amazon 5, eBay 10. Reduce over time as you see actual sync behaviour.
- Enable one channel at a time.Turn on sync for Amazon first. Watch a day of orders flow through. When confident, enable eBay. Don't flip both at once.
- Freeze stock edits on the marketplaces. Lock any manual adjustment permissions on eBay and Amazon. All stock changes go through the inventory platform from now on.
Platforms that do this correctly
Real-time API sync, proper oversell prevention, and per-channel buffers: MaxInvent, Linnworks, Veeqo (for Amazon-heavy sellers), Brightpearl, and Cin7 Omni. All of these are credible for eBay + Amazon multi-channel sync. Pick based on pricing, UK data residency, courier integrations, and the other channels you sell on.
Things to avoid: pure-Shopify setups (Shopify-as-master), CSV-based platforms, and any platform where the vendor refuses to quote average sync latency in seconds.
Measuring whether sync is working
Three metrics to track monthly:
- Oversell count. Number of orders cancelled because stock ran out between order and dispatch. Should trend towards zero.
- Sync latency P95. The 95th percentile time for a stock change to propagate from one channel to another. Under 60 seconds is acceptable, under 15 is good.
- Stock accuracy at quarter-end count. Physical count vs platform count. Over 99% accuracy is achievable. Under 95% means your sync is silently drifting.