A multi-market order can look like one total on a spreadsheet while hiding several different decisions. A launch quantity is not a replenishment forecast, and a packaging version is not simply a colour choice. Treating them as one line makes it hard to see what has been confirmed, what is a planning assumption and what still needs a commercial decision.
This planning scene places a trimmer beside blank package mockups. The selected product record and project documents determine the final product and packaging configuration.
Begin with separate demand stories
Write a short demand story for each market and each package version before adding quantities. A first-order story records the planned launch window, channel, assortment role and the date by which the goods are needed. A replenishment story records the signal that will trigger the next review, such as a defined sell-through report, retailer inventory check or campaign decision. Neither story needs an invented volume to be useful.
The public YP-7220 record identifies an existing beard-and-hair trimmer listing for close trimming and edging. It is a reference point for the selected product record, not evidence that every market will use the same package, claim set, quantity or replenishment timing.
Use one forecast card per market-package pair
Instead of one global total, give every market-package pair its own card. This is a planning device, not a promise of minimum order quantity, price, lead time, stock or availability.
| Forecast card | First-order fields | Replenishment fields | Keep open until confirmed |
|---|---|---|---|
| Market and channel | Planned launch date, channel and assortment role | Review cadence and the owner of the next signal | Actual demand, retailer acceptance and final allocation |
| Selected product record | Model code, sample or revision reference | Any approved change that would affect a later order | Whether a similar product record can be substituted |
