How to Switch to New Logo and Size Takeaway Containers Without Stopping Supply: Old Stock, Pilot Stores, and a Phased Rollout Plan
You have approved a new logo and a new container size, but the warehouse still holds roughly two months of the old packaging. You cannot close stores, and you cannot write off usable stock.
2026-09-03 - 11 min read

Summary: You have approved a new logo and a new container size, but the warehouse still holds roughly two months of the old packaging. You cannot close stores, and you cannot write off usable stock. This article lays out how to run the change as an inventory-led conversion instead of a date-led "big bang": build a store-by-store depletion map first, pick pilot stores that expose real problems rather than flatter the new design, keep old and new packaging separate in ordering systems, and expand in waves only when go/no-go criteria are met. It also covers the supply-side questions buyers usually discover too late — lid and closure compatibility after a size change, artwork proof approval before a print run, and how to phase order quantities so the new packaging arrives in step with the depletion curve rather than all at once.
Why a network-wide switch on a fixed date usually fails
A packaging change looks like a purchasing decision. In practice it is an operations change that touches shelves, delivery bags, packing lines, POS rules, and staff habits at every site.
Two failure patterns show up repeatedly. The first is a calendar-driven cutover: a date is announced, new containers ship everywhere at once, and stores are left with pallets of old stock they are told to stop using. That converts usable inventory into a write-off. The second is the opposite — no rules at all, so old and new run side by side indefinitely, orders get placed against a single blended code, and nobody can tell what is actually left.
There is also a quieter risk. A pilot that succeeds proves the new container works under selected conditions with attentive staff and a small SKU set. It does not prove the change repeats across every store format, every volume band, and every storage constraint. Wider deployment introduces variation in shelf depth, delivery-bag fit, operator familiarity, and reorder discipline that a small trial never surfaces.
The practical fix is to make the transition inventory-led rather than date-led. Each store switches when its own old stock is close to exhausted, not when a central calendar says so.
Step 1: Build the depletion map before any new container ships
Before allocating a single carton of the new size, get visibility into what exists and how fast it moves. For each location you need three numbers:
- On-hand quantity of the old container, by size and variant
- Usage rate, in units per week, from actual order volume
- Projected depletion date — on-hand divided by usage rate
That gives you a natural sequencing order. Sort stores by projected depletion date, not by geography or by which manager is most enthusiastic.
A simple segmentation usually emerges:
| Segment | Old stock on hand | Usage rate | Depletion window | Transition role |
|---|---|---|---|---|
| High volume | Low | High | Under 4 weeks | Early pilot candidate |
| Medium volume | Medium | Medium | 4–8 weeks | Second wave |
| Low volume | High | Low | Over 8 weeks | Stay on old stock; receive transfers |
This is the same discipline warehouses already apply to stock rotation. First-In-First-Out picking exists precisely so that older inventory leaves before newer inventory, and it is implemented by recording an arrival date against each item in the warehouse system and physically storing newer stock behind older stock. During a packaging conversion you are applying the same logic across a store network rather than inside a single warehouse (Savino Del Bene on FIFO and FEFO).
One immediate action: stop replenishing the old container to any store scheduled for an early wave. Ship old stock only where it already sits. This single rule prevents you from buying inventory you have already decided to retire.
Step 2: Choose pilot stores that will expose problems
The temptation is to pilot in flagship stores where staff are strongest and the new logo photographs well. That produces a clean pilot and a messy rollout.
A useful pilot set is 5–10% of locations, deliberately mixed:
- One or two high-volume stores, so issues surface quickly in real order counts
- One or two average stores that represent the bulk of the network
- At least one operationally awkward store — tight storage, unusual layout, high staff turnover
Guidance on pilot design in other operational domains lands in the same place: keep the pilot to a manageable population, define its objectives before it starts, and limit the number of pilot phases — running too many becomes unmanageable and dilutes the learning (Unisys on setting up an effective pilot and rollout).
What the pilot must actually test
A size change is not only a size change. Write these down as pilot questions, and answer each with a yes or no:
- Does the new container fit existing carrier bags, delivery bags, and shelf depth?
- Does the matching lid or closure still seat correctly, and does it stay sealed in transit?
- Does packing time per order change measurably?
- Does the new footprint change how many cartons a store can hold?
- Do leakage, deformation, or damage complaints move?
- Do customers notice the logo change, and does it need any explanation?
- Does the container still stack in the same way during service?
The lid question deserves special attention. Lids are specified to a rim dimension, not to a container name. A round bowl lid at a 142mm rim matches bowls built to a 142mm rim; a 120mm lid matches a 120mm rim bowl. If the new container changes rim diameter, base diameter, or height, the existing lid inventory may no longer fit — and you now have a second, hidden transition to manage on top of the first. Confirm rim-to-rim compatibility during the pilot, before the wave plan is locked.
Step 3: Deplete old stock deliberately, not randomly
With roughly two months of old inventory, you have enough runway to pilot properly and still finish the conversion. The runway only helps if depletion is directed.
Keep old containers flowing at:
- Lower-velocity stores that will take longest to clear
- Stores holding the largest remaining quantities
- Locations where a packaging difference is least visible to customers
Introduce new containers at:
- Pilot stores
- Stores whose old stock is already nearly gone
- Any location with genuine marketing visibility, once the pilot has passed
Two mechanics make this work. Transfer excess old stock from fast-transitioning stores to slower ones instead of letting it strand. And avoid mixing old and new within the same store on the same day — a single store should finish one before opening the other. Mixed logos on the same order or the same table read as a mistake rather than a refresh.
Hold a small buffer of old stock at the distribution centre until late in the programme. It absorbs any delay on the first production run of the new packaging, which is exactly when a delay is most likely.
Step 4: Separate old and new in your ordering system
This is the step most often skipped, and it causes the most confusion.
Old and new packaging must exist as distinct items in the ordering and inventory system. If both appear under the same item code, you lose the ability to see what remains of the old version, replenishment logic will happily reorder the retired container, and the depletion map you built in Step 1 becomes fiction within a week.
Alongside the item split, define three rules in writing:
Store rule. Stores use old containers until remaining stock reaches zero. Once new containers are issued to a store, that store does not revert to old stock without approval.
Exception rule. Define in advance what happens when a store exhausts old stock earlier than projected — who authorises the early switch, and where the new stock comes from. Also define the fallback path if the new packaging shows a quality issue in the field.
Customer-facing rule. If the product is unchanged and the logo refresh is minor, no announcement is usually needed. If the size change is visible enough that customers may read it as a portion change, prepare a short "new look, same portion" line for staff to use, plus a one-page internal FAQ so associates do not treat the new container as a picking error.
Step 5: Roll out in waves with go/no-go criteria
An eight-week shape works for a two-month runway, adjusted to your actual usage rates:
| Week | Activity |
|---|---|
| 1–2 | Pilot the mixed store set; monitor daily |
| 3 | Review pilot results; adjust size, artwork, or process if needed |
| 4–5 | Convert stores with under three weeks of old stock remaining |
| 6–7 | Convert remaining medium-volume stores |
| 8 | Complete conversion; quarantine and account for residual old stock |
Do not advance a wave because the pilot "looked fine." Set the gate before you start, and require every condition to hold:
- Packing time unchanged or within an accepted tolerance
- Damage and leakage complaints within target
- Lids and closures confirmed compatible
- Stores able to absorb the storage footprint during overlap
- Customer complaints negligible
- Supply of the new container confirmed stable for the next wave's volume
If one condition fails, fix it in the pilot rather than replicating it across the network.
Step 6: Phase the supply side to match the depletion curve
A phased rollout on the store side needs a phased supply plan behind it, otherwise you have simply moved the write-off risk from old packaging to new. Three supply questions decide whether the plan holds.
Can the first order be sized to the pilot rather than to the network? A pilot needs enough units to run a real store for several weeks, not a full network's worth. Where a supplier offers flexible minimums, the pilot quantity and the wave-one quantity can be separate orders — which means artwork problems found in the pilot are corrected before the large run is printed.
Is the artwork locked before production, not during it? A logo change is a print change. On custom-printed orders the practical safeguard is a digital proof generated from your own artwork files and approved in writing before production starts. That approval step is what stops a colour or placement error from being reproduced across an entire wave.
Do the matching components move with the container? If the new size changes a rim or base dimension, lids, trays, or carrier bags may need to change with it. Sequence those items into the same wave, not a later one.
Where Takeawaypack fits in a phased packaging change
Takeawaypack is a foodservice packaging supply chain partner serving buyers in North America, Europe, Australia, and the Middle East, with its own printing facility alongside multiple partner factories. That matters in a transition programme mainly because the two hardest supply constraints during a conversion are order sizing and print accuracy.
On order sizing, minimums are flexible rather than fixed at network scale — standard items typically start around 1,000 units, with bags carrying a higher minimum, and the final figure confirmed on the specific quotation. In practice that allows a pilot quantity and a wave quantity to be ordered separately instead of committing the whole network volume before the pilot has reported.
On print accuracy, custom-printed orders are produced against a digital proof generated from your artwork files, and production begins only after you approve that proof in writing. For a logo change rolling out in waves, that written approval is the control point that keeps wave two identical to wave one.
The catalogue spans the container families most affected by a size or logo change — cups, bowls, boxes, containers, trays, lids, bags, and cutlery — which means a container and its matching lid can be specified against the same rim dimension in one conversation rather than sourced separately and hoped to fit. Lids are quoted against a stated rim diameter with the matching container volumes listed, so compatibility can be confirmed on paper before the pilot ships.
Food contact documentation is confirmed per item, per order, and per destination market rather than asserted across a whole catalogue. If your new size or new material is entering a market with different requirements than the version it replaces, that scope needs to be confirmed for the new specification as part of the transition, not assumed to carry over from the old one.
A short checklist before you approve the plan
- Depletion map exists, with on-hand quantity and usage rate per location
- Replenishment of the old container has been stopped for early-wave stores
- Pilot set includes a high-volume, an average, and an awkward store
- Lid and closure compatibility confirmed against the new rim dimensions
- Old and new packaging exist as separate items in the ordering system
- Go/no-go criteria written down before the pilot starts
- Digital proof of the new artwork approved in writing before the first production run
- Pilot quantity and wave-one quantity ordered separately
- Buffer of old stock retained at the distribution centre through the middle waves
- Residual old stock accounted for, transferred, or repurposed rather than discarded by default
The measure of a successful transition is not that you switched on the announced date. It is that old inventory cleared cleanly, operational metrics held steady, and no store ran out of packaging along the way.
If you are scoping the supply side of a packaging conversion — matching a new size to its lids, sizing a pilot order separately from the network order, or confirming documentation for a new specification — the container, bowl, lid, cup, and bag categories and the RFQ process are at takeawaypack.com. Bringing your depletion map and wave schedule to that first conversation is what lets order quantities be phased to the plan rather than to a single calendar date.
References
- FIFO, FEFO methods: what they are, benefits, and how to implement them — Savino Del Bene — stock rotation logic, arrival-date tracking, and physical placement of newer behind older stock.
- Six Questions to Help Set Up an Effective Pilot and System Rollout — Unisys — pilot sizing, defining objectives before launch, and limiting the number of pilot phases.

