Two pack versions on shelf: the messy window
The first complaint is never about the new pack. It is from the customer who received the old one after seeing the new photograph on the listing.
- Channels drain at different speeds, so the coexistence window is set by your slowest channel rather than the average, and returns keep pushing old packs back into sellable stock after you thought the change was finished.
- A marketplace or quick commerce listing carries one main image while both packs are shipping, so some share of deliveries will not match the picture whatever you do.
- Give the two versions a mark you can read at goods-in and in a photograph, separate from the batch code, so you can answer version questions from data rather than from whoever picked the pallet.
- Agree the stopping rule in writing before the change, with a number attached, or the old version never formally dies and keeps reappearing through returns.
The first complaint is never about the new pack. It comes from the customer who received the old one after seeing the new photograph, and it arrives as a one-star review suggesting the item might be fake. That window, when both versions are in the market at once, is the part of a pack change nobody schedules and everybody experiences.
This is about pack version, not date code. Rotating stock by date is a separate and permanent discipline covered in expiry and FEFO management. What follows is about the temporary condition of shipping two different looking packs of the same product.
Why coexistence runs longer than planned
Channels drain at different speeds, and the window is set by the slowest one rather than the average.
- Your own D2C warehouse crosses over the moment you decide, because you control the pick face.
- Quick commerce dark stores turn quickly, but there are a lot of them and they cross over city by city rather than all at once.
- Marketplace fulfilment centres holding regional stock can sit on a slow SKU for a long time, and you cannot see the age of what is in each node.
- Distributors and modern trade hold the longest, and you have already invoiced that stock, so it is not yours to move.
Then returns reopen the window after you thought it had closed. A unit sold in the old pack, returned and graded back into sellable stock, ships again months later looking exactly like the thing you announced was gone. Plan for the tail, not the crossover.
One listing, two packs
A marketplace or quick commerce listing has one main image. It has no version field, no date range and no way to say that both of these are correct right now. Whichever image is up, a share of your deliveries will not match it, and the only real question is which share you would rather have.
The main image also has a job unrelated to your transition, and the rules around it do not relax because you are mid-change.
When to change the image
Three options, each with a cost you should choose deliberately rather than discover.
- Early, before the new pack ships. The new pack looks established and the actual switch is invisible. The price is that every delivery mismatches the picture for the entire window, which is the longest possible exposure to the complaint.
- At changeover, when the first new units ship. Logically tidy, and matched for whichever channel crosses first. Every slower channel is mismatched, and slower channels are usually the bigger ones.
- Late, when old stock is materially gone. Minimum mismatch overall, but the earliest buyers of the new pack receive something that looks nothing like the photograph, and those are the customers most likely to assume the product is counterfeit.
The workable answer for most brands is to switch when the channel carrying most of your volume has crossed, and to use the secondary image slots during the window to show the other version. Secondary images are the one lever a listing actually gives you here. Note also that changing a main image can put a listing into review on some marketplaces, so make the change on a morning when someone is watching account health.
Answer the counterfeit question before it is asked
Write one line, publish it where support can point at it, and use exactly that line everywhere: the packaging has been updated and the product inside is unchanged. Say it only if it is true. If you also changed what is inside, say what changed, because the downstream of a reformulation includes people noticing.
Brief support with photographs of both packs side by side and the approximate window. The subtext of nearly every message you will receive is not aesthetic disappointment, it is a suspicion that the unit is fake, and on marketplaces and quick commerce that suspicion is reasonable. Answering it in the first reply, with images, closes the conversation. Answering it in the third reply produces a review.
Tell the buyer inside the window
Category managers find old packs during store audits and treat them as a compliance finding unless someone has told them otherwise. Keep the note short and factual: what changed on the pack, the date the first new-pack dispatch left, the expected window, and what you want them to do with old-pack stock they still hold. Send both images. This costs one email and removes an entire category of escalation.
If the change was driven by a labelling requirement, whether old-artwork stock may continue to be sold through the window is not a question to settle with the buyer, or with a summary like this one. Confirm it with your own regulatory advisor and then tell the channel what you have been advised.
Keep the versions separable in your own data
Do not rely on the customer noticing, and do not rely on your warehouse team remembering. Put a readable version marker on the pack, distinct from the batch code, which is doing a different job and should stay clean for traceability purposes. A version letter or a short pack code that a picker can read and a photograph can capture is enough.
With that marker you can answer real questions with data. Which warehouses still hold old pack. Which cities have crossed. How many units of old artwork remain and what they are worth. Without it, every version question is answered by opinion, and the answer you get is always more optimistic than the truth. Keep the two artwork files clearly separated in your library as well, because the wrong file going to a printer is how a dead pack gets resurrected.
Write the stopping rule before you start
Agree in advance what makes the old version dead, with a number attached. Either remaining units across all channels below a stated weeks of cover, or a rupee value below which chasing the tail costs more than it recovers.
When the rule triggers, do all of it at once: close the old artwork for production, remove the transition secondary images, retire the support script, archive the old file with a clear status, and tell the buyer the window has closed. Teams that skip this end up running dual-pack messaging for a year because nobody had the authority to declare it finished. The upstream inventory arithmetic that shortens this whole window in the first place is a separate piece of planning, and doing it properly is what keeps the messy period measured in weeks rather than quarters.