Skip to content
Ecomwith

Inventory and Demand Planning: Replenish, Throttle, or Pause a SKU

  • Intermediate
  • 70 minutes

Start with one SKU, market, and dated inventory snapshot; decide whether to replenish, throttle, clear, or pause only after calculating how long that stock can support demand. This practice case uses the A-07 pet car mat: 68 units Available at 4 normal sales per day provide about 17 days of cover. Recent total lead time is 18 days, and the working reorder point is 112 units. The exercise shows how to reconcile evidence; it does not report a live store's stock or demand.

Set one SKU, market, and inventory cut-off

An inventory review asks whether growth can be fulfilled. Too little stock can disrupt ads, search landing pages, repeat purchases, and support at once. Too much can tie up cash, warehouse space, and budget for the next test. Give every priority SKU a decision for this week: keep promoting, throttle, replenish, substitute, clear, or pause.

Put the SKU, target market, stock location, snapshot cut-off, and demand window on one row. Then add normal and campaign sales, supplier lead time, confirmed inbound stock, cash payment dates, and the customer-facing promise. A quantity assembled from different dates, markets, or locations cannot approve an ad budget or a delivery date.

For a small catalog, review every core SKU and every product receiving traffic. With a larger catalog, sample by risk: A-tier core items, campaign products, slow-moving deep stock, market/location mismatches, and products with high refunds or support volume. Record each sample boundary so the team does not inspect only the most visible items each week.

Four terms to settle before reading the sheet

  • Safety stock is a buffer for demand variation and supply delay; set it for the SKU, market, and service goal at hand.
  • Inventory turnover describes how quickly stock becomes cash. Slow sales tie up cash; selling too quickly can leave a gap before replenishment arrives.
  • Demand planning separates historical sales, ads, campaigns, seasonality, and supply capacity.
  • Stockout risk can cost more than the missed order: it can also interrupt ad learning, organic-search demand, repeat purchases, and support promises.

Separate inventory states before calculating cover

Do not combine On hand, Available, Committed, Unavailable, and Incoming from the same snapshot into one total. Confirm the starting field before calculating cover. Until Incoming is received and put away, it should not count as today's sellable quantity or support a ship-now promise.

Inventory states and starting field

  • On hand

    Meaning in the review
    Physical stock at one location; it is not the same as sellable stock.
    Check to make
    Use as context; if starting here, subtract occupied and temporarily unsellable units once.
  • Available

    Meaning in the review
    Units currently available to sell, with Committed, Unavailable, and Incoming excluded.
    Check to make
    Use directly for cover; separately check whether the location can serve the target market.
  • Committed

    Meaning in the review
    Units already reserved by orders or another use.
    Check to make
    Keep for reconciliation; do not subtract them from Available again.
  • Unavailable

    Meaning in the review
    Stock at the warehouse held for QA, damage, reservation, or an app hold.
    Check to make
    Find the reason, then decide whether to release, isolate, or correct the rule.
  • Incoming

    Meaning in the review
    Transfer or purchase stock not yet received.
    Check to make
    Use to forecast arrival and a future gap, not to promise immediate fulfillment.

The A-07 practice snapshot labels 68 units Available and lists another 12 as Committed; those reserved units are already excluded from sellable stock. If an earlier worksheet treats 68 as total stock and subtracts 12, it gets 56 units and 14 days of cover, 4 days short of the 18-day lead time. That calculation is valid only when starting from On hand that still includes the reservation. Here 68 is already Available, so subtracting again double-counts it. Check the field definition before choosing a result.

Playable chart

When one order comes in, which of the five inventory states move?

As text: the whole walk-through
  1. Order in One order comes in: Available drops by 12 and Committed rises by 12, while On hand does not move because the goods are still in the building, just spoken for.
  2. Shipped The order ships: Committed and On hand both drop by 12 and Available stays put, because those 12 were already deducted when the order came in.
  3. On hold QC puts 20 units on hold: Available loses 20 and Unavailable gains 20, On hand is unchanged. The goods are here but cannot be sold for now.
  4. Order in One order comes in: Available drops by 12 and Committed rises by 12, while On hand does not move because the goods are still in the building, just spoken for.
  5. Received Only when the 120 units on the way are received and shelved do they enter On hand and Available together, and Incoming goes to zero.
  6. Released The cause is found and the hold is released: the 20 units go from Unavailable back to Available, and On hand still does not change.
  7. Cover read The sellable cover reads Available only: no second deduction of Committed and no Incoming added in.

