Fashion Wholesale Size Run Ordering: Curves, Prepacks & Matrix Grids

Fashion wholesale size run ordering is how apparel and footwear brands let retailers buy a style across sizes and colourways without ending up with unusable, incomplete assortments. Done well, it protects sell-through on the shop floor. Done poorly, it creates broken size runs, awkward leftovers and slow reorders.

This guide explains size curves, prepacks, case packs and matrix grids as catalogue and ordering design choices—not software jargon—so Nordic and wider EU brands can ship assortments retailers can actually sell.

What is fashion wholesale size run ordering?

Fashion wholesale size run ordering is the practice of structuring B2B orders so each style and colourway is bought as a coherent set of sizes rather than as random unit picks. A size run is that full, sellable set of sizes for a given style–colourway. A broken size run is what you get when key sizes are missing, oversold or never ordered—leaving the retailer with a rack that does not fit enough customers.

In wholesale, the size run is rarely left entirely to chance. Brands encode expected demand as a size curve (also called a size ratio), then expose that logic through prepacks, case packs, minimum order quantities (MOQs) and matrix order grids. EU retailers buying across borders still need the same clarity: which sizes exist, how they pack, and what must be ordered together.

balanced row of footwear in ascending sizes on a simple shelf

How do size curves and size ratios work for apparel and footwear?

A size curve (or size ratio) is the planned distribution of units across sizes for a style or category—for example more medium and large than extreme ends of the range. It is not a universal law; it is a demand hypothesis shaped by product type, fit, market and history.

Apparel curves often peak in the middle of the labelled range. Footwear curves can shift by last, gender and region, and half-sizes add more SKUs. Brands typically maintain separate curves by category (tees vs outerwear, sneakers vs boots) and refine them with sell-through and returns feedback—not with one global ratio.

Practical uses of the curve:

• Building prepacks and case packs so factory and warehouse cartons mirror sellable mixes
• Setting default quantities in a matrix ordering grid so buyers start from a sensible assortment
• Guiding MOQs at colourway or pack level instead of only at style level
• Explaining to retailers why open picking of single sizes is limited in early season

Keep curves written down, versioned by season, and shared with sales and warehouse teams. A curve that only lives in one planner’s spreadsheet will not survive prebook pressure.

What is matrix (grid) ordering and when should brands use it?

Matrix ordering (order grid ordering) is a catalogue pattern where the buyer sees a table—sizes across one axis, colourways or deliveries across the other—and enters quantities in the cells. Each cell maps to a SKU / variant (style + colourway + size, sometimes with length or fit).

Use matrix grids when:

• The buyer needs visibility of the full size run per colourway
• You sell many colourways of the same silhouette
• Open-to-buy decisions are made at assortment level, not one SKU at a time
• Sales reps and retailers both need the same structured view

Grids work less well when every size is sold only inside fixed prepacks, or when at-once stock is so thin that most cells should be blocked. In those cases a pack-first UI with optional open sizes is clearer than an empty-looking matrix.

Pair the grid with honest availability. A beautiful matrix that accepts orders for sizes you cannot ship simply moves the broken-run problem into fulfilment.

clean apparel colour-and-size order grid as abstract blocks

How do prepacks and case packs reduce broken size runs?

A prepack is a fixed assortment of sizes (and sometimes colourways) sold as one orderable unit. A case pack is the warehouse or factory carton configuration—often aligned with the prepack, sometimes a multiple of it. Both exist to stop buyers from cherry-picking only the fast sizes and leaving the brand with orphan inventory.

How they help:

• They hard-code the size curve into the unit of sale
• They speed picking and reduce packing errors versus loose size picks
• They make MOQs meaningful (order N packs, not N random units)
• They give smaller EU retailers a complete mini-run without deep open-stock commitment

Trade-offs to state clearly on the line sheet: prepacks reduce flexibility; retailers with atypical customer bases may need an exception path or a second pack ratio. Footwear brands often mix pair-prepacks with limited open sizes for refill of hero sizes—document which path applies per season.

Strong SKU management for variants and case packs is the backbone: each pack needs its own identity, contents list and barcode logic, not only the loose size SKUs inside it.

How should EU brands present size runs in a B2B catalogue?

EU retailers buy under time pressure and across languages. Present size runs so the assortment rules are obvious before the order is typed.

