Delta Garments runs Cedar & Co.'s hybrid denim account: a standing Make to Stock reorder cycle, illustrative 1,000-piece batches on a 4-week production cycle, sold on 60-day open account, plus a separate Make to Order seasonal top-up run placed when demand justifies it. Earlier lessons in this course covered three separate skills: telling a real retail planning system from a spreadsheet gap-filler, naming the KPIs worth a weekly review, and checking the data behind a report before trusting it. A real reorder decision needs all three at once, in the right order, not as three separate exercises. This lesson builds one complete worksheet that does exactly that, using Cedar & Co.'s hybrid account from start to finish.
You need: the ideas covered in lessons 6.1 to 6.3: what a retail planning system tracks beyond a spreadsheet, the core weekly KPIs, and how to check the data behind a report. All three are recapped here, so a reader who has only seen one or two can still follow this lesson.
By the end of this lesson you can:
Not covered here: any new KPI or data-check rule beyond what lessons 6.1 to 6.3 already taught; this lesson is a combined application, not a new topic.
| 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. |
| KPI catalogue | A single list of every KPI a business tracks, with its decision, owner and trigger value recorded together. |
| Review cycle | The regular interval, such as monthly, at which a business checks its KPIs and closes or updates its actions. |
| Stock cover | The number of weeks a brand's current stock is expected to last before it runs out, given its normal sales rate. |
| Source check | Comparing a dashboard number against the original record it was supposed to be built from. |
| Trigger value | The specific level a KPI must reach before it changes what the decision owner does. |
The three skills covered across this course are not interchangeable steps that can be done in any order; they build on each other. First, confirm the underlying record is a real retail planning system for the fact being checked, not a spreadsheet gap-filler that might already be out of date. Second, read the specific KPI that matters for the decision at hand, from the small catalogue built in lesson 6.2, not every number the dashboard can show. Third, check that KPI's data input against its source and refresh timestamp before treating it as trustworthy enough to act on. Only after all three steps does a worksheet record a decision, because skipping any one of them lets exactly the failure that lesson taught slip back in.
| What can differ | The shapes you will meet | Why it matters to you |
|---|---|---|
| MTS side versus MTO side of a hybrid account | Cedar & Co.'s standing 1,000-piece MTS reorder cycle is reviewed against stock cover every week; a separate MTO seasonal top-up is reviewed only once demand data suggests it, against its own separate trigger. | Merging both sides into a single KPI reading hides which decision, a reorder or a top-up, the numbers are actually supporting. |
| Factory side versus buyer side of the same worksheet | Delta Garments reads the worksheet to decide whether the 4-week production cycle needs to start now; Cedar & Co.'s own planner reads the same worksheet to decide whether to commit the next batch's cost. | The same completed worksheet answers two different decision owners' own questions without needing two separate documents. |
| Domestic versus export hybrid accounts | Cedar & Co.'s domestic hybrid account refreshes stock data quickly from its own point-of-sale system; an export hybrid account, like Fairway Stores' arrangement with Meridian Sourcing, often needs the data-check step to work harder because of the longer chain back to the original sale. | The three-step chain stays the same everywhere; the amount of care needed at the data-check step changes with how far the reader sits from the original record. |
| First worksheet entry versus a repeated one | The first time Delta Garments completes this worksheet for a new style, every step is done from scratch; on a repeated reorder cycle, the data-check history from the previous entry shows whether the same source has been reliable before. | A worksheet's own history becomes evidence in later decisions, not only a record of what was decided in the past. |
It is week 9 of Cedar & Co.'s hybrid denim account. Delta Garments' planner opens the worksheet to decide whether the MTS side needs its next 1,000-piece batch triggered. Step one, the system check: Cedar & Co.'s stock data now feeds directly from its own point-of-sale system into the shared worksheet, not from a manually updated file, so the record passes the system check. Step two, the KPI review: stock cover reads 4 weeks, exactly matching the 4-week production cycle, the trigger point named in lesson 6.2. Step three, the data check: the refresh timestamp shows the stock count was pulled that same morning, and a quick source check against Cedar & Co.'s till system confirms the figure. All three checks pass, so the worksheet records the MTS reorder decision: trigger the next 1,000-piece batch today. The separate MTO top-up side of the account is reviewed independently and, this week, does not meet its own trigger, so no top-up run is recorded.
The worked numberA common mistake is reading a hybrid account's stock cover, checking its data, and then writing down one combined "reorder yes or no" decision that does not say which side it applies to. On a hybrid account, the MTS side and the MTO side answer two genuinely different questions, using different triggers and often different data sources, and a merged decision can leave a factory unsure whether to run the standing batch, the top-up, both, or neither. The three-step chain has to be completed once for each side.
Bringing everything in this course together means running the same three checks every time, in the same order: confirm the system behind the numbers is trustworthy, read only the KPIs that matter for the decision, and check the data before acting on it. On a hybrid account, this whole chain has to be run separately for the standing reorder side and for the separate top-up side, because they answer different questions with different triggers. A worksheet that does all of this in one place, and keeps a record of what was checked, turns three separate lessons into one routine a factory can actually run every week.
Delta Garments' planner has just completed the week 9 worksheet entry for Cedar & Co.'s hybrid account: the MTS side's stock cover has hit its 4-week trigger, with a same-morning refresh timestamp and a confirmed source check; the MTO seasonal top-up side remains below its own separate trigger, using demand data confirmed as current only two days ago. The sewing floor needs one instruction for the coming week.
Should the planner instruct the sewing floor to run the MTS batch, the MTO top-up, both, or neither this week? Decide before opening the answer.
The planner should instruct the sewing floor to run only the MTS batch this week, not the MTO top-up.
1. The MTS side's trigger was reached with fully checked, same-morning data, meeting all three steps of the worksheet's own chain: system check, KPI review, and data check. 2. The MTO side has not reached its own separate trigger, so recording a top-up run this week would ignore the very rule that keeps the two sides of a hybrid account from being confused. 3. Running both simply because capacity happens to allow it would remove the meaning of having two separate triggers, since the MTO side's trigger exists precisely to decide when a top-up is actually justified by demand. 4. The correct instruction to the sewing floor is the 1,000-piece MTS batch alone, with the MTO side reviewed again at its own next check point rather than folded into this week's decision.
Running an unjustified MTO top-up alongside a correctly triggered MTS batch does not simply double the batch value; it commits production cost against demand that has not yet been confirmed, exactly the risk a separate MTO trigger exists to prevent, which is why the two sides of a hybrid account are never combined into a single recorded decision.
Use the T20-C06 Retail planning KPI worksheet. Its "Combined decision" sheet records, for each review, the system check result, the KPI reading, the data check result, and the final decision for the MTS side and the MTO side separately, the exact chain this lesson worked through for Delta Garments and Cedar & Co.
[Download the Retail planning KPI worksheet](../../templates/T20-C06-retail-planning-kpi-worksheet.xlsx)
1. Why does this lesson insist the three checks (system, KPI, data) are completed in that specific order?
2. Why did Delta Garments' planner instruct the sewing floor to run only the MTS batch, not the MTO top-up, in week 9?
3. A different hybrid account shows its MTS side below trigger and its MTO side above trigger, both with fully verified, same-day data. What should the worksheet record?
| 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. |
| KPI catalogue | فهرس المؤشرات | Catalogue de KPI | KPI kataloğu | A single list of every KPI a business tracks, with its decision, owner and trigger value recorded together. |
| Review cycle | دورة المراجعة | Cycle de revue | İnceleme döngüsü | The regular interval, such as monthly, at which a business checks its KPIs and closes or updates its actions. |
| 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. |
| Source check | التحقق من المصدر | Vérification de la source | Kaynak kontrolü | Comparing a dashboard number against the original record it was supposed to be built from. |
| Trigger value | قيمة التنبيه | Valeur de déclenchement | Tetikleme değeri | The specific level a KPI must reach before it changes what the decision owner does. |
This is the final lesson of Track 20, Course 6. The next course in the academy's sequence continues building on the systems, KPI and data-quality discipline covered across this course. Back to the course map