Key takeaways
- A multi-brand operation needs its brands separate at the front (menus, names, storefronts, receipts) and combined at the back (one kitchen queue, one stock count).
- The kitchen screen matters most: every ticket should show which brand it belongs to, so packaging and garnish go to the right bag.
- Shared ingredients make recipe-level stock deduction more useful, because one chicken thigh can end up in three brands’ dishes.
- Reports must split sales by brand and by channel, or you cannot tell which brand earns its place.
- Each brand name is a separate trade mark question. Registering a company or business name with ACRA is not trade mark protection.
A multi-brand restaurant runs two or more food concepts from the same premises and staff. Some are physical: a café by day and a bar under a different name at night. Many are virtual: a burger brand, a rice bowl brand and a dessert brand that exist only as listings on delivery apps and your own ordering page, all cooked on one line. This guide explains what a multi brand restaurant POS has to handle, the questions to put to vendors and where the traps are. It builds on our cloud kitchen POS comparison and our guide on how to start a cloud kitchen, so it does not repeat the setup and licensing steps covered there.
What multi-brand and virtual brands actually are
The terms get used loosely, so it helps to separate three set-ups:
- Virtual brands from an existing restaurant. A dine-in restaurant adds one or two delivery-only brands to use idle kitchen capacity in the afternoon or late evening. The main brand keeps its dining room; the virtual brands exist only online.
- A dedicated multi-brand cloud kitchen. No dining room at all. Several brands share one kitchen, one team and one set of equipment, and every order is delivery or pick-up.
- A multi-concept group. Different brands in different outlets, sometimes sharing a central kitchen. This is closer to a multi-outlet business, which our multi-outlet POS guide covers in detail.
The logic is the same in each case. You spread fixed costs (rent, equipment, staff) across more sales, and you reach customers who would never search for your main brand. A customer looking for “chicken rice” and one looking for “Korean fried chicken” can both end up with an order from the same kitchen.
The risk is also the same. Each extra brand adds a menu to maintain, a listing to manage, packaging to stock and reports to read. Without the right system, the savings in rent are eaten by mistakes: wrong stickers on bags, an item sold out on one brand but still live on another, and no clear view of which brand is losing money.
Separate menus and branding for each channel
Customers should never see that two brands share a kitchen unless you want them to. That means each brand needs its own:
- Menu, with its own item names, descriptions, photos and prices. The same fried chicken might be “Signature Crispy Thigh” on one brand and part of a “Chicken Bowl” on another.
- Modifiers, such as spice levels, add-ons and set upgrades, which may differ by brand even for a shared base item.
- Channel prices. Many operators price delivery app menus higher than their own ordering page to cover commission. With several brands, you are now managing brands multiplied by channels, so the POS should let you set prices per brand and per channel from one place. Our menu design guide and menu engineering guide help you decide what each brand’s menu should contain.
- Receipts, labels and order stickers showing the right brand name and logo, so the customer receives a bag that matches the listing they ordered from.
- Opening hours, because a dessert brand may only run from 2pm to midnight while the lunch brand closes at 3pm.
Ask each vendor to show how a new brand is created, how an item is shared between brands and what happens to every brand’s menu when you change the price or recipe of a shared item.
One kitchen queue with brand tags
The kitchen is where multi-brand either works or falls apart. Cooks should not have to check three tablets or three sets of printed chits. They need one queue, in the order orders need to go out, with the brand clearly marked on every ticket.
What to look for on the kitchen side:
- Brand shown on each ticket, prominently, so the packer uses the right bag, sticker and sauce pot.
- Station routing, so the fryer sees fried items from every brand, the wok station sees stir-fries from every brand, and nobody has to read items that are not theirs.
- Prioritisation and timers, because a delivery rider waiting at the door is a different kind of urgency from a pick-up order due in 20 minutes.
- A consolidated order view at the pass, where one person checks that every item for an order is ready before it is bagged.
ChaChaCha’s kitchen display system offers station routing, order prioritisation and prep timers, and our POS supports English and 中文 kitchen tickets. Epson cloud printing lets you send tickets to multiple printers. How brand names appear on tickets and screens for a multi-brand set-up is something to ask us to confirm and demonstrate with your own brands. Our restaurant delivery operations guide covers the physical side: packing stations, rider handover and labelling.
Shared inventory across brands
Shared ingredients are the point of running several brands in one kitchen. They are also where stock control gets harder. If rice, chicken thigh and chilli paste go into dishes on three brands, a manual count only tells you the total gone, not which brand used it.
Two features help:
- Recipe-level stock deduction. Every sale deducts its ingredients by recipe, regardless of which brand sold it. ChaChaCha does this, along with recipe costing per menu item, through our inventory management tools.
- Recipe costing per item. The same base ingredient can carry different portion sizes on different brands. Costing each item lets you see whether the dessert brand’s margin justifies its packaging.
The other shared-stock problem is availability. When you run out of chicken thigh, every item that uses it should go off sale on every brand and every channel at once. Otherwise one brand keeps taking orders you cannot fulfil, and the delivery app rating suffers. Ask each vendor how sold-out status spreads across brands and channels, and how fast. Other inventory details, such as purchase orders, transfers between a central kitchen and outlets, unit conversion and wastage tracking, are specifics to ask us to confirm for your set-up.
Reporting by brand and by channel
The question every multi-brand operator eventually asks is: which brand is earning its keep? You can only answer it if sales, discounts and costs are tagged by brand from the start.
At minimum, you want reports that show:
- Sales and order count per brand, per day and per hour.
- Sales per brand by channel: delivery app, your own online ordering page, QR or walk-in pick-up.
- Average order value per brand, and best and worst sellers within each brand.
- Food cost per brand, using recipe costing.
- Discounts and promotions per brand, since a promotion on one brand can pull orders from another that shares the same customers.
Commission is the other half. Gross sales on a delivery app are not what you keep. Grab’s Singapore merchant page states a 30% service fee on GrabFood and GrabMart orders, subject to GST. A brand that sells well on delivery but poorly on your own page may be less profitable than its sales suggest. Compare margins after commission, not gross takings.
ChaChaCha provides reports, and for groups with a head office, an ERP for central management. How reports are split by brand in your configuration is a point to ask us to confirm and show on screen during your demo.
Separate delivery storefronts and your own ordering page
Each virtual brand usually needs its own presence wherever customers order: its own delivery app listing and, ideally, its own ordering page that you control.
Delivery apps. ChaChaCha integrates with GrabFood. Grab’s merchant page says no shopfront is needed if your documents are in order, which matters for delivery-only brands, and lists a one-time activation fee of S$100 per outlet on your own Android device or S$300 per outlet with a Grab Order Device. Grab’s rules on how several brands from one address are listed, and whether each brand counts as a separate outlet, are not something we have seen stated on that page, so confirm them with Grab before you plan your brand line-up. Our delivery platform comparison covers each platform’s published terms.
Your own channel. Commission-free ordering matters more when margins are split across brands. ChaChaCha provides an online ordering page, QR ordering for pre-order and collect, and a mobile app. For delivering your own online orders, we work with Lalamove, so you can book a courier without a marketplace commission on the food. See our delivery integration page for how this fits together.
Bringing customers back. Loyalty tools such as points, stamps, vouchers, birthday rewards and WhatsApp marketing, covered on our CRM and loyalty page, give delivery customers a reason to order direct next time. Whether you run one programme across brands or one per brand is a branding decision; ask us to confirm how that would be configured.
Trade marks: one per brand
Every brand you put in front of customers is a name someone else could register first. IPOS states that registering a business name with ACRA, or a domain name with SGNIC, does not equate to trade mark protection. For a virtual brand that exists only as a logo on a delivery app, the name is almost the whole asset.
Points to plan for:
- Search each proposed brand name before you design packaging, not after.
- Restaurant and food-service services fall under Class 43, with goods classes for packaged products.
- IPOS fees are per class and per application. On IPOS’s Forms and Fees page, an application using pre-approved descriptions is S$280 per class. Three brands means three applications to budget for.
- Drop brands you are not going to use rather than carrying them for years; IPOS warns that unused marks can be revoked for non-use.
Our restaurant trade mark guide walks through classes, fees, timelines and the ™ versus ® question.
Questions to ask a POS vendor
Take this table into every demo. Ask the vendor to show each item using two of your brands, not describe it. If you are moving off Sapaad, see Sapaad alternatives in Singapore.
| Area | Question | What a good answer looks like |
|---|---|---|
| Brand set-up | How do I create a brand, and can one item be shared between brands? | Brands created centrally; a shared item keeps one recipe but its own name, photo and price per brand |
| Channel pricing | Can prices differ by brand and by channel? | Yes, set from one back office, with a clear view of every price for an item |
| Kitchen | How does the brand appear on the KDS and printed tickets? | Brand shown clearly on every ticket; station routing works across brands |
| Prioritisation | Can delivery orders be prioritised against pick-up and dine-in? | Order prioritisation and prep timers visible to cooks |
| Sold-out items | If an ingredient runs out, what goes off sale and where? | Affected items across brands and channels, with the steps shown on screen |
| Stock | Does each sale deduct ingredients by recipe, whichever brand sold it? | Recipe-level deduction and costing per item |
| Reports | Can I see sales, cost and discounts by brand and channel? | Standard reports split by brand; exportable |
| Delivery apps | Which platforms are integrated, and how are several brands mapped? | Named integrations, with brand-to-listing mapping demonstrated |
| Own channel | Can each brand have its own ordering page and courier booking? | Brand-specific ordering page; courier option for your own orders |
| Loyalty | Is loyalty shared across brands or separate? | Either, depending on your branding choice |
| Head office | If I add outlets, how are brands managed centrally? | Central menu and reporting for all outlets and brands |
Get the answers in writing from each vendor, including us. A vendor that says “yes” to everything in a sales call but cannot show two brands on one screen during a demo has told you what you need to know.
Where ChaChaCha fits
ChaChaCha, powered by AppsPOS, is a Singapore POS for F&B businesses. For a kitchen running several brands, what we can state is:
- Kitchen: KDS with station routing, order prioritisation and prep timers; English and 中文 kitchen tickets; Epson cloud printing to multiple printers.
- Ordering: an online ordering page, QR ordering and a mobile app.
- Delivery: GrabFood integration, and Lalamove for delivering your own online orders.
- Stock: recipe-level stock deduction and recipe costing per menu item.
- Back office: reports, an ERP for head office and Xero integration.
- Loyalty: points, stamps, stored value, vouchers, birthday rewards and WhatsApp marketing.
For multi-brand specifics, such as how brands are set up, how they appear on tickets, how menus sync and how reports split by brand, ask us to confirm with your own brand line-up. Pricing is quote-based, hardware is supplied by AppsPOS as part of the package, and AppsPOS is approved under the EDGE Grant; see our grant guide. When you are ready, contact us for a demo, or see our cloud kitchen POS page.
