All posts
September 9, 2026 · 10 min read

Wholesale pricing for fashion labels: keystone, markup vs margin, and the formulas

What is wholesale pricing?

Wholesale pricing is the price a brand charges retailers for goods those retailers will sell on to the public. It sits between two other numbers: below it, the cost of making the product; above it, the recommended retail price (RRP) the end customer pays. A label that sells to boutiques lives or dies by how intelligently it sets — and how consistently it applies — the number in the middle.

This guide covers the vocabulary that trips people up (markup versus margin, and why confusing them is expensive), the keystone convention that still anchors fashion retail, the formulas for building a wholesale price from either end of the chain, and the parts the textbooks skip: per-size pricing, option charges, per-retailer terms, and the discipline of applying all of it identically on every order.

The price chain: cost, wholesale, retail

Every wholesale business runs on a three-step chain:

  • Cost price — what it costs you to make one unit: materials, making, packaging, freight to you, plus an honest allocation of the overheads that exist because the product exists.
  • Wholesale price — what the retailer pays you. The gap between cost and wholesale is *your* margin, which has to fund your operation and your profit.
  • Retail price (RRP) — what the shopper pays. The gap between wholesale and retail is the *retailer's* margin, which funds their rent, staff, fitting appointments and profit.

The discipline is to build the chain from both ends and check it meets in the middle: cost-up (what must I charge to be viable?) and retail-down (what will the end customer pay, and does the implied wholesale work for both of us?). A price that only survives one of those tests is not a price — it is a wish.

Markup vs margin: the distinction that costs real money

The two words describe the same gap from different directions, and mixing them up systematically over- or under-prices a range.

Markup is the uplift on cost, expressed as a percentage of the *cost*. Margin is the profit share of the selling price, expressed as a percentage of the *selling price*.

The formulas, side by side:

  • Markup % = (selling price − cost) ÷ cost × 100
  • Margin % = (selling price − cost) ÷ selling price × 100

The same transaction wears very different numbers in each language. A gown that costs 250 and wholesales at 500 carries a 100% markup — but a 50% margin. The correspondence table worth memorising:

  • 25% markup = 20% margin
  • 50% markup = 33.3% margin
  • 100% markup = 50% margin
  • 150% markup = 60% margin
  • 300% markup = 75% margin

(For the working session rather than the theory, our free markup and margin calculator does all three conversions live — including the wholesale-to-retail multiple check below.)

Where it bites: a retailer who says "we need a 60 margin" means margin — they want to keep 60% of the retail price, which requires a 150% markup on what they pay you. If you hear "60" and apply a 60% *markup* to your wholesale price when suggesting their retail, you have proposed a retail far below their economics, and the range review goes badly for reasons nobody in the room can quite articulate. Retail buyers speak margin. Manufacturers tend to think markup. Translate carefully at the border.

Keystone pricing, and what it means today

Keystone pricing is the old retail convention of setting the retail price at double the wholesale price — a 100% markup, a 50% margin. Its virtue is speed: a buyer flipping through a line sheet can double every number and know instantly whether the range fits their shop's price architecture.

Is keystone still the rule? As a *benchmark*, absolutely — it remains the default mental arithmetic in independent fashion and bridal retail, and many boutiques still price at keystone or near it. As a *law*, no. Common real-world variations:

  • Above keystone (2.2x–2.8x) — common where the retailer carries heavy service costs. Bridal is the canonical case: a boutique that provides ninety-minute appointments, storage, steaming and fitting coordination needs more than keystone to survive, and many price bridal gowns at 2.2x to 2.6x wholesale.
  • Below keystone (1.8x–2x) — high-velocity or highly price-visible categories, where the retailer trades margin for turn.
  • Country and channel adjustments — export markets carry duty and freight that either the wholesale price or the retail multiple has to absorb; showing per-market price lists beats making every buyer do customs arithmetic.

The practical use of keystone for a label: when you set an RRP, check what multiple of your wholesale price it implies. If your suggested retail is less than 2x your wholesale, expect boutiques to either round it up or pass — you have priced their margin away.

Building the wholesale price: the formulas

Cost-up: Wholesale = landed cost × your chosen multiplier. Independent fashion labels typically need a multiplier between 2 and 2.5 on true landed cost for the wholesale channel to be worth running — below 2, growth quietly loses money, because every new stockist adds volume at a margin that never covered the overheads honestly.

Retail-down: Wholesale = target RRP ÷ the retail multiple your channel expects (2 for keystone; higher for service-heavy categories). Then check the implied margin over your cost. If the two methods disagree — cost-up says 540, retail-down says 460 — the product, the costs or the target customer needs rethinking *before* launch, not after forty boutiques have the line sheet.

