38 SKUs Were Low on Stock.
33 Were Overstocked.
Why Reordering Is Not Just a Sales-Velocity Decision.

A Marketplace Account Can Be Short and Long at the Same Time

That sounds like a contradiction. But in one real UAE marketplace account, the inventory view showed exactly that: 38 SKUs below their reorder point and 33 SKUs carrying more stock than their current demand required — at the same time.

There were also more than 1,500 units already sitting in the warehouse, ready to ship to marketplaces. So when a channel showed low stock, the next question was not automatically: place another purchase order. Sometimes the more useful question was: do we already have this stock somewhere else?

That distinction matters because a reorder is not only an inventory decision. It is also a cash decision. Every purchase order uses working capital that could sit elsewhere in the business. The question is whether the stock situation actually justifies deploying it.

If a team looked only at the first row, the conclusion might be: 38 products are running low, so reorder. But the wider inventory view showed something different. Some stock already existed in the local warehouse. Some products carried too much inventory. Some marketplace shortages could be resolved through redistribution. And only part of the low-stock portfolio required fresh purchasing.

Below Reorder Point Is a Signal, Not a Decision

A reorder point is a useful trigger. It tells the team that current marketplace stock is approaching a level where action may be required. But the action depends on what else is happening across the inventory network.

One SKU may genuinely need a supplier reorder. Another may already have stock sitting in a local warehouse. Another may have inventory arriving through an existing purchase order. Another may be low on Amazon but adequately stocked on Noon. And another may be selling slowly enough that buying more would create excess inventory rather than solve an availability problem.

So the useful question is not simply: has this SKU crossed the reorder point? It is: why has it crossed the reorder point, and what is the lowest-risk way to restore availability?

Low Marketplace Stock Does Not Always Mean Low Total Stock

This is one of the most common inventory mistakes when marketplaces are managed separately. Amazon shows low cover. The Amazon team raises an alert. A purchase order gets created. But somewhere else in the business, stock may already exist — in the local warehouse, allocated to another marketplace, waiting to be shipped, already covered by an inbound purchase order, or sitting in excess against slower demand.

If those inventory views are disconnected, the business can purchase more inventory while already holding enough stock overall. The marketplace problem gets solved. The cash problem gets worse.

That is why inventory planning needs two different views: how much stock is available on the marketplace, and how much stock does the business actually hold? They are not the same question.

Sales Velocity Matters, But It Is Only One Input

Demand should influence inventory allocation. A marketplace selling six units a day should normally be treated differently from one selling less than one unit a day. But sales velocity alone does not tell you how much to buy.

Consider a SKU selling quickly on Amazon. If 400 units are available in the warehouse, the first action may be a shipment. If there are no warehouse units, no meaningful inbound purchase order, and supplier lead time is long, a new reorder may be necessary. If sales velocity recently increased because of a short promotion, the team may need to decide whether that demand will continue before purchasing heavily. And if the product is profitable on one marketplace but weak on another, the inventory allocation may deserve to follow the economics rather than simply dividing stock equally.

Velocity helps answer: where is inventory being consumed? It does not answer, by itself: how much new inventory should we purchase?

Overstock Is the Other Side of the Same Problem

While 38 SKUs were below reorder point, 33 were overstocked. Those two numbers should be examined together. The business was not simply suffering from a shortage of inventory — it had an allocation and purchasing problem across the portfolio.

With too little stock, sales can be lost because a product is unavailable. With too much stock, cash remains tied up in inventory that is not moving quickly enough. Solving one without looking at the other can simply move the problem. Buying aggressively to avoid every stockout can create overstock. Reducing inventory too aggressively to release cash can create availability problems. The operator has to balance both.

1,510 Units Were Ready to Move

The same snapshot showed 1,510 units across 65 cartons already classified as ready to ship. That matters because stock sitting in a warehouse and stock available for sale on a marketplace are not the same thing. Inventory may physically exist, but until it reaches the channel that needs it, it cannot support marketplace demand.

So inventory planning is not just: how much do we own? It is also: what should move next? Allocation decisions should account for current marketplace inventory and sales velocity before committing warehouse stock — a SKU selling quickly on Amazon may deserve a different allocation from the same SKU on Noon or Minutes.

Existing Purchase Orders Matter Too

A SKU may appear low today while more stock is already on its way. So before another purchase order is raised, the team should check: quantity currently available, marketplace sales velocity, warehouse availability, stock already allocated for shipment, outstanding purchase orders, supplier lead time, minimum order quantity, and expected demand during the lead-time period.

Without that context, it is easy to react twice to the same problem. One person sees low stock and raises a purchase order. Another team already has replenishment in progress. The result can be excess inventory a few weeks later. The signal was correct. The second purchasing decision was unnecessary.

The Real Lesson from This Inventory Snapshot

The useful insight was not "38 SKUs were low, so buy more inventory." It was not "33 SKUs were overstocked, so stop purchasing." And it was not "always move stock instead of reordering." The account needed all three decisions simultaneously.

Some products needed redistribution. Some genuinely needed reordering. Some already had too much stock. That is why inventory management should not stop at a reorder alert. The better question is: what should happen to this SKU next? The answer may be to move warehouse stock, increase a marketplace allocation, reduce allocation elsewhere, wait for an existing PO, place a new purchase order — or simply do not buy more yet.

The job is to identify which one.