Plan the season once, and trade it from the same numbers.

Merchmix is a merchandising and inventory operating system with intelligence at its core, helping retailers connect planning, buying, allocation, suppliers and execution in one platform. For planners it runs the cycle from budget through merchandise financial planning and open to buy to the weekly trade review, all on one set of committed numbers, so the plan is traded against rather than rebuilt.

Both. Merchandise financial planning and Weekly Sales, Stock and Intake describe the same grid, and Merchmix calls it MFP. Sales, stock, intake and margin sit on it by week, planned and committed in one place. The term a business uses tends to follow where its planners trained, so the two are used interchangeably across retail. What matters is that the plan, the trading position and the open to buy all read from the same grid rather than three files that have to be reconciled.

Yes. Forecast values are edited in the grid itself, at department, category or subcategory level, and any earlier version can be restored, so an adjustment made in the trade meeting does not have to be rebuilt afterwards. Merchmix Intelligence can also re-forecast as the numbers move, so the plan reflects the week that actually traded rather than the assumptions the season opened on. Every version is saved, so a plan can be compared against what it looked like before a change.

Open to buy recalculates against the live sales and stock position rather than on a periodic refresh, so the number a buyer commits against is the number the plan holds that day. Orders count against the buy the moment they are raised, and sales, intake and forecast changes feed the position without anyone maintaining a separate sheet. Every order is tested against the remaining budget before approval, so the budget is checked at the point of decision rather than reconciled weeks later. For the underlying calculation, see our guide to open to buy.

Yes. Sales, margin, intake and closing stock are phased across the trading year by department in Budget Builder, and the approved budget flows into the merchandise financial plan rather than being re-keyed into it. That means the season a business signs off in March is the season it trades against in October, and a change to the budget position reaches the weekly plan rather than sitting in a separate file that someone has to remember to update.

Yes. Once committed, the weekly plan is the record that allocation and replenishment work from, so stock moves against the plan rather than against a copy of it. The weekly trade review reads straight off the same grid, which is why the trade pack can be compiled and written automatically rather than assembled by hand every Monday. Decisions taken in the review update the plan they came from, so the next week starts from where the last one finished.

No. Most retailers start with the planning layer, usually Core or Core alongside allocation and replenishment, and add suppliers, product development or the wider system afterwards. Every module added works off the same live numbers from the day it is switched on, so there is no migration between stages. Onboarding runs as a six-week proof of concept on your own data, so the first thing a team sees is its own season rather than a demonstration tenant.