Multi-Store Winter Menu Rollout: A Step-by-Step Guide

If you operate two or more bubble tea locations in Australia, the autumn-to-winter menu switch is the operational moment most likely to expose process gaps you didn't know you had. One store puts the new hot drinks on the board on a Monday. Another puts them up the following Friday because the manager was off sick. A third never updates the printed menus and keeps selling iced through June. Two months later, three stores have three different versions of "winter" running, and the central inventory orders don't match what any of them are actually pouring.

This guide walks through how to stage that rollout properly — from the central decision through to all stores serving the same drinks the same week — for an AU operator with 2 to 10 locations. It's an operations guide, not a menu-design guide. We're assuming you've already chosen which drinks are going on. The hard part is everything that happens between that decision and a clean cutover.

Step 1 — Lock the menu centrally before anything else moves

The first mistake we see multi-store operators make is letting the rollout start before the menu is finalised. A store manager hears that "we're switching to winter next month" and starts ordering hot-drink ingredients on their next regular order. By the time central operations has actually decided which six hot drinks are going on, two stores have already received stock for drinks that didn't make the final cut.

Lock the menu in writing before anyone outside the central team starts ordering. The bare minimum spec for each drink:

• Drink name as it'll appear on the board (consistent across all stores)
• Recipe with measured ratios — powder/syrup grams, water, milk, ice, toppings, default sweetness
• Approved ingredient SKU list (specific products, specific sizes)
• Default cup size and pricing tier
• Whether it's iced, hot, or both

Keep this in one document. One source of truth. If a store manager has questions a week later, they read this, they don't text the founder.

Step 2 — Run a single consolidated supply order

Once the menu is locked, do the next supply order centrally and consolidated, not store-by-store. Wholesale freight on bubble tea ingredients is heavy enough that batching saves real money even at small fleet sizes. More importantly, it gives every store the same baseline stock at the same time.

Order new winter-menu ingredients alongside your normal restock. Examples for a typical AU multi-store rollout, all from real product categories:

• Hot-drink-friendly powders: Hong Kong Style Milk Tea Powder, 3 in 1 Milk Tea Drink Powder
• Sweeteners that pull double-duty hot/cold: Brown Sugar Syrup
• Anything you're using as a winter signature: Mesona Grass Jelly Powder for warm grass jelly drinks, Original Coffee Powder for hot coffee milk tea, Cheese Foam Powder if cheese-foam-on-hot is going on the board

Before placing the order, decide: are all stores getting the same allocation, or are you weighting by store volume? For most operators with 2–4 stores, equal allocation is fine and simpler. Once you're past 5 locations, weight by historical milk-tea sales or it'll come back to bite you within a fortnight.

Step 3 — Pre-stage at one store before going wide

Don't roll out to all stores simultaneously. Pick the store with your strongest manager and run the new menu there for 5–7 days first. This is your live test environment. What you're checking:

• Recipes work as written when staff who didn't help design them follow the spec
• Stock consumption rates match what you predicted — if usage is wildly off in either direction, treat that as a planning issue, not a recipe issue
• Customer questions surface real menu copy gaps ("Is the hot brown sugar one sweet?")
• POS configuration covers all the new SKUs, modifiers, and price overrides

This week is uncomfortable. The trial store has a different menu from the rest of your fleet for a week. Customers might notice. That's the cost. The alternative — discovering at 11 am Saturday that 4 stores all have the same ingredient mismatch — is far worse.

If anything broke at the trial store, fix it in the central spec, then move to Step 4. If too much broke (say, three or more recipes need adjustment), extend the trial by another week. You will lose less money on a delayed multi-store launch than on a chaotic one.

Step 4 — Train every store in the same week, the same way

Once the trial is clean, schedule training for every other store within a 7-day window. The week the menu goes wide should be the same week training happens, not a fortnight earlier.

For each store:

• One in-store training session of 60–90 minutes covering the new drinks
• Same training script across all stores — written, not improvised
• The store's actual baristas, not just the manager
• Practice rounds: each barista makes each new drink at least once, with the manager spot-checking
• Sample taste session at the end so staff know what "right" tastes like

