Inventory Diagnostic Case Study · UAE · September 2026
35 SKUs Needed Stock Attention. Only 13 Still Had Pending Reorders.
How one UAE inventory plan separated stock movement, existing purchase orders and genuinely new purchasing requirements.
Saddl··122 active SKU planning rows · Snapshot: 21 September 2026
SKUs with Stock-Risk or Reorder Signal
35
OOS-risk / reorder statuses at point-in-time snapshot
SKUs Also Overstocked
33
In the same 122-SKU portfolio
SKUs with Pending Reorder Quantity
13
After existing commitments considered
Pending Reorder Cost
AED 14,389
1,794 units across 13 SKUs
122 active SKU planning rows·2,129 units already on order across 19 SKUs·1,610 units proposed for marketplace allocation across 38 SKUs·Three decisions: Move · Track · Buy
Direct Answer
A low-stock signal does not automatically mean a new purchase order is required. Before reordering, check marketplace stock, warehouse inventory, sales velocity, inventory already ordered and whether existing units can be moved. The right action may be to move stock, track an inbound purchase order or place a new reorder — and the same portfolio can require all three at once.
A low-stock warning creates urgency. But urgency does not always mean: buy more inventory.
In one real UAE marketplace inventory plan, 35 SKUs were carrying an out-of-stock risk or reorder signal. At the same time, 33 SKUs were overstocked. And when the replenishment plan was taken one level deeper, only 13 SKUs still carried a pending reorder quantity — representing 1,794 units and approximately AED 14,389 in pending purchasing requirement.
The account did not have one inventory problem. It had several different inventory decisions hiding underneath the same stock-risk signal. The distinction changed the question from "what is running low?" to "what should we move, what should we wait for, and what genuinely deserves new capital?"
The inventory snapshot
The planning export covered 122 active SKU rows. Two problems existed in the same portfolio simultaneously:
122 Active SKUs — Inventory Status Distribution
54
OK
33
Overstocked
23
Critical OOS Risk
11
OOS Risk
1
Reorder Now
Too much stock and too little stock existed in the same portfolio. An account-level inventory total was not enough.
On one side, 35 SKUs were carrying OOS-risk or reorder signals. On the other, 33 SKUs were overstocked. That immediately tells us why an account-level instruction such as "we need more inventory" would be too broad. The business did not simply need more stock. It needed to understand which products were short, where existing inventory was sitting, what was already on order, and where the next purchase commitment was genuinely required.
The alert count was not the purchasing requirement
The inventory plan moved through several layers before arriving at the capital question:
Stock-risk signal
35
SKUs carrying OOS-risk or reorder statuses
Replenishment calculation
17
SKUs with a suggested reorder quantity
2,681 units suggested
Existing commitments
19
SKUs already with inventory on order
2,129 units inbound
Pending purchasing requirement
13
SKUs still carrying positive pending reorder quantity
1,794 units · AED 14,389
The first number tells you where inventory may be insufficient. The last number gets closer to where additional purchasing capital still needs to be committed.
That progression matters. The first signal asks: where might inventory be insufficient? The final view asks something more useful for purchasing decisions: where does additional capital still need to be committed? Those are different questions — and the answer to the second is considerably smaller than the answer to the first.
Three different SKUs. Three different decisions.
When the inventory plan was reviewed at SKU level, three distinct situations emerged — each requiring a different response:
Decision 1
Move
The marketplace looked short. The network did not. Redistribute existing stock before committing more supplier capital.
Location
Units
Amazon FBA
66
Noon FBN
31
Minutes
67
Local warehouse
400
Total network
564
30-day requirement470 units
Shortfall0
Suggested supplier reorder0 units
MOVE
Allocate 100 units → Amazon, 50 units → Noon. No new supplier purchase required.
Decision 2
Track
Critical stock risk did not mean another purchase order was required. The next question was whether existing inbound inventory would arrive in time.
Current stock in hand39 units
30-day requirement170 units
Calculated shortfall131 units
Suggested reorder quantity180 units
Already ordered240 units ✓
Pending reorder0
TRACK INBOUND
Monitor whether the 240-unit inbound order arrives before current stock becomes a problem.
Decision 3
Buy
This requirement was still uncovered. No warehouse stock to close the gap. No existing supplier order covering the need.
Current stock27 units
Planning requirement148 units
Shortfall121 units
Suggested reorder qty125 units
Already ordered0
Pending reorder costAED 1,795
BUY
Genuine new purchasing requirement. No alternative stock position covers the 30-day need.
A stock alert should end in a specific inventory action
Evidence
Decision
What it means in practice
Sufficient inventory exists elsewhere in the network
MOVE
Redistribute to the marketplace where stock is needed — no supplier capital required
Required inventory is already inbound on an existing purchase order
TRACK
Monitor arrival timing — placing another order would create the next overstock problem
Requirement remains uncovered: no warehouse stock, no inbound PO
BUY
This is where new purchasing capital is genuinely required
Requirement no longer exists or stock is already excessive
HOLD
Avoid additional purchasing — review the overstock position first
Replenishment was partly a stock-movement problem
At the same time that the business needed to consider AED 14.4K of pending supplier purchases, it also had 1,610 existing units that the plan was proposing to redistribute across marketplaces. So the replenishment discussion was not just "how much inventory should we order?" It was also: how much inventory can we put to work before ordering anything else?
Proposed allocation (planned — not confirmed as completed)
38 SKUs · 1,610 units proposed for marketplace redistribution
Total proposed
1,610
units · 38 SKUs
→ Amazon
932
units proposed
→ Noon
578
units proposed
→ Minutes
100
units proposed
These were planned allocations in the inventory snapshot, not evidence that the transfers had been completed. Different marketplaces required different quantities for the same SKUs based on demand velocity and current availability.
13
Pending purchasing requirement · snapshot
1,794 units · AED 14,389.02 pending reorder cost
Is this where the next AED 14.4K of inventory capital should go?
The 13 pending reorders create a practical management question. The team can now review the requirement SKU by SKU — rather than treating every low-stock signal as equal — and consider:
AED 14,389.02 is the pending reorder cost in this planning snapshot — not realised spend, savings or a verified purchasing commitment.
The biggest shortage is not automatically the first purchase
Imagine two products. Product A has a large shortfall — but substantial stock is already inbound. Product B has a smaller shortfall — but no supplier order exists and the remaining marketplace stock may run out first. If we rank only by shortfall, Product A may appear more urgent. If we include inbound inventory, Product B may deserve the purchasing action first.
Likewise, a fast-selling product may deserve stock movement today even if it does not require a new supplier order. The decision depends on more than the size of the red number.
The Saddl Operating Workflow
From stock-risk alert to specific inventory action
Step 01
Inventory Risk
Which SKUs deserve attention? Identify OOS-risk and reorder statuses across the portfolio.
Step 02
Network Stock
What inventory exists and where? Check across Amazon FBA, Noon FBN, Minutes and local warehouse.
Step 03
Velocity & Requirement
How fast is each marketplace consuming stock? Calculate 30-day requirement and shortfall by SKU.
Step 04
Existing Purchase Orders
What is already coming? Inventory already on order changes what still needs to be purchased — and placing another order can create the next problem before solving the current one.
Step 05
Allocation
Can available stock be moved first? Identify proposed marketplace allocations from existing network inventory before committing new capital.
Step 06
Pending Reorder
What requirement remains genuinely uncovered? This is the more useful capital question — narrower than the original stock-risk count.
Step 07
Operator Decision
Move, track, buy or hold? The operator reviews supplier timing, marketplace conditions and business priorities alongside the plan.
Step 08
Purchasing / Fulfilment Follow-Up
Execute the agreed action — place the reorder, initiate the stock transfer or begin tracking inbound PO arrival. The plan gives the operator a more complete basis for deciding; it does not replace the decision itself.
What the inventory diagnostic actually revealed
The most useful finding was not "35 products are running low." The deeper diagnosis was:
Some products needed redistributionThe inventory existed, but not in the right place. Network stock was sufficient — the action was to move, not buy.
Some products needed inbound trackingThe shortage signal existed, but enough inventory was already ordered. The action was to monitor arrival timing, not place another supplier order.
Some products genuinely needed purchasingNo sufficient stock or inbound quantity covered the requirement. This was where new capital was actually required.
Some products were already overstockedAdditional purchasing could make the capital position worse, not better. New purchasing decisions needed to account for where stock was already concentrated.
Those are four different operating situations. They should not be managed with one blanket reorder rule.
What happened next — scope of this case study
This case study is intentionally a point-in-time diagnostic. The evidence establishes the inventory situation and the planning recommendations visible in the snapshot. It does not establish that all proposed transfers were completed, all pending reorders were placed, stockouts were subsequently avoided, or that the business saved a quantified amount of working capital. Those would require post-action evidence. The result of this case is not "Saddl saved AED X." The result is: the inventory problem became specific enough to act on. Instead of treating 35 stock-risk signals as 35 purchase requirements, the plan separated move, track and buy. That is the useful diagnostic outcome.
Frequently asked questions
Does a low-stock alert mean I should reorder?
No. First check total available inventory, warehouse stock, marketplace allocation and inventory already on order. The immediate action may be redistribution or inbound tracking rather than another supplier purchase.
What is the difference between suggested reorder and pending reorder?
A suggested reorder reflects the replenishment requirement calculated from the inventory situation. Pending reorder considers what still needs to be ordered after relevant existing commitments in the plan are taken into account. In this snapshot, 17 SKUs had suggested reorder quantities while only 13 still carried positive pending reorder quantities.
Why should existing purchase orders be part of inventory planning?
Because current stock can look insufficient even when enough replacement inventory is already inbound. Without the purchase-order context, a team may place another supplier order when the immediate need is actually to monitor arrival timing — and creating a second order can produce the next overstock problem before solving the current one.
Can a business be overstocked and at risk of stockout at the same time?
Yes. Inventory problems happen at SKU and location level. One set of products can carry excess stock while another group is running short. In this account, 33 SKUs were overstocked at the same time that 35 SKUs carried OOS-risk or reorder signals. That is why an account-level inventory total is not enough for replenishment decisions.
Should inventory be allocated equally across Amazon and Noon?
Not automatically. Allocation should consider demand, current availability, sales velocity, product priorities and the inventory already held on each marketplace. In this plan, 932 units were proposed for Amazon and 578 for Noon across the same group of SKUs — reflecting different velocity and availability on each marketplace, not a 50/50 split.
Does Saddl automatically manage every marketplace inventory feed?
No. Data availability and integration maturity differ by marketplace and workflow. Inventory recommendations should be interpreted within the data actually available for the account. The plan supports an operator decision — it does not replace supplier timing checks, marketplace condition reviews or business priorities.
Saddl Account Review
The inventory question wasn't "How much should we buy?"
Review marketplace stock, warehouse inventory, velocity and existing purchase orders together to identify what should move, what is already covered and where additional purchasing may be required.
The inventory data above uses anonymised operating data from a real UAE marketplace account. The planning snapshot is dated 21 September 2026 and covers 122 active SKU planning rows. Status counts (OK, Overstocked, Critical OOS Risk, OOS Risk, Reorder Now) are point-in-time inventory-planning classifications, not verified post-period outcomes.
Proposed allocation figures (38 SKUs, 1,610 units, marketplace splits) represent planner recommendations in the snapshot — not confirmed completed transfers. Suggested reorder quantities represent calculated replenishment requirements, not evidence that supplier orders were subsequently placed. The "already ordered" figures reflect the purchasing state recorded in the source snapshot.
AED 14,389.02 is the pending reorder cost figure in this planning view — not realised spend, savings or a verified commitment. This case study does not establish subsequent stockout prevention, sales uplift or working-capital savings. Marketplace integration maturity differs by platform. The case study is labelled as a diagnostic, not a verified customer success outcome.