Assortment planning in fashion

What is Assortment planning in fashion?

Assortment planning is the process of deciding which products enter an offer for a specific season, period, store, or channel and how they are composed. The plan moves from a broad product intention to buyable decisions: styles, colors, sizes, options, and quantities. Its boundary with collection planning is one of focus: collection planning organizes the product proposal; assortment planning decides which combination will be offered in each commercial context.

Retail Dogma describes the plan as a guide for buyers applying the buying budget. That places it alongside line planning and open to buy, but does not make them synonyms. The budget answers how much can be invested; the assortment answers which options and depths will receive that investment.

How does the process turn intent into a mix?

Start by naming the period, channel, and destination: a store, store group, ecommerce site, or another sales channel. The team can then organize the mix by category, style, color, and size. “Breadth” indicates how many different options enter; “depth” indicates how many units are planned per option. Keeping the decisions separate prevents a collection from looking broad merely because it accumulates variants, or deep merely because it concentrates units in a few styles.

Oracle describes fashion assortment planning as assigning seasonal styles to stores and channels, with a combination of styles, sizes, and colors suited to the destination. Its documentation also links assortment period, product, and store group—or cluster—and separates short-life-cycle and long-life-cycle items. In practice, this supports a destination-level view containing option, color, size range, depth, and a stated life-cycle hypothesis.

Sales history is an input, not an automatic answer. Oracle highlights several years of sales data and product attributes; a team still needs to record what changed between periods: price, availability, presentation, calendar, and channel. For a new category, keep the hypothesis explicit rather than presenting it as an observed fact.

How does it apply to stores, ecommerce, and clusters?

The plan becomes useful when every decision states where and when it applies. A retail network may use a store group with similar characteristics as a starting point, but a cluster does not remove the need to check each destination’s capacity, customer, presentation, and availability. In ecommerce, depth may depend on central availability and delivery promise; in a physical store, it also has to fit presentation and receiving constraints.

The relationship with assortment allocation comes after the mix decision: first decide which options belong to the set, then distribute units to destinations. Product-mix architecture helps name categories and roles, while color and size connect a style to its sellable SKU. The result should reach buying and replenishment with the unit clearly defined: an option, piece, case, and value are not the same denominator.

Which limits need control?

Assortment planning is not demand forecasting, buying, or allocation. It may use a forecast, guide a purchase, and feed an allocation, but each stage answers a different question. It also does not guarantee sales, margin, or inventory turn: the plan is a decision under uncertainty and depends on data quality and channel execution.

Review should compare planned and observed values without mixing options, units, and sales. A price change, stockout, or promotion can change how a style reads; returns and transfers need their own rules. Record the plan version, assumption, owner, review date, and decision for each exception. This lets the team distinguish a breadth choice from a depth choice and review sell-through without turning a local result into a universal benchmark.

Connections

collection planning · assortment allocation · product mix · size range · open to buy · line plan · sell-through