Publish Date :
Why Planners Won't Give Up Excel (and Don't Have To)
Planners can keep Excel for focused analysis without making a downloaded workbook the authority for the whole business. Core provides the planning baseline; the important hand-off is a validated, reconciled proposal returning to a current version, with commercial approval still intact.

THE MERCHMIX DECISION / Core
Keep the file useful and the baseline identifiable
Excel can remain useful for analysis when the return to Core has a defined scope, current baseline and a review of what changed.
Independent retail planning example. Financial amounts are US dollars. Forecasts, quantities and proposals are assumptions for this decision, not customer results.
Blue and cream shirts / controlled workbook return
| Option | Exported units | Working units |
|---|---|---|
| Blue shirt | 120 | 150 |
| Cream shirt | 80 | 90 |
Retain merchandise keys, fiscal period and the baseline version in the hand-off.
The exported plan contains 120 blue shirts and 80 cream shirts.
THE KEY IDEA
Keep Excel for analysis and make its return a deliberate change to a current, reviewable Core plan.
Keep the useful analysis and define the hand-off
Excel is a practical place to test a one-off assumption or compare a small set of options. The risk appears when an edited export returns with unclear identifiers, old commitments or an assumption that every changed cell should replace the current plan. The hand-off deserves as much attention as the analysis.
Merchmix publicly describes Excel and CSV import and export alongside Core planning. Exact templates and write-back behaviour must be checked for the supported workflow. This article recommends a controlled return process; it does not claim that Core can interpret or automatically merge any workbook formula, macro or layout.
Export a scope that someone can reconcile
Take two shirt options in one defined period. The approved baseline contains 120 blue and 80 cream units, both at $24 goods cost. Total units are 200 and goods cost is $4,800. Retain the option keys, period, cost basis and baseline reference beside the exported quantities.
Keep separate columns for baseline and proposal rather than typing over the only record of the approved position. That structure helps a reviewer see intent, but a well-labelled workbook is still a working copy. The accepted plan remains the reference until a supported approval records the change.
Show the financial effect of the workbook proposal
The planner tests 150 blue and 90 cream units. The proposal totals 240 units and $5,760 goods cost, an increase of 40 units and $960 against the exported baseline. These are independent planning assumptions, not a recommended shirt buy.
A returned file needs more than an intact total. Validate the merchandise identifiers, selected period, quantity type and currency. Check for duplicate rows and confirm that a cost value means goods cost rather than retail value. Reconcile the staged result before deciding whether the proposal is commercially acceptable.
THE FIGURES BEHIND THE DECISION
| Option | Current units | Proposed units | Change |
|---|---|---|---|
| Blue shirt | 120 | 150 | 30 more |
| Cream shirt | 92 | 90 | 2 fewer |
| Total | 212 | 240 | 28 more |
Export: (120 + 80) × $24 = $4,800. Current: (120 + 92) × $24 = $5,088. Proposed: (150 + 90) × $24 = $5,760. Current comparison: $672 more.
Check what changed while the file was away
Suppose another authorised change increased cream from 80 to 92 units after the export. The current accepted position is now 120 blue plus 92 cream, totalling 212 units and $5,088. The returned workbook still proposes 90 cream, which would now be a reduction of two units.
That conflict cannot be resolved by assuming every workbook difference is an addition. Review the reason for the intervening twelve-unit change and the returned ninety-unit proposal. Core’s versions provide the planning reference; any merge or controlled re-entry must follow the workflow actually supported for the selected data.
Reconcile to the current baseline before approval
Against the current accepted plan, 150 blue plus 90 cream means 30 more blue and two fewer cream, or 28 more overall. At the same $24 cost, the total difference is $672. This is smaller than the original $960 comparison because the baseline changed while the file was in use.
Make both comparisons available if they explain the decision, but label them. A reviewer should not approve a $960 increase and later discover that a different $672 change was applied. The accepted scope, current version and resulting quantities should agree before committing the revised plan.
Use validation as a gate, then apply commercial judgement
Microsoft documents Excel data validation as a way to constrain entries. That can improve a working sheet, but it cannot establish that a supplier date is still feasible or that the proposed stock will sell. Technical validation and commercial approval answer different questions.
Return only the fields intended for change through the supported Core process. If the particular template does not support a field or version conflict, use the controlled route agreed with the implementation team. Keep the unresolved item visible instead of relying on a successful file upload as proof that the plan is right.
| Signal | Merchmix workspace | Decision to review |
|---|---|---|
| Export baseline | Core / evidence | The exported plan contains 120 blue shirts and 80 cream shirts. |
| Reconcile proposal | Core / comparison | The edited proposal contains 240 units at $24, costing $5,760. |
| Return for review | Core / decision review | Use the supported import or controlled re-entry workflow; no automatic workbook merge is claimed. |
Make the spreadsheet part of a repeatable planning routine
A useful routine has a defined export scope, a named working owner, a return deadline, validation and a recorded planning decision. Core retains the accepted version and the basis for comparison. Excel remains available for analysis without becoming an untracked parallel plan.
After acceptance, reconcile the resulting quantities and costs to the approved proposal. If they differ, investigate before treating the new version as ready for buying. The practical objective is confidence in the numbers that return, not a requirement that every planner abandon a familiar analytical tool.
BEFORE THE NEXT DECISION
- Planning owner
Check keys, dates, currency and duplicate rows before accepting a staged return.
- Commercial owner
The workbook proposal would reduce cream from 92 to 90; that is not simply an additive update.
- Decision owner
Use the supported import or controlled re-entry workflow; no automatic workbook merge is claimed.
Common questions
Do planners have to stop using Excel?
No. Focused workbook analysis can remain part of the process when its return is controlled and reconciled.
Does Core import any workbook automatically?
No such claim is made. Confirm the supported template, fields, validations and write-back workflow for the deployment.
Why does the comparison change from $960 to $672?
The accepted baseline increased by twelve units at $24 while the workbook was being edited. The proposal must be compared with that current baseline.
Why is cream shown as two fewer units?
The current accepted quantity is 92 and the workbook proposes 90, despite the older export having contained 80.
Does file validation replace approval?
No. A technically valid file still needs a commercial decision about demand, stock and commitments.
FROM THE ARTICLE TO YOUR OWN RETAIL PLAN
Review the decision.
See the workflow.
Bring your planning questions to a demo, or explore a proof of concept on your own data.