A weekly routine for dead stock markdown review

Last updated: 2026-07-31

Written and reviewed by Seller Profit Guard Editorial Team.

A weekly markdown routine should reconcile aging inventory, select a bounded SKU-location cohort, refresh price and sell-through evidence, update costs and disposal options, run moderate and clearance sensitivity, record approval or hold, monitor any active markdown, and preserve rollback. It should not automatically change prices, publish offers, or dispose of inventory.

weekly markdown operating packet from aged inventory and markdown inputs through expected recovery, review, and restoration — This original diagram explains a repeatable review cadence with synthetic inventory data.

Monday aging triage

Refresh age buckets, last receipt, on-hand quantity, condition, commitments, and value. The weekly markdown operating packet records the exact source, definition, period, unit, currency, transformation, timestamp, owner, reviewer, exception, and prior accepted value needed for a repeatable review cadence.

Do not use stale exports. At checkpoint 1, reperform the affected Scenario A and Scenario B terms, identify the input that changes expected recovery, and state the operational, accounting, tax, policy, or privacy conclusion that remains outside the calculator.

Tuesday cohort selection

Choose a bounded SKU-location group with one commercial reason for review. The weekly markdown operating packet records the exact source, definition, period, unit, currency, transformation, timestamp, owner, reviewer, exception, and prior accepted value needed for a repeatable review cadence.

Avoid catalog-wide automation. At checkpoint 2, reperform the affected Scenario A and Scenario B terms, identify the input that changes expected recovery, and state the operational, accounting, tax, policy, or privacy conclusion that remains outside the calculator.

Wednesday evidence refresh

Reconcile price, sell-through definition, fee rules, fulfillment, storage, and disposal quotes. The weekly markdown operating packet records the exact source, definition, period, unit, currency, transformation, timestamp, owner, reviewer, exception, and prior accepted value needed for a repeatable review cadence.

Resolve missing lineage. At checkpoint 3, reperform the affected Scenario A and Scenario B terms, identify the input that changes expected recovery, and state the operational, accounting, tax, policy, or privacy conclusion that remains outside the calculator.

Thursday scenario run

Calculate moderate, clearance, low, base, and high probability cases. The weekly markdown operating packet records the exact source, definition, period, unit, currency, transformation, timestamp, owner, reviewer, exception, and prior accepted value needed for a repeatable review cadence.

Record crossover points. At checkpoint 4, reperform the affected Scenario A and Scenario B terms, identify the input that changes expected recovery, and state the operational, accounting, tax, policy, or privacy conclusion that remains outside the calculator.

weekly markdown operating packet: thursday scenario run — This original diagram makes a repeatable review cadence reviewable.

Thursday independent review

Reperform units, price, costs, recovery, threshold, and constraints. The weekly markdown operating packet records the exact source, definition, period, unit, currency, transformation, timestamp, owner, reviewer, exception, and prior accepted value needed for a repeatable review cadence.

Separate author and reviewer. At checkpoint 5, reperform the affected Scenario A and Scenario B terms, identify the input that changes expected recovery, and state the operational, accounting, tax, policy, or privacy conclusion that remains outside the calculator.

Friday decision meeting

Approve hold, test, transfer, bundle, moderate markdown, clearance, liquidation, donation, or disposal through owners. The weekly markdown operating packet records the exact source, definition, period, unit, currency, transformation, timestamp, owner, reviewer, exception, and prior accepted value needed for a repeatable review cadence.

The tool recommends none automatically. At checkpoint 6, reperform the affected Scenario A and Scenario B terms, identify the input that changes expected recovery, and state the operational, accounting, tax, policy, or privacy conclusion that remains outside the calculator.

Implementation control

Record effective price, channel, time, inventory, communications, and responsible operator. The weekly markdown operating packet records the exact source, definition, period, unit, currency, transformation, timestamp, owner, reviewer, exception, and prior accepted value needed for a repeatable review cadence.

Confirm rollback. At checkpoint 7, reperform the affected Scenario A and Scenario B terms, identify the input that changes expected recovery, and state the operational, accounting, tax, policy, or privacy conclusion that remains outside the calculator.

Daily monitoring

