The question this page answers
Which styles are behind pace, what depth was proposed on each, and who decided it? Markdowns records decisions and never changes a price: the cut is made in the POS or store system by whoever owns it. 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
The address is /finance/markdowns. In the retailer chair it is a rail row, Markdowns, under Finance; its title reads Markdowns. A brand's rail carries no row for it, and the page is reached from the Price tab of Trade the week or by its address, where the title reads Markdown candidates. Arriving from Trade the week, the page carries Back to decisions and, where the style is still a candidate, Review markdown, which opens the drawer on it. The place words are the chair's own: a brand's markdown names a Warehouse or a Store cluster, in the retailer chair it names a Store or a Store cluster, and one that names no place reads Everywhere or Every store. A markdown proposed on this page names no place.
What you see
The head has a Commitment picker (All decisions, or one Commitment), the Ask Tightly door, and a basis line: the day the pace is read at, the place, and the approval rule, for example:
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 lists the styles furthest behind first: Style, Sold through, Target, Behind by, On hand and Decision (a state, or Nobody has decided). Sold through is measured today, as units sold in the window over units sold plus on hand, against the target the Commitment's glidepath declares for today. Only an active Commitment with a season window, a declared glidepath and a window that has opened can be read. With All decisions picked the page reads the ten newest active Commitments it can score and ranks their styles together, furthest behind first; the table does not say which Commitment a row came from. A style the book holds no sale for is left out rather than shown as the furthest behind.
Decisions lists the 50 newest markdowns in scope (the picked Commitment's, or every one under All decisions): Style, Depth, Where, Reason, From, Proposed (the units, revenue, margin after, terminal saved and recovery it was proposed on), Floor (Under the floor, Inside the floor, or Not measured) and State (Waiting, Approved, Refused, Withdrawn). Each decision also carries three prices: Ticket, Current and Marked. The depth is always a cut off Current, so an already-discounted style shows both how far off ticket it already stood and the further cut this decision takes. A decision proposed before this was tracked reads No price was on file for this markdown when it was proposed, so the depth is a percentage off whatever the price stood at then. Achieved, the same figures once the season closes, and Proposed by are in the column picker; Achieved reads Not closed yet until then, and where every row would read the same the column is left out.
What to do
With at least read and write access, press Propose a markdown on a row, or tick styles and use the bar's own button. 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. Pick the Commitment in the head first: a markdown proposed under All decisions names no Commitment, so its Floor reads Not measured.
Once a depth is typed the drawer reads the price ledger for the whole selection before you press, and writes nothing: Demand (units and revenue), Margin, and Stock at close (terminal stock saved and recovery), with Depths this book has traded beneath. It is read against the active Commitment whose scope holds most of the selection. Where the engine declines the depth, for example one deeper than the book has traded, the drawer prints the engine's sentence instead of the figures. The server reads the figures again when you propose and keeps them on the row.
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.
A decision is taken once; a change of mind is a new proposal. The page carries no withdraw button, and only a markdown's proposer may withdraw it. The approval rule is an Admin setting, and no page in this release carries a control for it. Once anything is approved the Decisions card reads:
Apply approved markdowns in the owning POS or store system. Approval here does not change prices.
When it is empty or failed
Markdown candidacy is read against a Commitment's declared pace, and this workspace has no active Commitment to read one against.
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.