Planning Software and ERP: Why You Need Both

ERP records the transaction; planning tests the next decision

ERP stands for enterprise resource planning. In retail, the operational record connects products, stock movements, purchasing and financial transactions according to the modules and integrations in use. That record answers questions such as which units were received, which order is outstanding and which stock adjustment was recorded. Its reliability matters more as stores, products and channels grow.

Merchandise planning asks a different set of questions: what will sell over the remaining weeks, how much stock should be left, and what intake can the budget support? ERP vs merchandise planning is a question of responsibilities rather than a contest between products. Some ERP systems include planning capabilities. The retailer still needs to distinguish recorded transactions from forecasts and approved plans.

Merchmix Core provides the planning workspace, including budgets, MFP/WSSI, open to buy and assortment planning. Horizon is Merchmix’s retail ERP option. The existing ERP can remain the system of record; adopting Core does not by itself require replacing it. Confirm the required connection and supported workflow for the retailer’s own systems.

Start with a reconciled stock and order position

The two older ERP articles described the operational pressure created by more stores, channels and products: conflicting stock totals, delayed reports and repeated manual entry. Those concerns belong in the transaction record first. A forecast based on an unreconciled opening position can look precise while answering the wrong question.

Before the weekly planning review, agree the product identifiers, locations, period boundaries and valuation basis. Distinguish physical stock from stock that is reserved or unavailable. Outstanding orders need quantities, statuses and relevant dates; an order outside the selling window should not be treated as usable intake for that window.

Core needs a consistent operational starting point. Horizon’s documented retail scope includes styles, variants and SKUs, receiving and stock corrections. Where another ERP holds those records, establish which system owns each field and how the planning team will identify missing or stale updates. Do not assume every integration updates instantly.

A changed forecast does not change a purchase order

Consider an independent apparel example for one selling period. Opening stock is 180 units, confirmed intake is 420 units and planned sales are 450 units. Expected closing stock is 150 units. All quantities refer to the same merchandise scope and period.

The planner reduces expected sales to 390 units after reviewing the current selling pattern. Opening stock and confirmed intake remain unchanged, so expected closing stock rises to 210 units. The operational record can be accurate in both views: the change is the sales assumption, not a newly received delivery or an amended purchase order.

If the retailer retains its 150-unit closing target, required intake becomes 360 units: 390 expected sales plus 150 closing units minus 180 opening units. The existing 420-unit order is 60 units above that requirement. At an assumed $35 unit cost, the gap represents $2,100 of committed stock at cost. It is neither a confirmed cancellation nor a saving.

Use Core to make the planning consequence visible

Core brings budgets, MFP/WSSI and buying assumptions into the planning discussion. MFP/WSSI is the merchandise financial planning view that puts sales, stock and intake across trading periods. Open to buy, or OTB, is the remaining buying allowance under the selected plan and calculation basis.

In this example there is no room for additional intake against the retained closing target: existing orders exceed the current requirement by 60 units. That does not mean the supplier has agreed to reduce an order. The buyer must examine timing, terms and the authorised alternatives before treating any commitment as changeable.

Keep the original plan and revised outlook distinguishable. Review whether the weaker sales assumption concerns a particular style, size, location or week before applying it more widely. The plan should explain which input changed and what decision follows, rather than overwrite the transaction record to make the totals look aligned.

Keep the ERP as the operational record

The buyer could request a quantity amendment, investigate a permitted date change or accept the higher closing position. Each option has a different commercial consequence. Until the relevant amendment is agreed and recorded, the operational commitment remains 420 units in this example.

When an authorised change is confirmed, reconcile its quantity, status and timing back into the planning position. A planned reduction, a supplier response and a recorded order amendment are separate states. Keeping them separate prevents the team from reporting the $2,100 gap as cash recovered before anything has changed.

An ERP’s order controls, permissions and transaction history support this operational discipline. Core supports the merchandise decision around that record. The precise hand-off depends on the connected system and configured workflow; neither the article nor its animation asserts that an order has been changed.

Choose Horizon when the record layer also needs attention

Merchmix Horizon is the retail ERP option for teams reviewing the operational record as well as planning. Its product model covers styles, colours, sizes and sellable SKUs. Its documented receiving and stock-correction workflows support the question of what physically changed and why.

Keeping an existing ERP and adding Core is another route. Start with the actual gap: a team that trusts its operational records but struggles to compare forecasts, budgets and intake has a planning problem. A team that cannot reconcile receipts or product identities also needs to address its operational foundation.

Assess purchasing, finance and commerce requirements against the available scope before choosing Horizon or changing an existing connection. Parts of those workflows and integrations are only partially available in the current product description. Do not infer complete accounting replacement, universal connectors or an implementation timetable from the fact that planning and ERP can work together.

Run a review that ends with a decision and a reconciliation

Bring the same period, product scope and valuation basis to the review. Establish the ERP stock and order position first. Then compare the approved Core plan with the current outlook and identify the quantity or timing gap. Give the resulting decision an owner and a clear approval path.

For the apparel example, the review should leave a precise statement: 420 units remain committed, the revised plan requires 360, and 60 units need a commercial decision. If the order cannot change, the team must decide how to manage the 210-unit expected closing position. Approving the lower forecast alone does not resolve it.

The useful outcome is a planning decision that can be reconciled with operational reality. Core explains what the retailer intends to do; Horizon or the existing ERP records the transactions that actually occur. Keep both views connected without confusing a proposal with a completed action.

Common questions