Fashion price architecture

What is Fashion price architecture?

Fashion price architecture is a way to organize economic decisions across collection development. The starting point is to name the product, channel, unit of analysis, cost basis, markup, intended margin, and review moment. The product mix and line plan give the assortment its shape; the architecture records how each item should occupy a band and which conditions can move it.

The term does not mean choosing one multiplier and applying it without context. FIT places fashion product development between concept and pre-production and lists costing, sourcing, construction, quality, and marketing within that field. A pricing decision should therefore travel with the product path instead of appearing only when a garment is ready to sell.

How do markup and margin enter the process?

Markup and margin answer different questions. Markup starts from cost and adds an amount to reach a price; margin asks what share of selling price remains after costs and expenses. Because Sebrae describes different bases for the two terms, one percentage should not be read as if it were both markup and margin at once.

A price sheet can separate production cost, fixed and variable expenses, taxes, planned discounts, and desired margin. That breakdown keeps one number from hiding the decision. It also lets product costs and the technical sheet speak to one another: a change in material, construction, or finish may require a new cost reading before a band is retained.

The operational rule is to record the chosen formula and its base. If selling price is compared with cost, the team is reading markup; if the result is compared with selling revenue, it is reading margin. The record should name the measure, currency, channel, and period. Without those references, comparisons between items or collections can look precise without being equivalent.

How can a collection be organized into price bands?

Start with an item matrix rather than a table of percentages. For each family, record product proposition, channel, available cost, intended price, band, owner, and review date. Then compare nearby items: the architecture should make clear why products with different functions or constructions occupy different price points.

FIT describes contemporary fashion development as relying on technology, process control, and resource management. In practice, this supports keeping cost and price versions as the product advances. A decision made at concept stage may change at sampling, sourcing negotiation, or pre-production; preserving the earlier version makes the change legible without automatically calling it an error.

Markup may be standard or adjusted by product, as AccountingTools notes. A common rule can organize a first pass, but item-level review is useful when cost, channel, expected volume, or position in fashion retail are not equal. Adjustment does not mean chasing any external price; it means recording the reason and testing whether the choice still fits the defined cost and margin.

How should the architecture be reviewed after launch?

Review should compare plan with outcome and preserve exceptions. AccountingTools suggests looking at planned markups and actual gross margins, as well as discounts, returns, write-downs, sales volume, customer response, and competitor prices. For a collection, this can become a routine linked to demand planning: record the observed signal, the hypothesis that was in force, and the decision taken.

A sale below plan does not identify its cause by itself. Before changing a band, check whether the unit is still the same, whether a discount was included, whether returns or write-downs occurred, and whether the observed channel matches the plan. The analysis can then separate a cost issue, a price choice, a channel change, and an execution issue. This is a method recommendation, not a promise that architecture will remove uncertainty.

The architecture also needs explicit boundaries. Markup is not margin; a competitor price is not internal cost; and a collection band is not a guarantee of an outcome. To keep the process auditable, close each review with formula, version, date, owner, and reason. Then the product mix can be reconsidered without erasing history, while line plan, technical sheet, and product costs remain connected to the economic decision.