Track realized price, units, fees, returns, storage release, and residual stock. The weekly markdown operating packet records the exact source, definition, period, unit, currency, transformation, timestamp, owner, reviewer, exception, and prior accepted value needed for a repeatable review cadence.

Use comparable windows. At checkpoint 8, reperform the affected Scenario A and Scenario B terms, identify the input that changes expected recovery, and state the operational, accounting, tax, policy, or privacy conclusion that remains outside the calculator.

Exception handling

Stop on data conflicts, price mismatch, policy warning, wrong inventory, or unexpected loss. The weekly markdown operating packet records the exact source, definition, period, unit, currency, transformation, timestamp, owner, reviewer, exception, and prior accepted value needed for a repeatable review cadence.

Escalate safely. At checkpoint 9, reperform the affected Scenario A and Scenario B terms, identify the input that changes expected recovery, and state the operational, accounting, tax, policy, or privacy conclusion that remains outside the calculator.

Monthly learning review

Compare expected and realized recovery, update evidence rules, and archive the prior packet. The weekly markdown operating packet records the exact source, definition, period, unit, currency, transformation, timestamp, owner, reviewer, exception, and prior accepted value needed for a repeatable review cadence.

Do not overfit one event. At checkpoint 10, reperform the affected Scenario A and Scenario B terms, identify the input that changes expected recovery, and state the operational, accounting, tax, policy, or privacy conclusion that remains outside the calculator.

weekly markdown operating packet: monthly learning review — This original diagram makes a repeatable review cadence reviewable.

Weekly Dead Stock Markdown Routine: population integrity control

Keep one SKU-location, condition state, availability rule, unit count, and cost basis. Control 1 defines a pass condition, evidence owner, independent reviewer, correction deadline, sensitivity range, monitoring signal, stop condition, and restoration trigger before the weekly markdown operating packet can support a repeatable review cadence.

Mixed inventory blocks. Apply the control to both synthetic fixtures while keeping inventory age, markdown price, expected units, selling costs, storage, disposal recovery, cost basis, recovery rate, and decision authority as separate concepts.

Weekly Dead Stock Markdown Routine: probability lineage control

Record sell-through definition, window, price, season, placement, availability, and source delay. Control 2 defines a pass condition, evidence owner, independent reviewer, correction deadline, sensitivity range, monitoring signal, stop condition, and restoration trigger before the weekly markdown operating packet can support a repeatable review cadence.

Unsupported probability requires Review. Apply the control to both synthetic fixtures while keeping inventory age, markdown price, expected units, selling costs, storage, disposal recovery, cost basis, recovery rate, and decision authority as separate concepts.

Weekly Dead Stock Markdown Routine: cost separation control

Map fees, fulfillment, storage, disposal, and cost basis once. Control 3 defines a pass condition, evidence owner, independent reviewer, correction deadline, sensitivity range, monitoring signal, stop condition, and restoration trigger before the weekly markdown operating packet can support a repeatable review cadence.

Duplicate or missing cost blocks. Apply the control to both synthetic fixtures while keeping inventory age, markdown price, expected units, selling costs, storage, disposal recovery, cost basis, recovery rate, and decision authority as separate concepts.

Weekly Dead Stock Markdown Routine: three seller thresholds control

Compare expected recovery rate, cost-basis shortfall rate, and evidence days with three separately entered seller controls. Control 4 defines a pass condition, evidence owner, independent reviewer, correction deadline, sensitivity range, monitoring signal, stop condition, and restoration trigger before the weekly markdown operating packet can support a repeatable review cadence.

One passing threshold cannot override another. Apply the control to both synthetic fixtures while keeping inventory age, markdown price, expected units, selling costs, storage, disposal recovery, cost basis, recovery rate, and decision authority as separate concepts.

Weekly Dead Stock Markdown Routine: dated evidence governance control

Record a real source-review date and seller-policy effective date, with policy no later than the reviewed evidence. Control 5 defines a pass condition, evidence owner, independent reviewer, correction deadline, sensitivity range, monitoring signal, stop condition, and restoration trigger before the weekly markdown operating packet can support a repeatable review cadence.

Impossible or reversed dates block. Apply the control to both synthetic fixtures while keeping inventory age, markdown price, expected units, selling costs, storage, disposal recovery, cost basis, recovery rate, and decision authority as separate concepts.

