Publish Date :
Promotions and Markdowns Need Separate Budgets
A promotional discount and a stock-exit reduction can reduce the same sales total for different reasons. Merchmix Core helps keep the intended price, quantity and financial consequence connected in the plan. Separate the commercial purpose before judging whether the discount budget is doing its job.

THE MERCHMIX DECISION / Core
One discount total. Two different decisions.
Keep the commercial purpose visible beside the reduction and stock consequence.
Independent worked retail example. Quantities are planning assumptions, with financial amounts shown in US dollars. Proposed changes remain subject to review.
One discount total. Two different decisions.
100 units at $80
$500 allowance retained
60 units at $60
$200 allowance retained
The $4,400 reduction is counted once against original ticket value. The article’s separate demand sensitivity shows why more promotional units need not mean more gross profit.
The hundred-unit promotion differs from the sixty-unit stock exit.
THE KEY IDEA
Keep the commercial purpose visible beside the reduction and stock consequence.
The same reduction can answer a different question
A planned promotion may aim to generate a visit, basket or trial. A later markdown may seek to recover value from stock whose full-price window is weakening. Both affect the price received, but they should not be evaluated as if they were the same commercial action.
A markdown is not automatically evidence of a buying mistake; some exits are planned. Likewise, a promotion is not automatically incremental demand. Core connects the forward price and stock assumptions so the review can ask what each reduction is intended to achieve rather than assign every discount to one unexplained bucket.
Define the baseline before calculating the allowance
Use the original ticket value of units actually sold as this example’s common discount denominator. Exclude tax and returns from the illustration. Real reports need an agreed treatment for returns, price changes and stacked offers so the same reduction is not counted twice.
Core supports the merchandise plan; the article does not assert a dedicated promotion-versus-clearance budget screen. A separate planning line or agreed classification is useful only when its definition remains consistent from the forecast to the transaction evidence and the financial review.
Compare the two purposes on one price basis
The promotion expects a hundred units at $80 against a $100 ticket, a $2,000 reduction. The stock-exit plan expects sixty units at $60 against the same ticket, a $2,400 reduction. Together, original ticket value is $16,000 and net selling value is $11,600.
Combined reduction is $4,400, or 27.5% of original ticket value. That total hides that the smaller stock-exit quantity consumes the larger reduction. Label the amount by purpose before judging the promotional activity; a campaign owner should not appear responsible for an unrelated exit merely because the reporting total combines them.
THE FIGURES BEHIND THE DECISION
| Purpose | Units | Net selling price | Reduction | Allowance retained |
|---|---|---|---|---|
| Promotion | 100 | $80 | $2,000 | $500 |
| Stock exit | 60 | $60 | $2,400 | $200 |
| Combined | 160 | $11,600 revenue | $4,400 | $700 |
Combined reduction = $16,000 original ticket value − $11,600 net sales = $4,400, or 27.5%. Goods cost is $6,400 and product GP $5,200.
Read the goods margin behind each price
Assume all 160 units cost $40. The promotion yields $8,000 revenue and $4,000 product gross profit; the exit yields $3,600 revenue and $1,200 product gross profit. Combined gross profit is $5,200 before other expenses, not $11,600.
These results do not prove the promotion was worthwhile. It may discount purchases that would have occurred at full price, or generate additional profitable demand. Keep the evidence for incrementality separate from the discount arithmetic. The worked plan contains no claimed traffic uplift or customer-acquisition result.
A separate demand sensitivity illustrates why a promotion needs a counterfactual. Seventy units at the $100 ticket and $40 cost would produce $4,200 product gross profit. A hundred at $80 produces $4,000. Even thirty more sales could therefore leave $200 less gross profit under those assumptions, before event costs. This is a comparison to test, not a measured promotional effect.
Give each allowance its own review question
Suppose the promotional reduction allowance is $2,500 and the exit allowance $2,600. The planned activity leaves $500 and $200 respectively, $700 combined. Those balances remain allowances under review, not cash automatically available for another discount.
For the promotion, ask what would happen without the offer and whether supply can support the event. For the exit, ask what stock remains afterwards and which alternative route is available. Core’s MFP/WSSI context keeps the unit and price consequences alongside their dates rather than treating the allowance as a marketing-only number.
Separate planning approval from price execution
A reviewed price assumption does not change the retailer’s selling price by itself. Confirm the applicable approval and the POS or ERP execution before treating the price as active. Check what happens if an exit reduction and promotional offer apply to the same units.
Retain the intended commercial classification and compare it with recorded transactions. A stacked reduction may need more than one reason code, but the total net price should reconcile once. The article does not promise automatic prevention of every overlapping offer across connected systems.
Reconcile the original ticket, any permanent reduction and the final promotional offer in sequence. The same dollar of reduction should enter the combined total once, even when more than one commercial reason applies. Retain the reasons separately without adding two overlapping gross reductions to explain one final net price.
| Signal | Merchmix workspace | Decision to review |
|---|---|---|
| All discounts share one total | Core / financial plan | Retain the purpose and denominator behind each reduction. |
| An event is reviewed | Core / MFP/WSSI | Check incremental demand, supply and price assumptions. |
| An exit is approved | Core / price review | Keep planning status distinct from actual selling-price execution. |
Judge the two budgets by their intended outcomes
For the worked plan, the promotional reduction is $2,000 and the stock-exit reduction $2,400, against their separately stated allowances. The shared $4,400 total is still useful for financial control, provided it does not erase why the reductions exist.
Merchmix Core connects the buying and trading discussion with the financial consequence. Separate purposes make the review more precise: a promotion needs evidence of its customer response, while an exit needs evidence that the remaining stock risk improved. Neither is justified by recording a larger discounted sales total.
BEFORE THE NEXT DECISION
- Trading owner
Define the purpose and transaction classification.
- Planner
Reconcile ticket value, net sales and allowances.
- Price owner
Confirm approved execution and overlapping offers.
Common questions
Are all markdowns mistakes?
No. A planned exit can be deliberate; the reason and stock consequence still need review.
What denominator gives 27.5%?
$4,400 reduction divided by $16,000 original ticket value of the sold units.
Does the promotion prove incremental sales?
No. The illustration calculates price consequences, not a causal uplift.
What remains in the allowances?
$500 promotional and $200 exit allowance, or $700 combined.
Does approving the plan change the POS price?
No. Planning approval and price execution are separate steps in the applicable workflow.
FROM THE ARTICLE TO YOUR OWN RETAIL PLAN
Review the decision.
See the workflow.
Bring your planning questions to a demo, or explore a proof of concept on your own data.