Illustrative: only Available 68, Committed 12, Incoming 120 and 4 sales a day come from the A-07 case.

Watch three things: the On hand bar at the top keeps its length when an order comes in and only its segments shift, and it grows or shrinks only on shipping and receiving; the same units cross between Available and Committed only once; and the two wrong readings on the right, one subtracting Committed again and one adding Incoming that is not on the shelf.

The review must also check whether the location serves the target market. Available at one warehouse does not prove that every Canadian, EU, or bundle order can be fulfilled. Keep Committed visible for reconciliation, but do not let it reduce sellable stock twice.

Calculate cover and A-07's one-day gap

Calculate cover from Available at one cut-off divided by daily sales, then round down to count only complete selling days. Normal daily sales should exclude stockouts and one-off campaigns; campaign sales belong in a separate scenario. Recent actual lead time includes production, freight, customs, receiving, and put-away. Safety stock is a buffer chosen for this SKU by the store.

In the May 2026 practice snapshot, A-07 has 68 sellable units and normal sales of 4 per day: 68 ÷ 4 = 17 days. Recent receiving records show total lead time of 18 days, a difference of 1 day. That is a prompt to throttle and verify replenishment; it does not establish the day the product will run out.

This case assumes 40 units of safety stock. The reorder point is normal daily sales × total lead time + safety stock: 4 × 18 + 40 = 112 units. Current stock is 44 units below that local review point. The gap triggers a replenishment review; it does not mean that the store should buy exactly that many units. Quantity also depends on inbound status, minimum order quantity, cash, forecast error, and the next receiving date.

If the snapshot starts from On hand, first reconcile occupied orders and holds. The 120 units here are not yet received, so they cannot be counted as sellable today or used to promise a customer shipment. Good ad ROAS does not cancel stock evidence.

Owners and stop lines

  • Operations keeps the reconciliation date for Available, Committed, holds, and location eligibility.
  • Supply chain attaches actual lead times from recent batches, the next receiving date, and split-delivery risk.
  • The ad owner pauses new scaling tests; keep only approved steady spend that remains within the inventory boundary.
  • Product pages and support use a shipping promise supported by receiving evidence; if the date is unreliable, offer a substitute or back-in-stock notice.
  • Finance checks whether deposits and balances crowd out approved creative, ad, or core-SKU cash.

Keep a small, steady campaign only when the next batch has a dated receiving path, the page promise is accurate, and the purchase fits the agreed contribution-margin and cash limits. Keep throttling while lead time is uncertain. Pause the affected market or campaign if sellable stock, location, or receipt date cannot be reconciled. Preorder is not an automatic fix: without an owner in support, a checkable ship date, and a real fulfillment path, do not transfer uncertainty to customers.

Reconcile evidence from three places

Evidence sourceWhat to checkDecision it can supportFirst action when it disagrees
Shopify Products / Inventory / LocationsAvailable, Committed, Unavailable, On hand, Incoming, location and market eligibility, and bundle reservationsHow much stock can really be fulfilled nowCorrect the location, market, shipping profile, or app hold; do not scale before totals reconcile
Purchase sheet or purchase orderOrdered quantity, purchase cost, MOQ, deposit/balance dates, estimated warehouse date, and 3PL receiving/put-away dateWhether future stock can support this week's planIf arrival timing is uncertain, record it, throttle, and use a back-in-stock notice or substitute
Supplier lead-time recordActual production, transit, customs, and receiving dates for recent batches; delay reasons, MOQ, and small-batch capacityWhether reorder point and safety stock use actual lead timeRevisit buffers for A-tier SKUs; split C-tier tests or lower quantities and reschedule campaigns

Record one location and one snapshot time per count. Review every SKU in a small catalog; for a larger catalog, sample by risk and include core, campaign, slow-moving deep stock, market/location mismatch, and products with refund or support issues.

Forecast demand the store can fulfill

Sales over the last 30 days are not a plan for the next period. Store demand changes with ad budgets, creative fatigue, promotions, seasonality, SEO rank, email, creator content, and stockout history. Separate five layers before deciding whether inventory and cash can support them:

