Plain-English summary#
Foodops is Hubits's restaurant management platform — the all-in-one system a café, restaurant or food business uses to take orders, run the kitchen, take payments, track stock and see its numbers. It's one of two product lines Hubits builds: Foodops for food and restaurants, and Shops (its point of sale is branded Salesmade) for retail. If you sell food, Foodops is your side; if you run a retail store, that's Shops/Salesmade. Both are built by Hubits, a Maldivian software company, and share one login (sso.hubits.io).
When you'd use this#
- You want to know "what is Foodops?" or which products Hubits offers.
- You're not sure whether you need Foodops (restaurant) or Shops/Salesmade (retail).
- You want to understand how Foodops, Shops and Salesmade relate.
- You're getting oriented before diving into a specific Foodops feature.
How to access#
Foodops runs as four connected web apps, all reachable from the app switcher in the admin back office. The counter and back office use your Hubits account (sso.hubits.io):
- Counter POS — counter.foodops.io — the till on the floor: orders, payments, kitchen, register sessions.
- Admin back office — admin.foodops.io — menu, settings, users, taxes, discounts, reports, inventory setup.
- Kitchen (kds.foodops.io): the kitchen display.
- Online Ordering (order.foodops.io): the storefront your customers order from.
Delivery riders use a separate mobile app. In the app switcher, the Driver, Reservations, Loyalty and Insights tiles read "coming soon".
See Foodops Navigation & Module Map for every screen.
Key concepts#
- Hubits — the Maldivian company that builds these products. One company, one login, several apps.
- Foodops — the restaurant side.
- Shops / Salesmade — the retail side (a shop, pharmacy, mini-mart, boutique). The established retail app is Shops at shop.hubits.io; the newer point of sale and back office are branded Salesmade (counter.salesmade.io for the till, app.salesmade.io for the back office, website salesmade.io).
- Same login, different lens — Foodops and Shops/Salesmade share the same Hubits account and much of the same data (customers, suppliers, inventory). Each app presents it through its own workflow — food service vs retail checkout.
- Salesmade in one line — "Retail POS with the back office built in" — point of sale, inventory and accounting for Maldivian retailers.
Common questions#
Q: I run catering / events (weddings, functions) rather than a restaurant — is Foodops a fit? A: Foodops is built for food businesses generally, not only sit-down restaurants — so parts of it fit catering well and one part is missing. Here's what exists and what doesn't, so you can judge:
Fits catering well
- Customer accounts with credit terms and invoicing — exactly the pattern of a company booking an event and paying later. A customer record carries payment terms, credit limit and outstanding balance (e.g. a company books catering and pays Net-30), and you can take payment against the account afterwards. See Customers & CRM.
- Event/catering markup as a service fee — a service fee can be applied per order type, and "event catering markup" is exactly what it's designed for. See Service Fees.
- Delivery orders with a named customer (a delivery address can be added but isn't required), sent to a deliveries queue.
- Quotes in the admin back office (Sales → Quotes). The counter app has no quote screen for Foodops.
- The usual core: menu and pricing, stock and purchasing, cash sessions, and reports (including sales per customer).
Not built for it — know this before you decide
- There is no event booking, scheduling or calendar. Foodops orders are for now, not a future date: the order types are Dine-In, Takeout and Delivery only — there's no "event" or "catering" order type — and there's no pre-order or scheduled-order feature. There are no reservations, so there's no built-in way to hold a date or keep a function diary. See Order Types and Reservations.
In practice: Foodops can handle the money and food side of catering — menu, costs, stock, an invoiced customer account, event markup — but it won't run your event diary. You'd keep bookings wherever you keep them today and create the order when you serve it. Ask us and we'll walk through your workflow.
Q: Which products can you help with? A: Two product lines from Hubits. Foodops — restaurant management: counter POS, kitchen display, dine-in/takeout/delivery orders, menu, inventory, purchasing, cash sessions, reports, online ordering. Shops / Salesmade — retail point of sale and inventory for shops (barcode checkout, stock control, sales receipts, returns, loyalty).
Q: What is Foodops? A: Foodops is Hubits's restaurant management platform — one system to take orders (dine-in, takeout, delivery), run the kitchen, take payments, manage your menu and stock, and see your reports. It runs at counter.foodops.io (the till), admin.foodops.io (the back office), kds.foodops.io (the kitchen display) and order.foodops.io (online ordering).
Q: What's the difference between Foodops and Shops (Salesmade)? A: Foodops is built for food businesses — it has a kitchen display, dine-in tables, recipes, and takeout/delivery. Shops/Salesmade is built for retail — barcode checkout and stricter stock control. They're sister products on the same Hubits platform, so a business that runs both a restaurant and a shop can use both under one account.
Q: Is Salesmade the same thing as Shops? A: Salesmade is Hubits's retail point-of-sale brand — the retail counterpart to Foodops, in the same family as the Shops app at shop.hubits.io. If you run a retail shop, that's your side; if you run a restaurant, Foodops is.