Send a short video walkthrough as a backup so a barista who joins next week can self-train without booking another session. This is also where centralised recipe documentation pays for itself — the same document used in Step 1 is now the training script.

Don't outsource this to "watch the YouTube video the supplier sent". For multi-store consistency, in-store practice with feedback is what makes drink #200 taste like drink #1.

Step 5 — Coordinate the board change to a single date

Pick one calendar day. Every store's menu board changes on that day. Every store's POS gets the new SKUs activated on that day. Every store's staff knows that day is launch day.

Tools that make this easier across stores:

• Pre-cut printed inserts for menu boards delivered to all stores 2–3 days before launch
• POS templates updated by central ops, pushed once, rather than each store editing individually
• A single staff WhatsApp / Slack channel for launch-day questions so the same answer goes to everyone

If your board uses chalkboard or magnetic letter-by-letter setups, send a photo of the finished board layout to all managers a week ahead. Photo plus written copy beats written copy alone for getting consistent boards across non-co-located teams.

Step 6 — Retire the outgoing iced items deliberately, not by accident

The other half of a menu switch is what comes off, not what goes on. Multi-store operators routinely forget this and end up with stores still selling summer specials in mid-June because no one explicitly took them down.

Make a written list of items being retired. Send it to all stores in the same launch package as the new menu. Specify:

• Last day each retired drink can be sold (give 1–2 weeks' wind-down for stock)
• What to do with leftover inventory (use up, transfer to another store, write off)
• Which stores have which leftover stock and a plan for each

For example: if you're retiring a heavy tropical fruit tea using Mango Flavoring Syrup, and store #2 has half a 2.5 kg bottle while store #4 has a full one, the plan should be "store #2 finishes theirs first, store #4 transfers to #2 once #2 runs out, then store #4's gets used as a 'manager's special' through May".

This sounds like overkill at 2 stores. At 5 stores, it's the difference between a clean menu and ingredient sprawl that quietly bleeds margin.

Step 7 — Run a same-day audit on launch day

Send central ops (or whoever your most operational person is) to physically visit each store on launch day or the day after. Don't trust photo-only check-ins. What to verify in person:

• Board matches the central spec, no rogue drink names
• All POS SKUs ringing through correctly (do a test transaction at each)
• Recipe cards (laminated, behind the counter) are up and match
• Old menu items are actually retired — physically removed, not just "marked as inactive"
• Staff can name and describe each new drink without consulting the menu

If any store fails the audit, fix on the spot and follow up by phone the next morning. The cost of catching one inconsistent rollout on Day 1 is one drive across the city. The cost of catching it three weeks later is a customer who ordered a hot brown sugar at one store and a different drink under the same name at another.

Step 8 — Set the review date now, not later

Two weeks after launch, run a structured review across all stores. This is genuinely the step most operators skip. Without it, the next menu switch is exactly as bumpy as this one.

Review should cover:

• Which drinks are actually selling vs your forecast
• Stock consumption by store — anyone running through a powder twice as fast as expected?
• Recipe adherence — pick three drinks at random and have a manager describe how their staff prepares them
• Customer feedback gathered by counter staff (informal is fine, just ask managers what they've heard)

Decide based on this whether to push more drinks to the board for May/June, swap any underperformers, or pull anything that's not earning its space.

A short note on the "easy" version

Two-store operators sometimes ask whether all of this is necessary at their scale. Honestly — most of it, yes. The difference is you can compress the timeline (Step 3 trial is 3 days, Step 7 audit is two phone calls and one drop-in). What doesn't compress is having the spec written down centrally, training both teams the same way, and changing both boards on the same date. Those three things are what separate a 2-store operation that scales cleanly to 5 from one that hits 4 and stalls because the operator is running between stores putting out fires.

If you're putting your winter menu together this week and need wholesale support across multiple sites, browsing the full powder range is a reasonable starting point — most of what your stores need for hot-drink rollouts can be ordered together and split-delivered to multiple addresses.

The cleanest multi-store rollouts aren't done by the most ambitious operators. They're done by the ones who treat the menu switch as a process, not an event.