Forecast layerWhat to reviewNext owner
Normal baselineNormal-day sales across 7 / 14 / 60 days; remove stockouts and unusual campaignsOperations updates forecast error weekly
Campaign peakPromotions, gifting periods, creator partnerships, email timing, and content spikesCampaign owner reserves peak stock and a substitute SKU
Traffic planAd budget, SEO page changes, email, and social schedule; doubling budget does not justify a static sales forecastOperations and media review plan changes together
Supply constraintsProduction, freight, customs, receiving, MOQ, and confirmed inbound stockSupply chain records the latest safe order date
Cash pressureTurnover after replenishment, clearance risk, and cash needed for ads and creativeFinance or growth approves large purchase commitments

A practice forecast can be written as baseline daily sales × forecast days × traffic adjustment × seasonal/campaign factor. A starting replenishment estimate is forecast demand + safety stock − current sellable stock − confirmed inbound stock. Both are weekly-review aids, not automatic instructions; give every factor a date and version and compare it with actual sales. Keep campaign peaks out of the normal baseline, and do not count unreceived Incoming as current sellable stock.

Related retail forecasting research discusses multi-week forecasts around high-risk sales periods. This lesson borrows only the practice of reviewing the normal baseline, campaign peak, supply constraints, and cash pressure separately. The paper does not establish this store's demand, stock, reorder point, or ad outcome. Read the cited arXiv study.

Set a reorder point and track forecast error

A reorder point triggers a review; it is not an automatic purchase instruction. The basic formula is average daily sales × total lead-time days + safety stock. This practice case starts with a 10-day buffer and reviews a range of 7 to 21 days. Set the buffer against supply stability, sales variation, and the local service goal; the goal is not a universal 95% shipping guarantee.

A useful forecast-error ledger keeps at least these fields:

FieldWhat to write this weekHow to use it next week
Forecast version/dateThe forecast version and date used this weekReconstruct why the order was placed
Expected normal daily salesExpected daily sales after removing stockouts, unusual discounts, and one-off spikesSet the next normal baseline without campaign peaks
Actual normal daily salesActual normal daily sales this weekCompare with the estimate and decide whether to adjust factors
Variance % / reason tagVariance and tags such as stockout, promo, creator spike, ad budget, seasonality, page issue, or feed mismatchIf it exceeds the store's threshold for 2 consecutive weeks, reset the baseline, media boundary, or reorder point
Next correctionA factor, quantity, campaign pace, or ad cap to change next weekLeave a checkable correction instead of an after-meeting hunch

For A-07, 4 daily units × 18 lead-time days + 40 safety units gives a 112-unit reorder point. B-12 uses 12 daily units, 21 lead-time days, and 60 units of buffer for a 312-unit point. D-03 uses 3 × 14 + 20 = 62 units. These are case assumptions; recalculate when demand, lead time, location, or cash changes.

Daily alerts watch low stock, unusual sales, and stockouts. At the start of each week, review baseline sales, lead time, safety stock, and MOQ. Before a campaign, calculate peak cover, warehouse capacity, and delivery timing separately. Assign an owner and next review date to each. For this practice case, recalculate after forecast error exceeds 25% for two weeks; synchronize ads, pages, and support if supplier delay exceeds 3 days; and alert when A-tier buffer falls below 10 days. Check these working thresholds against store data.

Choose the weekly action that fits the case

An inventory sheet is a fulfillment plan, not a screenshot of back-office figures. Work through four steps: distinguish On hand from sellable stock; reconcile committed, unavailable, inbound, lead time, safety stock, reorder point, and cover; classify the SKU; then write ads, purchasing, page/support, and a review date into the weekly record.

Use the A-07 core item, C-tier test, D-tier slow mover, and Canadian market/location mismatch to choose a weekly action. Changing the case clears the previous action; without a choice, there is no conclusion. The safe action must fit the active case. Selecting something that sounds positive must not show a pass by itself.

