Pack change: tell the channel before the shelf

The pack change itself is a production problem. Telling everyone about it is a sequencing problem, and it is the part that turns a routine update into a trust problem when it goes wrong.

None of this is a negotiation. You are not asking a buyer for permission or trading terms. You are removing surprise, and the price of getting it wrong is credibility rather than margin.

Order matters more than the message

Your own sales and key account team, first. They get asked first, usually in a corridor, and the worst answer they can give a buyer is that they had not heard. Brief them with the change, the reason in one sentence, and the date the first new-pack stock leaves your warehouse.

The category buyer or account manager, second. One named human at each platform and each modern trade account. This is a heads-up, not a request. What they need is the SKU list, whether the barcode changes, and whether anything they sell against moves: net quantity, price, ingredients, claims.

The platform catalogue or content team, third. Different people, different inbox, different requirements, and they will not have heard it from the buyer. This is where the mechanical work actually gets scheduled.

Distributors, super stockists and your CFA, fourth. They are holding old stock and they will pick up rumours from the trade before you reach them. Tell them what happens to what they hold before they ask. Your distribution structure decides how many hops this has to travel.

Customer support and whoever reads your reviews, last, but before the first new pack ships. They field the “this is not the pack in the photo” messages, and they need an answer that does not sound improvised.

The rule underneath the order: no buyer should hear about your pack change from your distributor, from a store walk, or from a shopper review.

The image and the stock do not change on the same day

This gap causes most of the noise. A listing image changes the moment someone hits save. Physical stock changes node by node over weeks, as old inventory drains through a pipe you only partly control. For that whole period a shopper either sees the new pack and receives the old one, or the reverse.

Decide in advance which direction you would rather be wrong in, and decide it per fulfilment node rather than per brand. The usual answer is to hold the image until the new pack is the majority of what ships from that node, because a shopper who receives an unexpected old pack complains less than one who receives an unexpected new one. The exception is a change the shopper is meant to notice, where the old image undersells the reason you changed at all.

Whichever way you go, write the answer down before the images are ready, or the decision gets made by whoever has catalogue access. The mechanics of holding both states are in running two pack versions on shelf; the stock side sits in changing pack artwork without stranding stock.

What a platform will typically want

Requirements differ by platform and they change, so treat the list below as a class of question to prepare answers for, not as anyone’s stated policy, and confirm the current version with your account contact.

• Whether the barcode changes. That single fact usually decides whether this is an edit to the existing listing or a new listing, and therefore whether you keep your review history.
• Whether any declared attribute moves: net quantity, MRP, ingredient list, allergen information, country of origin, shelf life.
• New images to their current spec, including the pack faces used for verification.
• A document set, where the change touches anything the platform verified at onboarding.
• A date from which the new pack ships, so their content and inwarding teams are not working from different assumptions.

Where the change touches a declared or regulated element, get the scope confirmed by your own legal or regulatory advisor as well as by the platform. Platform content rules and statutory requirements are not the same thing, and clearing one does not clear the other. Existing label obligations sit in labelling for ecommerce, as background rather than guidance on your change.

One thing to keep separate: a pack change surfaces every stale attribute on the listing. Resist fixing all of it at once. A catalogue audit is its own job on its own cadence, and folding it in makes the change look bigger than it is.

When the shelf gets there first

The failure mode is not a dispute. It is a buyer finding your new pack during a store walk, or in a complaint forwarded by their own team, and realising nobody told them. What changes is that the account starts verifying things it used to accept, asks for confirmations it never asked for, and treats your next forecast with more suspicion. That tax is paid over the following two quarters and never appears in a cost model. Category managers are measured on surprises they did not cause and cannot explain upward, and you have just handed them one.

Keep it away from commercial conversations too. If your annual terms discussion is live, do not bundle the pack notice into it. Putting a change notice inside a terms negotiation invites the buyer to price it.

One notification pack, sent five times

Write it once. One page plus an image sheet.

• What is changing, and just as importantly what is not.
• The SKU list with your codes and the platform codes, and the barcode against each, flagged where it changes.
• A yes or no line against each of net quantity, MRP, ingredients, claims, shelf life and case configuration.
• Before and after images at the size they will actually be seen.
• The date the first new-pack stock ships from your warehouse, and your best estimate of when it reaches shelf.
• What happens to old stock, in one sentence.
• One named contact who can answer follow-ups.

Send the same document to all five audiences. Different people will care about different lines, but a single source stops your buyer and your distributor working from two different stories. If the change runs deeper than artwork, the notification widens with it and reformulation brings its own downstream list. Build it after costing the change in what a pack change actually costs, and after satisfying yourself, using when not to change the pack, that it should happen at all.