Foodops Platform — What It Is & Which Products We Cover

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 is one of two product lines Hubits builds: Foodops for food & restaurants, and Shops (its modern point-of-sale is branded Salesmade) for retail shops. If you sell food, Foodops is your side; if you run a retail store, that's the Shops/Salesmade side. Both are built by Hubits, a Maldivian software company, and share one login (sso.hubits.io).

When you'd use this

• Someone asks "which products can you help with?" or "what is Foodops?" — this page is the answer.
• A customer is unsure whether they want Foodops (restaurant) or Shops/Salesmade (retail).
• Explaining how Foodops, Shops, and Salesmade relate to each other.
• Getting oriented before diving into a specific Foodops feature.

How to access

Foodops runs as two connected web apps (both use your sso.hubits.io account):

• Counter POS — counter.foodops.io — the on-the-floor till: orders, payments, kitchen, register sessions. [code: foodops.counter.app/src/config/brands.ts — foodops brand, applicationId 24 (RestaurantPOS) @main]
• Admin back-office — admin.foodops.io — menu, settings, users, taxes, discounts, reports, inventory setup.

The old single app at app.foodops.io is retired (July-2026 launch) — if it won't load or log in, nothing is wrong with your connection; use counter.foodops.io and admin.foodops.io instead. See Foodops Navigation & Module Map for every URL.

What Foodops helps you do

Foodops covers the full restaurant workflow. At a high level:

• Take orders — dine-in (with tables), takeout, and delivery, all from the counter. [code: foodops.counter.app/README.md — "Order Management: Create, edit, and manage dine-in, takeout, and delivery orders" @main]
• Take payments — cash, card, and transfer, including split payments and multi-currency.
• Run the kitchen — a Kitchen Display (KDS) shows orders to the kitchen and tracks what's ready.
• Manage the menu — items, variants, modifiers, menu groups, recipes/BOM.
• Track stock & purchasing — inventory, suppliers, purchase orders, stock adjustments.
• Handle the cash drawer — open/close register sessions with cash reconciliation.
• See the numbers — dashboards and a full reports catalogue.
• Sell online & deliver — an online-ordering storefront and delivery/driver tools.
• Know your customers — customer profiles, standing discounts, and loyalty.

For the exact screen-by-screen detail of any of these, see the specific KB entry for that feature.

Key concepts

• Hubits — the Maldivian company that builds these products. One company, one identity system, several apps.
• Foodops — the restaurant side. Internally this is the "RestaurantPOS" application (application id 24). [code: haafai.domain/Haafai.Models/Constants/ModelConstants.cs:3073 RestaurantPOS = 24 @staging]
• Shops / Salesmade — the retail side (a shop, pharmacy, mini-mart, boutique). Internally this is the "RetailPos" application (application id 20). [code: haafai.domain/Haafai.Models/Constants/ModelConstants.cs:3069 RetailPos = 20 @staging] The established retail app is Shops at shop.hubits.io; the newer point-of-sale and back-office ship under the Salesmade brand (counter.salesmade.io for the till, app.salesmade.io for the back-office, marketing site salesmade.io). [code: foodops.counter.app/src/config/brands.ts — salesmade brand, counter.salesmade.io + admin app.salesmade.io @main] See Shops Platform — Overview & Module Map.
• Same login, different lens — Foodops and Shops/Salesmade share the same Hubits account and much of the same underlying data (customers, suppliers, inventory). Each app presents that data 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. (From the Salesmade product site, salesmade.io.)

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 genuinely missing. Rather than a yes/no, here is what exists and what doesn't, so you can judge:

Fits catering well

• Customer accounts with credit terms and invoicing — the exact 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 configurable service fee can be applied per order type, and "event catering markup" is exactly the shape it is designed for. See Service Fees.
• Delivery orders with a named customer + delivery address, routed to a deliveries queue.
• The usual spine: menu/pricing, stock and purchasing, cash sessions, and the reports (including per-customer sales).

Not built for it — know this before you decide

• There is no event booking, scheduling, or calendar. Foodops orders are created for now, not for a future date: the order types are Dine-In, Takeout and Delivery only — there is no "event" or "catering" order type — and there is no pre-order/scheduled-order feature. Reservations were deliberately dropped in the current product, so there is no built-in way to hold a date or manage a function diary. See Order Types and Reservations.
• Quoting is documented on the Shops/Salesmade side, not as a Foodops workflow — so if formal written quotes per event are central to how you sell, ask us about that specifically rather than assuming the Foodops counter covers it.

In practice: Foodops can handle the money and food side of catering — menu, costs, stock, an invoiced customer account, event markup — but it will not run your event diary; you would keep bookings wherever you keep them today and create the order when you serve it. Whether that trade is worth it is a sales conversation, not a product fact — 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 & inventory for shops (barcode checkout, stock control, sales receipts, returns, loyalty). Ask about whichever fits your business and I'll help with that side.

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) and admin.foodops.io (the back-office).

Q: What's the difference between Foodops and Shops (Salesmade)? A: Foodops is built for food businesses — it has kitchen display, dine-in tables, recipes, and takeout/delivery. Shops/Salesmade is built for retail — barcode checkout, stricter stock control, price lists, and quotes. They're sister products on the same Hubits platform, so one 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 the retail (point-of-sale) brand on Hubits's modern app stack — the retail counterpart to Foodops. It's the retail/"RetailPos" side of the platform, the same family as the Shops app at shop.hubits.io. If you're a retail shop, that's your side; if you're a restaurant, Foodops is.

Q: Can I use one Hubits account for both my restaurant and my shop? A: Yes — Foodops and Shops/Salesmade share the same sso.hubits.io login and org. A business running both a café and a merchandise shop can subscribe to both and switch between them. See Shops Platform — Overview & Module Map.

Related

• Shops Platform — Overview & Module Map — the retail (Shops/Salesmade) sibling
• Foodops Navigation & Module Map — every Foodops URL and screen
• Users, Roles & Permissions — accounts, roles, and app access