Weekly Dead Stock Markdown Routine: nine confirmations control

Confirm SKU-location grain, on-hand and cost basis, price and fees, sell-through, storage and fulfillment, residual recovery, condition, privacy, and accounting boundaries. Control 6 defines a pass condition, evidence owner, independent reviewer, correction deadline, sensitivity range, monitoring signal, stop condition, and restoration trigger before the weekly markdown operating packet can support a repeatable review cadence.

Any missing confirmation blocks. Apply the control to both synthetic fixtures while keeping inventory age, markdown price, expected units, selling costs, storage, disposal recovery, cost basis, recovery rate, and decision authority as separate concepts.

weekly markdown operating packet: weekly dead stock markdown routine: nine confirmations control — This original diagram makes a repeatable review cadence reviewable.

Weekly Dead Stock Markdown Routine: distinct scenarios control

Change at least one markdown, probability, selling cost, residual recovery, age, or evidence-window assumption between the two cases. Control 7 defines a pass condition, evidence owner, independent reviewer, correction deadline, sensitivity range, monitoring signal, stop condition, and restoration trigger before the weekly markdown operating packet can support a repeatable review cadence.

A copied scenario is not a comparison. Apply the control to both synthetic fixtures while keeping inventory age, markdown price, expected units, selling costs, storage, disposal recovery, cost basis, recovery rate, and decision authority as separate concepts.

Weekly Dead Stock Markdown Routine: output masking control

Mask derived money, rates, units, preference, and threshold gaps whenever structural validation returns Block. Control 8 defines a pass condition, evidence owner, independent reviewer, correction deadline, sensitivity range, monitoring signal, stop condition, and restoration trigger before the weekly markdown operating packet can support a repeatable review cadence.

Never act on partial invalid arithmetic. Apply the control to both synthetic fixtures while keeping inventory age, markdown price, expected units, selling costs, storage, disposal recovery, cost basis, recovery rate, and decision authority as separate concepts.

Weekly Dead Stock Markdown Routine: decision boundary control

Separate scenario recovery from forecasting, accounting, tax, pricing authority, promotion setup, and disposal approval. Control 9 defines a pass condition, evidence owner, independent reviewer, correction deadline, sensitivity range, monitoring signal, stop condition, and restoration trigger before the weekly markdown operating packet can support a repeatable review cadence.

Arithmetic cannot authorize action. Apply the control to both synthetic fixtures while keeping inventory age, markdown price, expected units, selling costs, storage, disposal recovery, cost basis, recovery rate, and decision authority as separate concepts.

Weekly Dead Stock Markdown Routine: privacy and recovery control

Use aggregates, protect source rows, retain prior values, monitor variance, and preserve restoration. Control 10 defines a pass condition, evidence owner, independent reviewer, correction deadline, sensitivity range, monitoring signal, stop condition, and restoration trigger before the weekly markdown operating packet can support a repeatable review cadence.

Public buyer or order data is prohibited. Apply the control to both synthetic fixtures while keeping inventory age, markdown price, expected units, selling costs, storage, disposal recovery, cost basis, recovery rate, and decision authority as separate concepts.

Monday aging triage: recovery lab 1

Recalculate the relevant output from both fixtures. Refresh age buckets, last receipt, on-hand quantity, condition, commitments, and value. Change one input only, retain every other population and cost assumption, and record the new expected sold units, unsold units, net recovery, recovery rate, threshold headroom, and preferred scenario.

Do not use stale exports. Test a low and high case for sell-through, price, fee, fulfillment, storage, and disposal recovery. Explain when the preference crosses over and which protected evidence or approval would still be required before an inventory action.

Tuesday cohort selection: recovery lab 2

Recalculate the relevant output from both fixtures. Choose a bounded SKU-location group with one commercial reason for review. Change one input only, retain every other population and cost assumption, and record the new expected sold units, unsold units, net recovery, recovery rate, threshold headroom, and preferred scenario.

Avoid catalog-wide automation. Test a low and high case for sell-through, price, fee, fulfillment, storage, and disposal recovery. Explain when the preference crosses over and which protected evidence or approval would still be required before an inventory action.

Wednesday evidence refresh: recovery lab 3

