Amazon, eBay and Kaufland each reach a different pool of buyers, which is why sellers add all three rather than pick one. The cost: each one is a separate system with its own idea of how much stock you have.
In Vedron there is one stock number. Three marketplaces read from it and write to it.
Why this gets harder with each marketplace
One channel is easy. Two is manageable. Three is where coordination becomes the problem: each marketplace has its own API, its own update cadence, its own rate limits, its own way of reporting a sale. A dropship SKU adds another source of truth outside your warehouse.
What runs today
Amazon (SP-API), eBay (Inventory API) and Kaufland’s seller API all connect to the same stock record per SKU. A sale on any one of the three decrements the shared number immediately. The other two see the true remaining quantity without waiting for a scheduled sync.
For dropship SKUs, available stock is calculated from the supplier’s own availability, not assumed to be the same number sitting in your warehouse.
Common questions
What happens if two marketplaces try to sell the last unit at the same time? The second attempt sees accurate (zero) availability as soon as the first sale is recorded. The risk window is the sync latency itself, which is why near-real-time matters more than the channel count.
What about FBA stock held in an Amazon warehouse? FBA stock is its own pool, tracked separately but counted toward the same product’s total availability across every connected channel.
Can I add a fourth marketplace later? Yes. Each marketplace is an API connection to the same stock model, not a redesign of the model.
Talk to us about your setup
Book a short call and we will walk through yours. Beta clients get two months of custom setup on us, and the standard trial can be extended if you need it.