Retail markdowns: choose between transfer, discount and hold

One store holds 60 winter jackets. Another expects demand for 20, while the first store's manager wants to mark down the entire line. Moving stock can protect selling price, but transport consumes time and the receiving store may not sell what it requests.

Compare feasible actions over the same horizon, with explicit demand and leftover assumptions. A transfer is a stock movement. Its financial benefit depends on a later sale, so the decision must show both expected cash recovery and the stock that remains exposed.

Put all three options on the same basis

Assume 60 jackets are physically available and eligible to sell. Each originally cost ₹1,000. For a two-week decision window, ignore tax, payment fees and fixed overhead, and assume any unsold jacket remains in stock with no assigned terminal cash recovery. That last assumption is deliberately conservative for comparing near-term cash; it is not an inventory valuation policy.

The planner estimates these sales, rather than claiming observed demand:

The transfer option gives 18 × ₹1,700 + 25 × ₹1,300 − ₹2,000 = ₹61,100. It sells 43 of the original 60 units and leaves two at the destination plus 15 at the origin. The comparison does not assume all 20 transferred jackets sell.

For a separate merchandise-margin view, deduct the original cost of units actually sold. The three illustrative figures are ₹8,000, ₹12,000 and ₹61,100 − ₹43,000 = ₹18,100, respectively. Remaining inventory stays outside that sold-unit calculation. Finance must decide any valuation adjustment separately; the operational comparison is not a write-down instruction.

Shopify's markdown guide provides the distinction between a price reduction and broader inventory decisions. The choice here is an original scenario analysis, with no assumption that a lower price guarantees the forecast quantity.

Challenge the transfer forecast

If only eight transferred jackets sell, while 25 still sell locally, recovery falls to 8 × ₹1,700 + 25 × ₹1,300 − ₹2,000 = ₹44,100. That is ₹7,900 below the local markdown scenario, with 27 jackets left across the two stores.

This sensitivity changes the decision. The planner should ask for evidence behind the destination's request: recent sales at the intended price, comparable sizes, local stock, reservations, and remaining selling days after transit. A demand forecast for “jackets” may not support a transfer of unpopular sizes.

For cash recovery to exceed ₹52,000 under the stated local-sales assumption, transferred sales must satisfy 1,700 × quantity + 30,500 > 52,000. Thirteen sales give ₹52,600; twelve give ₹50,900. That break-even comparison is useful only while the local 25-unit sales estimate and other costs remain unchanged.

1. Confirm 60 eligible unitsExclude damaged, reserved or otherwise unavailable stock.
2. Evaluate the same horizonHold: ₹18,000; markdown: ₹52,000; transfer scenario: ₹61,100.
3. Stress the destinationOnly eight destination sales reduce recovery to ₹44,100.
4. Approve and revisitTrack actual sales and all unsold units at both locations.

Exception: A transfer request without size-level demand or arrival capacity returns to the planner; movement is not booked as a sale.

Check the physical decision before the financial one

Validate sellability, ownership, size and location. Inventory-state definitions illustrate why stock on hand can include quantities that are unavailable to sell. A markdown should not accidentally release inspection stock, and a transfer must not consume units already committed to another customer.

Confirm receiving capacity and transit timing. Include handling, transport, relabelling or channel costs that differ between options. Do not allocate a fixed cost to one option simply because its owner has a larger budget. Use consistent assumptions and show which costs are incremental.

The merchandising head owns the action; store teams own dispatch and receipt evidence; pricing owns the approved selling price. Keep the original decision and later observations together. If the receiving store changes its price, preserve that change rather than treating all sales as if they occurred at ₹1,700.

Automate the review queue, then evaluate the action

A simple spreadsheet can compare a small number of cases if stock snapshots, forecasts and approvals are controlled. An ERP report can flag aged units and join transfer requests. More advanced optimisation is useful only when the required constraints and feedback are reliable.

For a first pilot, keep a planner approval step. Record the chosen action, rejected alternatives, assumed sales, costs and review date. At the end of the horizon, reconcile starting quantity to sold, returned, transferred, damaged and remaining units. Explain differences without quietly replacing the original forecast.

The acceptance test includes a destination shortfall, a delayed transfer and a price change. The workflow passes when it retains the remaining exposure and supports a revised decision. A green “transfer completed” status cannot close the commercial review.

Choose the action with a visible downside

The best apparent recovery depends on demand that may not occur. Showing the downside lets a planner make a reasoned choice and identify when to change course.

1. Reconcile the eligible quantity and choose one selling horizon.
2. Compare recovery and leftovers under consistent assumptions.
3. Stress the uncertain demand and approve a bounded action.
4. Review actual sell-through and the remaining units before extending the policy.