Move, Track, or Buy: How to Categorise Every SKU That Needs Stock Attention
A low-stock alert is not a purchase order. Every SKU that triggers a stock-risk signal needs one of three decisions — and only one of them requires new capital.
Saddl··Inventory & Cash
Starting signal
35
SKUs flagged as OOS-risk or reorder in one UAE portfolio
Still requiring a purchase
13
After Move and Track decisions were applied
Capital question narrowed to
AED 14,389
Pending reorder cost · 1,794 units across 13 SKUs
The framework in one sentence
When a SKU triggers a low-stock alert, check three things before deciding to reorder: is there sufficient inventory elsewhere in the network that can be moved? Is an existing purchase order already covering the shortfall? If neither is true, then — and only then — does the right answer become Buy.
A low-stock warning creates urgency. And urgency tends to produce one response: order more. But reordering before checking the full inventory picture can mean placing a supplier order when existing stock just needs to be moved — or when the inventory is already inbound on a purchase order that's been forgotten.
In one real UAE marketplace portfolio, 35 SKUs were flagged with out-of-stock risk or reorder signals. After applying Move, Track and Buy decisions at SKU level, only 13 still had a genuine pending purchasing requirement. The question for the other 22 was not "how much to order" — it was either "where to move existing stock" or "when will the inbound order arrive."
The distinction matters because each of the three responses has a different operational and financial consequence.
Three decisions. Only one requires new capital.
Every SKU with a stock-risk signal belongs in one of four states. Three of them involve action; one of them is a hold.
Decision 1
Move
Sufficient inventory exists in the network — warehouse, another fulfilment centre or another marketplace. The marketplace looks short. The business doesn't.
Condition
Network stock is sufficient to cover the 30-day requirement. No new supplier capital needed.
→ Redistribute. Don't reorder.
Decision 2
Track
An existing purchase order covers the shortfall. Inventory is already inbound. The risk isn't supply — it's timing.
Condition
Inbound quantity on existing PO meets or exceeds the suggested reorder quantity. Pending reorder = 0.
→ Monitor arrival. Don't reorder.
Decision 3
Buy
No sufficient inventory exists elsewhere. No existing purchase order covers the requirement. The gap is genuine.
Condition
No warehouse stock closes the gap. No inbound PO covers the shortfall. Pending reorder quantity is positive.
→ Place the purchase order.
Hold
Hold
The requirement no longer exists, or the SKU is already overstocked elsewhere. Additional purchasing would worsen the capital position.
Condition
Overstock exists. Or the velocity calculation no longer supports replenishment at this time.
→ Review overstock first.
The sequence matters. Move is checked first because it requires no new capital and no supplier lead time. Track is checked second because placing another order when one is already inbound creates the next overstock problem. Buy is the last category to reach — only after the other two have been ruled out.
How the evidence points to each decision
Three pieces of evidence determine which category a SKU falls into: what inventory exists and where, what is already on order, and what the 30-day sales requirement is. Here is how those inputs map to decisions:
Evidence
Decision
What happens next
Sufficient stock in warehouse or on another marketplace — total network covers the 30-day requirement
MOVE
Allocate from existing network stock to the marketplace where the gap exists. No supplier order required.
Current marketplace stock is low but an existing PO quantity meets or exceeds the suggested reorder quantity
TRACK
Monitor the inbound purchase order. Confirm arrival timing relative to current stock runway. Do not place another order.
No sufficient warehouse stock. No existing PO. Pending reorder quantity is positive.
BUY
Place the supplier order. The 30-day requirement is genuinely uncovered by any other inventory position.
SKU is overstocked elsewhere. Or the calculated requirement no longer warrants a reorder.
HOLD
Avoid purchasing. Review why the overstock exists. Do not create another layer of excess before the current one moves.
What each decision looks like in practice
Move: the marketplace looked short. The network didn't.
In the UAE portfolio example, one SKU showed OOS-risk on a marketplace view. But when total network stock was checked — Amazon FBA, Noon FBN, Minutes and local warehouse — the combined inventory was 564 units against a 30-day requirement of 470. Suggested reorder: zero. The action was to allocate 100 units to Amazon and 50 units to Noon from existing warehouse stock. No supplier order was placed.
Move: what to check
Before treating a low-stock alert as a purchase requirement, check total available inventory across every fulfilment location: Amazon FBA, Noon FBN, Minutes and local warehouse. A product can be "running out" on one channel while the network holds weeks of supply.
Track: Critical OOS risk — but inventory was already coming.
A second SKU in the same portfolio showed Critical OOS Risk. Current stock was 39 units against a 30-day requirement of 170 — a 131-unit shortfall, and a suggested reorder of 180 units. But the team had already ordered 240 units from the supplier. Pending reorder: zero. The right action was to track the inbound order and confirm it would arrive before the current 39 units ran out.
Track: the risk changes from supply to timing
When a purchase order already covers the shortfall, the operational question shifts from "should we order?" to "will the inventory arrive in time?" That is a tracking and supplier-coordination question, not a purchasing question. Placing another order without checking the existing PO is how overstock problems get created while trying to solve stockout problems.
Buy: nothing covered the requirement.
A third SKU had 27 units in hand, a 30-day planning requirement of 148 units, and a shortfall of 121 units. The suggested reorder was 125 units. No existing supplier order. No warehouse stock to redistribute. Pending reorder cost: AED 1,795. This was the right situation to place a supplier order — because every other option had been checked and ruled out.
Buy: the last category, not the first
Buy is not the default response to a low-stock alert. It is the decision reached after Move and Track have been ruled out. This sequence matters because it prevents unnecessary capital commitment when the inventory already exists — somewhere — in the business.
The sequence to apply for each flagged SKU
Working through this in order prevents the most common error: treating every stock-risk signal as a purchase requirement without checking the inventory position first.
Step 01
Check the total network stock
Amazon FBA, Noon FBN, Minutes and local warehouse. Add up what is actually available across all locations before drawing any conclusion from a single marketplace number.
Step 02
Calculate the 30-day requirement and shortfall
Use sales velocity to estimate how much each marketplace needs over the next 30 days. Calculate the shortfall as: (requirement) minus (current marketplace stock).
Step 03
Can existing network stock close the gap? → Move
If warehouse or other channel inventory is sufficient to cover the shortfall, the right action is redistribution. No new supplier capital is required.
Step 04
Is an existing PO covering the shortfall? → Track
Check any open purchase orders for this SKU. If inbound quantity meets or exceeds the suggested reorder, pending reorder is zero. The action is to monitor arrival timing.
Step 05
Is the SKU overstocked elsewhere? → Hold
Check whether this SKU carries overstock on a different marketplace or in the warehouse. Additional purchasing into an already-heavy position needs review before commitment.
Step 06
Nothing else covers it → Buy
Pending reorder quantity is positive. No network stock to redistribute. No inbound PO. This is a genuine new purchasing requirement — and the only situation where a supplier order is the right response.
Before placing a reorder: six things to check
Total network stock across all fulfilment locationsAmazon FBA, Noon FBN, Minutes and local warehouse — not just the marketplace showing the alert.
30-day sales velocity and estimated requirementA product selling slowly needs a different replenishment response than one selling fast. Velocity starts the calculation.
Open purchase orders for this SKUCheck any inbound quantities already committed to the supplier. An existing PO changes the pending reorder calculation entirely.
Overstock position on other marketplaces or in the warehouseIs this SKU overstocked somewhere else in the same portfolio? If so, the right question is redistribution, not reorder.
Proposed marketplace allocation from existing stockCan existing warehouse stock be proposed for transfer before any supplier order is placed?
Pending reorder quantity after existing commitmentsThis is the number that should drive the supplier conversation — not the first alert count. In the UAE portfolio example, 35 signals became 13 genuine pending reorders after this check.
What Move / Track / Buy doesn't tell you
This framework categorises where to act. It doesn't decide MOQ, supplier lead time, safety stock levels, or whether the commercial priority of a SKU justifies the reorder cost. Those remain operator decisions. The framework narrows the set of SKUs that genuinely need purchasing attention — it doesn't replace the decision itself.
Frequently asked questions
What does Move mean in inventory management?+
Move means the stock exists somewhere in the network — warehouse, another fulfilment centre or another marketplace — but it is not in the right place. The action is to redistribute existing inventory rather than place a new supplier order.
What does Track mean in inventory management?+
Track means a purchase order covering the shortfall is already placed and inbound. The action is to monitor arrival timing rather than place another supplier order, which would create the next overstock problem before solving the current stockout risk.
When should I choose Buy?+
Buy is the right decision only when no sufficient inventory exists elsewhere in the network and no existing purchase order covers the shortfall. It is the last category to reach, not the first. In the UAE portfolio example, 35 stock-risk signals narrowed to 13 genuine Buy situations after Move and Track were applied.
Why do the same SKUs sometimes appear in both low-stock and overstock lists?+
Inventory problems are SKU-level and location-level, not account-level. A SKU can be overstocked on one marketplace while running short on another. An account-level total inventory number obscures this. That is why the check must be done at the SKU and location level, not just the account total.
Does the Move / Track / Buy framework work for both Amazon and Noon?+
Yes. The logic applies across both marketplaces. What changes is the available inventory data and fulfilment context — Amazon FBA, Noon FBN, Minutes and warehouse — but the decision sequence is the same: check network stock, check existing POs, then decide whether a new supplier order is actually required.
Saddl Account Review
35 stock alerts. 13 actually needed purchasing.
Check network stock, existing purchase orders and overstock positions together before placing a supplier order. The answer for most flagged SKUs is Move or Track — not Buy.
Figures referenced in this post (35 SKUs, 13 pending reorders, AED 14,389, 1,794 units) are drawn from a real UAE marketplace inventory planning snapshot dated 21 September 2026, covering 122 active SKU rows. The individual SKU examples (Move: 564 units / 470-unit requirement; Track: 39 units + 240 inbound; Buy: 27 units / AED 1,795 pending reorder cost) are from the same snapshot.
All figures are point-in-time planning data. Pending reorder cost is a planning figure, not realised spend. Proposed allocations are planner recommendations, not confirmed completed transfers. This article is derived from the CS03 inventory diagnostic case study — see the full case study for the complete portfolio view.