MinimalPOS is a free POS for cloud kitchens and delivery-only brands. Each brand runs as its own business with its own menu and reporting, orders are entered under a delivery service type, and preparation tickets keep a shared kitchen straight. Free as a limited-time launch offer.
Free — limited-time launch offer · Last reviewed
Generic POS marketing treats every venue the same. These are the things that are genuinely different here — and what they mean for the system you pick.
A cloud kitchen often runs three or four virtual brands off one line. Each needs its own menu, its own pricing and — critically — its own P&L, or you cannot tell which brand is actually working.
No tables, no covers, no service staff. The entire operation is order in, prepare, dispatch. Anything built around seating is irrelevant.
GrabFood, foodpanda, LINE MAN and their equivalents each have a tablet. The kitchen still needs one view of what to cook, in what order, regardless of which tablet it came from.
A delivery order is finished when it is bagged correctly, not when the food is cooked. Tickets that survive to the packing bench prevent the missing-item complaints that damage platform ratings.
Each virtual brand is its own business with its own menu, so an order is attributed correctly from the start.
Orders from every brand appear on the same kitchen display, so the line works one queue rather than four tablets.
Items move through preparing and completed states, so the packing bench knows what is ready and what is still coming.
Sales, items and payment mix reported per brand, which is the only way to see which concept is worth keeping.
A feature list means nothing without the reason your venue type needs it.
| Feature | Why it matters for cloud kitchens and delivery-only brands |
|---|---|
| Multi-business switching | Each virtual brand keeps separate menus, settings and reporting under one account. |
| Kitchen display | One queue across every brand, instead of the line reading four platform tablets. |
| Delivery service type | Delivery orders report separately, so brand performance is not muddled with anything else. |
| Per-brand reporting | Tells you which concept earns and which is borrowing the kitchen's capacity. |
| Staff roles | One team across several brands, with permissions that do not need duplicating per brand. |
What it does not do
Yes. Each brand is a separate business with its own menu, settings and reporting, and one owner account switches between them. Per-brand reporting is what tells you which concept is actually earning.
No, and that is worth being direct about. Orders are entered under a delivery service type rather than synced from the platforms. If automatic aggregation is your main requirement, a dedicated aggregator will serve you better than we will.
The value shifts from billing to the kitchen and the numbers: one queue across brands, preparation states that reach the packing bench, and per-brand sales reporting. Those hold whether or not anyone sits down.
Nothing during the launch offer. There is no per-outlet or per-brand charge, which is unusual — most systems price multi-location management as a tier upgrade.
No credit card required. Add your menu and team, then take your first order.