Assortment Planning Template That Actually Works

The Q3 buy review starts with a familiar file named Q3_Assortment_FINAL_v7. Merchandising has changed the color mix, planning has adjusted unit depth, wholesale has added a commitment, and the buyer has flagged a supplier delay in a chat thread nobody else can find. By the time finance opens the workbook, the team isn't reviewing a plan. They're reconstructing one.

A useful assortment planning template should do more than list styles, colors, and units. It should show how each product is identified, priced, allocated, sourced, approved, and changed when demand or supply moves. The practical standard is a shared planning record that connects line architecture with commercial decisions and operational constraints, without turning every seasonal review into spreadsheet archaeology.

Why Your Assortment Planning Template Needs More Than a Spreadsheet

By Tuesday morning, the fashion team has three versions of the same assortment file. One planner has updated retail prices, another has reduced a colorway, and the wholesale manager has added committed units in a separate copy. Everyone believes their file is current because each version contains recent work.

The conflict appears during the buy review. A style looks profitable in one workbook because it uses the old cost. In another, its color count is lower. A late substitution appears in a message thread, but not in the file used for the margin discussion. Nobody can confidently answer which units are available to which channel.

Where flat files break

A flat spreadsheet fails because it treats a line as a description rather than a connected decision. The style number, color, size scale, supplier, price, channel allocation, and commitment status need to remain tied together when someone changes one of them.

That requirement reflects how assortment planning has matured. The process began as the selection of products carried in each store, constrained by budget, space, and operating limits, then moved toward quantitative planning based on historical demand, product attributes, and store clustering. Fashion teams now need the same structure across seasonal styles, colors, sizes, channels, and locations. The research reference on assortment planning as a data-driven retail process documents that shift and notes that seasonal decisions typically use at least 2 to 3 years of sales history.

Generic templates usually respond by adding columns. Soon the file contains fields nobody owns, duplicate calculations, hidden filters, and free-text values such as “DTC,” “Direct,” and “E-comm” for the same channel. More columns don't create control. They create more places for a decision to disappear.

Practical rule: If a buyer can't trace a unit from parent style to channel, supplier, and scenario, the template isn't yet a source of truth.

Build a connected planning record

Use one row per style/color line for the commercial plan, then connect child SKU detail for size and inventory execution. Keep approvals, exceptions, and scenario changes in visible fields rather than leaving them in email or chat.

A directory such as the Procright vendors index file can help teams organize vendor references, but vendor discovery isn't a substitute for recording supplier constraints inside the assortment file. The template still needs to show who supplies the line, what can be booked, and which alternative applies if the original plan fails.

This is also why teams should evaluate workflow tools alongside spreadsheets. A comparison of assortment planning software is useful when several functions need to review the same lineup without creating another chain of emailed attachments. The tool matters less than the operating rule: one controlled record, clear ownership, and a visible history of what changed.

The Core Columns Every Assortment Planning Template Should Have

Start with the row structure, not the colors or formatting. The most reliable template separates identifiers, product attributes, commercial inputs, supply inputs, and tracking fields, so each column answers one operational question and has an accountable owner.

Block one, identifiers

These fields prevent duplicate products and broken joins:

• Style number: The brand's durable style identifier, not a descriptive nickname.
• Parent SKU: The shared identifier connecting color and size variants.
• Colorway code: A controlled code that matches the product lifecycle management system.
• Size scale: The intended run, such as a standard apparel scale or a category-specific range.
• Season and drop: The planning window and delivery moment attached to the line.

Naming discipline matters here. Use the same logic across PLM, ecommerce, wholesale documents, and the assortment file. The guidance in product naming conventions and best practices is relevant because inconsistent names create duplicate records long before inventory reporting exposes them.

Block two, product attributes

Record the information that explains where the style belongs:

• Category and subcategory
• Fabric or material
• Target fit
• Collection
• Hero, core, or long-tail tier
• Fit sample status and photo sample status

Fit and photo sample fields are often omitted because they don't affect the first margin calculation. They affect whether the team can launch the product as planned. A line without an approved fit sample can create a late technical change, while a line without a photo sample can delay ecommerce content and wholesale selling.

Block three, commercial inputs

Include planned retail price, wholesale price, cost, target margin, launch window, channel intent, planned units, planned sales, and markdown or exit status. Auto-calculate margin from price and cost rather than allowing planners to overwrite the result manually.

The channel fields should separate intended allocation from actual commitment. DTC, wholesale, and marketplace plans can sit beside store or ecommerce splits, but they shouldn't be collapsed into one vague “channel” field. The template should make it possible to compare the total buy with the units already promised.

Block four, supply inputs

Add supplier, country of origin, MOQ per color, MOQ per style, lead time, payment terms, minimum replenishment threshold, and alternate supplier or factory. These columns convert a desirable line into a bookable line.

Block five, tracking fields

Finish with forecast units, actual orders, commitment status, pricing approval state, scenario version, owner, last updated date, and notes. Use dropdown validation for statuses such as Concept, Sample, Priced, Confirmed, On Hold, and Phased Out. Lock header rows, protect formulas, and prevent free-text drift before the first review.

