How do I set up supply chain planning software for long lead times and style-color-size complexity?

Setting up supply chain planning software for long lead times and style-color-size complexity usually comes down to making sure the system can plan at the right level of detail, with the right time buckets, and with realistic assumptions about demand, supply, and inventory.

Here’s a practical setup approach:

---

1) Define the planning hierarchy

For style-color-size businesses, you usually need at least these levels:

• Style: the main product concept
• Style-color: a sellable variant
• Style-color-size (SKU): the inventory and orderable unit
• Optionally:
  • Style-color-size-location
  • Style-color-size-channel

Use the hierarchy consistently across:

• Demand planning
• Supply planning
• Inventory planning
• Replenishment
• Allocation

If your software supports it, plan at a higher aggregation level for forecasting and lower level for fulfillment.

---

2) Set planning horizons to match long lead times

Long lead times require a longer planning horizon than normal retail/consumer goods.

Typical setup:

• Forecast horizon: 12–24 months
• Supply horizon: at least the full lead time plus review cycle plus buffer
• Frozen window: protect near-term orders from frequent changes
• Planning buckets:
  • Weekly for near-term
  • Monthly for mid-term
  • Possibly quarterly for very long-term capacity or raw materials

Example:

• Raw material lead time = 20 weeks
• Production lead time = 8 weeks
• Transit/customs = 4 weeks
• Buffer = 4 weeks

Then you need to plan many months ahead before demand hits the shelf.

---

3) Use the right forecast level

Do not forecast every SKU independently unless volumes are high and stable. In style-color-size businesses, forecast at a level where demand is more statistically reliable, such as:

• Style
• Style-color
• Style-family/category

Then use:

• Allocation rules
• Size curves
• Color splits
• Channel splits
• Historical mix

to distribute demand down to SKU level.

This avoids noise from sparse SKU history.

---

4) Build and maintain size/color curves

For style-color-size complexity, you need explicit assumptions for how demand breaks down.

Examples:

• Color mix by style
• Size curve by style-color or category
• Channel mix by style

Best practice:

• Calculate curves from history
• Allow planners to override them
• Store them by season, region, and channel if needed
• Refresh them periodically, but not so often that they become unstable

If styles are seasonal, use season-specific curves.

---

5) Model lead time components separately

Long lead times are usually not one number. Break them into components:

• Sourcing / material lead time
• Manufacturing lead time
• QA / inspection
• Transit time
• Customs / import clearance
• DC receiving / putaway

This helps you:

• identify bottlenecks
• calculate realistic order release dates
• set better safety stock
• improve exception management

---

6) Configure safety stock and order policies carefully

For long lead times, safety stock is critical.

Set policies by:

• SKU or style-color-size
• Service level target
• Demand variability
• Lead time variability
• Replenishment frequency

Common methods:

• Min/max
• Days of supply
• Statistical safety stock
• Reorder point + reorder quantity

For complex assortments, it’s often better to maintain safety stock at a higher level and allocate to SKUs based on demand mix.

---

7) Use pegging and supply allocation logic

You need the software to show where supply is committed and what demand it covers.

Configure:

• Demand pegging: which forecast/order consumes which supply
• Supply allocation: priority rules for limited inventory
• Substitution rules:
  • size substitution
  • color substitution
  • channel substitution
  • style substitution if allowed

This is especially important when supply is constrained and late.

---

8) Separate new product planning from replenishment

Long lead time and style-color-size businesses often have:

• New product introduction (NPI)
• Core replenishment
• Seasonal buy
• End-of-life / markdown planning

These should not all use the same logic.

For NPI:

• Use analog styles
• Use launch curves
• Plan inventory before demand history exists

For core items:

• Use actual sales history
• Replenishment rules
• Service-level-based inventory

For seasonal items:

• Buy plans
• Commit quantities earlier
• Freeze decisions closer to launch

---

9) Set up exception-based workflows

Your planners should not inspect every SKU equally. Set alerts for exceptions like:

• Projected stockout before next supply receipt
• Purchase orders inside the frozen zone
• Demand spikes beyond threshold
• Late supplier acknowledgments
• Inventory imbalance across sizes/colors
• Low forecast accuracy at style level
• Excess inventory against sell-through targets

This makes the system usable at scale.

---

10) Clean and master your item data

Style-color-size planning fails quickly if item data is messy.

Make sure master data includes:

• Style, color, size attributes
• Pack/case configuration
• MOQ / order multiples
• Supplier and source
• Lead times by source
• Cost and price
• Lifecycle dates
• Season
• Channel eligibility
• UOM conversions

Also ensure:

• consistent SKU naming
• no duplicate variants
• valid parent-child relationships
• lifecycle status controls

---

11) Start with a pilot

Don’t roll out to everything at once.

Pilot with:

• one category
• one region
• one supply source
• one season

Then validate:

• forecast accuracy
• service levels
• inventory turns
• buy accuracy
• planner workload

Adjust the hierarchy and parameters before scaling.

---

12) Measure the right KPIs

For this type of planning, track:

• Forecast accuracy by style and SKU
• Bias
• Fill rate / in-stock rate
• Stockouts
• Inventory weeks of supply
• Overstocks and aged inventory
• Purchase order adherence
• Lead time reliability
• Size-run completeness
• Sell-through by season

---

Common pitfalls to avoid

• Forecasting every SKU with too little history
• Using one generic lead time for all products
• Ignoring size curves
• Not modeling color/size substitutions
• Planning too close to demand
• Not separating new product and replenishment logic
• Too much manual override without governance

---

A simple target architecture

A good setup often looks like this:

1. Forecast at style or style-color
2. Apply color and size curves
3. Convert demand to SKU-level requirements
4. Net against inventory and open supply
5. Apply lead times and safety stock
6. Generate buy/production orders
7. Use exception alerts and planner overrides

---

If you want, I can also give you:

1. a sample configuration checklist,
2. a data model for style-color-size planning, or
3. an example process flow for long lead-time apparel/footwear planning.