When Product Development and Planning Don't Talk

The mismatch begins before purchase orders exist

Design can develop more candidates than the range intends to buy. That is not necessarily waste: some options are exploratory. The problem begins when different teams treat the candidate list as the committed range without checking quantities, costs and the financial boundary.

Forge supports the product record from concept towards sign-off. Core supports option planning, budgets and MFP/WSSI. Connect them through an explicit decision about what is being considered, what is costed and what is accepted for the next plan, rather than assuming every developed style has approval to buy.

Agree the identity and maturity of the hand-off

A planning placeholder and a developed style need a clear relationship. Keep style, colourway, supplier, cost basis and revision identifiable so a buyer does not compare one concept’s expected cost with another product’s approved specification. A shared name alone is not enough.

Forge’s product context and Core’s range context help keep that relationship visible. Confirm which fields and accepted states pass between them in the configured workflow. This article does not claim that every document or development edit synchronises instantly into a live buying commitment.

Put the candidate count beside the envelope

The worked Core plan allows four styles at 200 units each and a $30 assumed unit cost: 800 units and $24,000. Development has five candidates. Treating all five as 200-unit buys would imply a thousand units and $30,000, or $6,000 above the envelope.

One proposal retains all five at 160 units each. It still totals 800 units and $24,000. Another could retain four buys while deferring the fifth. These are different commercial choices, not proof that reducing depth preserves all the expected sales or that the fifth candidate must be discarded.

Make the changed depth visible to the buyer

Keeping five rather than four styles lowers the average opening quantity from 200 to 160. The team needs to examine size depth, store coverage and the customer role of the extra option. A budget-neutral range can still be too thin to serve its intended locations.

Core makes the option and quantity consequence reviewable. Forge keeps the actual developed product and costing context available. Do not describe a balanced financial total as a completed range decision if the product specification, cost or usable arrival remains unresolved.

Replace provisional costs deliberately

An early $30 cost may be a planning assumption rather than a negotiated quote. When the product matures, compare the accepted new basis with the original before carrying it into Core. A revision that adds detail but changes cost can alter the buy even when option count stays constant.

Retain the source of the cost, its included components and the relevant quantity. Forge supports cost sheets and supplier comparisons; Core holds the resulting forward assumptions. Acceptance of a development cost is not automatically authority to increase the budget or amend an existing order.

A cost sensitivity can expose another hand-off issue. If the accepted unit cost becomes $32, the 800-unit proposal costs $25,600, or $1,600 above the envelope. Five styles at 150 units each would fit $24,000 at that cost, but would reduce the total to 750. Keep that separate from the original $30 comparison.

Give the two teams a common decision gate

The hand-off should answer which candidates are ready for a buying decision, which remain exploratory and what evidence is missing. An unresolved concept can remain useful without being counted as confirmed range supply. A complete-looking folder can still lack the commercial information the planner needs.

Choose a review point early enough to change depth, supplier or timing. The purpose is not a product tour or another approval form. It is a consistent distinction between development effort, accepted range scope and the actual financial commitment.

Identify the point where a provisional product becomes eligible for a buy decision. A technically complete style may still lack accepted cost or a usable date, while an affordable placeholder may not yet be technically feasible. A shared gate should make those missing conditions visible rather than equate development completion with buying authority.

Close the gap with an accepted range basis

For the example, five 160-unit candidates fit the $24,000 envelope at the stated cost, while five 200-unit buys do not. The buyer still needs to justify the thinner depth and accepted costs. No purchase order is created or cancelled by this comparison.

Merchmix Forge and Core connect product maturity with the financial plan so an attractive range becomes a supported buying decision. Let development explore, but make the quantity and commitment explicit before a candidate becomes stock the business must fund.

Common questions