LensQuestion to answer firstWhat it prevents
WhatWhat can the inventory table tell media, page, support, purchasing, and merchandising about which growth moves can continue, for how long, and when to replenish or exit?Treating stock as a back-office screenshot
WhyHow do committed orders, location limits, inbound stock, unavailable units, and bundle reservations change the amount that can really be fulfilled?A healthy-looking total that cannot support the page promise
HowSeparate sellable, committed, inbound, lead time, safety stock, reorder point, and cover before choosing the weekly action.Scaling before stock and lead time reconcile
PracticeDoes the weekly row name the SKU tier, first evidence, risk state, media/purchasing/page/support actions, and review date?Leaving only “keep watching” with no owner or next step
Exercise · pick oneCheckpoint

Inventory replenishment decision practice

① Choose the situation
② What would you do

This choice is wrong in all four cases; do not treat it as an ordinary near-miss.

The pet car mat sells 4 units per normal day. Total lead time is 18 days, safety stock is 40, and only 68 units are Available; ad ROAS still looks good.

First evidence
Reorder point = 4 × 18 + 40 = 112 units. 68 is below the point; 17 days of cover is shorter than the 18-day lead time.

Each safe action has one matching case: same-day review for A-07; small-batch validation for the C-tier content spike; stop reordering and clear D-03; or repair inventory/location rules for the market mismatch. The "keep scaling" option matches none of them. Other pairings should remain unmatched; an action's generic positive explanation must not turn the active case into a pass.

Compare cover, inbound stock, and actions across three SKUs

These cases use the same inventory definitions. Calculate current cover from Available, retain Committed for reconciliation, and list Incoming separately. Campaign sales belong in campaign cover; still verify arrival, cash, substitutes, and page promises before acting.

Exercise · pick one

Choose a cover case

ROAS is acceptable and the team wants to increase budget, but sellable stock is below the reorder point.

Cover calculation
68 ÷ 4 = 17 normal days, below the 18-day total lead time; campaign cover at 7 units a day is 9 days.
Reorder point and inbound
The reorder point is 112 units. The 12 committed units are already excluded from Available; another 120 units are inbound but not received.
This week's action
Open a replenishment review today and pause scaling tests; align low-stock wording on the page and with support, and keep only steady ad spend.
Blocked move
Do not raise budget because ROAS looks acceptable, and do not treat inbound units as sellable today.
Weekly write-back
A-07 has 68 available, 17 normal days of cover, below the 18-day lead time; state: replenish + throttle.

Fields to write into the same weekly row

FieldWhat to record this weekOwner
SKU tierA core, B profit, C test, or D clearanceMerchandising and operations
Available / committed / inboundShopify state, purchase order, and shipment detailsOperations
Normal daily salesRemove stockouts, unusual discounts, and one-off spikesOperations, weekly
Total lead time and reorder pointProduction, freight, customs, receiving; average daily sales × lead time + safety stockSupply chain and operations
Media boundaryDays of cover, replenishment cycle, campaign plan, and substitute SKUMedia owner
Risk statePromote, observe, throttle, replenish, clear, or pauseBusiness owner

If error exceeds the store's threshold for two weeks in a row, recalculate the normal baseline. Recalculate the reorder point when supplier lead time changes. Do not increase spend when cover is shorter than replenishment time. Record this week's action; do not leave the meeting with “keep watching” as the only decision.

Test four assumptions behind a replenishment decision

Average daily sales and a standard lead time are only starting points. Name the SKU, market, location, cut-off, and fulfillable demand window; then put low/base/high demand, recent actual lead time, the 3PL's last-sync time, bundle components, and any relevant expiry window in one record. A cover number or selected card does not prove stock is sellable, a shipment is on time, or a customer promise is allowed.

Exercise · pick one

Choose the least certain inventory assumption

Comparable normal-day A-07 sales in the same U.S. market are low/base/high practice values of two, four, and seven units per day across a 7-day window. The last three order-to-available lead times were 16, 18, and 25 days. Do not record “four daily, 18 days” as the only truth.

Check first
Low/base/high sales for the same SKU, market, location, and cut-off; actual lead-time range from recent batches; and the store's chosen service goal.
Allowed action
Use the baseline and high-demand case to inspect the reorder point; reserve safety stock for high demand and the long end of lead time. If the local service goal cannot be met, throttle, split the campaign, or prepare a substitute instead of merely increasing an average.
Weekly artifact
SKU, market, cut-off, low/base/high demand, last three lead times, service goal, safety-stock assumption, and this week's action.
Evidence boundary
A local service goal is not a universal 95% rule or a customer shipping promise; read back real stock, receipts, payment, returns, and fulfillment state.