Recalculate the relevant output from both fixtures. Reconcile price, sell-through definition, fee rules, fulfillment, storage, and disposal quotes. Change one input only, retain every other population and cost assumption, and record the new expected sold units, unsold units, net recovery, recovery rate, threshold headroom, and preferred scenario.

Resolve missing lineage. Test a low and high case for sell-through, price, fee, fulfillment, storage, and disposal recovery. Explain when the preference crosses over and which protected evidence or approval would still be required before an inventory action.

Thursday scenario run: recovery lab 4

Recalculate the relevant output from both fixtures. Calculate moderate, clearance, low, base, and high probability cases. Change one input only, retain every other population and cost assumption, and record the new expected sold units, unsold units, net recovery, recovery rate, threshold headroom, and preferred scenario.

Record crossover points. Test a low and high case for sell-through, price, fee, fulfillment, storage, and disposal recovery. Explain when the preference crosses over and which protected evidence or approval would still be required before an inventory action.

Thursday independent review: recovery lab 5

Recalculate the relevant output from both fixtures. Reperform units, price, costs, recovery, threshold, and constraints. Change one input only, retain every other population and cost assumption, and record the new expected sold units, unsold units, net recovery, recovery rate, threshold headroom, and preferred scenario.

Separate author and reviewer. Test a low and high case for sell-through, price, fee, fulfillment, storage, and disposal recovery. Explain when the preference crosses over and which protected evidence or approval would still be required before an inventory action.

Friday decision meeting: recovery lab 6

Recalculate the relevant output from both fixtures. Approve hold, test, transfer, bundle, moderate markdown, clearance, liquidation, donation, or disposal through owners. Change one input only, retain every other population and cost assumption, and record the new expected sold units, unsold units, net recovery, recovery rate, threshold headroom, and preferred scenario.

The tool recommends none automatically. Test a low and high case for sell-through, price, fee, fulfillment, storage, and disposal recovery. Explain when the preference crosses over and which protected evidence or approval would still be required before an inventory action.

Implementation control: recovery lab 7

Recalculate the relevant output from both fixtures. Record effective price, channel, time, inventory, communications, and responsible operator. Change one input only, retain every other population and cost assumption, and record the new expected sold units, unsold units, net recovery, recovery rate, threshold headroom, and preferred scenario.

Confirm rollback. Test a low and high case for sell-through, price, fee, fulfillment, storage, and disposal recovery. Explain when the preference crosses over and which protected evidence or approval would still be required before an inventory action.

Daily monitoring: recovery lab 8

Recalculate the relevant output from both fixtures. Track realized price, units, fees, returns, storage release, and residual stock. Change one input only, retain every other population and cost assumption, and record the new expected sold units, unsold units, net recovery, recovery rate, threshold headroom, and preferred scenario.

Use comparable windows. Test a low and high case for sell-through, price, fee, fulfillment, storage, and disposal recovery. Explain when the preference crosses over and which protected evidence or approval would still be required before an inventory action.

Exception handling: recovery lab 9

Recalculate the relevant output from both fixtures. Stop on data conflicts, price mismatch, policy warning, wrong inventory, or unexpected loss. Change one input only, retain every other population and cost assumption, and record the new expected sold units, unsold units, net recovery, recovery rate, threshold headroom, and preferred scenario.

Escalate safely. Test a low and high case for sell-through, price, fee, fulfillment, storage, and disposal recovery. Explain when the preference crosses over and which protected evidence or approval would still be required before an inventory action.

Monthly learning review: recovery lab 10

Recalculate the relevant output from both fixtures. Compare expected and realized recovery, update evidence rules, and archive the prior packet. Change one input only, retain every other population and cost assumption, and record the new expected sold units, unsold units, net recovery, recovery rate, threshold headroom, and preferred scenario.

Do not overfit one event. Test a low and high case for sell-through, price, fee, fulfillment, storage, and disposal recovery. Explain when the preference crosses over and which protected evidence or approval would still be required before an inventory action.

Weekly Dead Stock Markdown Routine: intent-specific implementation walkthrough

weekly markdown operating packet checkpoint 1 addresses monday aging triage as a distinct requirement for a repeatable review cadence. Refresh age buckets, last receipt, on-hand quantity, condition, commitments, and value. Record the source decision, formula effect, failed alternative, reviewer question, correction owner, monitoring signal, and restoration value. Do not use stale exports.

