What is a model-year changeover?

A model-year changeover is the transition from one engineered version of a product platform to its successor — a new stroller chassis, a revised car seat shell, an updated crib construction. It differs from a season change in three ways: it is driven by engineering and certification rather than by fashion, it often runs on a multi-year rather than annual cadence, and it forces every colourway or configuration built on the outgoing platform to an exit simultaneously, whether or not each was individually ready to retire.

How far ahead should a changeover run-out be planned?

Far enough that the remaining inventory can clear at a realistic rate of sale before the boundary, which means the schedule is derived rather than chosen. Work backwards: take the units expected to remain, divide by a realistic weekly rate of sale by channel, and that many weeks before the changeover is when the run-out has to begin. In practice the binding input is usually the last purchase order rather than the first markdown — stopping receipts late is far more expensive than starting markdowns late.

Why doesn't discounting always clear superseded juvenile inventory?

Because the constraint can be regulatory rather than commercial. When a safety standard changes or a platform is superseded, remaining stock may lose its route to market entirely rather than merely becoming less desirable, and no price makes an unavailable transaction happen. This breaks the assumption underneath most markdown planning. Exit planning in this category therefore has to manage inventory down to the boundary on a schedule, rather than allowing it to accumulate on the expectation that price will resolve the position later.

Should the outgoing and incoming model overlap in market?

A short controlled overlap is usually right, but it should be a decision with a defined length rather than a drift. Overlap protects against a supply gap on the new platform and gives price-sensitive buyers a reason to take the outgoing stock, which helps the run-out. Left undefined, it does the opposite: the outgoing model cannibalises the launch it was supposed to fund, and the run-out stalls precisely when it needs to accelerate. The useful discipline is to set the overlap window and the price gap between the two at the same time as the changeover date.

What is a running change and why does it complicate planning?

A running change is a mid-lifecycle modification to a platform — a revised component or a supplier change — made without a full model-year transition. It complicates planning because it creates two physically different units under one commercial name and often one SKU, so inventory that reports as a single position is actually two. If the change is certification-relevant, the two are not interchangeable at all, and any plan that treats the SKU as homogeneous will misstate what is genuinely available.

Who should own the changeover date?

Engineering and certification set the earliest feasible date, but the commercial changeover date should be a joint decision that includes merchandising, because it determines the run-out runway. The common failure is treating the date as a product milestone communicated to planning rather than a constraint negotiated with it. Moving a changeover four weeks is often cheap in engineering terms and worth a great deal in inventory terms, and that trade is only available if the conversation happens early enough.

Planning a Model-Year Changeover

A model-year changeover forces every colourway on the outgoing chassis to an exit at once, on a date engineering sets rather than demand. This guide covers backwards-planning the run-out, why discount does not always clear certified stock, handling running changes mid-year, sequencing the channel transition, and the overlap decision most brands get wrong.

Why a changeover is a planning event, not a product event

In most retail, product transitions are gradual and negotiable. A style is dropped when it stops selling; a colour is retired when the season turns. A model-year changeover is neither gradual nor negotiable. It is a dated boundary set by engineering and certification, and when it arrives every configuration built on the outgoing platform stops being current at the same moment.

That simultaneity is the whole difficulty. A colourway that is selling beautifully and a colourway that is struggling both exit on the same date, because what retires is the chassis underneath them. Nothing in a normal seasonal exit process is shaped like this, which is why brands that plan changeovers as though they were season ends reliably end up with a stranded position.

The wider category context — two lifecycles in one product, certified inventory, cube economics — sits in the baby and juvenile planning guide. This guide is about executing the transition.

Derive the run-out schedule; do not choose it

The most common mistake is picking a markdown start date that feels reasonable. The date is not a preference. It is an output of arithmetic that should be run explicitly:

Project the units that will remain at the point the run-out would begin, by channel and by configuration.
Establish a realistic clearance rate per week per channel — realistic meaning derived from how comparable run-outs actually cleared, not from the current full-price rate of sale, which will not hold.
Divide. That many weeks before the changeover boundary is when the run-out must start.
Compare that date to today. If it has already passed, the problem is larger than a markdown schedule and should be escalated as an inventory position rather than managed as a promotion.

Weeks of supply is the natural unit for steps 1 to 3, with one modification that matters: the coverage question here is not "how long will this last" but "will this clear before a fixed date", which makes the remaining runway the denominator rather than an open horizon.

The binding decision is usually the last purchase order, not the first markdown. Receipts arriving late in a platform's life are the single largest contributor to stranded stock, and they are almost always authorised long before anyone is thinking about the changeover. A run-out plan that starts by scheduling markdowns has already accepted a position it could have avoided by stopping receipts eight weeks earlier.

Why discount is not a guaranteed exit

Most markdown planning rests on an unstated assumption: that a deep enough discount clears any stock eventually. In juvenile hard goods that fails in two ways, and both remove the option rather than making it more expensive.