A worked example (illustrative numbers, not anyone's real price list): a made-to-order gown with a landed cost of 210. Cost-up at 2.3 gives a wholesale of 483 — call it 485. Retail-down: the boutique's bridal customer expects gowns around 1,150, and bridal boutiques in this bracket price at roughly 2.4x, implying a wholesale near 480. The two methods agree; 485 holds, with an RRP guidance of 1,150. Then the structure work starts — which is where fashion pricing gets interesting.

Where clothing pricing gets structural

A single wholesale price per style is the textbook case. Real ranges — especially made-to-order ones — carry structure that a spreadsheet groans under and a pricing system has to formalise:

  • Per-size price matrices. Larger sizes use meaningfully more fabric and making time. Bridal and occasionwear ranges commonly step the price at a size break — a flat uplift or a percentage surcharge above, say, a UK 22 — and curve lines may carry their own base prices entirely.
  • Option and customisation charges. Lining choices, boning, extra length, sleeves on or off, made-to-measure itself: each carries a charge, and each combines with the others. The options price list is a first-class part of the wholesale price, not a footnote.
  • Bundled products. The belt sold with the gown, the veil designed for it — bundles need their own price logic so the pair prices correctly whether ordered together or apart.
  • Delivery and rush charges. A priority lead-time band that costs more to produce should cost more to buy, applied once per order rather than smeared across line items.

None of this is exotic — it is Tuesday for any bridal label. The management question is not whether to have the structure (the product demands it) but where the structure *lives*: in a workbook applied from memory, or in a system that applies it identically on every order.

Per-retailer terms: one list price, many real prices

The wholesale price on the line sheet is the list price. What each stockist actually pays is that number passed through their terms:

  • Trade discount — the negotiated percentage off list that rewards volume, loyalty or strategic value. Ten boutiques can hold ten different discounts, all legitimate.
  • VAT treatment — domestic accounts priced VAT-inclusive or ex-VAT, export accounts zero-rated; every figure on the invoice changes with the setting.
  • Payment terms — pro-forma, deposit-and-balance or account terms don't change the price, but they change its cash value; a price on 60-day terms is not the same money as a price paid up front.

This is where wholesale pricing stops being a formula and becomes a system, because the combinations multiply: per-size matrix × options × discount × VAT treatment, per boutique, per order, forever. Applied by hand, that arithmetic is a standing invitation to inconsistency — the same gown priced three different ways in one month, each version defended by a different email thread. We have written before about what a trade pricing engine has to get right: one set of rules, computed server-side on every order, reconciled against the original workbook to the penny. However you implement it, the standard is the point — a wholesale price only functions as a price if everyone computes it identically.

The pricing mistakes that recur

  • Pricing from cost alone. Cost-up with no retail-down check produces ranges that are internally profitable and externally unsellable.
  • Forgetting the label's own overheads. The multiplier has to fund photography, trade shows, agents, sampling, carriage and the founder's time — not just the factory invoice.
  • Underpricing to win the first stockists. Prices ratchet: lifting a wholesale price on an existing account is one of the hardest conversations in the industry. Launch at the price the business needs.
  • A "from" price hiding the structure. Buyers who stock structured product expect the matrix and the options table; hiding them reads as either naivety or a trap.
  • Discounts as improvisation. A discount given once in an email becomes a precedent forever. Set terms per account, write them down, and let the paperwork apply them — the money mechanics of wholesale covers the terms side in depth.
  • Letting stale price lists circulate. Every emailed price list is a snapshot that ages. The version problem is solvable with discipline — or structurally, by making the current price list the only one a buyer can order from.

Keeping the price honest at order time

A closing observation from the trenches: most wholesale pricing failures are not strategy failures but *application* failures. The strategy was fine; the arithmetic on a Thursday afternoon was not. The gown was priced from January's list, the curve surcharge was forgotten, the discount was applied after VAT instead of before.

That is an infrastructure problem, and it has an infrastructure answer: let the system that takes the order compute the price. On Labels.io, the pricing engine holds the size matrices, option charges, surcharges and each stockist's discount and VAT treatment, prices the order live as the boutique builds it, and recomputes it server-side at submission — so a buyer can never order from a stale number, and two boutiques with different terms each see exactly their own price. When Jane Aston Bridal moved a hundred-style range across, the acceptance test was blunt: the platform's totals against the original workbook, to the penny.

Set the strategy with the formulas above. Then take the Thursday-afternoon arithmetic out of human hands.