02 Inventory Rhythm
This week’s SKU: replenish, throttle, or pause?
This week, the question is not “how many units are in the warehouse?” It is how long this SKU can safely carry demand: whether ads can continue, page promises can hold, and a purchase order would trap cash in the wrong SKU.
Start with the full case: a US pet-travel store with steady early orders reviews its A-07 pet car mat in the first week of May. It has 14 days of sellable cover against 18 days of actual total lead time, so 18 - 14 = 4 days of exposure and it throttles rather than scales this week. Ops subtracts Committed and holds, supply checks recent receipts, ads pauses tests, and finance checks purchase cash; the still-unvalidated rear-seat protector cannot borrow A-07 sales or reorder proof.
This week’s record
Inventory risk and replenishment cadence table
Pass standard
Know which SKUs scale, throttle, replenish, or clear out
Stop line
If cover is below replenishment cycle, do not scale budget
Inventory risk workbench preview
Scale
Coverage is healthy; keep planned media.
38d
Throttle
Lead time is 18 days; pause scale tests.
14d
Clear
Low turn and high refunds; no reorder.
96d
01 Correct The Misread
Inventory is not how many units remain. It is how long growth can be carried.
A stockout does not only cost a few orders. It breaks ad learning, weakens SEO landing pages, hurts repeat purchase, and floods support with restock questions. Overstock is not only warehouse space; it blocks cash, media budget, product tests, and supply decisions.
Avoid stockouts
Core SKUs must carry ads, organic traffic, and repeat purchase.
Avoid dead stock
New or weak SKUs should not bet growth with oversized inventory.
Avoid random replenishment
Replenishment should follow velocity, lead time, margin, and turn.
Avoid uncontrolled promises
Preorder, stockout, exchange, and delay need rules.
Translate the admin labels before calculating: On hand is the total at a location and does not prove it can sell now; Available is stock that can currently fulfill; Committed is already tied to paid, unfulfilled orders; and Incoming is still in transit, not a same-day shipping promise. Cash flow here is the timing among purchase deposits, balances, media spend, and received sales cash. It shows whether a purchase order crowds out a core SKU or approved media; it does not prove that the order should be placed.
01A Work the four-day gap in full
When cover is shorter than replenishment time, protect capacity before chasing strong ROAS.
A-07 is a reviewable operating chain, not a threshold that can be copied to another SKU. Put sellable units, actual lead time, reorder point, cash, and page promise on one row before making a move.
Start from one dated snapshot: 68 Available minus 12 Committed equals 56 sellable units, so 68 - 12 = 56. At four normal units per day, 56 / 4 = 14 normal days of cover. Supply should not repeat a standard lead time. It should show recent receipts as 10 production days, 6 freight days, and 2 receiving days, or 10 + 6 + 2 = 18 days.
The gap is therefore 18 - 14 = 4 days. It does not predict a stockout exactly four days from now and it is not a universal platform rule. It says this A-07 snapshot cannot carry its own recent replenishment cycle. The local reorder point is 4 x 18 + 40 = 112 units, so 112 - 56 = 56 units sit below it. That 56 is a replenishment-review gap, not an automatic 56-unit purchase order without checking inbound stock, MOQ, cash, and forecast error.
On Monday, operations reconciles Available, Committed, holds, and location availability. Supply attaches the last three actual lead times, next receiving date, and split-shipment risk. Media freezes new scale tests. Page and support use only a ship-date promise that receiving evidence supports. Finance checks whether deposits and balances crowd out approved creative, media, or core-SKU cash. Inventory becomes a set of linked responsibilities instead of one admin number.
The continue line must be explicit: retain only a small, stable media cadence when the receiving path has a date, the page promise is accurate, and purchase cash stays inside established contribution and cash guardrails. Keep throttling while 18 days remains the best evidence. Pause the affected market or campaign when sellable stock, location availability, or receiving date cannot reconcile. Preorder is not an automatic fix. Without a support owner, checkable date, and fulfillment path, it merely moves uncertainty to the customer.
02 Replenishment decision practice
Decide the SKU state before choosing replenish, throttle, clearance, or state repair.
This turns the inventory lesson from a table summary into an operating decision. Read What / Why / How / Practice, then choose a real inventory scenario and this-week action to see whether it can be written back to the weekly review.
What
An inventory table is not an admin screenshot
It is a growth capacity table: it tells media, page, support, purchasing, and merchandising teams whether a SKU can keep scaling, for how long, and when it must replenish or exit.
Why
On hand does not mean sellable
Inventory can be committed to orders, limited by location, inbound, unavailable, or reserved by bundles. Reading total stock alone can split page promises from real fulfillment.
How
Split states before choosing action
For each core SKU, split sellable, committed, inbound, total lead time, safety stock, reorder point, and days of cover before choosing scale, throttle, replenish, clear out, or pause.
Practice
Turn one SKU into a weekly-review action
A valid row includes SKU tier, first evidence, risk state, media action, purchasing action, page/support action, and next review date.
The practice below is not asking you to choose the most optimistic move. It tests whether the numbers permit it. Read sellable stock, lead time, daily sales, refunds, or location state in the scenario before choosing this week's action. The feedback identifies whether you lack replenishment proof, cash review, page synchronization, or a reason not to mistake one spike for a reorder signal.
Use A-07 as the reference: when 14 days of cover sit below 18 days of lead time, strong ROAS cannot cancel throttling. Conversely, deep stock does not automatically prove safety. It can merely trap cash in a slow SKU. Choose one state that can enter the weekly review: replenish plus throttle, small-batch watch, clear out, repair inventory state, or pause, not a generic keep watching.
Step 1: choose a real scenario
Step 2: first evidence
A core SKU has only 14 days of cover
Reorder point = 4 x 18 + 40 = 112 units. Current 56 units are below reorder point and below lead-time cover.
Risk state
Decide state before ordering
Media boundary
Throttle when cover is weak
Sync target
Purchasing, page, support
Step 3: choose this-week action
Step 4: weekly review row preview
Choose a this-week action first, then this area will show whether it can enter the inventory review.
After choosing, write the SKU, arithmetic, state, blocked move, owner, evidence date, and next review date into the weekly review. Without those fields, even correct interactive feedback cannot authorize an order, scale, or preorder. It only identifies the evidence to add first.
Replenishment cash-flow field
PO payment date
Deposit, balance, and supplier payment dates.
Decide whether replenishment crowds out ad, creative, or next-test cash.
Expected receiving date
Expected arrival, 3PL receiving, and put-away date.
Decide whether the store can support a campaign or must stage the launch.
Shopify payout delay
Payout cycle, reserve, or payment-provider delay.
Check whether sales cash can cover the next purchase order.
Inventory aging bucket / clearance floor
0-30, 31-60, 61-90, 90+ day stock and break-even or controlled-loss floor.
Choose clearance, bundle, no replenishment, or cash release.
03 Weekly Inventory Table
Put inventory risk and replenishment rhythm on one table.
Forecast, reorder point, safety stock, SKU tier, and media boundary should not live in separate files. Each core SKU needs one operating row.
SKU tier
A core, B profit, C test, D clear-out.
Different tiers use different buffers, replenishment, and media rules.
Merch + ops
Sellable / locked / inbound
Shopify stock, paid unfulfilled orders, purchase orders, inbound shipping.
Calculate true available cover before scaling.
Ops
30-day normal daily sales
Exclude stockout days, abnormal discount days, one-off viral spikes.
If variance exceeds 25% for two weeks, recalculate baseline.
Ops, Monday
Total lead time
Production + freight + customs + receiving.
Supplier delay over 3 days triggers media, page, and support sync.
Supply chain
Reorder point
Average daily sales x total lead time + safety stock.
Below reorder point means same-day replenishment review.
Ops lead
Media boundary
Days of cover, replenishment cycle, campaign plan, substitute SKUs.
If cover is below replenishment cycle, do not scale budget.
Media owner
Risk state
Scale, watch, throttle, replenish, clear out, pause promotion.
State decides the next move; not every SKU is “watch.”
Operator
Use this table at three moments: daily, watch low stock, unusual sales, and stockouts and freeze media or correct page promises when needed; on Monday, review the sales baseline, lead time, safety stock, and MOQ before assigning replenishment; before a campaign, recalculate peak cover, warehouse capacity, and delivery timing to set the product and scaling boundary. The table does not blur the three checks together; it leaves a reviewable action for each one.
04 Data Foundation
Before forecasting, complete the inventory base table.
Many teams do not lack forecasting skill; they lack complete fields. Shopify inventory alone does not show locked stock, inbound units, supplier lead time, campaign plans, stockout days, return risk, or cash use.
SKU basics
Product, variant, supplier, purchase cost, weight, volume, fragile/special handling.
Without cost and fulfillment boundaries, reorder quantity becomes guessing.
Inventory state
Sellable, locked, inbound, reserved, stockout days.
Admin stock can overstate real capacity.
Sales velocity
7 / 14 / 30-day daily sales, split campaign and normal days.
Forecast gets polluted by stockouts, discounts, and viral spikes.
Supply parameters
Production, freight, customs, receiving, MOQ, supplier delay record.
Media and campaigns outrun supply.
Operating metrics
Margin, refund rate, ad spend, conversion, repeat purchase, inventory turn.
Weak SKUs get replenished like core SKUs.
On hand
Total inventory at a location; not the sellable number.
Use as context, not the direct scaling signal.
Available
Sellable stock not tied to orders, holds, or location rules.
Use for normal and campaign days of cover.
Committed
Paid but unfulfilled inventory already tied to orders.
Subtract from growth capacity; do not sell again.
Unavailable
Physically present but held by QA, damage, reserve, or app hold.
Check hold reason and release, isolate, or fix rules.
Incoming
Inbound transfer or purchase-order stock not received yet.
Use for receiving forecast, not immediate shipping promises.
Align inventory evidence from three places first
Replenishment decisions cannot rely on one admin number. Put current Shopify state, future arrivals from the purchase sheet, and real supplier lead time together before choosing this week’s action.
Shopify Products / Inventory / Locations
Check Available, Committed, Unavailable, On hand, Incoming, market/location availability, and bundle allocation.
Confirm how much stock can actually be fulfilled now.
Purchase sheet or purchase order
Check ordered quantity, expected receiving date, purchase cost, MOQ, payment status, and inbound status.
Confirm whether future stock can support this week’s action.
Supplier lead-time record
Review recent real production, shipping, customs, and receiving days instead of relying only on a supplier promise.
Confirm whether reorder point and safety stock reflect real lead time.
Small catalogs can review every core SKU. Larger catalogs should sample by A core products, campaign products, deep stock, market inventory mismatch, and high-refund products so the review does not only cover the most visible items.
05 Demand Capacity Forecast
Do not only forecast sales. Forecast demand you can carry.
Direct-store sales are shaped by ad budget, creative fatigue, promotions, seasonality, SEO rank, email campaigns, creators, and stockout history. Using the existing source report, static average sales are split into baseline, peak, supply constraint, and cash pressure.
Normal baseline
14 / 30 / 60-day normal sales, excluding stockout and abnormal campaign days.
Ops owner updates forecast error weekly.
Campaign peak
Promotions, gifting season, creators, email schedule, content spike.
Campaign owner locks peak stock and substitutes before launch.
Supply constraint
Production cycle, freight, receiving, MOQ, inbound stock.
Supply owner writes the last order date.
Cash pressure
Inventory turn after reorder, clearance risk, media and asset budget use.
Finance or growth lead approves large purchase.
How to calculate the reorder point
Reorder point = average daily sales x total lead time + safety stock. If a SKU sells 4 units per normal day, total lead time is 18 days, and safety stock is 40 units, the reorder point is 4 x 18 + 40 = 112 units. Below 112 sellable units, it triggers replenishment review. A suggested order can be written as “forecast demand + safety stock − current sellable stock − confirmed inbound,” but it is only a planning start; receiving date, MOQ, cash, and forecast error still need review.
The existing source treats multi-week retail forecasting as especially difficult around high-stakes sales events. That is why this lesson separates the normal baseline, campaign peak, supply limit, and cash pressure instead of letting the last 30 days stand in for every decision. Read the existing Georgia Institute of Technology related research.
Forecast error ledger field
Forecast version/date
Forecast version and date used this week.
Prevents guessing which assumption drove the order.
Expected normal daily sales
Expected daily sales after removing stockout, discount, and spike days.
Becomes next week’s normal baseline.
Variance % / reason tag
Variance percentage plus stockout / promo / creator spike / ad budget / seasonality / page issue / feed mismatch.
If it misses for two weeks, recalculate baseline, media boundary, or reorder point.
Next correction
Coefficient, order quantity, campaign cadence, or ad cap to change next week.
Turns demand planning into a reviewable forecast error ledger.
06 Inventory Coverage Calculator
Calculate how long stock can carry demand before choosing ads, campaigns, and replenishment.
Many inventory reviews do not fail from lack of discussion; they fail because the numbers are not on the same table. These three SKU cases turn sellable stock, committed orders, normal velocity, campaign velocity, lead time, and safety stock into an operating decision.
Before selecting a case, set the calculation boundary. Sellable units come from one inventory snapshot, normal daily sales exclude stockouts and one-off abnormal campaigns, campaign daily sales apply only to the campaign scenario, lead time comes from recent actual batches, and safety stock is this store's buffer for this SKU. Combining different dates, markets, or SKUs can create attractive coverage math that cannot be executed.
The calculator shows sellable units, normal cover, campaign cover, reorder point, and lead-time gap. Its job is not to forecast revenue. It exposes blocked moves: normal cover that looks sufficient may not support campaign velocity, and Incoming does not mean a customer can be promised shipment today. Read the formula and dates before the state and this-week action.
Inventory coverage calculator
A-07 pet car mat
Sellable stock
56
68 Available - 12 Committed
Normal cover
14d
56 / 4 normal daily sales
Campaign cover
8d
56 / 7 campaign daily sales
Reorder point
4 x 18 + 40 = 112
Inbound stock
120
Lead-time gap
Campaign cover is 10 days short of lead time
Blocked move
Do not keep increasing budget because ROAS looks good, and do not treat 120 inbound units as sellable today.
This-week action: Trigger replenishment review today and pause scale tests. Sync low-stock language to page and support, and keep only stable media budget.
Write back: Review write-back: A-07 has 56 sellable units, 14 normal days of cover, below the 18-day lead time. State: replenish + throttle.
Do not treat the color or state as approval. Write the selected case's inventory snapshot, sales-velocity version, lead-time evidence, cash action, and blocked move into the inventory risk and replenishment cadence table. Next week, only a new receipt, corrected Committed count, actual lead-time change, or campaign-cadence change should alter that state.
07 Inventory Demand Board
Put inventory, cash, and demand forecast into one weekly board.
The inventory review is not a stock-count reading. It decides whether this week should scale, cap, replenish, clear out, fix data, or pause. Choose the closest inventory scenario, then write cash signal, demand trigger, blocked move, and next route into copyable lesson notes.
Choose this week’s inventory-demand scenario
Click a card and the right side becomes a cash, demand, and route decision for the weekly inventory review.
Inventory Demand Board
A core SKU below reorder point
Cash signal
Replenishment locks cash, but stockout damages ad learning, repeat rhythm, and hero-page trust.
Demand trigger
Days of cover are below total lead time, and Incoming does not have a confirmed receiving date.
This-week action
Open same-day replenishment review; do not scale new creatives, keep stable budget, and sync low-stock language on page and support.
Blocked move
Do not increase budget because ROAS looks good, and do not wait for stockout before notifying page and support.
Write back to review
Inventory Demand Board: core SKU is below reorder point; this week needs replenishment review, media throttle, and page/support sync.
Tip: when you click “Copy lesson notes” below, this Inventory Demand Board’s cash signal, demand trigger, this-week action, and next route are included automatically.
08 Inventory Pressure Router
Ads and campaigns must pass inventory pressure before scaling.
Inventory planning is not only for purchasing. It tells media, campaigns, pages, and support whether a SKU can scale, how long it can carry demand, and what must change first.
Campaign lifts demand
Surface signal
Ads and email are planned to scale, the campaign page is scheduled, but the inventory sheet only uses the past 30-day average.
Hidden risk
Average daily sales can understate campaign peak demand, causing mid-campaign stockout and breaking ad learning, page promises, and support scripts.
First evidence
Campaign budget, email volume, lift from similar past campaigns, current days of cover, receiving date, and substitute SKU.
Allowed move
Split forecast into normal baseline plus campaign peak. If peak demand crosses the reorder point, downgrade the campaign or prepare substitutes.
Blocked move
Do not scale only because ROAS looks strong, and do not let the campaign page promise demand inventory cannot carry.
Write back to review: Write back: campaign peak is calculated separately; if stock is short, downgrade campaign, throttle ads, and launch substitute SKUs.
Term note: Shopify inventory states can separate Available, Committed, Unavailable, On hand, and Incoming; the weekly review should not rely on one total stock number.
09 SKU Tiers
Different SKUs cannot share the same replenishment rule.
More safety stock is not always better. A core SKUs need protection, C test SKUs need small-batch validation, and D clear-out SKUs should not be replenished.
A core SKU
High sales, strong margin, ads and repeat purchase depend on it.
Higher buffer, lock supply early; throttle media when below lead time.
B profit SKU
Not always top sales, but strong profit contribution.
Stable replenishment; good for bundles, add-ons, repeat offers.
C test SKU
New product, variant, or market test.
Small batch, short cycle; do not overbuy for lower unit cost.
D clear-out SKU
Low turn, weak margin, high refunds, hard to sell.
Stop replenishment, bundle clearance, delist when needed.
10 Stockout Response
Low stock is not one inventory issue. It touches media, pages, support, purchasing, and merchandising.
Pick a state to see entry rule, common mistake, next move, and lesson-note field.
Low stock
Entry
Days of cover approaches lead time or buffer line.
Wrong move
Keep spending and wait until actual stockout.
Next move
Throttle budget, update page note, prepare substitute SKU.
Lesson-note field
Low-stock SKU, days of cover, media action.
Preorder / Backorder release gate
Expected receiving or shipping date
A verifiable date exists and can be stated on the page.
Do not open preorder; use back-in-stock capture or substitute SKU.
Feed availability
preorder / backorder / out_of_stock and availability_date are correct.
Fix feed and landing-page consistency first.
Checkout, support, and payment boundary
Shipping region, cancellation rule, support script, preorder app, and payment method all pass.
Downgrade campaign, pause spend, or switch to a fulfillable SKU.
11 Supplier Lead Time
Do not let MOQ decide your operating rhythm.
Lower unit cost often comes from higher MOQ, but buying too much before validation is risky. Early-stage work needs inventory turn and learning speed more than the lowest purchase price.
Lead Time Variance Ledger
standard lead time
Normal production, freight, customs, 3PL receiving, and put-away days.
Use as reorder-point baseline, not only a supplier promise.
recent actual lead time
Actual lead time and split receipts from the last three batches.
If variance grows, add safety stock for A SKUs and reduce MOQ or split orders for C SKUs.
delay reason
Production queue, freight, customs, receiving, QA, or supplier backlog.
Choose purchasing follow-up, media throttle, page note, or support sync.
11A Variance And Fulfillment Scope
An average is only a starting point; confirm which demand it can still represent before replenishing.
This separates demand variation, service targets, lead-time distribution, 3PL freshness, multi-location scope, bundles, seasonal peaks, preorder, and expiry into reviewable branches. They do not replace the coverage calculation above; they decide whether that calculation fits this SKU, market, and this-week action.
First lock the SKU, market, location, data cutoff, and fulfillable-demand window, then read an average daily rate and standard lead time. Put low/base/high demand, recent actual lead time, the 3PL’s last sync, bundle components, and any applicable expiry window into one record. Safety stock serves an explicit service target and scope, not the instinct that more warehouse stock is always safer. One coverage value, service target, or selected card does not prove live sellability, on-time receipt, or permission to make a customer promise.
The paper's synthetic multi-depot e-grocery allocation simulation points to a possible trade-off: proximity-only allocation can be cheaper while producing lower fill, and combining availability with distance creates different trade-offs among fill, cost, and emissions. State the local objective, constraints, and scope before comparing allocation policies. This is a boundary from scenario simulation, not a policy ranking, a result from real stores or orders, an Ecomwith or Shopify network result, or a local service-cost result, and not a replenishment recommendation.
Choose the most uncertain assumption
This does not score inventory. It decides which evidence comes first this week, which growth action stays frozen, and who receives the copyable review record.
Inventory Assumption Gate
Demand range and service target
A-07 has comparable normal days of 2, 4, and 7 units in the same US market, while its last three order-to-sellable lead times are 16, 18, and 25 days. The review cannot treat “4 units a day, 18 days” as the only fact. It must state which SKU, market, and date window of fulfillable demand the team is trying to protect.
- Evidence first
- Low/base/high daily demand for the same SKU, market, location, and cutoff; the recent actual lead-time range; and the store’s local service target for that scope.
- Allowed move
- Read the reorder point under base and high scenarios, reserving safety stock for higher demand and the long lead-time tail. If the local service target cannot be supported, throttle, stage the campaign, or prepare a substitute instead of merely inflating one average.
- Weekly-review artifact
- SKU / market / cutoff, low-base-high demand, last-three-batch lead time, service target, safety-stock assumption, and this-week action.
- Evidence boundary
- A service target is not a universal 95% rule or a customer shipping promise. It cannot replace live stock, receipt, payment, refund, or fulfillment readback.
This selection is added to the existing copyable lesson notes. Before copying, still fill the store-specific SKU, market, evidence date, owner, and review date below; this classroom record does not persist, export, or change any admin system.
12 Weekly Inventory Review
The weekly review only needs five topics, but every topic needs an owner action.
The value of inventory review is not reading counts. It tells growth which SKUs can scale, which need throttling, and which need substitutes.
Risk list
SKUs at risk in 14 / 30 days.
Growth plan
Next-week ads, email, campaigns, creators.
Replenishment
How many, when to order, when to receive.
Clear-out
Clearance, bundle, no reorder, remove from ads.
Forecast variance
Cause and correction when variance passes threshold.
13 Quick Check
Make one inventory decision before moving on.
An A core SKU has 14 days of cover, total lead time is 18 days, and ROAS still looks good. What should happen now?
Before answering, review the full A-07 chain: 68 - 12 = 56 sellable units, 56 / 4 = 14 normal days of cover, 10 + 6 + 2 = 18 actual lead-time days, and 18 - 14 = 4 days of exposure. The question is not whether ads look good. It is which move will not enlarge the gap this week.
Whatever you choose, turn the answer into a reviewable weekly row: state, owner, evidence date, affected market, media action, page or support action, and next review time. Do not reverse the inventory stop line on one or two days of ROAS or sales without new evidence.
14 Stop / Go
Write when to throttle, replenish, and clear out.
Stop / Go
No inventory cover check before scaling media.
Each promoted SKU has days of cover, reorder point, and risk state.
Stop / Go
A/B/C/D SKUs share one replenishment rule.
Tier maps to buffer, media boundary, and clear-out action.
Stop / Go
Support and pages are notified only after stockout.
Low stock already has page, support, substitute SKU, and purchasing plan.
15 Copyable Lesson Notes
Turn this lesson into copyable weekly inventory notes.
Do not copy stock counts alone. Copy the pressure, first evidence, replenishment boundary, media action, stockout plan, responsible person, and review date.
Weekly inventory review copyable lesson notes
The point is not filling a table. The point is writing a decision the next teammate can review. The common mistake is reading “we still have stock” as “we can keep scaling.” The note must state whether stock is sellable, how long it can carry demand, when the next receipt arrives, whether media or campaigns need throttling, and which move is blocked this week.
Inventory pressure
This is not a stock-count review. It checks whether growth is outrunning sellable stock, inbound stock, and replenishment time.
First evidence
Write Available, Committed, Unavailable, On hand, Incoming, days of cover, reorder point, and total lead time, not only Shopify total stock.
This-week action
The action must be scale, throttle, replenish, small-batch watch, clear out, fix inventory state, or pause promotion. Do not write “keep watching.”
Blocked move
Write what is not allowed this week: scaling below lead-time cover, overbuying from one spike, or reordering just because stock is deep.
Review window
Write the next review date, alert trigger, and who updates page, support, media, and purchasing actions.