Sales plan by store
One row per store and month: area, traffic, conversion, average ticket, planned revenue and growth over last year.
What the template is for
Splitting the chain plan by store and checking feasibility on traffic and conversion.
- What one row is
- one row = store × month
Columns
| Column | Code | Type | Required | Validation rule |
|---|---|---|---|---|
| Month | month | Text | yes | month as YYYY-MM |
| Store code | store | Text | yes | a value from the customer and point reference |
| Format | format | List value | yes | mall, street, outlet or shop-in-shop |
| Sales area, m² | area | Number | yes | a number not below 0 |
| Traffic, visitors | traffic | Integer | yes | an integer not below 0 |
| Conversion, % | conv | Number | yes | from 0 to 100 |
| Average ticket excl. VAT | ticket | Number | yes | a number not below 0 |
| Planned revenue excl. VAT | revenue | Number | yes | calculated: traffic × conversion ÷ 100 × average ticket |
| Last year revenue excl. VAT | ly | Number | yes | a number not below 0 |
| Growth over last year, % | growth | Number | yes | calculated: (plan ÷ last year − 1) × 100 |
Example rows
| Month | Store code | Format | Sales area, m² | Traffic, visitors | Conversion, % | Average ticket excl. VAT | Planned revenue excl. VAT | Last year revenue excl. VAT | Growth over last year, % |
|---|---|---|---|---|---|---|---|---|---|
| 2027-02 | ST01 | mall | 320 | 24,000 | 7.5 | 3,900 | 7,020,000 | 6,350,000 | 10.6 |
| 2027-02 | ST02 | street | 180 | 15,500 | 9 | 4,300 | 5,998,500 | 5,800,000 | 3.4 |
| 2027-03 | ST01 | mall | 320 | 27,500 | 8 | 4,000 | 8,800,000 | 8,300,000 | 6 |
| 2027-03 | ST02 | street | 180 | 17,000 | 9.5 | 4,400 | 7,106,000 | 6,900,000 | 3 |
The example data is illustrative: an exercise, replace it with your own.
Note
If growth comes only from conversion above its history, flag the store for review: traffic is usually planned more conservatively. For new stores fill the last-year column with an analog actual. The example data is illustrative: an exercise, not a norm or an industry benchmark.
How to open the file
The file is UTF-8 with a BOM, comma separated, with a decimal point. Set the text format for code columns (SKU, article, GTIN) so that long numbers and leading zeros are not distorted. The validation rules are suggested defaults, not norms: your systems and contracts may require something else.
Calculations that use these fields
- Sales plan by store
- Store comparison across the chain
- Merchandise plan traffic light
- Display: productivity of a linear meter and of facings by zone
- Store payback: ramp-up and rent holiday by month
- Chain pilot: the effect against control stores
- Category roles: traffic driver, profit core, image
- Queue M/M/c: how many tills and assistants are needed at the peak
Documents that need this data
- Sales plan
- Store KPI pack: traffic, conversion, ticket, revenue per m², payroll and shrinkage
- LFL and comparable sales (4-5-4 calendar)
- Formats by economics: haute couture, luxury, bridge, mass market, off-price, flash sales, travel retail and live shopping
- FSBU 25, 6 and 26: lease, fixed assets and capital investments in the accounts of a retailer and a brand
- Management accounting: financial responsibility centers, overhead allocation, standard cost and the accounting policy
- Planogram and display in apparel: rails, walls, tables, selling slots, display stock and execution control
- Job profiles: merchandiser and collection product manager — what they count, which documents they make, how the week works
- The store team: service standards, shift schedule by traffic, grades, incentives and the cost of turnover
- State support for light industry and development fund loans: map of measures, conditions, application and effect calculation
- The display in numbers: usable hall area, running meters, capacity and density, zoning by productivity and the rotation of the display
- Visual merchandising and hall zoning: guide, window, customer path, fitting rooms, till, visit checklist