Setting Up Colorways, Size Runs, and Channel Splits

A parent style tells the commercial story. Child SKU rows make the plan executable. Keep both in a linked structure rather than putting colorways on one tab, sizes on another, and channel commitments in a third place that someone has to reconcile manually.

Consider a women's woven top with one parent style and three colorways: Ivory, Navy, and Terracotta. If the planned size scale runs from XS to XL, the style creates 15 child rows, one for each color and size combination. The parent row can hold the collection, category, retail price, and launch window. Each child row should carry the colorway code, size, planned units, channel split, and supply exception.

A practical row design

Use fields such as:

Field	What it should hold
Parent style	The shared style identifier
Child SKU	The unique color and size combination
Colorway	Controlled name and code
Size	One size value only
Channel split	Planned allocation across DTC, wholesale, and marketplace
Committed units	Units already accepted by a channel or account
Size exception note	Reason for a nonstandard run
Inventory status	Planned, booked, received, or blocked

The percentage split should describe the allocation logic, while committed units should show the hard obligation. Those are different decisions. A planner might intend to allocate across three channels but have confirmed units only for wholesale, leaving the remaining quantity flexible for direct ecommerce demand.

Handle exceptions visibly

Suppose Navy carries the full XS to XL run, while Ivory drops XS and Terracotta drops XL to protect margin or simplify production. Don't delete those child rows without explanation. Mark the unavailable combination with a size exception note and an explicit status, such as Not Planned or Supplier Constraint.

That detail protects reporting. If the row disappears, the team may interpret the missing size as a data error rather than a deliberate assortment decision. It also helps merchandising explain why the colorway has a different customer promise from the core run.

Keep colorway names synchronized with PLM and catalog systems. “Terracotta,” “Terra,” and “Rust” may describe the same visual idea, but they can create separate records when systems rely on exact text matching. A product catalog management workflow, including the capabilities described in product catalog management software, can support consistent product records across channels. The template should still enforce the approved values through validation lists rather than relying on memory.

Planning Levers the Template Must Support

Every line decision has three separate dimensions: breadth, depth, and service level. Teams get into trouble when a planner changes one lever while the other two remain hidden.

Breadth is the number of styles, colors, or options offered. Depth is the unit commitment behind each SKU. Service level is the inventory availability you intend to provide against demand. The template should surface all three beside the line, not bury them in separate planning views.

Lever	Template Field	Primary Metric	Common Failure When Ignored
Breadth	Style count, color count, option status	Coverage by category or collection	Too many options create complexity and dilute receipts
Depth	Target units per SKU, size-run units	Sell-through, weeks of supply, margin	Strong styles stock out while weak styles remain overbought
Service level	Replenishment flag, minimum threshold, availability target	Fill rate against demand	The team protects margin by cutting units, then misses customer demand

Breadth controls choice

A six-color jacket may look more compelling than a four-color jacket during line review. But breadth consumes development, sampling, content, purchasing, and inventory attention. If the team cuts the jacket from six colors to four, the template should show the reduced option count and the resulting unit change on the same view.

Depth funds availability

The four remaining colors may receive deeper unit commitments. That doesn't automatically solve the problem. The planner still needs to see size-level depth, supplier feasibility, and channel demand, because adding units can collide with MOQ or lead-time constraints.

Service level protects the customer promise

A replenishment flag should trigger when a style approaches its minimum threshold or when demand exceeds the planned curve. It shouldn't be a vague “reorder?” note. Include the threshold, owner, expected supplier response, and scenario effect so the team can decide whether to reorder, transfer, substitute, or allow the style to sell down.

The operating tension becomes clearer when teams explore alternatives such as what manufacturing on demand means in fashion. On-demand models may change the depth decision, but they don't remove the need to define breadth, service expectations, or supplier feasibility.

Running a Seasonal Planning Cycle With the Template

A seasonal template works best as a workflow log. Each gate should have named inputs, a decision owner, and an output that becomes the starting point for the next gate.

Start with hindsight

Load prior-season sell-through, returns, and margin by SKU into a read-only history tab. Flag every style below 60 percent sell-through for phase-out, using the supplied assortment planning template reference for the role of sell-through and margin in line decisions. The history tab should preserve the original values, while the working tab records the decision and rationale.

The output is a clean list of exits, carryovers, and candidates for deeper investigation. Don't overwrite history with the new season's assumptions.

Build the line architecture

Lock the total style count before the team gets lost in individual color debates. Set family-level unit budgets and assign each style a tier, such as hero, core, or long-tail.

The inputs are category strategy, prior performance, customer coverage, and financial guardrails. The output is a controlled skeleton with space for newness, continuity, and planned exits.

Build the buy

Populate colorways, size runs, channel splits, prices, costs, supplier lead times, MOQs, and risk flags row by row. Require each line to move through visible statuses from concept to priced, approved, and confirmed.

The output is a bookable assortment rather than a wish list. Missing fields should block confirmation, especially cost, channel intent, supplier, and commitment status.

