Pattern / Modules / Item Planning
Module · Planning

A line plan for every style, down to the store.

Item Planning auto-generates a rolling, bottom-up plan for every style at store level, 18 months forward. Planners review and refine by exception, not by hand, then push finalised buy quantities straight into Assortment Studio.

18 months forward, rolling Planned at store level, rolled up to clusters One click into Assortment Studio
Pattern · Item Planning · Outdoor Equipment · Rolling 18MLive on your data
Sales vs MFP target
94% on track
Steer · replen budget
R 6.8M headroom
Stock turn · annualised
5.12 +0.4 vs LY
Stock low · 3Stock high · 5Sales low · 2Sales high · 4
StyleStoresAWS · predAWS · planFwd coverOn order
Trail Puffer Jacket1423183409.4 wks12,400On plan
2L Hiking Flask18620520521.7 wks8,200Stock high
Merino Crew Tee1644526106.1 wks15,900Sales high
Camp Chair Pro981241243.2 wks0Stock low
Alerts filter the grid · totals track the live filter · grid or gallery viewPlan · Send to Assortment Studio · Order by size
Our philosophy

A line plan shouldn't be built by hand. The system drafts every number; planners approve, steer and manage the exceptions.

The Pattern approach

For planners

The engine predicts stores, weekly sales and receipts for every style; planners simply approve, or override at the level they choose. Alerts surface the handful of plans that need attention, so the day is spent on exceptions, not data entry.

For merch leadership

An independent, bottom-up sense-check against the top-down MFP, with a live steer showing how the range builds against the core and replen budget. Over-commitment is caught while the range is being built, not at range review.

For the exec

Stock turn annualised and unit-based, GP% at a glance, and buys phased across the season instead of one or two large commitments. An 18-month forward view your suppliers and own manufacturing can actually plan against.

Capabilities

The system plans, the planner approves.

Everything needed to build and maintain a living line plan for every style in the catalogue, in one governed surface.

Auto line plan forecasting

Pattern generates and maintains the full plan at the lowest level, style by store. Review and override at whichever level makes sense: total, store or style, with the system's suggestion always visible beside yours.

Exception management

Four style alerts, stock low, stock high, sales low and sales high, surface the plans that need review across the whole business. Stores that can't clear their minimum are cut from the plan, not pushed token stock.

A rolling 18-month horizon

Eighteen months forward, always, plus trailing actuals and a full last-year comparison. Quarter grain across the horizon, with month and week detail where it counts: the trading quarters ahead.

One tool, both worlds

Replenishment-driven core and equipment lines and faster-moving fashion planned in the same model, with the workflow fitted to each. One data model, one process, no parallel spreadsheets.

Balance to targets

Full balance-set totals, sales, inflow, cover, sell-off rate, stock turn and GP%, tracked live against MFP targets, with confirmed on-order from your procurement system shown beside planned inflow.

One-click push to Assortment Studio

Store-level plans roll up to your assortment clusters automatically. Choose the months to send, see the status of each before it goes, and confirm any override. No re-keying, no exports.

Outcomes

What a living line plan is worth.

Item Planning is configured to your stores, your suppliers and your planning rhythm, then measured on the outcomes that move cash, margin and range quality.

01
Cash flow phased, not front-loaded

With no forward line plan, categories get bought in one or two large annual commitments. An 18-month rolling view lets buys phase across the season, and gives suppliers and your own manufacturing a demand picture they can plan production against.

How Pattern does it
  • Receipts planned by month and store across a rolling 18-month horizon
  • Supplier minimums and shipping windows planned for, not discovered at order time
  • Forward demand visible far enough out to drive production planning
What it drives
  • Phased intake and steadier cash flow
  • A forward book suppliers can commit to
02
A range where every style earns its place

A line plan naturally forces a realistic, culled range instead of a catalogue that only ever grows. Stores that can't sell a style are excluded from the start, and new models launch as the old sells through, not on top of it.

How Pattern does it
  • Predicted weekly sales per store, checked against each store's own minimum threshold
  • Launch month and life cycle planned per style, with sell-through visible ahead of the transition
  • Size-level order recommendations built from cleansed, full-price demand
What it drives
  • Fewer, deeper, better-timed buys
  • Cleaner model transitions, fewer forced markdowns
03
A bottom-up plan the top-down can trust

The line plan is an independent, bottom-up build that sense-checks the MFP rather than blindly obeying it. A live steer shows how the working range tracks against the core and replen budget as every style is added, so over-commitment surfaces months before range review.

How Pattern does it
  • Totals tracked as a percentage of the matching MFP target, live under any filter
  • Steer and variance against the core and replen budget recalculate as styles are added
  • Confirmed on-order from procurement shown beside planned inflow, so the plan and the order book reconcile
What it drives
  • Over- and under-commitment caught early
  • A plan and an order book that agree
The shared foundation

Built on the Pattern Engine.

Item Planning is not a forecasting spreadsheet with a database behind it. It is assembled on the Pattern Engine, which is why every number starts system-generated and every hand-off is native.

1

Store-level prediction: the engine forecasts average weekly sales per store, per quarter, and includes only the stores that clear their own minimum threshold.

2

Cleansed demand-by-size curves, built only from weeks with the full size range in stock at regular price, so clearance noise never skews the size order.

3

Store-to-cluster roll-up: plans are built at store level, then rolled up to your assortment clusters for the hand-off to the buy.

4

Shared constructs: the same clusters, optimums and size curves that Assortment Studio and Allocations use, so a plan made here is understood everywhere.

05

Configured Workflows

Tailored to how you trade

04

AI Intelligence

Forecasting & reasoning

03

Retail Science Engines

Optimisation engines & methodologies

02

Data Foundation

Single extendable model, built for high-volume SKU retail

01

Data Ingestion

Any source system

Connected modules

The bridge from plan to buy.

Item Planning sits between the financial plan and the assortment, turning targets into a style-by-store build that the buy inherits directly. All modules draw from the same single source of truth.

← What flows in

Sales and inflow targets at subclass level, the benchmark every line plan is sense-checked and steered against.

Data foundation

Daily sales, stock and receipts by store, plus confirmed on-order from your procurement system, shown beside planned inflow.

Platform constructs

Clusters, optimums and size curves, the same definitions Assortment Studio and Allocations already use.

What flows out →

Finalised buy quantities, rolled up from store level to cluster, pushed in one click with per-month status checks.

Plan versus actual at style and store level, feeding in-season tracking and stock-health intelligence.

Deliberately, only via the buy. The line plan shapes the order, while live allocation maths stays real-time and is never locked to a months-old receipt plan.

See it on your own data

Every style planned, before the buy is committed.

See Item Planning running on your own styles and stores in weeks, not months.

Next module · Assortment Studio →