A superseded certified platform may lose its route to market. If a standard changes or the platform is formally superseded, remaining inventory can become unsellable rather than merely unattractive. There is no clearing price when the transaction is not available.

A recall is a stop-ship. It is not an aggressive markdown; it removes units from sale immediately and requires tracing them to holders — an operation no merchandise plan performs, and one that belongs to quality and consumer registration systems.

The practical consequence is that carry-forward — the apparel planner's standard relief valve, moving goods into the next season — is frequently unavailable. There may be no next season for that chassis. Exit planning therefore has to be forward-looking and scheduled, treating the changeover as a hard constraint to manage inventory down to, rather than a date after which aging inventory gets dealt with.

Deciding the overlap deliberately

Should the outgoing and incoming models be in market at the same time? Usually yes, briefly — but the value comes entirely from the overlap being defined rather than allowed to happen.

A controlled overlap does two useful things. It protects against a supply gap if the new platform's first production runs late, which is common. And it gives price-sensitive buyers a reason to take outgoing stock at a discount, which is exactly the demand the run-out needs.

An undefined overlap does the opposite. The outgoing model, now cheaper, cannibalises the launch it was supposed to help fund, and because it is still available the urgency drains out of the run-out precisely when it should be accelerating. Both models under-perform, and the post-mortem usually blames the new platform.

The discipline is to set three things at once, at the point the changeover date is set: the overlap window length, the price gap between the two models, and the date the outgoing model comes off the primary merchandising position. Deciding the price gap later, under pressure, is how the cannibalisation happens.

Running changes: two products, one name

A running change is a mid-lifecycle modification — a revised component, a new supplier, a materials substitution — made without a full model-year transition. It is operationally sensible and it quietly breaks the plan's model of inventory.

After a running change, there are two physically different units carrying one commercial name and frequently one SKU. Inventory reports one position. In reality there are two, and if the change is certification-relevant they are not interchangeable: a service part, a compatibility claim, or a recall scope may apply to one and not the other.

The planning defence is unglamorous but effective: give a certification-relevant running change its own identifier in the data model, even when marketing keeps one name. If the two units cannot be substituted for each other in every circumstance, they are not one item, and a plan that says they are will misstate availability at exactly the moment accuracy matters most.

RetailNorthstar has no baby gear or juvenile products customers today — apparel is the flagship vertical and that is where its track record is. What it offers a changeover is a configurable lifecycle that carries the chassis and its colourway layer on separate cadences, with coverage and aging visibility against a dated boundary so the run-out schedule can be derived rather than guessed. Certification records, serial traceability and recall execution sit outside the platform and belong in ERP and quality systems.

Sequencing the channel transition

Channels do not transition at the same speed, and forcing them to is a reliable way to strand stock.

DTC moves fastest. The brand controls the site, so the new platform can be presented the day it is available and the outgoing one can be repositioned to a clearance context immediately.

Specialty retail moves at the pace of the account. Independent doors carry limited depth and often want to sell through what they hold before taking new inventory. Pushing a changeover ahead of that appetite creates returns pressure and account friction, and specialty accounts are usually the ones who most reward being handled well.

Mass retail moves on the reset. The transition happens when the planogram changes, which is the retailer's calendar, not the brand's. A changeover that lands just after a reset has effectively lost a full cycle of shelf presence for the new platform, while leaving the outgoing model in prime position.

The workable sequence is generally to lead in DTC, use it to establish the new platform's positioning and read early demand, run specialty on account-by-account timing with clear run-out support, and align mass to the reset — planning backwards from the reset date, since it is the least movable of the three.

The connected version

Each of these steps is individually manageable. What makes changeovers painful in a spreadsheet process is that they live in different places: the changeover date with engineering, the remaining inventory in a warehouse report, the markdown schedule with merchandising, the account timing with sales, and the reset calendar with the retailer. By the time they are reconciled, the run-out window has usually shortened.

In a connected model, the changeover is a modelled boundary on the platform in the same assortment plan that carries its colourways, with inventory coverage reported against the remaining runway rather than an open horizon, and receipts in the buy plan constrained by the boundary rather than by lead time alone. The question "will this clear before the date" becomes a number in the plan instead of a spreadsheet exercise someone runs when it is already too late.

For the wider category picture, see the baby and juvenile planning guide and the baby and juvenile industry page.

See how RetailNorthstar reports coverage against a dated changeover boundary rather than an open horizon.

Book a Demo →

Related resources

Merchandise Planning for Baby & Juvenile Brands — The pillar this guide sits under
Planning With Registry Demand — The forward signal that improves run-out forecasts
Baby & Juvenile Brands — RetailNorthstar — Platform fit for juvenile planning teams
Inventory Optimization — Coverage and aging against a hard boundary
Weeks of Supply Formula — The arithmetic behind the run-out schedule
Carry-Forward — Glossary — The relief valve that is often unavailable here
Aging Inventory — Glossary — Why reactive exit management fails in this category