Northline Apparel supplies Order A, 15,000 basic cotton T-shirts, to Fairway Stores, a department-store chain selling the style across 12 locations. Once the T-shirts reach the shop floor, someone at Fairway Stores has to know, store by store and size by size, how fast the style is selling, how much stock is left, and when a reorder decision becomes urgent. Many retailers still try to answer that question from a spreadsheet someone updates by hand once a week. A spreadsheet can hold the same numbers a planning system holds, but it cannot keep them current, connected and trustworthy on its own. This lesson names the specific things a retail planning system tracks that a spreadsheet, by its own nature, tends to lose.
You need: the general idea that a retailer sells a style across several stores and needs to know stock levels and sales speed to plan a reorder. Track 17, Course 1 and Course 3 are useful preparation.
By the end of this lesson you can:
Not covered here: the specific KPIs a planner reviews each week (lesson 6.2), how to check the data behind a report before trusting it (lesson 6.3), and building a complete retail planning KPI worksheet (lesson 6.4). No specific software product is named or recommended in this course.
| Term | Meaning |
|---|---|
| Retail planning system | A shared, connected record that tracks stock, sales and reorder decisions by store and by size automatically, instead of a file someone updates by hand. |
| Master data | Reusable reference data that stays stable across many orders until it is deliberately changed. |
| Data input | One of the individual figures that a dashboard calculation combines to produce its displayed number. |
| Stock cover | The number of weeks a brand's current stock is expected to last before it runs out, given its normal sales rate. |
| Sell-through rate | The share of stock actually sold within a planned period, used to judge whether a forecast was right. |
| Version conflict | Two records showing different values while both are treated as current. |
| Spreadsheet gap-filler | A spreadsheet used only for information that no controlled system currently holds. |
A spreadsheet is a file. A retail planning system is a discipline for keeping stock counts, sales figures and reorder decisions connected to each other, updated on a fixed schedule, and visible to everyone who needs them at the same time. The two overlap in what they can display: both can show a stock count, a sales figure, a stock-cover number. They differ sharply in what happens the moment two people need to update the same fact from two different locations at the same time. A spreadsheet has no way to stop that from producing two different "current" answers. A retail planning system is built specifically to prevent it.
| What can differ | The shapes you will meet | Why it matters to you |
|---|---|---|
| Export made-to-order chain versus domestic made-to-stock brand | Fairway Stores reads Order A's sell-through across 12 export stores; a domestic brand such as Cedar & Co. reads the same kind of data to decide its next reorder cycle from its own forecast. | An MTO order's data mainly informs the next separate order; an MTS reorder programme needs current data fast enough to act inside the current cycle. |
| Single store versus multi-store chain | A single shop can survive on a spreadsheet a manager updates each evening. A 12-store chain like Fairway Stores cannot, because the same style's stock count changes in 12 places at once. | The more locations report into the same number, the higher the chance two people update it differently at the same moment. |
| Buyer or brand side versus retailer side | Northline Apparel needs Fairway Stores' own sell-through to plan its next production run; Fairway Stores needs its own stock counts to decide a store-level reallocation. | Each side needs the same underlying facts kept current for a different decision, so the record has to be trustworthy for both purposes at once. |
| Agent-mediated hybrid accounts | An agent such as Meridian Sourcing, coordinating a hybrid account between a factory and more than one buyer, needs one current record rather than separate spreadsheets from each side that can disagree. | A hybrid account mixing a standing forecast with extra top-up runs is exactly where two disconnected spreadsheets are most likely to disagree. |
Before Fairway Stores connected Order A's stock and sales data into its retail planning system, each of the 12 stores emailed its own weekly stock count to a head-office planner, who pasted the figures into one master spreadsheet. Two stores updated their counts on the same Thursday afternoon: one from the till system, one from a manual recount. Both versions were saved under the same file name, an hour apart. The planner worked from whichever version happened to open last, with no way of knowing a second version existed. Once Fairway Stores' retail planning system took over the same task, every store's till transaction fed the same stock record automatically, with a timestamp on every change, so only one current stock figure for the style ever existed at any moment.
The worked numberA shared spreadsheet feels connected because everyone can technically reach the same file, but reaching a file is not the same as trusting the number inside it at any given moment. A common mistake is treating a spreadsheet emailed weekly across 12 stores as equivalent to a connected retail planning system, because both display a stock-cover figure that looks equally precise on screen. The cost of this mistake is invisible until two versions genuinely disagree, at which point nobody can say which number was actually current when the reorder decision was made.
A spreadsheet and a real planning system can look the same on screen, showing the same kind of stock and sales numbers. The real difference only shows up the moment two people update the same fact from two different places at the same time. A spreadsheet has no way to stop that from creating two different "correct" answers; a proper system is built specifically so only one current answer ever exists, with a record of who changed it and when. The more stores a retailer runs, and the faster its reorder decisions need to happen, the more that difference matters, because the chance of two people updating the same number at once grows with every extra store added.
Fairway Stores still runs Order A's stock count on a shared spreadsheet while its retail planning system is mid-rollout. At 2 p.m., the downtown store's manager updates size M's stock count to 40 pieces after a till reconciliation. At 3 p.m., a head-office planner updates the same cell to 65 pieces after a manual recount phoned in earlier that day. Both versions are saved under the same file name. The Friday reorder meeting is in 18 hours, and the reorder decision for size M depends on knowing which stock figure is actually current.
Should the planner trust the 65-piece figure and proceed straight to Friday's reorder decision? Decide before opening the answer.
No. The planner should not trust either figure alone and must confirm the true current count before Friday's meeting.
1. The file shows only the last-saved value, 65 pieces, with no timestamp trail linking it to the earlier 40-piece entry that the downtown store's own till reconciliation produced an hour before. 2. Neither figure carries an owner's name, so there is no way to tell which update reflects an actual physical count and which may already be stale. 3. A reorder decision for size M made on an unverified figure risks either an unnecessary reorder (if 40 was correct) or a missed reorder (if 65 hides an even lower true count). 4. This is exactly the version-conflict risk a connected retail planning system is built to remove, by feeding every store's till transaction into one record with a timestamp and an owner on every change.
Against Order A's own total shop-price value across all 12 stores (15,000 x USD 19.90 = USD 298,500), a single unresolved version conflict on one size at one store is a small figure on its own, but it recurs at every store, every week, for as long as the underlying record stays a spreadsheet rather than a connected system, with no way to know how many similar conflicts are happening unseen at the same time.
Use the T20-C06 Retail planning KPI worksheet. Its "System versus spreadsheet check" sheet records, for each fact a retail planning system needs, whether it is entered once as master data, updated automatically from a live source, or still relying on a manually maintained spreadsheet, so a gap can be closed before it causes a version conflict like the one on Order A above.
[Download the Retail planning KPI worksheet](../../templates/T20-C06-retail-planning-kpi-worksheet.xlsx)
1. What is the real difference between a spreadsheet and a connected retail planning system, according to this lesson?
2. Why did Fairway Stores' two stock-count entries for size M create a real risk before the Friday reorder meeting?
3. A 20-store chain updates one style's stock count by spreadsheet, with any two stores able to disagree on the same fact. How many separate pairs of stores could produce a version conflict?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Retail planning system | نظام تخطيط التجزئة | Système de planification du commerce de détail | Perakende planlama sistemi | A shared, connected record that tracks stock, sales and reorder decisions by store and by size automatically, instead of a file someone updates by hand. |
| Master data | البيانات المرجعية | Données de référence | Ana veri | Reusable reference data that stays stable across many orders until it is deliberately changed. |
| Data input | مدخل بيانات | Donnée d'entrée | Veri girdisi | One of the individual figures that a dashboard calculation combines to produce its displayed number. |
| Stock cover | تغطية المخزون | Couverture de stock | Stok kapsama süresi | The number of weeks a brand's current stock is expected to last before it runs out, given its normal sales rate. |
| Sell-through rate | معدل البيع الفعلي | Taux d'écoulement | Satış oranı | The share of stock actually sold within a planned period, used to judge whether a forecast was right. |
| Version conflict | تعارض الإصدارات | Conflit de versions | Sürüm çakışması | Two records showing different values while both are treated as current. |
| Spreadsheet gap-filler | جدول بيانات لسد فجوة | Feuille de calcul de complément | Boşluk dolduran e-tablo | A spreadsheet used only for information that no controlled system currently holds. |
You now know what a retail planning system tracks beyond a single spreadsheet. The next lesson names the specific KPIs a retail planner actually reviews every week, and why each one earns its place in that weekly review. Back to the course map