Publish Date :
How to Run a Retail Planning Software Proof of Concept
A useful retail planning software proof of concept tests whether your team can reconcile inputs, compare a commercial change and retain control of the chosen decision. Merchmix’s six-week POC provides an evaluation period on your data; Core supplies the planning comparison. Define success before the presentation begins.

THE MERCHMIX DECISION / Core
Choose a decision the team can independently reconcile
A retail planning POC should prove a small set of real decisions against agreed inputs, expected calculations and clear acceptance criteria.
Independent retail planning example. Financial amounts are US dollars. Forecasts, quantities and proposals are assumptions for this decision, not customer results.
Knitwear / six-week evaluation case
| Baseline check | Value |
|---|---|
| Expected sales | 400 units |
| Goods cost per incoming unit | $25 |
| Selected buying envelope | $9,000 |
These values define an independent evaluation case, not a customer result.
The example uses 480 held units, two hundred incoming and four hundred expected sales.
THE KEY IDEA
Define the decisions and expected answers first, then use the POC to collect retailer-verifiable evidence for a proceed-or-stop decision.
Choose a commercial question before choosing the screens
Start with a decision the team already struggles to make reliably, such as revising demand without losing the original intake commitment. Select a narrow merchandise scope and an owner who can verify the numbers. A broad tour of features cannot substitute for an accepted answer to that question.
Merchmix’s published POC describes data in the first week, setup in the second, training and walkthroughs in weeks three and four, and retailer evaluation in weeks five and six. Treat that as the evaluation structure, not proof that an implementation or commercial outcome is already complete.
Agree the baseline and expected answer independently
An independent knitwear case begins with 480 held units, two hundred confirmed incoming and four hundred expected sales over the selected window. Closing stock should be 280. The assumed incoming cost is $25 per unit, so goods commitment is $5,000 against a selected $9,000 buying envelope.
Retain those expected answers before the Core comparison. The selected scope has no other commitments in its simplified envelope calculation. A real POC must reconcile reservations, returns, order statuses and cost bases rather than inherit the illustration’s exclusions without checking them.
Test a demand change without changing the order
Increase expected demand from four hundred to 480 while leaving held stock and intake unchanged. Closing should become two hundred. The $5,000 incoming goods commitment and $4,000 remaining envelope should stay unchanged because the test has not added a purchase.
Core’s weekly MFP/WSSI and version comparison should make that separation understandable to the retailer evaluating it. Ask the user to reproduce the result and explain which assumption changed. A correctly displayed total is less useful if the team cannot identify its inputs or preserve the original version.
THE FIGURES BEHIND THE DECISION
| Test | Evidence required |
|---|---|
| Reconciliation | Reproduce 280 and 200 closing units |
| Commitment | Separate the optional $2,000 |
| Authority | Confirm who may commit the selected version |
Baseline: 480 + 200 less 400 = 280. Revised: 480 + 200 less 480 = 200. Incoming cost is 200 × $25 = $5,000; selected headroom is $9,000 less $5,000 = $4,000.
Make a separate commitment test deliberately visible
An optional eighty-unit addition would cost $2,000, raise incoming units to 280 and leave $2,000 in the selected envelope. Under the revised 480-sale assumption, closing would return to 280. That is a separate comparison, not an order that the evaluation has placed.
The revised case already closes at two hundred against an independent 160-unit target, so this illustration does not recommend the extra buy. A worthwhile POC should allow the team to challenge an unnecessary proposal as readily as it demonstrates the arithmetic of accepting one.
Write acceptance criteria that the retailer can verify
Record the required input reconciliation, the two closing-stock results and the separate effect of the optional commitment. Identify which user may edit, review and accept the supported planning version. Test exceptions as well as the expected path, including a stale input or an unresolved incoming line.
These are proposed evaluation criteria, not claims that a particular customer passed them. Use Core within the agreed scope and retain evidence of the actual result. If a configured connection or field is outside the POC, document that limitation instead of treating a successful narrow comparison as proof of every production workflow.
Keep POC success separate from go-live readiness
Finishing the six-week evaluation does not confirm production integrations, permissions, operating ownership or a service agreement. Merchmix describes subsequent go-live work and internal decision time separately. Agree the actual scope and readiness steps with the responsible team.
Compare the observed outcome with the acceptance criteria, including what remains unresolved. A missing requirement may be a reason to extend a specific test, change scope or stop. Avoid declaring success merely because the evaluation period ended or a presentation looked polished.
| Signal | Merchmix workspace | Decision to review |
|---|---|---|
| Retained baseline | Core / evidence | The example uses 480 held units, two hundred incoming and four hundred expected sales. |
| Forecast-only change | Core / comparison | At 480 expected sales, closing falls to two hundred while goods commitment stays $5,000. |
| Evaluation record | Core / decision review | Commercial acceptance, integrations and operational readiness remain separate decisions. |
Leave with a decision and evidence the team understands
The outcome should name the tested decisions, accepted calculations, user feedback, unresolved requirements and the owner of the next step. Keep the underlying assumptions so the team can explain why a result changed rather than rely on a saved image.
A Merchmix POC is valuable when Core helps the retailer make and understand a controlled planning decision on relevant data. The six weeks create a framework for that evaluation; they do not remove the need for commercial judgement about proceeding.
BEFORE THE NEXT DECISION
- Planning owner
The buying-envelope calculation uses the same $25 goods cost and no other commitments.
- Commercial owner
The revised case already closes above the separate 160-unit target.
- Decision owner
Commercial acceptance, integrations and operational readiness remain separate decisions.
Common questions
How long is the published Merchmix POC?
The public offer describes six weeks, with data, setup, training and retailer evaluation stages. Confirm current terms and scope with Merchmix.
What should the example close at before revising demand?
480 held plus two hundred incoming less four hundred sales leaves 280 units.
Why does buying headroom stay $4,000 after the forecast change?
Only demand changes. The same two hundred incoming units still cost $5,000 against the selected $9,000 envelope.
Does the POC recommend the optional eighty-unit buy?
No. It is a separate commitment test; the revised case already closes above its stated 160-unit target.
Does finishing the POC mean the system is live?
No. Acceptance, operational readiness and the agreed production go-live work remain separate.
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.