Publish Date :
Markdown Approvals That Slow Everything Down
Markdown decisions slow down when the approver has to reconstruct the product scope, stock position and commercial case from separate messages. Merchmix Core keeps the comparison together, while Yukti can prepare a bounded proposal for review. The approved plan and the price applied in the retailer’s POS or ERP still need to agree.

THE MERCHMIX DECISION / Core + Yukti
A price decision needs a complete scope
A markdown approval needs the product, price, selling dates and financial consequence in one review, followed by confirmation that the intended price is actually active.
Independent retail planning example. Financial amounts are US dollars. Forecasts, quantities and proposals are assumptions for this decision, not customer results.
Teal linen dress / price authority
| Scope | Selected assumption |
|---|---|
| Product | Teal linen midi dress |
| Window | 20–27 November |
| Locations | Named eligible stores |
The dates, quantity and price are independent planning assumptions.
Review one teal linen dress option before the chosen offer window.
THE KEY IDEA
Prepare a complete price decision, record its authority and verify the actual selling price before judging the response.
Prepare the decision before requesting the approval
A message asking whether a product can be reduced is incomplete if it omits the stores, sizes, start date or current stock. The reviewer must then chase the detail before deciding. That delay can consume part of a short selling opportunity without improving the quality of the decision.
In Core, connect the proposed price with the relevant sales, stock and intake assumptions. Give the request one commercial owner and a response deadline. Yukti can help present the supported proposal with its reasoning; it should not turn an incomplete price request into an apparently authorised action.
Keep the intended price and eligible scope together
An independent retailer holds 150 teal linen midi dresses at a $100 ticket and $40 goods cost. It considers an $80 selling price for selected stores from 20 to 27 November. The chosen dates span eight calendar days and are scenario assumptions, not a reported retailer event.
Specify whether all eligible sizes share the offer and whether other discounts can overlap. A twenty-percent reduction from ticket does not establish the final customer price if another offer also applies. Core’s planning comparison needs the same price basis that the execution owner will later check.
Give the approver a financial comparison they can follow
At sixty assumed sales, the $80 price produces $4,800 revenue and $2,400 product gross profit after $2,400 goods cost. Expected closing stock is ninety units. These figures exclude returns, tax and operating expenses; they are a defined product comparison rather than a complete profit forecast.
The proposed sales response is the uncertain input. Retain the evidence behind it alongside the stock and price. Core provides a place to compare those assumptions before committing the planning decision. A large percentage reduction is not a substitute for explaining which units it is expected to sell.
THE FIGURES BEHIND THE DECISION
| Record | Required position |
|---|---|
| Planning decision | Scope and owner recorded |
| Downstream price | Confirmation required |
| First trading check | Realised price and availability |
Sixty sales: 60 × ($80 less $40) = $2,400 product GP. Fifty sales: 50 × $40 = $2,000. Closing stock is 150 less the assumed sales.
Use a delay sensitivity without inventing missed sales
If the shorter remaining opportunity supports only fifty sales at $80, revenue becomes $4,000 and product gross profit $2,000. Closing stock becomes one hundred. The difference from the sixty-sale case is ten units and $400 product gross profit.
That is an assumed sensitivity, not a measured loss caused by a late approver. Traffic, size availability and the offer’s appeal could change the outcome. Use it to make the decision window concrete, while keeping the forecast and any claim about causation separate.
Let Yukti prepare a reviewable proposal
A useful Yukti proposal names the dress option, eligible locations, proposed $80 price, eight-day window and current 150 units. It includes the sixty-sale assumption and asks the authorised person to review the financial consequence. The illustration stays awaiting review.
If the reviewer changes the scope or price, refresh the comparison before treating the earlier calculation as approval evidence. A decision on one option and period should not silently authorise another product or an extended event. Keep the actual permission as specific as the proposal.
Confirm the live price through the supported operational route
Approval in the merchandise plan does not, by itself, establish what customers will pay. The designated owner must complete the supported price workflow in the retailer’s POS or ERP and confirm that the relevant stores and dates received the intended instruction.
Core carries the planning assumption and decision context. The connected execution behaviour depends on the configured system and permitted workflow. Check the downstream result rather than report a lower price as active merely because a planning screen shows a completed review.
| Signal | Merchmix workspace | Decision to review |
|---|---|---|
| Price proposal | Core / evidence | Review one teal linen dress option before the chosen offer window. |
| Commercial comparison | Yukti / comparison | Sixty assumed sales at $80 leave ninety units and $2,400 product gross profit. |
| Execution check | Core / decision review | Yukti may prepare the proposal; this illustration does not approve or publish a selling price. |
Review price, stock and the remaining window together
At the first trading check, compare realised price, availability and units sold with the retained assumption. If the price did not activate everywhere, distinguish an execution exception from weak customer demand. If the sizes were unavailable, the sales result needs that context.
Core and Yukti are most useful when the request reaches a timely, accountable decision and its outcome is checked. The objective is a shorter, clearer approval path with a dependable price record, rather than faster acceptance of every proposed reduction.
BEFORE THE NEXT DECISION
- Planning owner
The calculation excludes operating costs, returns and taxes.
- Commercial owner
A ten-unit sales difference is assumed; it is not proof of an approval delay’s causal effect.
- Decision owner
Yukti may prepare the proposal; this illustration does not approve or publish a selling price.
Common questions
What should a markdown approval include?
The eligible products and locations, proposed realised price, dates, stock basis, demand assumption, financial comparison and authorised owner.
Is the $80 price live in the example?
No. The animation shows a proposal and the checks required before execution is confirmed.
Why does the later case show $400 less product gross profit?
Ten fewer assumed sales at $40 goods contribution per sold unit create the $400 difference.
Does that prove a delay caused ten lost sales?
No. It is a planning sensitivity, not a measured causal result.
What happens after approval?
The supported POS or ERP price change needs confirmation, followed by a review of realised price, availability and sales.
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.