weekly markdown operating packet checkpoint 2 addresses tuesday cohort selection as a distinct requirement for a repeatable review cadence. Choose a bounded SKU-location group with one commercial reason for review. Record the source decision, formula effect, failed alternative, reviewer question, correction owner, monitoring signal, and restoration value. Avoid catalog-wide automation.

weekly markdown operating packet checkpoint 3 addresses wednesday evidence refresh as a distinct requirement for a repeatable review cadence. Reconcile price, sell-through definition, fee rules, fulfillment, storage, and disposal quotes. Record the source decision, formula effect, failed alternative, reviewer question, correction owner, monitoring signal, and restoration value. Resolve missing lineage.

weekly markdown operating packet checkpoint 4 addresses thursday scenario run as a distinct requirement for a repeatable review cadence. Calculate moderate, clearance, low, base, and high probability cases. Record the source decision, formula effect, failed alternative, reviewer question, correction owner, monitoring signal, and restoration value. Record crossover points.

weekly markdown operating packet checkpoint 5 addresses thursday independent review as a distinct requirement for a repeatable review cadence. Reperform units, price, costs, recovery, threshold, and constraints. Record the source decision, formula effect, failed alternative, reviewer question, correction owner, monitoring signal, and restoration value. Separate author and reviewer.

weekly markdown operating packet checkpoint 6 addresses friday decision meeting as a distinct requirement for a repeatable review cadence. Approve hold, test, transfer, bundle, moderate markdown, clearance, liquidation, donation, or disposal through owners. Record the source decision, formula effect, failed alternative, reviewer question, correction owner, monitoring signal, and restoration value. The tool recommends none automatically.

weekly markdown operating packet checkpoint 7 addresses implementation control as a distinct requirement for a repeatable review cadence. Record effective price, channel, time, inventory, communications, and responsible operator. Record the source decision, formula effect, failed alternative, reviewer question, correction owner, monitoring signal, and restoration value. Confirm rollback.

weekly markdown operating packet checkpoint 8 addresses daily monitoring as a distinct requirement for a repeatable review cadence. Track realized price, units, fees, returns, storage release, and residual stock. Record the source decision, formula effect, failed alternative, reviewer question, correction owner, monitoring signal, and restoration value. Use comparable windows.

weekly markdown operating packet checkpoint 9 addresses exception handling as a distinct requirement for a repeatable review cadence. Stop on data conflicts, price mismatch, policy warning, wrong inventory, or unexpected loss. Record the source decision, formula effect, failed alternative, reviewer question, correction owner, monitoring signal, and restoration value. Escalate safely.

weekly markdown operating packet checkpoint 10 addresses monthly learning review as a distinct requirement for a repeatable review cadence. Compare expected and realized recovery, update evidence rules, and archive the prior packet. Record the source decision, formula effect, failed alternative, reviewer question, correction owner, monitoring signal, and restoration value. Do not overfit one event.

Evidence boundary for a repeatable review cadence

The moderate fixture uses 100 units, USD 12 unit cost, USD 30 current price, a 30 percent markdown, 55 percent expected sell-through, 10 percent selling fees, USD 4 fulfillment per sold unit, USD 1.50 storage per on-hand unit, and USD 2 disposal recovery per unsold unit. Expected net recovery is USD 759.50, or 63.29 percent of cost basis. The clearance fixture uses the same inventory and cost basis, a 50 percent markdown, 90 percent expected sell-through, 10 percent selling fees, USD 4 fulfillment per sold unit, USD 0.25 storage per on-hand unit, and USD 2 disposal recovery per unsold unit. Expected net recovery is USD 850, or 70.83 percent of cost basis.

The enhanced packet also displays cost-basis shortfall rates of 36.71 and 29.17 percent, expected net recovery per opening unit of USD 7.60 and USD 8.50, and recovery-floor gaps of negative 6.71 and positive 0.83 percentage points. It can demonstrate entered arithmetic and sensitivity, but it cannot prove future demand, optimal price, incrementality, accounting value, tax treatment, cash timing, policy compliance, buyer response, disposal eligibility, or the correct business action.

