The first shop runs smoothly, so the owner opens a second bubble tea location. It sounds light — same menu, same recipes — but the first two weeks are always messy: the new shop keys in every item again, the boba is cooked a little thicker, the selling price is off by five thousand and nobody remembers why, and at month end the owner adds up two revenue sheets by hand. All of that is avoidable if you set up the new shop's data in the right order.
Each location has its own data set — know this up front
In Ordersys, items are declared per branch. That sounds like extra work, but it is why the shop near the university can carry a few drinks students like while the shop in the office district does not have to. Stock, staff and label printers are also kept separate by location, because they genuinely differ.
What should be identical, do not retype. The items screen can import products from a file: download the template, fill it in or export from the shop already running, then import it into the new one. Item names, groups, codes and prices go in one pass — nobody clicks thirty times, and you avoid one shop writing "Boba milk tea" while the other writes "BMT brown sugar", which later shows up as two different lines in a combined report.

Four option groups and the recipe: identical, not up to the person
A cup of bubble tea is one item plus four customer decisions: size, sugar level, ice level, toppings. Set those four groups up as buttons and a new hire can take orders the day they start instead of typing notes by hand — and topping prices are added to the cup automatically, so one shop cannot charge for them while the other forgets.
Keeping the taste identical comes down to the recipe. Declare it per cup: how much tea, how much milk, how much sugar, how much boba. Each cup sold deducts exactly that amount from that location's stock. The benefit is twofold: the taste does not drift with whoever is making it, and at month end comparing the quantity that should have been used against what was actually received shows immediately which location is running higher waste than normal.
Prices can differ between locations — declare them in a price list
Two shops, two leases; if rent differs, selling prices do not have to match. Instead of editing the price on each item, use a price list: declare one list and set which branch it applies to, over which date range, which days of the week, which time slots. Off-peak discounts at one shop while the other stays as is — declared once, with nobody having to remember to change it back.
- Keep the base price on the item and the location difference in the price list — later you can still trace how much was discounted.
- Declare promotions per location; do not declare them chain-wide and then tell staff "at our shop, don't press that".
- Every price change goes in the price list, not the base price, otherwise earlier reports stop matching.
See the whole chain, drill down to one shop
This is what a chain owner needs most. The product report has a branch column and a branch filter: view it combined to see which drinks carry the whole system, filter one shop to see what that shop sells. The overview page has a revenue ranking by branch; pick a date range and it is there.
| What the chain owner asks | Where to look |
|---|---|
| Which shop sold more? | Revenue ranking by branch, over the same date range |
| Did the new drink land at any shop? | Product report, filter each shop and compare cups sold |
| Which shop has unusual ingredient waste? | Each location's stock, against the amount deducted by recipe |
| Which shift at which shop is busy? | Sales report by time slot, filtered by branch |
One note when comparing: the shop with higher revenue is not necessarily the better shop. With different premises, opening hours and headcount, an absolute figure says nothing. Revenue per opening hour, or cups per staff member per shift, is what shows which location is genuinely running well.
Three things to do before the new shop opens
First, finish the menu and option groups at least three days ahead, then ring up a few orders to check that the cup labels print the right size and sugar level. Second, declare recipes from day one — declare them later and you spend the first month not knowing where ingredients went. Third, one account per staff member; do not let the whole shop share one, or you will not be able to separate who sold what.
Per-branch menus, option groups, drink recipes, per-location price lists and reports split by branch are part of Ordersys coffee and bubble tea shop management software, with a free 7-day trial. Read more: size, sugar, ice and topping options for a bubble tea shop and managing a chain of stores: which numbers to watch.
Checkout in a few taps, print cup labels with toppings, send drinks to the bar screen and issue e-invoices from the POS.
Other news
Sales software for household businesses that fits the new rules
From 2026 household businesses no longer pay presumptive tax and declare based on actual revenue; stores with revenue of 1 billion VND/year or more selling directly to consumers must use e-invoices generated from cash registers. This guide summarises the regulatory milestones that affect retail stores and what sales software must do: record every order, issue e-invoices, report by period, keep purchase records and track debts.
Scan a QR code to order at the table: guests order for themselves, the restaurant needs fewer staff
When guests scan a QR code to order at the table, handing out menus, taking orders, running tickets to the kitchen and answering "where is our food?" move to the guest. This guide separates what guests do themselves, what staff still have to do, how to rearrange shifts by table zone, and where things slip when the restaurant runs with fewer people.
Ordering software for wedding banquet restaurants: serving many tables at once without the bill going wrong
A thirty-table wedding banquet usually goes wrong on the extras: drinks added mid-party, tables set up at the last minute, dishes sent to the kitchen twice, deposits remembered by word of mouth. This guide puts the whole banquet into one order from a multi-table booking or by merging tables, takes extra orders by phone, sends only new items to the kitchen, and settles with the host using a provisional bill, surcharges and automatic deposit deduction.
Complete coffee shop management software: how ordering, checkout, inventory and reports connect
Complete coffee shop management software is not a long feature list but ordering, checkout, inventory and reports working together: ring up one cup and the money goes into the right shift, ingredients are deducted by recipe and the end-of-day report updates itself. The article follows one cup through four stages, shows four common break points and the order to switch things on.
Billiards management software for a small new club: what to set up before opening day
For a new billiards club with five to ten tables, where the owner works the counter and starts the clocks, the software needs to do a few things right: set up tables, hourly rates, the menu and QR codes before opening; let players order drinks themselves and have table lights follow playing time; use camera highlights to get the club known; and after the first month read reports by table, debts and shift close.
Retail order management software: counter sales and online orders in one place
Counter orders, phone and Zalo orders, and orders from the store's web shop all go into one order book in Ordersys. Each online order moves through five clear statuses, delivery requires the address, delivery time and delivery person, customers track their own order, and there is no adding up two places at the end of the day.
Spa and hair removal appointment software with no double bookings
Hair removal sessions are short, tightly packed and crowded into one machine room, so they clash easily. Each Ordersys appointment records the time, duration, room/bed and therapist; on save the software checks for room clashes, therapist clashes and therapists busy in the spa, adds bed turnover time, and shows exactly which booking is holding the slot.
QR table ordering software for restaurants and eateries
One round of QR ordering in Ordersys goes through five steps: the guest scans the code on the table, picks dishes with options and notes, sends the order (with or without a confirmation step), the kitchen and bar receive it, and the guest reopens the page to check the order and order more. Plus a list of what to set up before putting codes on tables.
Ordersys or KiotViet? A Straight Comparison to Choose Right
An honest Ordersys vs KiotViet comparison by real needs: retail, services, billiards, QR ordering, automatic payment — choose right, not the wrong fit.