Sales plan
The document fixes how much revenue and how many units the company will sell by channel, category, season and location, and what the figure is built from. It decides how much to buy and produce, how many people to hire and how much space to rent, because the purchase budget, staffing, rent and production order are all derived from it.
Why this document
The sales plan is the first number on which all the others depend: purchasing, production, warehouse, staff, cash. If it is overstated the company overbuys and cuts prices, if understated it loses sales to empty shelves. That is why it is built from drivers (traffic, conversion, average ticket, store count) rather than taken as last year plus a percentage. The commercial director sets team targets by it, the finance director builds the budget, and the owner sees what to expect in the season.
At a glance
- What is this document and why is it needed?
- The document fixes how much revenue and how many units the company will sell by channel, category, season and location, and what the figure is built from. It decides how much to buy and produce, how many people to hire and how much space to rent, because the purchase budget, staffing, rent and production order are all derived from it.
- Who owns the document and how often is it rebuilt?
- Brand: commercial director and planner, once a season with monthly updates, approved by the owner or the board. Retailer: sales director and category managers, an annual plan split by month and outlet, reviewed quarterly.
- What mistakes are the most common?
- The plan is built from desired growth with no bottom-up → targets do not reconcile and the team fits numbers → keep both versions and show the gap. Sales with VAT in one month and without in another → a false base, and the VAT/price change passes for demand growth → count excluding VAT only and state the rate. Comparing non-comparable periods (different week counts, holidays on other days) → false growth → use the 4-5-4 calendar and LFL.
For whom
- Brand
- Brand sales split into wholesale (preorder and reorders), own retail, the web shop and marketplaces. Wholesale is planned by customer: the preorder order book plus expected in-season reorders; each customer has a limit and a ship window. The trap is mixing shipment (sell-in) with sales to the shopper (sell-out): the factory order is built from sell-in, and brand health at a retailer is read from sell-out.
- Retail
- A retailer builds sales by store: traffic × conversion × average basket, a like-for-like (LFL) base and a ramp curve for new outlets. Online is planned separately: visitors, conversion, buyout rate. The owner target (growth over last year) sits on top, store plans converge from the bottom; the gap between them is discussed openly.
What it consists of
Header and assumptions
- Period, currency, prices excluding VAT: VAT is not part of plan revenue; the rate and the date it changes are stated in the header.
- Assumptions: price growth, FX, inflation, trading weeks under the 4-5-4 calendar, holidays and sale days.
- Base: last-year sales on the same calendar and the list of stores in the comparable base.
- Brand: wholesale by customer: the plan line per customer = Preorder × (1 + reorder) − already shipped; in the Model B example three customers (45%, 35% and 20% of the season wholesale volume of 30,000 units at RUB 2,400 excluding VAT) give RUB 72 million of revenue before returns.
Rows: what is planned
- Channel (wholesale, retail, web, marketplace) → category (women, men, kids, footwear, accessories) → season group → store or wholesale customer.
- New outlets on a separate row: months to maturity and the share of a mature outlet plan.
- Retailer: Seasonal split: month indices (6 season months) 0.82; 0.9; 1.02; 1.08; 1.12; 1.06, mean equal to 1; the monthly store plan = average month × index: for “Mall North” the average month is RUB 35.836 million, by month 29,386, 32,252, 36,553, 38,703, 40,136, 37,986 thousand (the sum equals the season plan). Traffic and check in the split differ by month, not one for all.
- Brand: the sell-in plan from partner sell-out (Model B, wholesale). Sell-in = Sell-out + (Target partner stock − Current stock): sell-out 26,400 units over the season (4,400 a month), target stock of 2 months 8,800, current 11,000: sell-in 24,200 units, while the preorders and the Model B plan are 30,000: the difference of 5,800 units is a risk of overloading partners, a decision for S&OP. The ramp curve of a new store: 70% → 90% → 100% of mature revenue in the first three months.
Columns: months and measures
- Retailer: Months or weeks; for each: revenue excluding VAT, units, receipts, average basket, units per transaction (UPT), traffic, conversion.
- Comparison: last year, planned growth, actual and the deviation in percent and money.
- Share of sales on markdown and the markdown amount: needed for the open-to-buy plan.
Brand and retailer: what is computed differently
- Retailer: a store plan is built from traffic, conversion and check with a seasonal split and the ramp curve of a new store; the top-down target is growth against last year in comparable stores (LFL).
Brand: how the document differs and what to add
- Brand: a brand sales plan has two parts: sell-in (shipments to partners) and sell-out (partner sales to customers); without sell-out a preorder turns into stock at the customer.
- Brand: the base of the wholesale plan is the order book and partner preorders: a confirmed part and an expected one, with probability by customer.
- Brand: plan by channel: wholesale 140 million, site 34 million, marketplace 33 million roubles in Model B; each has its own return rate and payment term.
- Brand: the shipment schedule is tied to the season window: a shift of 2 to 3 weeks moves revenue into another quarter and changes cash.
- Brand: site growth is planned from traffic and acquisition cost: paid-channel traffic is counted separately from organic and repeat purchases.
- Brand: the marketplace plan depends on search positions, platform promotions and stock at the platform warehouse; a stock-out zeroes sales without lowering the plan.
- Brand: plan check: partner sell-through in past seasons; if a partner sells 60% of the shipment, its new-season shipment is not raised.
Retailer: how the document differs and what to add
- Retailer: the retailer plan is built from the store: traffic, conversion, ticket and space; the network is the sum of points, not a general growth percentage.
- Retailer: new stores go in a separate line with a ramp curve; comparable ones are compared with last year on LFL.
- Retailer: the event calendar (sales, holidays, mall promotions) is written into the plan by week: a week without the calendar gives a false deviation.
- Retailer: the retailer online plan is built separately from traffic and returns, and its effect on stores (halo and cannibalization) is counted.
How to read the result and which decisions follow
- The bottom-up plan is below the top-down target by more than 2 to 3 pp of growth (a guide): name closing measures with owners and deadlines or renegotiate the target; do not raise conversion in the model without a reason.
- Store plan growth exceeds traffic and ticket growth together: find the source (refit, assortment, price); without it the growth is not taken into purchasing.
- Actuals are below plan by 5% or more two weeks in a row: revise the season forecast and purchasing while re-supplies can still be stopped.
Control checks
- The sum of stores equals the network plan (RUB 472.044 million against last year 455000); growth is computed from a comparable base.
- Seasonality indexes are normalized (mean equals 1); monthly sales add up to the season.
- Typical traps: growth computed against last year with a different number of stores, price without and with VAT in different cells, sell-in mistaken for sell-out.
Where the data comes from
| Data source | Fields |
|---|---|
| POS and accounting | Receipts for 2-3 years: date, store, SKU, quantity, price, discount. Excluding VAT only. |
| Store traffic counters | Visitors by hour and day; for the web: sessions, add-to-cart, orders, buyout rate. |
| Order book and wholesale CRM | Customer, preorder, shipments, reorders of past seasons, limit, payment status. |
| The “Sales” data template | The common upload format (see the sales template): receipt rows for recalculating the base. |
How to build it step by step
- Step 1. Fix the calendar: 4-5-4 weeks, holidays, collection launch and sale dates. Without it the comparison with last year shifts by weekdays.
- Retailer: Step 2. Clean the history: remove one-offs (a closed store, a single wholesale deal), bring everything to prices excluding VAT.
- Step 3. Set the top-down target: growth over last year from strategy, the profit budget and cash limits. It is a guide, not the plan.
- Step 4. Build the plan from the bottom. Store: traffic × conversion × average basket by month, adjusted by the seasonal index. Wholesale: customer preorder + reorder from history. Online: sessions × conversion × basket × buyout rate.
- Step 5. Add new outlets with a ramp curve and remove those being closed.
- Retailer: Step 6. Reconcile top and bottom: show the gap in money and by store, agree which assumptions change and which stay.
- Step 7. Split by category and season group, check each share against last year and the category role.
- Step 8. Hand over to open-to-buy, headcount, rent and the production order; record the assumptions and the version.
- Step 9. Each month compare plan with actual and update the remaining months (a forecast, not a rewrite of the plan).
Formulas
| Measure | Formulas | Note |
|---|---|---|
| Store revenue | Revenue = Traffic × Conversion × Average basket | Conversion is counted from entries, not passers-by; average basket excludes VAT. |
| Monthly seasonal index | Index = Sales of the month ÷ Average monthly sales of the year (over 2-3 years) | Exclude anomalous months (mall closure, restrictions) and replace with the average. |
| Like-for-like growth | LFL % = (Sales of comparable stores now ÷ the same stores a year ago − 1) × 100 | Details: the LFL document. |
| Wholesale: customer plan | Customer plan = Preorder + Preorder × Reorder share (history) − Contractual returns | Reorders depend on weather and season; keep the coefficient conservative. |
| Top-down vs bottom-up gap | Gap = Top-down target − Sum of bottom-up plans | Close the gap with actions (outlets, promo, assortment), not by stretching conversion. |
Formulas in notation
- Store sales
S = T · c · a
T is monthly traffic, c is conversion, a is average ticket; the season equals monthly sales times the number of months with a seasonality adjustment.- Seasonality index
SI_m = x_m / x̄
x_m is month sales, x̄ is the period mean; indexes are normalized so that their mean equals one.- Plan growth
g = Plan / LY − 1
LY is sales of the comparable period last year; growth is shown by store and in total.- Gap to target
Gap = LY · (1 + t) − Plan
t is the target growth from above; a non-zero gap is closed by specific measures with an owner and a deadline.- Sell-in from sell-out
SI = SO + ΔStock
SO is partner sales (sell-out), ΔStock is the target change of their stock; brand shipments are derived from partner sales, not the other way round.
Worked example
Retailer: a season plan for three stores (6 months), bottom-up and top-down (an independent example: three flagship stores, the average Model R store gives RUB 30.94 million a year)
| Store | Traffic per month | Conversion, % | Basket, RUB | Sales per month, RUB m | Season sales, RUB m | Last year, RUB m | Growth vs last year, % |
|---|---|---|---|---|---|---|---|
| Mall North | 62,000 | 8.5 | 6,800 | 35.84 | 215 | 205 | 4.9 |
| Mall South | 41,000 | 10 | 5,900 | 24.19 | 145.1 | 150 | −3.2 |
| High street | 18,000 | 14 | 7,400 | 18.65 | 111.9 | 100 | 11.9 |
| Total | 121,000 | 78.67 | 472 | 455 | 3.7 |
The owner set growth of 8% on top: RUB 491.4 m. Bottom-up converges at RUB 472 m (3.7%), a gap of RUB 19.4 m. It is closed not by eyeballing conversion but by decisions: a new outlet, a promo with proven payback, a wider assortment. A brand would plan wholesale on the same data: the customer preorder plus a reorder from history (for example 12% of the preorder), checked against the customer limit.
Figures
- Last year
- Season plan
Data as a table
| Measure | Last year | Season plan |
|---|---|---|
| Mall North | 205,000 | 215,016 |
| Mall South | 150,000 | 145,140 |
| High street | 100,000 | 111,888 |
Season plan by store and last year. The plan by “traffic × conversion × ticket × months” against last year: where the plan grows and where it does not.
- positive
- negative
- total
Data as a table
| Step | Change | Level |
|---|---|---|
| Last year | — | 455,000 |
| Mall North | +10,016 | 465,016 |
| Mall South | −4,860 | 460,156 |
| High street | +11,888 | 472,044 |
| Bottom-up plan | — | 472,044 |
| Gap to target | +19,356 | 491,400 |
| Top-down target | — | 491,400 |
From last year to the target: the plan gap. Store growth adds up to the plan, and the difference to the top-down target is a gap closed by new measures, not by rounding.
Specifics by category
- Apparel
- The main volume: temperature-driven seasonality, two main waves (spring-summer, autumn-winter) and end-of-season sales. Forecast by week with a weather adjustment; keep the share of new versus carryover in the plan.
- Footwear
- Sales are in pairs rather than garments; the average basket is higher and UPT is only slightly above one. The season starts 4-6 weeks earlier than apparel. Size-driven returns are higher than in apparel: plan the buyout rate per channel, especially online.
- Accessories
- There are no sizes, so a unit forecast is simpler, and sales are more tied to gift holidays: spikes before 8 March, 23 February and New Year. High margin, slower turnover; do not inflate the plan unless supply is scarce.
- Kids
- Two peaks: September (school and uniform) and the pre-New Year period; for small sizes the child outgrows quickly: sizes move up with age. Plan by age group, not by a single total.
- Men
- Demand is steadier and less fashion-driven: more basics, more repeat purchases, a lower share of markdown. Peaks: February (gifts) and November-December. The plan builds from repeat purchases and the basics share.
- Women
- The widest and most fashion-driven area: a higher share of new styles, faster collection decay, more markdowns. Split the plan by role (core, fashion, image) and allow for micro-seasons (capsules, drops).
Common mistakes
- The plan is built from desired growth with no bottom-up → targets do not reconcile and the team fits numbers → keep both versions and show the gap.
- Sales with VAT in one month and without in another → a false base, and the VAT/price change passes for demand growth → count excluding VAT only and state the rate.
- Comparing non-comparable periods (different week counts, holidays on other days) → false growth → use the 4-5-4 calendar and LFL.
- Wholesale is counted from the preorder without cancellations and late payments → revenue does not turn into cash → plan from confirmed, paid orders and customer limits.
- A new outlet is planned at mature level at once → a shortfall in the first months → set a ramp curve (months to maturity and share of the mature plan).
Russian specifics
- In Russia the general VAT rate has been 22% since 1 January 2026, and 10% for listed kids goods; the plan is built excluding VAT while price tags and receipts show the price with VAT. Rule: Law 425-FZ of 28.11.2025: Federal Law of 28.11.2025 No. 425-FZ (amendments to parts one and two of the Tax Code; VAT 22%) (rule check not completed).
- The 10% rate for kids clothing and shoes applies when certificate or declaration data is in the register: reflect this in the plan if the document is missing. Rule: Law 218-FZ of 04.07.2026: Federal Law of 04.07.2026 No. 218-FZ (amendments to part two of the Tax Code, including Arts. 164 and 170).
- Sales are backed by cash-register data: find mismatches between the register and the books before approving the base. Rule: Law 54-FZ of 22.05.2003: Federal Law of 22.05.2003 No. 54-FZ on the use of cash registers (rule check not completed).