Flag slow-moving baby toys by comparing remaining stock age, recent customer sales and stock cover against agreed targets, then check availability before changing the reorder. For baby toy wholesale replenishment planning, low sales alone are not enough: stockouts, blocked listings and existing inbound orders can change the decision. Record one decision per SKU—reorder as planned, reduce, pause or escalate—with the supporting records, responsible approver and review date. Treat unexplained figures as a reason to investigate, not proof of weak demand.
Which stock-age and sales signals should a buyer verify?
Verify the age of units still on hand, the last customer sale, sales within a fixed window, sell-through and stock cover at the same SKU, location and channel scope.
Keep receipt age separate from sales inactivity. A fresh delivery does not make an older remaining lot younger, and a warehouse transfer is not a customer sale. Where physical lot tracking is unavailable, label any receipt-layer calculation as estimated rather than presenting it as observed lot age.
Choose the review window and targets before running the report. Use comparable trading periods for seasonal lines, and identify newly launched items with only a short selling history.
| Remaining-stock age | Check: review date minus receipt date for each remaining lot, retaining its quantity. Owner: inventory analyst, supported by warehouse control. Retain: receipt ledger and remaining-lot allocation. Escalate: older lots exceed the agreed age target or their remaining quantities cannot be reconciled. |
|---|---|
| Days since last customer sale | Check: review date minus the last fulfilled customer-sale date; do not substitute the last transfer, count adjustment or receipt. Owner: sales operations. Retain: dated order-line history. Escalate: inactivity exceeds the agreed limit while the item was available to buy. |
| Units sold in the review window | Check: fulfilled customer units, returned units and net units separately. Owner: inventory analyst. Retain: transaction export with the exact start and end dates. Escalate: zero customer sales despite continuous availability, or returns materially change the apparent sales pattern. |
| Window sell-through | Check: net customer units sold divided by opening sellable units plus sellable receipts during the window, multiplied by 100. Reconcile transfers, adjustments and changes in sellable status before comparing results. Owner: inventory analyst. Retain: opening balance, receipt and sales reconciliation. Escalate: sell-through falls below the agreed target on a comparable basis. |
| Stock cover | Check: uncommitted sellable units on hand divided by the recent daily sales rate. State whether that rate uses calendar days or available-to-buy days. Owner: replenishment planner. Retain: quantity snapshot and calculation. Escalate: cover exceeds the agreed maximum. If the rate is zero or negative, report cover as not calculable and review the sales and returns records. |
| Availability and customer commitments | Check: stockout days, listing blocks, quarantined quantities and units already committed to customers. Owner: channel operations and warehouse control. Retain: daily availability history and allocation records. Escalate: low sales overlap unavailable periods, or system stock was not actually sellable. |
| Confirmed inbound supply | Check: open purchase-order quantities, expected receipt dates and outstanding customer commitments. Owner: purchasing. Retain: current purchase-order and allocation references. Escalate: another order would duplicate supply already due for the same demand period. Show inbound separately; do not treat a future receipt as stock available today. |
Which exception rules should change the reorder decision?
Change the reorder only when a flag has a documented basis: reduce excess supply, pause replenishment for sustained non-movement, or escalate figures distorted by availability or other identifiable conditions.
Set numerical thresholds for your own assortment and review cycle; they are purchasing controls, not universal definitions. For this workflow, call an item slow-moving when sales continue but are weak relative to its stock position. Reserve a dead-stock designation for a separately approved conclusion that further normal sales are not expected. A no-sales window is a flag, not that conclusion.
| Older remaining stock plus weak sell-through | Condition: remaining-lot age exceeds the approved target and sell-through is below target. Evidence: receipt layers, remaining quantities, sales reconciliation and availability history. Decision: reduce the planned reorder only if a smaller quantity is justified; pause it when existing supply already exceeds the approved cover ceiling. |
|---|---|
| No customer sales despite continuous availability | Condition: sellable stock was available throughout the agreed window but no fulfilled customer sales occurred. Evidence: order history, listing availability and sellable-stock records. Decision: pause routine replenishment and route any request to reorder to the category manager for a dated exception. |
| Cover above the approved maximum | Condition: on-hand cover exceeds the ceiling, or confirmed inbound supply would create excess within the relevant planning period. Evidence: cover calculation, open purchase orders and customer allocations. Decision: reduce or pause the new order; review existing inbound commitments separately rather than assuming they can be canceled. |
| Stockout or listing interruption | Condition: low calendar-window sales overlap days when customers could not buy the item. Evidence: daily stock and listing-status history. Decision: suspend the slow-mover classification and escalate for an availability-adjusted review. An available-day sales rate is an observation, not a guaranteed forecast of lost sales. |
| Seasonal, launch or confirmed-order exception | Condition: the ordinary window does not represent the intended selling period, or a confirmed customer order supports additional supply. Evidence: comparable seasonal history, launch date or the customer order with quantity and required date. Decision: approve only the supported quantity, record the reason, and set a review date. A planned promotion alone is not confirmed demand. |
| Unreconciled balances or unusual returns | Condition: receipts, sales and remaining stock do not reconcile, or net sales conceal substantial sales and returns. Evidence: movement ledger, return transactions and count investigation. Decision: hold automated quantity changes until the responsible owner resolves the discrepancy or an approver documents an interim decision. |
How does the checklist distinguish a slow mover from a false flag?
The worked comparison below pauses replenishment for genuine excess, separates a no-sales item for review, and prevents a stockout-constrained item from being labeled slow-moving.
All inputs, thresholds, identifiers and decisions in this example are hypothetical. The review covers September 28–October 27, 2026, inclusive: 30 calendar days. Each item has no receipts, returns, transfers, customer allocations or confirmed inbound supply during the example. These are demonstration records, not catalog products.
Illustrative policy revision 1 flags remaining stock older than 90 days, sell-through below 25%, or on-hand cover above 60 days. Zero sales triggers a pause only after continuous availability is confirmed. Two or more supported flags require category-manager approval. These thresholds are proposed buyer criteria, not industry standards.
| Demo item A — excess stock with continuing sales | Observed: opening stock 120 units; net sales 12; ending sellable stock 108; available 30 days; oldest remaining lot 150 days; last customer sale 3 days ago. Calculations: sell-through 12 ÷ 120 = 10%; daily rate 12 ÷ 30 = 0.4 unit; on-hand cover 108 ÷ 0.4 = 270 days. Flags: age, sell-through and cover. Exception applied: none. Decision: pause the new reorder and escalate the multiple flags. Owner: category buyer; approved by category manager on October 27, 2026. Evidence: DEMO-A receipt, sales, availability and stock exports. Follow-up: buyer to confirm the purchase-order hold by October 28; closure requires the dated order-system reference. |
|---|---|
| Demo item B — low calendar sales distorted by stockouts | Observed: opening stock 30 units; net sales 24; ending sellable stock 6; available 6 days and unavailable 24 days; oldest remaining lot 60 days; last customer sale 1 day ago. Calculations: sell-through 24 ÷ 30 = 80%; calendar-day rate 0.8 unit; available-day rate 4 units; cover using the available-day rate 6 ÷ 4 = 1.5 days. Exception applied: interrupted availability. Decision: do not classify as slow-moving; escalate the replenishment quantity for a separate demand review rather than approving it automatically. Owner: replenishment planner; review approved by category manager on October 27, 2026. Evidence: DEMO-B daily availability and transaction exports. Follow-up: quantity review due October 28; close with the approved quantity and order reference. |
| Demo item C — no sales while continuously available | Observed: opening and ending sellable stock 60 units; customer sales 0; available 30 days; oldest remaining lot 180 days; last customer sale 75 days ago. Calculations: sell-through 0%; daily rate 0; cover not calculable because the sales-rate denominator is zero. Flags: age, sell-through and no sales with availability. Exception applied: none. Decision: pause replenishment and review whether the item should retain a normal replenishment status; do not automatically label it dead stock. Owner: category buyer; approved by category manager on October 27, 2026. Evidence: DEMO-C lot, sales and availability exports. Follow-up: status review due October 30; close with the dated status decision and confirmation that the reorder rule was updated. |
What must each SKU decision record contain?
Keep one decision row per SKU, with the policy target beside the observed result and linked records that let another buyer reconstruct the decision.
Map the functional owners below to named people in your team. If the same person prepares and approves a decision, record that explicitly rather than implying an independent review.
| Identity and revision | Record SKU and variant, warehouse or channel, review cutoff, reporting window, checklist revision and threshold-policy revision. Owner: inventory analyst. Retain the source export timestamp so a later stock movement does not silently change the reviewed figures. |
|---|---|
| Targets versus observations | Store agreed age, inactivity, sell-through and cover targets beside the actual values, including remaining quantities by age, availability days and confirmed inbound quantities and dates. Owner: inventory analyst. Link receipt, sales, stock, availability and purchase-order records. |
| Rule, exception and quantity decision | Record every triggered rule, the exception applied, its evidence reference, the original planned quantity, the approved quantity and the reason for the change or override. Owner: category buyer. Keep unconfirmed explanations separate from established observations. |
| Approval and conditions | Enter the responsible approver's name, role and decision date, plus any condition that must be satisfied before order release. Owner: category manager or delegated approver. Retain the approval reference; a narrative note without a decision is not a completed approval. |
| Follow-up and closure | Assign a named action owner and due date. Close only after the approved quantity, purchase-order hold or replenishment setting is updated and its reference and completion date are recorded. An approved exception with an unmet release condition remains open. |
When should a flagged SKU be escalated?
Escalate when several supported flags coincide, the evidence is disputed, or the proposed action exceeds the buyer's delegated authority.
A practical approval policy can require category-manager review for two or more flags, disagreement between the analyst and buyer, or a quantity change above a company-set percentage or value limit. Reordering an item paused for no sales should also require a documented exception. Agree those limits before the review, not after seeing which order they affect.
While a case is open, state exactly what is held: the new purchase order, its release, or an automated replenishment change. Do not imply that an internal reorder hold cancels an existing supplier commitment. Close the escalation with a dated decision, any release conditions, the updated order reference and confirmation by the assigned action owner.
What does a slow-mover flag not establish?
A slow-mover flag identifies a stock-and-sales pattern; it does not establish its cause, future demand or product suitability.
Seasonality, limited selling history, a blocked listing or a genuine demand change can produce similar figures. Even an availability-adjusted rate can be distorted by promotions or a small number of selling days. Use the flag to decide what needs review, not to claim that the calculation has explained demand.
Stock age is not a product expiry date, and this checklist does not verify safety, infant suitability or destination-market compliance. Confirm SKU-specific age and intended-use evidence separately; a baby-toy category label, material name or image is not that evidence.
The retained record supports traceability of the reorder decision. It does not, by itself, establish that every underlying transaction or subsequent product change has been captured.