By Bartosz Grajewski, sales director, TRANSPAK Copacking

I HAVE come to see late-stage work as a bit like fire: dangerous when it is out of control, but extremely useful when it is contained and directed. When you have the right processes in place – and a partner you can genuinely rely on – those “firefighting” jobs stop feeling like emergencies and start to feel like a capability you can lean on.

But it is no longer the whole story. A growing number of consumer brands now build their networks so that products sit in a generic, unfinished state for as long as possible, and get packaged, labelled or kitted only once they are close to the market that will sell them. The principle is not new. It is postponement, a long-standing idea in supply chain design, now applied to value-added services. And it quietly changes how teams think about three things: how many SKUs they carry, how much working capital they tie up, and where customisation should actually happen.

The principle: hold generic, finish late

Postponement means one thing. Hold off on the final, market-specific version of a product until the last sensible moment. A brand makes a generic base. Then it waits. Once demand is clearer and the goods are nearer the shelf, it decides how to finish them, and where. The finishing is the differentiation: the language on the pack, the regulatory wording, the promotional flash, the gift set.

This matters most for a brand selling one core range across several European markets. The same product might need a different language in each, a different compliance line, a promotion built for one retailer, a different format. Lock all of that in at production, and you are betting on every market months before you know how any of them will buy. Postpone it, and the bet stays open. What really shifts is the question being asked. Not how many finished SKUs do we need, but how late can we leave the finishing, and where should it happen.

One personal care brand we work with made a deliberate choice to design postponement into its European launches. Instead of printing a different finished pack for every market and every promotion, it runs a generic base pack with neutral artwork and keeps the market-specific elements – language labels, on-pack flashes, sleeves and display materials – separate. For a new range, they will often launch an initial wave with one or two promotional concepts, while holding additional sleeve designs and label sets in reserve at the late-stage node. If one execution clearly outperforms the others, they do not have to wait for the next factory run; they convert the remaining generic stock into the winning variant within days, simply by changing the materials fed into the finishing line. The benefit for them is not heroics, but the absence of drama: fewer SKUs, fewer write-offs at the end of each season, and the ability to double down quickly on what the market has just told them.

In other words, the late-stage node is there to make conscious choices reversible – not just to patch over bad ones.

A few years ago, a global confectionery brand badly misread demand for a Valentine’s Day range in several Eastern European markets. The volume of heart-shaped packs looked sensible on a spreadsheet in autumn; by mid-February it was clear that a large part of the stock would not sell through, and there was no realistic way to carry it into the rest of the year in that form. We ended up helping them strip out and rework a significant portion of those products into a completely different Easter promotion, using new sleeves and display materials. It saved a lot of value, but it was a classic example of committing to very specific finished SKUs too early, with very little room to manoeuvre once the season moved on.

The SKU and inventory problem it solves

Start with the SKU count. Give every market its own finished SKU, with its own language and claims and promotional variants, and the catalogue swells quickly. Each line has to be planned, allocated, stored, counted. Multiply markets by variants by promotions and the tail gets very long indeed.

Hold one generic product instead, and apply the market labels late, and the picture changes. Working capital now sits in fewer, more flexible units rather than dozens of committed finished lines. Obsolescence risk falls, because generic stock can go wherever the demand actually turns up, instead of stranding as finished goods in a country that did not sell through. Planning gets simpler too, with fewer lines to reconcile and fewer awkward write-offs at the end of a season. The textbook version is neat enough: ten finished SKUs for ten markets become one generic SKU plus ten sets of labels, applied only when the order is real.

Where the value-added work belongs

So if you finish late, where do you do it? Broadly, two options. The first is to run the value-added work, the kitting and labelling and shrink wrapping and display building, inside the distribution centre. It is close to dispatch, and that is the appeal. The trouble is that this work and core fulfilment want different things. A DC is built for high-volume, repeatable picking. Feed a stream of small, fiddly finishing jobs into it and they compete with the core flow for space, for people, for the supervisor’s attention. A pan-European centre trying to build thousands of seasonal gift sets while running its normal pick and pack tends to do neither especially well.

The alternative is a dedicated node, or a specialist co-packing partner, sitting beside the core network. The trade-off flips. Finishing capacity is ring-fenced, so the DC keeps its rhythm. A peak, a promotion, a seasonal surge gets absorbed somewhere designed to absorb it. You pay for that with an extra handling step and a lead time that depends on where the node sits. Which model wins comes down to one thing: how spiky and how varied your finishing work really is.

What it demands of the operation

Postponement leans hard on the finishing operation, because by design it runs close to the deadline. Speed comes first. The whole point is to act on late information, so a slow node defeats the purpose. Then accuracy. A wrong language, a wrong claim, the wrong offer on a multipack: a rejected delivery at best, a recall at worst. The operation also has to handle short, varied runs without dropping whatever else it is doing, and keep records good enough to satisfy a regulator and a nervous brand-protection team. None of that is glamorous. All of it is the job.

An example makes it concrete

A recent project brought this home to me. A multinational FMCG client changed the mechanics of a promotion for a major retailer less than a week before the first dispatch. The artwork changed, the on-pack message changed, and the mix of SKUs the retailer wanted on each pallet changed with it. On paper, it was exactly the kind of late change everyone dreads.

Because the finishing work was already sitting in a dedicated late-stage node, with people who were used to short runs and rapid changeovers, it did not turn into a crisis. We re-sequenced the jobs for a couple of days, brought in an extra shift over the weekend and rebuilt the affected kits to the new specification. It was a hard push, but the loads still left on time and the core DC never had to stop its normal flow. That, for me, is the acid test. Late information will always arrive. The question is whether your operation is built to absorb it without breaking everything behind it.

The shape is always the same. Something changes late. The value of the node is simply whether it can cope without breaking the chain behind it.

When to build it and when to buy it

Build or buy? A few honest questions settle most of it. Start with utilisation. If finishing demand arrives in peaks, owned capacity sits quiet for much of the year, and idle capacity is expensive. Then labour. Trained, flexible hands for manual finishing are genuinely hard to find and harder still to scale, and a partner doing this every day usually has the better pipeline. After that, the money question: capex against opex, plus the risk of buying kit for a packaging format that next year’s marketing brief quietly kills off. And the more promotional and unpredictable your category, the more you are really buying flexibility, not machinery.

This holds across the board, from seasonal confectionery to personal care to drinks. But buying is not the default answer. Where the work is steady, the volumes high and the format settled, or where control and confidentiality matter more than flexibility, keeping it in-house is the sensible call.

A checklist for supply chain leaders

Before rebuilding a network around any of this, a handful of questions are worth sitting with:

• Where do we actually need differentiation, and where are we customising out of habit?
• How many SKUs could collapse into one if we held more product in a generic state?
• Have we got the speed, the quality control, the traceability and the flexible labour that late finishing needs, or can we build them?
• Where in the network does late-stage work pay off most, and disrupt least?
• And which partners can really do this, rather than simply say they can?

The brands getting the most out of postponement are not the ones treating late-stage packaging as an emergency. They worked it out earlier than that. They chose to finish late, on purpose.