Help

Help›Finance›Markdowns

Markdowns

Reviewed Oct 29, 2026

View as Markdown
Words
TierPro

The question this page answers ​

Which products are behind pace, what depth was proposed on each, and who decided it? Markdowns records decisions and never changes a price. It reads the pricing engine, described in the pricing engine, and a Commitment's declared pace and margin floor, so it is on Tightly Pro only.

Where the page lives ​

Open Markdowns under Finance, or choose Prices on a continuity commitment's plan. Back to decisions returns to Trading; Financial assumptions preserves the selection. An ordinary proposal names no place; scoped execution names its destination.

What you see ​

Choose Candidates or Decisions, then a Commitment. Candidates is headed Behind pace. Open a row’s proposal or decision; Explore in Ask retains context. Fixed Commitment views keep reads and actions in that Commitment. Invalid scope cannot show company data. The approval rule remains visible:

Nobody has set a depth that needs a senior, so an editor may decide any markdown.

A markdown at or over {n}% off is decided by an approver.

Behind pace ranks sold-through against the declared glidepath of active Commitments with opened windows. Products without sales are omitted. All decisions combines ten eligible Commitments; rows do not identify their Commitment.

Where shows frozen destinations; missing names read Not measured.

Decisions lists the 50 newest scoped markdowns. The column picker offers Depth, Where, Reason, From, Proposed, Achieved, Floor, Proposed by and State; Depth is a cut off the current price. Achieved reads Not closed yet until the season closes, and Proposed by is hidden until you pick it.

What to do ​

Open an approved scoped decision’s execution record. Reported implementation proves neither sales nor cash.

With read and write access, choose a product row, or tick several rows, and open the proposal drawer. The drawer asks for Depth (percent off the current price, 0 to 99), Reason (Behind pace, Over cover, Season end, Terminal stock, Competitive, Other), From (typed as Sep 21, 2026) and a Note. It lands as Waiting and applies nothing. Select a Commitment first. All decisions has no Commitment scope, so its margin floor remains unmeasured.

Proposals read demand, margin and closing stock without writing. Unsupported depths show the engine's reason; proposing records a read.

Approve and Refuse sit on each Waiting row. Deciding needs at least an editor on Commitments, and a depth at or over the approval rule needs an approver:

This workspace sends a markdown at or over {n}% off to an approver, and this one is {n}% off.

Decisions are taken once; a change of mind requires a new proposal. Only the proposer may withdraw through the existing authority. The Admin approval rule remains unchanged. Approval applies no prices; the owning system does that.

Compare prices across a range ​

Select a Commitment, then choose Compare range prices. Search its full authorized range, including healthy neighbours. Choose compatible variants, consumer channel, location and up to 182 days. Load current prices reads that forecast, stock and price scope. Proposed prices start at current values.

Review compatible alternatives, price sensitivity and outside/no-purchase assumptions. Compare shows current, isolated and joint gross profit, demand movement and residue. Sensitivities are not calibrated shopper forecasts. Gross profit excludes returns, fulfilment, carrying and cash timing.

Enable Include return economics and declare gross or kept-unit forecasts. Enter each variant's reviewed returns, tax, recovery and expense reference; explicit zeros are required. Compare contribution, signed drivers and physical residue. Editing clears the result. These scenarios do not predict calibrated returns or received cash.

Missing forecast, stock, denomination or source evidence prevents comparison. Changed sources require fresh inputs. Compare writes nothing. Choose a reason and Send to Finance to stage exact discounted variant prices. Review the immutable joint result and approve each native decision. All changed variants require approval before export. Changed source/engine revisions refuse stale staging, approval or first export. Explore in Ask opens a draft about this same saved scenario; it sends nothing automatically.

Prepare and report price execution ​

In the proposal drawer, select Prepare scoped execution for approval. Name an account, sales channel, store or warehouse, or store cluster, and set Effective until (exclusive). An account uses its sell-in price book and cannot be combined with a store or cluster. Store and channel proposals use catalogue prices as their basis. Approval freezes the selected variants, destinations, prices and dates; the ordinary demand preview does not run for this scoped proposal.

Open Review on the decision to review its snapshot. After approval, Create export prepares the items and Download export saves them as JSON. Neither action sends prices to a connected store. An older approval without a scoped snapshot needs a new scoped proposal and approval. Overlapping exports for the same price scope and dates are refused.

Apply the prices in the owning system, then review each item. Enter the observed price, observation date and evidence reference, and press Record readback. Matching prices read Reported implemented; different prices read Price mismatch. Record failure also needs an evidence reference. Retry item opens another attempt for a failed or mismatched item; Receipt history retains the evidence. These actions require write access and an editor on Commitments.

When it is empty or failed ​

Markdown suggestions are read against an active commitment's planned sell-through curve, and this workspace has no active commitment.

No markdown decided yet.

The markdowns did not load.

Try again repeats the read. A Commitment that cannot be read prints its own sentence in place of the candidates.