A POS for cafés and cloud kitchens needs five things: a counter screen fast enough for a morning queue, clean modifiers for every drink and dish, a kitchen display or printer that shows orders by channel, stock deduction at ingredient level, and VAT-correct receipts. Cafés add a simple loyalty hook; cloud kitchens add aggregator order handling and multi-brand menus. Almost everything else sold as a feature can wait until you have the basics running smoothly.
What cafés and cloud kitchens have in common
Both are high-volume, low-ticket operations where seconds per order add up. Both live on consumables (milk, beans, packaging, sauces) that disappear quietly. And both in the UAE must issue receipts with a TRN and 5% VAT once they cross the registration threshold of AED 375,000 in taxable supplies over the past 12 months (voluntary from AED 187,500), as set by the Federal Tax Authority at tax.gov.ae. Records must be kept generally for 5 years.
The difference is the front of house. A café has a counter and a queue; a cloud kitchen has no customers at all, just screens full of incoming delivery orders.
The POS for cafés: five essentials
1. A counter screen built for speed
Favourites on the first screen, one-tap sizes, clear pictures if staff turnover is high. A barista should ring up a flat white with oat milk in two taps. If the demo takes five, the live shift will take seven.
2. Modifiers that charge correctly
Milk type, syrup, extra shot, size. Each modifier needs its own price and its own stock deduction. Paid extras given away because the button was missing are the most common silent loss in cafés.
3. Order numbers or names and a pickup screen
Customers should know when their order is ready without staff shouting. A simple pickup display or printed order number keeps the counter calm.
4. Loyalty by phone number
A stamp or points scheme tied to the customer's phone number, with redemption at the counter, brings regulars back and builds a list you can message. No app download required. Our loyalty programme guide covers the options.
5. Consumables tracking
Track milk, beans, cups and lids as ingredients. Compare theoretical use with the weekly count. The gap tells you about over-pouring, spillage and free drinks for friends.
The POS for cloud kitchens: five essentials
1. One screen for every channel
Orders from each delivery aggregator, your own website and phone orders should land on a single kitchen display, tagged by channel and brand, in time order. Juggling four aggregator tablets causes missed orders and angry riders.
2. Multi-brand menus on shared stock
A cloud kitchen often runs three or four virtual brands from one kitchen. The POS needs separate menus and reports per brand, with ingredients deducted from one shared inventory.
3. Prep-time and pause controls
When the kitchen is slammed, staff should be able to pause a brand or extend prep times across channels from the POS, not log into each aggregator portal.
4. Recipe costing per channel
Aggregator commissions differ, so the same dish earns a different margin on each platform. The POS should report sales and food cost by channel so you can price each menu properly.
5. Packaging as stock
Boxes, bags, cutlery and sauce tubs are real costs. Deduct them per order type so you see the true cost of a delivered meal.
Quick comparison
| Need | Café | Cloud kitchen |
|---|---|---|
| Counter speed | Critical | Not needed |
| Modifiers | Critical | Important |
| Kitchen display | Useful | Critical |
| Aggregator orders | Useful | Critical |
| Multi-brand menus | Rare | Critical |
| Loyalty | Important | Useful via own website |
| Ingredient stock | Important | Critical |
| QR ordering | Useful | Not needed |
Hardware you actually need
A café can run on one Android tablet or iPad, an 80 mm thermal receipt printer, a small kitchen or bar printer and a cash drawer. A cloud kitchen needs a kitchen display screen (a rugged tablet or a mounted monitor), a label printer for order bags and a receipt printer for rider slips. Neither needs a branded POS terminal. See the POS hardware guide for models and connection types. For cafés with tables, QR menu ordering can reduce counter pressure at busy times.
Things you can skip at the start
- Table maps and reservation modules (cafés with counter service do not need them).
- Complex tiered loyalty before you have regulars.
- Full accounting inside the POS; export clean data instead.
- Dozens of integrations; connect only the channels that bring orders.
Setting up in a week
- Day 1: menu, modifiers, prices (VAT inclusive) and brands.
- Day 2: recipes and packaging per item, opening stock count.
- Day 3: hardware, printers, kitchen display, offline test.
- Day 4: aggregator and website order routing, test orders end to end.
- Day 5: staff training, PIN roles, first live shift with a fallback plan.
Our services page describes how we set up ZainiPOS for food businesses, including kitchen displays and delivery channel routing.
Frequently asked questions
Can a cloud kitchen run several brands on one POS?
Yes, and it should. Each brand has its own menu and reports, orders from every brand flow to a shared kitchen display, and stock is deducted from one shared store. Without this you end up juggling tablets and counting ingredients twice.
Do I need a separate tablet for each delivery aggregator?
Not if your POS integrates with them or accepts orders through a middleware service. Integration varies by platform and region, so list the aggregators you actually use and ask the vendor to show live orders arriving in the POS before you commit.
Is a kitchen display better than a kitchen printer for a café?
For a small café a printer is cheaper and perfectly adequate. A display earns its keep once you handle many simultaneous orders or several channels, because it shows timing, lets staff bump completed items and never runs out of paper. Many kitchens use both.
How should a café POS handle VAT in the UAE?
It should print receipts with your TRN and the 5% VAT amount once you are registered. Registration is mandatory above AED 375,000 in taxable supplies in the past 12 months and voluntary from AED 187,500. Keep full transaction records for generally 5 years and export a VAT summary for EmaraTax filing.
What is the simplest loyalty setup for a café?
A points-per-dirham or stamp-card scheme tied to the customer's phone number, redeemed at the counter in one tap. It needs no app download and gives you a customer list you can message. Start simple and add tiers only when you have a real base of regulars.
How Zaini Developers can help
ZainiPOS, our web and mobile POS, covers counter sales, modifiers, kitchen displays, multi-brand menus, ingredient and packaging stock, phone-number loyalty and VAT receipts, in English, Arabic, Urdu, Hindi, French and Dutch. We build the delivery-channel routing and reports around how your kitchen actually works, and quote each project on its scope. See the live demo or contact us on WhatsApp at +971 50 260 0409.