Wilson Wu
Chief Revenue Officer, Snappy
A bubble tea catering order is one large pre-order, often a hundred cups or more, for an office, a school or an event. Unlike a walk-in order, it is priced, paid and configured cup by cup for sugar, ice and toppings before a single drink gets made.
When a shop publishes no minimum, no lead time and no order form, these orders arrive by direct message, voicemail and walk-in instead. The fix is a published intake, with payment collected before the cups get made.
The demand is already reaching you. It is just reaching you in a format that pulls a staff member off the bar and still produces a handwritten list nobody can read on the morning of pickup. Below is the online catering order form a bubble tea shop should actually publish, the fields it has to capture, and how the order gets from the form to the counter without being retyped.
Summary
On this page
Five buyers account for almost all of it: an office administrator ordering for a team meeting, a school or campus club, an event or wedding planner, a sports team or dance studio, and a real estate or retail brand running an open house. None of them are ordering for themselves, which changes everything about how they buy.
They need a number they can put in an expense report and a time they can promise their own people. That is why an ambiguous catering page sends them straight to your phone, and why they will call three shops in an afternoon and buy from the first one that answers with a firm quote.
Geography is on your side here. Those 143,000 Peel businesses are the buyer pool. Staff meetings, onboarding days and summer parties run all year.
When the buyer has several tea shops to choose from inside a short drive, they are not choosing on flavour. They are choosing on whoever made the order easy to place.
Because the order arrives through a channel with no memory. A direct message at 9 PM, a voicemail during Saturday rush, a walk-in who asks the sixteen year old on the register whether you can do eighty cups on Thursday. Snappy’s AI Phone page describes the other shape of this: calls are answered instantly and routed to staff on request, so the catering lead never lands in a voicemail box.
The second failure is ambiguity in your own published rules. The catering page of one Dallas boba and donut operator asks only that orders “be placed as early as possible, especially for large events, weekends, holidays, and full-service catering requests” (Fat Straws), and offers a bulk donut order at 10+ dozen while naming no cup count for drinks. That is that one shop’s policy, not an industry standard. The page takes catering orders online, but it never states a lead time in hours, so a buyer with a fixed date still has to ask.
The third failure is the drink itself. Bubble tea is configured per cup, with a sugar level, an ice level and one or two toppings on every single one. A fifty-cup order dictated over a phone during service is fifty configurations captured by a person who is also making drinks, and the detail that goes missing is discovered at pickup.
What good looks like is not a mystery: order ahead, pay ahead, no phone call. That is the shape a catering flow needs, at fifty times the volume.
The form itself should capture contact details, pickup or delivery specifics, the per-cup drink build with sugar and ice levels, allergen notes, packaging and payment, since all of that has to be settled before a big order gets made. Start with the three numbers you publish above the form, because they do most of the filtering for you.
Minimum. State it in cups, not dollars. Twenty cups is a common floor for a shop with one bar; thirty or forty if you also run a lunch rush at the same hour.
Lead time. State it in hours or days, and state it as a rule rather than a preference. “Catering orders require 48 hours notice, 72 hours for orders above 100 cups” is a rule. “As early as possible” is a conversation.
Cutoff. The latest hour on the day of pickup that you will still accept a change. Without it, someone calls at 10 AM to change forty toppings on an 11 AM pickup.
Then the form itself. These are the fields that stop the follow-up call:
One more decision saves you more time than any of the fields: publish a shortened catering menu. Six to eight drinks that batch well, rather than your full forty-item board. A caterer choosing from eight options places the order without calling you. A caterer choosing from forty asks you which ones travel well, which is a phone call again.
How many catering orders slipped through DM last month?
Walk through your recent catering orders with us: where each one landed, what got retyped by hand, and what was paid before the cups were made.
Show me my catering gapsEvery channel can take a bubble tea catering order. They differ on how much of it survives the trip to the counter, and on how much of your service hour it eats.
| Intake channel | Lead time captured | Per-cup modifiers captured | Payment up front | Reaches the kitchen as a ticket | Staff time during service |
|---|---|---|---|---|---|
| Phone call during service | Only if someone writes it down | Rarely at 40 cups or more | No | No, a handwritten note | High, one person off the bar |
| Social direct message | Sometimes, scattered over many messages | Partly, in prose | No | No, a screenshot at best | Medium, and usually after close |
| Usually, after you reply with questions | Yes, after two or three rounds | No, unless you invoice separately | No, retyped at the counter | Medium, plus a day of back and forth | |
| Structured online pre-order on your own ordering page | Yes, as a required field | Yes, per cup | Yes, at checkout | Yes, in the same order flow as every other online order | Near zero |
| Snappy AI Phone General Inquiries | It answers the caller from your own FAQ and routes to staff on request | No, it is not taking the order | No | No, it hands a live lead to a person | Near zero, and it never goes to voicemail |
| Snappy AI Phone Ordering (requires Snappy Online Ordering) | Yes, on the call | Yes, the complete order as spoken | Yes, via a payment link before the ticket prints | Yes, it prints straight to the kitchen | Near zero |
Read the table by column, not by row. The two columns that decide whether catering is profitable for you are “payment up front” and “reaches the kitchen as a ticket,” and only two rows clear both: the structured online pre-order and Snappy AI Phone Ordering.
The two Snappy AI Phone rows are different products with different jobs. General Inquiries has no prerequisite and answers every call from your own FAQ, which is the cheapest way to stop losing a catering lead to a voicemail box during Saturday rush. Ordering requires Snappy Online Ordering, takes the complete order on the call, collects payment up front through a link, and prints the ticket straight to the kitchen. Both run on the same AI Phone product, and the overview is on the Snappy AI Phone page.
Price up from cost, then decide what the volume is worth to you and how much of it you collect up front, before the cups get made. Ingredients are the floor, and that floor moves with the build and with your wholesale tier: the tea base, the milk or powder, the syrup, the tapioca and the cup on your own invoices are the only per-cup ingredient numbers worth pricing against.
Cost out two of your own drinks before you quote anything: your cheapest simple build and your most expensive one. That gives you the band a fifty-cup order sits inside. A taro drink with two toppings sits near the top of the band, a plain green tea near the bottom, so a fifty-cup order of premium builds costs you materially more to produce than the same count of simple ones. Price the catering menu against your own band, in Canadian dollars, off your own invoices.
Then add the three costs a per-cup price hides. Packaging for transport, which is carriers, sealed lids and often labels. The labour hour, because fifty sealed cups is a person at the bar who is not serving the counter line. And the opportunity cost of the walk-in line you slow down if the pickup lands at 12:15 on a weekday.
On payment, take it all up front, or take a deposit large enough that a cancellation does not eat your margin. Unpaid large orders carry the same exposure as unpaid phone orders: the product is made, the customer does not arrive, and the loss is fifty finished drinks rather than one. A checkout on your own ordering page settles this at the moment of order, and Snappy’s AI Phone Ordering collects payment through a link before the ticket prints.
The channel matters to the margin too. Snappy Online Ordering carries “0% commission fee on every online order” (Snappy), which means a large pre-order placed on your own page keeps its full value. Our guide to commission-free online ordering systems for restaurants walks through how that compares to selling the same volume through a marketplace.
The catering order should arrive the same way every other order arrives, on the screen your bar already reads. Snappy’s Kitchen Display System is screens that route orders straight to kitchen stations, and a fifty-cup pre-order routed that way is a ticket, not a note taped to the fridge.
Batching is the part most shops get wrong. Do not make a fifty-cup order in the sequence it was entered. Group it by base tea, then by topping, so one person seals thirty milk teas in a run instead of switching syrups fifty times. A per-cup list on a screen lets you sort; a handwritten list does not.
Sequence the prep against the pickup window, not against the order time. Sealed cups with ice are good for a short hold, so a 12:00 pickup starts at 11:30, not at 9 AM when the shop is quiet and it feels convenient. Assign one person to the order and take them off the counter for that window rather than interleaving it with walk-ins.
Finally, look at the order the day before. A dashboard that shows tomorrow’s orders alongside today’s lets you order more taro powder on Tuesday instead of discovering the gap on Wednesday morning. For the counter-side mechanics of speeding up ordinary orders, see our guide to choosing a POS for a bubble tea shop and the kitchen display product page.
A catering order is a lead with a budget attached, and most shops throw the lead away at pickup. The buyer’s name, workplace and exact drink split are the three things that make the second order trivial to win, and none of them survive a handwritten note.
Keep them in a customer record. Snappy’s Marketing product is a CRM with customer profiles and segmented campaigns (Snappy), which is enough to build the only two segments that matter here: everyone who has placed an order above thirty cups, and everyone who placed one more than sixty days ago.
Then work the calendar, because office catering is seasonal and predictable. Reach out before back to school in late August, before the December party window, and two weeks before any long weekend. One message to a list of past catering buyers, timed to the week they are already planning, outperforms a month of generic posts.
Two small moves at handoff do the rest. Ask for the next date while they are picking up the cups, when the event is fresh and the answer is often a real one. And save their build as a named order so the follow-up can be one line: same fifty as last time, Thursday at noon, confirm and pay here.
Publish both as numbers. A common shape is a twenty to forty cup minimum with 48 hours notice and a longer window above 100 cups. Vague wording is what creates the phone tag: one operator’s catering page asks only for orders “as early as possible, especially for large events, weekends, holidays…” (Fat Straws), and never states a lead time in hours, so a buyer with a fixed date still has to ask.
Only if the page captures quantity, per-cup modifiers and a pickup time, so check those three things before you promise a caterer they can order online. Snappy Online Ordering is a commission-free branded ordering page with Google integration, and it carries “0% commission fee on every online order” (Snappy).
Collect payment when the order is placed, not at pickup. An online checkout does this at the moment of order, and Snappy’s AI Phone Ordering, which requires Snappy Online Ordering, collects payment up front through a link before the ticket prints to the kitchen.
That is the call worth catching, because a catering buyer who reaches voicemail calls the next shop. Snappy’s AI Phone General Inquiries answers every call from your own FAQ with no other product required, and routes the caller to a person on request, so the lead is captured rather than lost.
Quote a total in dollars, but build it from a per-cup price that reflects the actual drink, because a taro build with two toppings costs you materially more than a plain green tea, and a flat catering rate quietly subsidises the expensive half of your menu.
Bubble tea catering is demand your shop is already receiving and mostly mishandling. The orders come from offices, schools and event planners who need a firm number and a firm time, and they arrive through direct messages and voicemail when the shop has not published a minimum, a lead time or a form they can fill in.
Fix the intake in that order. Publish the three numbers. Put a real form or a structured pre-order on your own ordering page, with per-cup detail and payment at checkout. Make sure the result lands on the kitchen screen as a ticket instead of a note, and keep the buyer’s record so the next order takes one message instead of one afternoon.
The channel you catch it on decides what you keep. A commission-free order on your own page keeps its full value, and a phone line that answers during rush keeps the lead that voicemail would have lost.
Ready to put a catering pre-order flow on your ordering page and stop taking fifty-cup orders by voice? Talk to our team.
Book a walkthrough
Put your catering intake on your ordering page
Book a walkthrough and we will go through your minimum, your lead time, your per-cup detail and payment at checkout, together.
No-obligation walkthrough
Catering orders getting lost in DMs?
See what a published minimum, lead time and online form would catch on your next big catering order.
On this page
Get The Latest Restaurant Data, Trends & Tips