Include on the catalogue and what to include on a wholesale line sheet:

• Size scale used for the product (and any market-specific labels you map to)
• Which colourways are active for the delivery
• Whether the item sells open size, prepack only, or hybrid
• Pack contents and pack MOQ versus unit MOQ
• Delivery window (prebook versus at-once) and cut-off
• Clear “available / limited / closed” state per size when stock is finite

Size labels differ by market and product type; brands still need one internal size code per variant and a consistent way to show the retailer’s familiar label. Ambiguous “M/L” dumps without a defined scale create wrong-size orders and returns.

For wholesale for fashion brands selling cross-border, keep currency, VAT treatment and pack rules next to the grid so the buyer is not reconstructing policy from email threads.

What rules stop retailers from ordering incomplete assortments?

Rules beat reminders. Define them at catalogue level, then enforce them at order entry:

• Minimum pack quantities per colourway before a style can ship
• “Full run or defined core run” requirements on key doors
• Blocked cells for sizes not produced or not in the delivery
• MOQs that count packs, not only loose units
• Optional max caps on extreme sizes so the curve is not inverted
• Account-level exceptions that are explicit, not silent overrides in email

A branded B2B storefront can enforce clean size-run and prepack rules at order entry so EU fashion retailers self-serve complete assortments instead of negotiating every grid by spreadsheet. If you want to see how that workflow looks in practice, book a demo.

sealed carton of folded garments packed as a matched size assortment

How do prebook vs at-once seasons change size-run strategy?

Prebook (advance) seasons favour locked curves: production is planned from wholesale orders, so prepacks and firm matrix minimums protect the factory mix. At-once (immediate) seasons favour availability truth: open sizes matter more, broken runs appear when warehouse stock diverges from the original curve, and replenishment should prioritise completing runs already in stores.

Operational differences:

• Prebook: publish pack architecture early; limit one-off size exceptions; align sales targets to packs
• At-once: show real-time size availability; offer completion packs for doors missing sizes; be strict on backorder promises
• Transition: when prebook leftover becomes at-once stock, revisit MOQs so odd sizes are not sold in isolation

For a deeper seasonal framing, see prebook vs at-once ordering for Nordic brands.

How do SKU variants, GTINs and case packs support clean size runs?

Each sellable size–colourway combination is a SKU (variant). Each needs stable identification so orders, cartons and invoices refer to the same thing. A GTIN identifies trade items at the unit and higher packaging levels; case packs that ship as trade units need their own identification distinct from the single pair or garment inside.

Clean master data supports size runs when:

• Variant attributes (style, colourway, size, fit) are structured, not buried in free-text names
• Prepacks list component SKUs and quantities
• Unit and case GTINs are allocated consistently and printed on the right labels
• The order grid and the warehouse both read the same pack definitions

Messy codes are how “two mediums and a mystery carton” enter the ledger. Follow a deliberate GTIN setup for units and cases before peak ordering, not during it.

What operational checks keep fill rate high after size-run orders?

Fill rate here means how completely you ship what the retailer ordered in the sizes they need. Size-run orders fail quietly when one missing size cancels the commercial value of the rest of the colourway.

Checks that help:

• Promise only sizes you can allocate across the run, not cell by cell in isolation
• Prioritise picking complete colourway runs for priority accounts when stock is short
• Separate cosmetic short-ships (labels, polybags) from true size shortages in claims handling
• Feed returns and size-level sell-through back into the next season’s curve
• Keep cut-offs and order confirmation content explicit about substitutions and partials—substituting a different size without agreement recreates broken runs downstream

Warehouse and portal views should match. If sales can order a size the WMS already knows is gone, fill rate becomes a dispute process instead of a metric.

Bringing the assortment together

Size curves decide the shape of demand you plan for. Prepacks and case packs industrially encode that shape. Matrix grids make it visible and editable for buyers. Catalogue rules, MOQs and honest availability decide whether EU retailers receive a sellable assortment or a partial that sits on the back rail.

Treat fashion wholesale size run ordering as assortment design plus order-entry discipline. When those stay aligned, retailers reorder with confidence—and your leftover inventory looks like a plan, not an accident.

Ready to tighten how retailers order complete runs? Book a demo or see pricing.