How to Use This Tool
Translate an end-of-window sell-through target into weekly incremental units. A markdown percentage is chosen before anyone calculates how many extra units must actually move.
Why Clearance Pace needs more than a raw total
The target should subtract sales expected without promotion, otherwise the discount gets credit for the baseline. For this page, the useful comparison is incremental units needed weekly, not whichever input happens to be largest. The Clearance Pace result answers the decision in the heading and should not be reused as a score for a different workflow.
The exact Clearance Pace formula
Weekly incremental units equal target units minus organic units, divided by weeks remaining. The visible fields are Starting inventory, Target sell-through, Expected organic sales and Weeks remaining. For Clearance Pace, read each printed unit before entry and make the values describe one transaction, cohort or reporting window. If those scopes differ, the displayed incremental units needed weekly may be arithmetically valid but operationally meaningless.
Interpreting incremental units needed weekly
Test whether the required lift is realistic before scheduling deeper markdown steps. The ten-percent comparison is deliberately narrow: it tests the influence of starting inventory and is neither a forecast nor a confidence interval. Preserve the values used, their dates and the resulting decision so a later reviewer can reproduce why Clearance Pace supported the choice.
What this Clearance Pace model leaves out
Price elasticity, replenishment, returns and weekly demand decay are not forecast. That is where Clearance Pace stops being trustworthy. If an excluded factor could reverse incremental units needed weekly, extend the model explicitly or use the authoritative account system instead of hiding the factor inside an unexplained adjustment.
Evidence and independent verification
The reference reviewed for Clearance Pace is FTC — Guides Against Deceptive Pricing. FTC — Guides Against Deceptive Pricing supports the named definition or rule but does not supply private values for incremental units needed weekly. Before acting on the result, reconcile the worked example with the relevant dashboard, invoice, export or measurement.
Private, reproducible calculation
Clearance Pace runs its arithmetic in the current browser tab and requests no login or API key. That keeps the Clearance Pace inputs away from the site's calculation server, while leaving the user responsible for detecting stale data or a changed platform rule. When an assumption changes, reopen FTC — Guides Against Deceptive Pricing and rerun the saved Clearance Pace scenario.
Sources & assumptions
Tool Spec v2 · verified 2026-08-20. Platform rules and fees can change; the editable inputs remain authoritative for your account.
Official references
- FTC — Guides Against Deceptive Pricing (checked 2026-08-20)
Model assumptions
- Every input covers the same reporting period or cohort.
- Price elasticity, replenishment, returns and weekly demand decay are not forecast.
- The calculator uses only the visible fields and does not fetch account data.