Synthetic multi-location e-grocery allocation research illustrates a trade-off: prioritizing distance may lower cost while reducing availability/fill, and considering both can change the trade-off among fill rate, cost, and emissions. It is not a policy ranking, real store/order result, Ecomwith or Shopify network result, or evidence of local service cost or a replenishment recommendation. State the local goal, constraints, and scope before comparing options. Read the cited study.

Route inventory pressure before growth outruns supply

Choose the closest pressure case and check its surface signal, hidden risk, first evidence, allowed action, blocked move, and weekly write-back. Inventory planning coordinates purchasing, ads, campaigns, pages, and support.

Exercise · pick one

Choose this week's inventory pressure

Ads and email are set to ramp and the campaign page is scheduled, but the inventory sheet uses only the last 30-day average.

Hidden risk
An average understates the peak; stock can run out midway through the campaign, disrupting ad learning, the page promise, and support wording.
First evidence
Campaign budget, email volume, uplift from comparable campaigns, current days of cover, next receipt date, and a substitute SKU.
Allowed move
Separate the normal baseline from the campaign peak. If peak demand may cross the reorder point, scale down the campaign or prepare a substitute first.
Blocked move
Do not scale only because ROAS looks good or let the campaign page promise demand the inventory cannot fulfill.
Weekly write-back
Calculate the campaign peak separately; if stock is insufficient, downgrade the campaign, throttle ads, and launch the substitute path together.

Plan for low-stock, stockout, and preorder promises

StateEntry conditionCommon mistakeNext step
Low stockAvailable days approach total lead time or the local buffer lineKeep advertising and wait for an actual stockoutThrottle budget, update the page notice, and prepare a substitute SKU
Temporary stockoutMain SKU is unavailable, but replenishment timing can be verifiedLet customers discover the problem at checkoutOffer a back-in-stock notice, keep the SEO page, and recommend an alternative
PreorderSupply is credible and ship timing plus cancellation terms are clearTreat preorder as a universal fallbackState ship date and cancellation terms, explain delay handling, and provide a support route
Delist / clearanceLong supply gap, low margin, high service risk, or weak turnoverKeep ordering to lower unit costStop ads, exit low-value variants, clear stock, or move to an alternative collection page

Each state needs a different follow-up and weekly output. Choose the current state, then check its entry condition, common mistake, and next move; selection alone does not release a preorder or purchase.

Exercise · pick one

Choose the customer-promise state

Entry condition
Days of cover approach total lead time or the safety-buffer line.
Common mistake
Keep spending and wait until actual stockout.
Next move
Throttle budget, update the page notice, and prepare a substitute SKU.
Weekly row
Low-stock SKU, days of cover, and media action.

Before releasing a preorder or stockout path, check each gate:

GatePass conditionIf it fails
Expected receipt or ship dateA verifiable date can be stated clearly on the pageDo not open preorder; use a back-in-stock notice or substitute
Feed availabilitypreorder / backorder / out_of_stock and availability_date match the pageFix the feed and landing page before resuming ads
Checkout and delivery areaThe market is serviceable, and timing matches the promiseFreeze scaling in that market; correct shipping profile and page wording
Support and cancellation rulesSupport can explain timing, cancellation/refund, substitutes, and delay handlingKeep only a back-in-stock notice; do not turn an unready plan into preorder
Payment and preorder-app boundaryPayment method, app, store, and customer-location rules permit itDowngrade the campaign, pause ads, or switch to an SKU that can be fulfilled

When stockout risk appears, reduce or pause spend on that SKU and move budget toward an alternative. Update stock, back-in-stock, and delivery notes on the page. Give support one account of replenishment timing, cancellation, exchange, and compensation. Purchasing verifies supplier lead time, inbound state, and the next receipt plan. Preorder cannot replace those owners and evidence.

Supplier review should also record lead-time stability, small-batch capacity, batch quality, ability to scale, and backup supply. A lower unit cost that requires a larger MOQ may tie up cash; for an unvalidated new item, protect small-batch learning and replenishment flexibility.

