A Milk Tea POS That Understands the Order Is the Modifiers
In a drink shop, the product name is the least important part of the order. Sugar, ice, size and sinkers are what the customer actually asked for. WSI POS treats them as first-class data — priced where they change the price, printed where the barista needs them, and attached to the sale for your reporting.
What breaks in a drink shop
Every order is a customisation
A milk tea order is not a product — it is a product plus six decisions. Sugar at 50%, less ice, oat milk instead of fresh, extra pearls, no pearls. If those decisions live in a free-text note, your barista is decoding handwriting during the busiest hour of the day.
The cup needs its own label
A receipt goes to the customer; the cup needs a sticker the barista can read while making three drinks at once. The useful label is short and structured — drink, size, sugar, ice, sinkers — not a paragraph.
Cup size changes the price
Medium and large are different products with different prices, and the sugar and ice levels do not change the price at all. A POS has to distinguish between modifiers that cost money and modifiers that are simply instructions.
Mall and street wifi is unreliable
Kiosks sit in malls with contended wifi, and provincial shops run on connections that drop during storms. A queue does not pause politely while the router reconnects.
How the modifier groups are configured
Each group is set up during implementation. The important distinction is between options that change the price and options that are only instructions for the barista — a POS that cannot tell them apart will either overcharge or undercharge you all day.
| Group | Typical options | Affects price? |
|---|---|---|
| Size | Medium / Large | Yes — different price per size |
| Sugar | 100% / 75% / 50% / 25% / 0% | No — instruction only |
| Ice | Regular / Less ice / No ice | No — instruction only |
| Temperature | Iced / Hot | Usually no |
| Milk base | Fresh / Oat / Almond / None | Usually yes |
| Sinkers | Any combination | Yes — per sinker |
| Extras | Extra shot, cheese foam, extra pearls | Yes — per extra |
Common sinkers and toppings we configure
Add-ons are priced individually, so “pearls + pudding + cheese foam” totals correctly without the cashier doing arithmetic.
The cup label is a workflow, not a receipt
During a rush a barista is not reading sentences. WSI POS prints condensed modifier codes on the label and keeps the long-form description on the customer receipt, where someone might actually read it.
- Drink and size on the first line
- Sugar and ice as short codes, not prose
- Sinkers listed so they can be ticked off as added
- Special instructions preserved verbatim
- Order number large enough to shout across the counter
#A-1043 TABLE 7 -------------------- 1x LARGE CLASSIC MILK TEA SUGAR 50% LESS ICE + PEARLS + CHEESE FOAM -------------------- NOTE: STRAW NOT NEEDED
Illustrative layout with demonstration data. Your label format is configured against your printer during implementation.
Two things you should know before comparing
Ingredient-level stock is not in the product yet
Product-level stock is tracked with low-stock thresholds and a movement ledger. What WSI POS does NOT do today is deplete your pearl or milk inventory automatically from recipes. That is on the roadmap. If cup-by-cup ingredient costing is the reason you are shopping, tell us during scoping — we would rather you hear this now than discover it after signing.
No per-transaction fee
WSI POS is licensed per deployment and we do not take a percentage of your sales. Some POS offers in this market are cheap up front and expensive per transaction; check that before comparing headline numbers.
Related reading: cloud POS versus local-first · POS for resto-bars · the full FAQ
Bring a real drink from your menu
We will build it live — size, sugar, ice, sinkers and all — and print the label, so you can judge the workflow rather than the pitch.