Freeze and negotiate

Freeze the review version before sending it to planning, merchandising, finance, and buying. Create a scenario copy for supplier negotiations so proposed changes don't overwrite the approved baseline.

A structured system may use dedicated assortment headers, store clusters, product-store combinations, forecasts, price inputs, and weekly assortment periods, as described in Oracle assortment planning documentation. Even when the working tool is a spreadsheet, that principle is useful. Separate baseline, scenario, and execution data instead of placing every assumption in one editable grid.

The video below provides another visual reference for applying assortment decisions across the seasonal process.

Adding Supply Risk and Supplier Flexibility to the Template

Most assortment templates assume every approved line is equally bookable. That assumption fails as soon as a fabric is delayed, a factory misses an MOQ, or a supplier can't reproduce the approved color. Demand and margin still matter, but they don't help if the product can't arrive inside the launch window.

Current planning guidance identifies sourcing uncertainty, tariff shifts, and inconsistent lead times as reasons to build flexible assortments, while also integrating MOQs, lead times, and supplier flexibility rather than treating them as separate procurement details. The 2026 global assortment strategy outlook projects the merchandise assortment management applications market at US$1.4 billion in 2026 and US$2.6 billion by 2033, which signals ongoing demand for more operational planning capability. Those figures are projections from the cited source, not a guarantee of adoption or performance.

Add a supply-risk block

At minimum, include the fields below. Use a controlled scale for risk rather than a long narrative that nobody can sort.

Column	Purpose	Example Value
Supplier name	Identifies the booking partner	Approved Mill A
Factory lead time	Shows production exposure	75 days
MOQ per color	Tests color-level feasibility	120 units
MOQ per style	Tests total booking feasibility	360 units
Country of origin	Supports sourcing review	Vietnam
Payment terms	Shows cash timing	Net terms
Supplier rating score	Records internal confidence	Medium
Minimum reprint quantity	Tests reorder flexibility	80 units
Color substitution allowed	Shows recovery option	Yes
Alternate factory	Provides fallback route	Factory B
Scenario rollback ID	Restores the prior plan	Q3 Base

The example values above are illustrative field entries, not external facts or benchmarks. Replace them with your own supplier terms.

Make vulnerability sortable

Add a bookability score that combines MOQ feasibility with lead-time risk. The exact formula should match your team's risk model, but the output must help planners sort the line from most vulnerable to most resilient.

For example, a high-score style might meet its MOQ comfortably, have an approved alternate factory, and fit inside the launch calendar. Keep it in the base plan. A low-score style might require an impractical color MOQ, have no approved substitute, and sit close to the launch deadline. Move it into a rollback scenario with a replacement color or alternate style.

A scenario column is useful only if the team can execute the fallback without rebuilding the entire assortment.

Record the original decision, proposed change, owner, approval state, and rollback path. A static template becomes a planning instrument for volatility rather than a historical list of what the team hoped to buy.

Operating the Template Season After Season

A template stays useful only when the team operates it with discipline. The file or system needs a review rhythm, clear ownership, and a rule for retiring fields that no longer affect decisions.

Establish the operating cadence

Use a weekly review for sell-through exceptions, blocked receipts, supplier changes, and replenishment flags. Hold a fortnightly assortment health check for breadth, depth, channel balance, margin, and risk exposure. At season end, run a retrospective that feeds actual outcomes into the next season's defaults.

The retrospective should update unit-count assumptions, MOQ overrides, supplier-risk scores, size-run rules, and scenario choices. Don't carry a field forward because it existed in the last template. Carry it forward because someone used it to make a better decision.

Assign ownership by decision

The merchandiser owns line architecture, category roles, collection structure, style tiers, and planned option counts. The planner owns volume, channel splits, forecast units, and performance tracking. The buyer owns supplier, MOQ, lead-time, payment, alternate-source, and flexibility inputs.

Finance should own approval of economic guardrails, while ecommerce and wholesale teams should validate channel commitments. One person can hold several roles in a smaller business, but the columns still need explicit owners.

Freeze, name, and audit

Use a naming convention that identifies season, planning stage, scenario, and freeze date. Keep the baseline separate from negotiation copies and execution updates. Never overwrite a frozen review version.

A simple evolution loop works well:

1. Add: When a new constraint affects a decision, add a field, owner, validation rule, and review date.
2. Test: Use the field through a full review cycle and check whether it changes an action.
3. Retire: Remove or archive fields that create maintenance work without influencing a buy, allocation, approval, or exit decision.
4. Document: Keep a short change log so future planners understand why the structure moved.

That governance prevents the assortment planning template from becoming either a fragile spreadsheet or an oversized database nobody wants to maintain. The right design is the smallest controlled structure that preserves the decisions the business must revisit.

---

Sprello offers an assortment visualization workflow for fashion, beauty, and lifestyle teams, helping them review lineups, colorways, size runs, and variants on a shared seasonal canvas. Visit Sprello to see how its reusable workflows can support clearer handoffs between merchandising, design, and marketing as your assortment moves from plan to production.