Keep a lead-time-variation log with standard lead time, recent actual lead time for the last three batches and split deliveries, delay reason (production scheduling, transit, customs, receiving, QA, or supplier queue), and buffer decision (safety stock, latest safe order date, or backup supply). If variation rises, revisit the A-tier buffer and reduce or split C-tier MOQ. Decide whether to expedite purchasing, throttle ads, update the page, or notify support.

Set a weekly inventory review cadence

The team does not need a meeting every day, but sales, media, support, purchasing, and finance need a regular place to compare notes. At the start of the week, review SKUs at risk of stockout in 14 / 30 days and items with long turnover. Check next week's ads, email, creator activity, promotions, and new-product plan. Confirm quantities, supplier, expected receipt, and cash impact. Choose clearance, bundle, stop-reorder, or removal from ads. Then review why the forecast differed.

At minimum, the weekly inventory table includes SKU, variant, supplier, purchase cost, weight/volume, fragile or special shipping; available, committed, inbound, reserved, and stockout days; normal sales over 7 / 14 / 30 days and campaign sales; production, transit, receiving, and MOQ; margin, refund rate, ad spend, conversion, repeat purchase, and turnover days.

Data groupMinimum fieldsRisk when missing
SKU basicsProduct, variant, supplier, purchase cost, weight, volume, fragile or special handlingReorder quantity becomes a guess without cost or fulfillment boundaries
Inventory stateSellable, committed, inbound, reserved, and stockout daysAdmin stock can overstate real fulfillment capacity
Sales velocitySeven-, 14-, and 30-day average sales, separated into normal and campaign daysStockouts, discounts, and spikes can pollute the forecast
Supply parametersProduction, freight, customs, receiving, MOQ, and supplier-delay recordMedia and campaigns can run ahead of supply
Operating metricsMargin, refund rate, ad spend, conversion, repeat purchase, and turnover daysWeak SKUs can be replenished like core items

Weekly indicators include days of cover, stockout risk before the next receipt, cash tied up in stock, slow movers older than 90 days, and reasons when variance exceeds the local 20% line. The monthly SKU review also identifies products with the largest sales and margin contribution, repeat stockouts, stock that ties up cash without strategic value, low-selling variants, and high-refund items. Use A/B/C/D tiers; do not apply a bestseller's replenishment rule to every SKU.

SKU tiers and daily, weekly, and pre-campaign checks

TierTypical caseInventory action
A core SKUHigh sales and margin; ads or repeat purchase depend on itReserve supply early; throttle spend when cover falls below lead time
B profit SKUMay sell less but contributes good marginMaintain steady supply; consider bundles, add-ons, and repeat-customer offers
C test SKUNew item, variant, or marketBuy small and review quickly; do not buy deep just to get a lower unit price
D clearance SKUSlow turnover, low margin, high returns, or hard to sellStop ordering, bundle or clear, and delist if needed

Daily alerts cover low stock, unusual sales, and stockouts. The weekly replenishment review resets baseline sales, lead time, safety stock, and MOQ. A pre-campaign review calculates peak cover, capacity, and shipping separately and states the product scope and release boundary. Each review has its own owner and date; do not combine them into one “inventory is fine” conclusion.

What you finished

No checkpoint finished in this lesson yet. Start with “Go to the exercise”.

Self-check not answered

Write this week's decision into the inventory review

The inventory demand board puts three things on one row: how long stock can fulfill demand, how much cash replenishment or clearance uses, and whether next week's ads, email, creators, or campaign add demand. Select a case and check its cash signal, demand trigger, action, blocked move, and next route.

Exercise · pick one

Choose this week's inventory demand case

Is the SKU core to advertising, repeat purchase, or the hero page, or is it a long-tail item that can temporarily be out of stock?

Cash signal
Replenishment uses cash, but a stockout damages ad learning, repeat-purchase rhythm, and hero-page trust.
Demand trigger
Available days are below total lead time and Incoming has no confirmed receiving date.
This week's action
Open a replenishment review today; do not scale new creative. Keep steady spend and align low-stock language on the page and with support.
Blocked move
Do not increase budget because ROAS looks good or wait for stockout before telling the page and support teams.
Inventory review line
Core SKU below reorder point: review replenishment, throttle ads, and align page and support this week.

Cash fields for replenishment