Release, monitor, and restore the weekly markdown operating packet

Block invalid or non-finite units, costs, prices, rates, dates, evidence, scope, currency, confirmations, duplicated scenarios, privacy, or conflicts, and mask every derived output. Review short evidence, very old inventory, negative sold-unit recovery, recovery below the seller floor, or shortfall above the seller ceiling. Ready clears only the three entered thresholds, nine confirmations, and the rest of the entered worksheet.

Before indexing or operational use, preserve evidence and rollback artifacts; run typecheck, unit, integration, build, content, similarity, SEO, image, link, mobile, strict-route, deployment, and live checks; then compare later evidence without claiming same-period causality.

Weekly Dead Stock Markdown Routine: concrete working record

The routine log records run date, aged-inventory snapshot, selected cohort, exclusion reason, all refreshed inputs, source freshness, scenario outputs, sensitivity results, independent reviewer, decision, approvals, execution evidence, daily variance, exceptions, corrective actions, stop events, rollback results, and next scheduled review.

Sources and further reading

Seller Profit Guard methodology: Evidence, formula, privacy, correction, release, monitoring, and rollback rules.
Seller Profit Guard data privacy: Local-first boundaries for inventory, supplier, customer, order, and raw export data.
Shopify Help: Product analytics overview: Official definitions for product sell-through, days of inventory remaining, and inventory value context.
Shopify Help: Inventory reports: Official reporting periods, month-end inventory snapshots, sell-through, ending quantity, and days-remaining boundaries.
Square Support: Run an aging inventory report: Official weighted age, last-received date, age bands, on-hand quantity, value, and location filters.
Microsoft Learn: Item Age Composition by Quantity and Value: Current official receipt-date aging report for on-hand quantity and value with item and location filters.
Oracle Retail: Markdown data requirements: Official treatment of permanent, clearance, and promotional markdown data.
Oracle Retail Markdown Optimization User Guide: Official lifecycle context for markdown timing, depth, profitability, and inventory targets.

Related Seller Profit Guard tools

Dead Stock Markdown Calculator: Compare moderate and clearance scenarios using expected net recovery and cost-basis recovery rate.
Inventory Carrying Cost Calculator: Estimate the annual holding burden separately from a markdown decision window.
Maximum Discount Calculator: Calculate a contribution-based discount ceiling for ordinary retained orders.
Contribution Margin Calculator: Measure retained order contribution separately from inventory disposition.
Methodology: Review evidence, formula, privacy, correction, release, and rollback.
Data Privacy: Protect inventory, supplier, customer, order, and raw export data.
Dead Stock Markdown Formula and Inputs: Define markdown price, sell-through probability, selling costs, storage, disposal recovery, cost basis, and expected net recovery.
Dead Stock Markdown Worked Example: Reperform a moderate markdown example from aged inventory through expected units, selling costs, storage, disposal, and recovery rate.
Clearance Markdown Recovery Scenario: Reperform a clearance markdown example with higher expected sell-through, lower storage, deeper price reduction, and unsold-unit recovery.
Dead Stock Markdown Modeling Mistakes: Find population, probability, fee, storage, disposal, cost-basis, accounting, privacy, and decision errors in markdown recovery models.
Dead Stock Markdown Data Sources: Map inventory age, on-hand units, cost, price, sell-through, fees, fulfillment, storage, and disposal recovery to controlled evidence.
Dead Stock Markdown Decision Threshold: Set a seller-owned recovery threshold, evidence floor, sensitivity range, approval boundary, stop rule, and restoration trigger.
Moderate vs Clearance Markdown: Compare moderate and clearance markdowns across price, expected units, costs, storage, disposal, recovery, uncertainty, and reversibility.
Interpret Markdown Recovery Results: Interpret expected units, recovery, rate, threshold, uncertainty, operating boundaries, and actual-versus-expected results without false precision.
Dead Stock Markdown Audit Template: Audit inventory scope, price, sell-through, costs, storage, disposal, formula, approvals, execution, monitoring, privacy, and rollback.

Next step: Open Seller Profit Guard.

This is operational planning help, not tax, accounting, legal, financial, or platform-policy advice. Review the Terms and disclaimer, and verify current platform rules and fee assumptions before changing prices.