Publish Date :
Planning Software and ERP: Why You Need Both
An enterprise resource planning (ERP) system records what has happened, including orders, stock and receipts; merchandise planning decides how much to buy and hold next. Retailers need both. When expected sales fall, the plan changes, but the recorded purchase order stays the same until an agreed amendment is made.

THE MERCHMIX DECISION / Core + Horizon
The forecast falls. The order stays at 420.
The revised plan needs 360 incoming units, leaving 60 more on order than required.
USD worked example.
Apparel / one aligned selling period
| Same period / units | ERP record | Core comparison |
|---|---|---|
| Opening stock | 180 | 180 |
| Confirmed intake | 420 | 420 |
| Required intake | Recorded order above | 420 |
| Expected closing | Calculated in plan | 150 |
A revised forecast changes the planning calculation. It does not amend the recorded purchase order.
180 opening units plus 420 incoming support 450 sales and 150 closing units.
THE KEY IDEA
Keep the ERP’s order record and Core’s forward plan connected. A forecast change reveals the next decision; the supplier agreement determines whether the recorded order changes.
Use the ERP for records and Core for the next plan
Merchmix Core is the merchandise planning workspace for budgets, ranges, open to buy (OTB) and merchandise financial planning (MFP), including weekly sales, stock and intake (WSSI). We refer to that connected planning view as MFP/WSSI. It helps a buyer compare expected sales with the stock held and due.
Horizon is Merchmix’s retail ERP for products, receiving and stock corrections. It holds styles, variants and stock records that help the team explain what changed. A retailer can also keep its existing ERP and use Core for planning. The choice depends on whether the problem lies in the transaction records, the forward plan or both.
Agree the stock and orders before changing the forecast
Use the same product, location and trading period in both systems. Check physical stock, reservations, units that cannot be sold and outstanding orders. Include each future receipt in the week it can actually support sales.
The team also needs consistent unit costs and selling prices. A stock-at-cost figure cannot be compared directly with sales value without the relevant cost calculation. Reconcile missing receipts or duplicate product codes before treating the opening position as a reliable starting point.
A lower forecast leaves 60 more units on order than needed
An apparel retailer starts with 180 units, has 420 incoming and expects 450 sales. Closing stock is 150 units: 180 plus 420 minus 450. If expected sales fall to 390, the unchanged order leaves 210 units at the end of the period.
To keep the original 150-unit closing target, the revised plan needs 360 incoming units: 390 sales plus 150 closing minus 180 opening. There are 60 units more on order than the plan needs, worth $2,100 at $35 each. This is an independent USD example; the excess is not a confirmed cancellation or saving.
The buyer can ask for a smaller order, discuss a permitted delivery change or accept the higher closing stock. Until a change is agreed and recorded, the order remains 420 units. If only 30 units are removed, the plan still needs to account for the other 30.
THE FIGURES BEHIND THE DECISION
| Measure | Original plan | Revised outlook |
|---|---|---|
| Opening stock | 180 units | 180 units |
| Confirmed intake | 420 units | 420 units |
| Expected sales | 450 units | 390 units |
| Expected closing | 150 units | 210 units |
| Closing target | 150 units | 150 units |
| Required intake | 420 units | 360 units |
Required intake = expected sales + target closing stock − opening stock. Extra units on order = confirmed intake − required intake.
Use Core to compare the available choices
Core brings the revised sales forecast, expected closing stock and intake into MFP/WSSI. OTB shows the buying allowance under the selected plan. In this example, the existing order already exceeds the quantity required, so a lower forecast does not create room for another buy.
Check whether the weaker sales affect a particular size, store or week before reducing the whole range. Compare a smaller receipt with a later arrival and with retaining the current order. Each choice changes the stock available during the remaining selling period.
Record the supplier agreement in the order
Once the buyer and supplier agree a permitted amendment, update the order through the retailer’s authorised process. Check its quantity, date and status, then bring that confirmed information into the plan. A date change should appear in the receipt weeks; it should not be recorded as a quantity reduction.
This is where ERP and planning need to stay connected. The order record explains what the business has committed to. Core shows whether that commitment fits expected demand. The team needs both figures at the next review, including any part of the requested change the supplier did not accept.
Choose the system change that solves the actual problem
If stock and order records reconcile but buyers struggle to compare budgets, forecasts and intake, start with planning. If receipts, stock corrections or product identities cannot be reconciled, review the operational records as well. Horizon addresses that retail ERP layer; Core addresses the merchandise plan.
For the example, the next decision is specific: keep 420 units on order or agree how to deal with the 60 above the revised requirement. The forecast, supplier agreement and recorded order should tell the same story before the next buy is approved.
BEFORE THE NEXT DECISION
- Planner
Keep period, product scope, units and stock cost and selling-price definitions consistent.
- Buyer
Distinguish the requested amendment from the confirmed supplier commitment.
- Operations owner
Reconcile only authorised, recorded changes back into the planning position.
| Signal | Merchmix workspace | Decision to review |
|---|---|---|
| The sales outlook changes | Core / MFP/WSSI | Compare the revised 360-unit requirement with the 420-unit order. |
| A commitment may need changing | Core / buying review | Review terms and approval before requesting an amendment. |
| An operational change is confirmed | Horizon / operational record | Reconcile the recorded quantity and status with the plan. |
Common questions
What does ERP stand for?
Enterprise resource planning. In retail, it records the operational transactions supported by the system, such as orders, receipts and stock movements.
What is MFP/WSSI?
Merchandise financial planning (MFP), including the weekly sales, stock and intake (WSSI) view, connects the sales forecast with stock and buying assumptions.
Why are there 60 extra units on order?
The revised plan requires 360 incoming units, but 420 remain ordered. The difference is 60 units.
Do I need to replace my ERP to use Core?
Not necessarily. Core is the planning workspace. Horizon is an option when the retail ERP records also need attention; the required connection to an existing ERP should be agreed for the business.
When does the purchase order change?
When an authorised amendment is agreed and recorded. Reducing the sales forecast alone does not change the supplier commitment.
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.