PO payment date records deposits, balances, and due dates. Expected receiving date records arrival at the warehouse, 3PL receipt, and put-away. Shopify payout delay captures the payment cycle, reserve, or processor delay. Campaign spend before receipt records ad, email, and creator budget before stock arrives. Inventory aging bucket / clearance floor groups stock into 0–30, 31–60, 61–90, and 90+ days and records a break-even or controlled-loss floor. Together these fields show whether replenishment would crowd out creative, ads, or the next test.

Open the inventory review record to carry the current pressure, first evidence, cover calculation, inventory assumption, cash signal, demand trigger, allowed and blocked actions, and next route together. Enter the store's SKU, reorder boundary, cash and preorder limits, media/campaign action, cross-team owners, and review date/stop line. Make the row challengeable by the next teammate: what is the evidence date, who updates it, and what proof allows activity to resume?

Before copying the review

  • The snapshot, market, location, and cut-off match; Available and Committed are not counted twice.
  • Lead time comes from recent receiving records, Incoming has a dated receipt, and bundle scope and 3PL freshness can be checked.
  • Owners, action, stop line, review date, and evidence needed to resume are written down.
  • Without these fields, exercise feedback does not authorize an order, ad scale-up, or preorder.
Decision · 1 question0/1 answered

What should A-07 do now?

An A-tier core SKU has 17 days of cover, an 18-day total lead time, and good ROAS. What should the team do first?

Self-check not answered

Whatever the answer, write the state, owner, evidence date, affected market, ad action, page/support action, and next review date in one row. Do not drop an inventory stop line because ROAS or sales moved for a day or two without new evidence.

Stop lines and release conditions for this week's inventory action

Stop hereGo
Ads scale before anyone checks inventory cover.
Each priority SKU has sellable days, a reorder point, and a risk state.
Evidence
Shopify states, recent lead time, next receipt date, owner, and next review date reconcile to one snapshot.
A/B/C/D SKUs all use the same replenishment rule.
SKU tier sets the safety buffer, media boundary, and clearance action.
Evidence
Each priority SKU has an action word, owner, and evidence that can be checked at the weekly review.
Support and the page are told only after stockout; preorder lacks a real date or cancellation plan.
Low-stock work already has a page update, support wording, substitute, and purchasing plan.
Evidence
The page's sellable scope, delivery promise, support wording, and receiving plan use the same verified stock state.

Use current evidence to decide which core products can keep selling, which tests should stay small, which slow movers should exit, and whether supply can support the plan.

Frequently asked questions

If Available is 68 units, why not subtract 12 Committed units?

This A-07 snapshot records 68 as Available; the 12 Committed units have already been excluded. Subtracting them again understates cover at 14 days. Subtract the matching reservations only when starting with On hand that still includes them.

Do 17 days of cover and a 112-unit reorder point mean we should place an order now?

They call for a review, not an automatic order. Seventeen days is one day shorter than this case's 18-day total lead time, and 112 uses four daily units, 18 lead-time days, and 40 safety units. Quantity still depends on the next receipt date, MOQ, cash, and forecast error.

Why throttle a campaign if normal inventory cover looks acceptable?

Normal and campaign sales use different rates. B-12 covers 19 days at 12 units a day, but only eight days at the campaign rate of 28. If the peak crosses the lead-time window, stage the release, cap daily sales, or prepare a substitute.

Can inbound stock count toward today's available cover?

No. Record expected receipt and put-away dates for Incoming and use them to review a future gap. Until receipt, it is not sellable today and cannot support a ship-now promise.

When can the store offer preorder?

Verify the receipt/ship date, market delivery, feed availability, payment and preorder-app conditions, cancellation/refund path, support owner, and bundle components first. If any is unclear, use a back-in-stock notice, substitute, reduced campaign, or pause.

When multi-location or 3PL counts disagree, which number should be repaired first?

First align one location's snapshot time and time zone, stock states, and bundle components; then check market eligibility. Do not add partial counts from different locations or keep feed, page, ads, and support repeating an unverified promise.

Continue from the inventory pressure

Align stock state and the owner first, then follow the issue in front of the team:

Edition notes

  • Author Ranfeng Wei
  • Published
  • Updated
  • Reviewed
  • Next review

This update: Updated the lesson layout.