Order Management Across Marketplaces

One marketplace is a spreadsheet. Two is a spreadsheet somebody updates twice. Three is where the spreadsheet starts being wrong, and the first sign is usually an oversell on the channel that matters most.

Distributed order management is the unglamorous name for the answer: one place that knows what stock exists, which channel sold it, and where it has to ship from.

Overselling. Two channels sell the last unit within the same few minutes. One of those orders has to be cancelled, and a cancellation is a metric on every marketplace, not just an apology.

Stale availability. Stock is there, the channel does not know, and the listing sits unavailable while a competitor takes the sales.

Split fulfilment. The same product held in two places, so which warehouse ships depends on which channel sold, and nobody knows why one channel's delivery times are worse.

Returns nobody reconciles. A return goes back into stock on the channel it came from and stays invisible to the others, so the numbers drift a little every week.

One system owns the stock number, and every channel reads from it. Which system does not matter much. That there is exactly one matters enormously.

The most common failure is two systems that both think they are authoritative, usually an accounting package and a listing tool, reconciled by a person. That works until the person is on holiday.

Holding back a few units per channel prevents oversells and costs sales on everything with thin cover, which is usually the products worth the most.

Use a buffer while the sync interval is long, and treat it as a symptom. When the sync is quick enough, the buffer comes down, and the products that were quietly capped start selling again.

Pricing. Each marketplace has its own competitive position and its own fee structure, so one price pushed everywhere is either uncompetitive in one place or unprofitable in another.

Listing copy, to a point. The product is the same and the way people search for it is not: a title written for Amazon's search box is not the title that works on eBay, and a feed that pushes identical copy everywhere is leaving ranking on the table on at least two channels.

Customer messages. Each marketplace has its own response time expectations and its own rules about what may be said, and a single templated reply is how a seller gets a policy warning for offering something off-platform.

Roughly: more than two channels, or more than a few hundred SKUs, or any product held in more than one place. Below that a disciplined spreadsheet and one person is genuinely fine and much cheaper.

What to ask of a tool: how often it syncs, what it does when a channel's API is down, whether it maps your own SKU across channels rather than making you rename everything, and whether it handles returns back into stock. The last question is the one that gets skipped and the one that causes the drift.

If Amazon holds your stock and another channel sells it, something has to raise a fulfilment order and pass the tracking back before the channel's dispatch deadline. That is a real integration and not a manual job at any volume.

The alternative is holding separate stock per channel, which is simpler to run and ties up more money. Neither is wrong; what is wrong is drifting into one of them without deciding.

The order layer is what decides whether a third channel is a growth or a mess, which is why it comes up before anybody adds Walmart or eBay to an account that already sells in two places.

It is also the argument for keeping your own store honest: a store that reads the same stock number as the marketplaces is a channel, and one that keeps its own is a fourth thing to reconcile.

Every one of those channels is a service we run, and the reason they are described together on one page rather than sold separately is that the order layer underneath them is one problem, not four.

If your numbers stopped agreeing and nobody is quite sure when, it is usually one missing sync rather than everything.