A bubble tea shop with twelve drinks, three sizes, five sugar levels, four ice levels and eight toppings does not have twelve items. Built the wrong way it has several hundred, each needing its own price update, and a best-seller report that is completely meaningless because every real drink is spread across forty rows.
The structure that works
Size is a variant with its own price. Large, medium, small are the same drink at three prices. Point of sale, QR page and receipt all read the one record.
Sugar and ice are single-choice scales. Pick one real scale — 0%, 25%, 50%, 75%, 100% — and stop there. Do not create separate items for “less sweet” and “three-tenths sugar” and “kurang manis”. They are the same setting described in different languages by different guests.
This is where the multilingual side earns its keep: one scale, several display names. The Chinese-reading owner sees 三分糖, the Malay-speaking guest sees kurang manis, the English menu says 30%, and the staff member hears any of the three and presses the same key. Same record, different labels — the same mechanism described in who translates the menu.
Toppings are add-ons that stack and carry a price. Pearls, grass jelly, oat milk, an extra espresso shot. Some stack (two shots), some must be single-choice (milk type — you cannot have oat and soy at once). Configure which is which; that distinction is what stops impossible orders reaching the bar.
Preparation notes ride along as text. No spring onion, mild, sauce on the side. These reach the kitchen with the dish rather than being shouted across the pass.
Why it matters commercially, not just tidily
Three things follow from doing it this way.
A price change is one edit. Put up the price of the large size and it changes at the counter, on the QR page and on the printed receipt at once, because there is one record. See changing a price in three places.
Your reports become true. “Brown sugar milk tea” appears as one line with a real total, not as forty fragments. You can actually see what to keep on the menu.
And guests spend more. When the options are laid out in front of someone ordering on their own phone, they add the topping. That is not a claim about our software — it is what happens when the upsell is a checkbox instead of a question a busy server has to remember to ask.
The one thing to get right at setup
Decide which option groups are mandatory. A drink where sugar level is optional will be ordered without one, and the bar will guess. Make the choice required at ordering and the ticket that reaches the bar is complete.
