Skip to content

All features

Every feature, with its status

Each capability is marked from our engineering records. Where one only partly works, the limit is written next to it.

Available
34
working end to end
Partial
12
limits written down
Planned
20
not built yet
Available
in the product, working end to end
Partial
some of it exists, limits stated
Planned
not built yet

66 of 66 capabilities

Run

Taking orders, sending them to the kitchen and running the floor.

  1. Browser POS on any device

    Dine-in, takeaway and delivery order types on any tablet, laptop or phone with a browser. No proprietary terminal.

    Available
  2. Variants, modifiers and combos

    Half/full plates, spice level, add-ons. One calculation function prices the POS and QR orders identically.

    Available
  3. Split and merge bills

    Split by item or evenly; splits always sum exactly to the total, including awkward divisions.

    Available
  4. Void vs refund, kept separate

    A paid order cannot be voided or edited; money going back is always a refund with a reason.

    Available
  5. Floor plan and live table status

    Tables, sections and seat counts with live occupancy.

    Available
  6. Guest table requests

    Guests tap to call a server, ask for the bill or water; it lands on the floor staff screen.

    Available
  7. Kitchen display by station

    Live web KDS over websockets, routed by station, with cancellations reaching the pass.

    Available
  8. KOT printing and routing

    Printers per station, routed by category: kitchen, bar, bakery.

    Limit: Routing model and printer records exist; no ESC/POS driver yet. Receipts print through the browser.

    Partial
  9. Offline order taking

    Orders queue on the terminal with stable idempotency keys and replay once when the line comes back.

    Limit: Order creation only. Card payments and the kitchen display need the network.

    Partial
  10. Roles and permissions

    Eight built-in roles, enforced server-side on every endpoint; suspending someone takes effect on their next request.

    Available
  11. Manager approval

    Refunds, voids after send, price overrides and cash adjustments can be authorised inline by a manager signing in on the same screen, and every approval is audited.

    Available
  12. Cash shifts and drawer close

    Expected vs counted, pay-ins, pay-outs and adjustments, each with a mandatory reason.

    Available
  13. Local-network kitchen fallback

    Keep POS and KDS talking over the restaurant LAN when the internet drops.

    Planned
  14. Time clock and scheduling

    Clock-in/out tied to shifts, feeding labour cost.

    Planned
  15. Self-order kiosk

    A kiosk mode of the guest ordering flow.

    Planned

Control

Stock, recipes, suppliers and what each dish costs to make.

  1. Ingredients and stock ledger

    Every movement is a ledger row; on-hand quantity always equals the sum of the ledger.

    Available
  2. Recipes with unit conversion

    A recipe in grams against stock in kilograms is converted, not guessed.

    Available
  3. Automatic stock deduction

    Stock is deducted atomically when an order completes; concurrent orders cannot lose a deduction.

    Available
  4. Plate cost and food cost %

    Cost per dish from the same unit graph used for deduction.

    Available
  5. Weighted-average costing

    Delivered prices roll into ingredient cost as a weighted average on receipt.

    Available
  6. Suppliers and purchase orders

    Raise POs, receive in part or in full; duplicate receiving cannot double-count a delivery.

    Available
  7. Wastage with reasons

    Spoiled, dropped, over-prepped: logged with a reason and reported.

    Available
  8. Expenses

    Rent, gas, repairs captured and fed into the P&L.

    Available
  9. Negative-stock signal

    Stock that goes below zero is surfaced for a count, never silently clamped.

    Available
  10. Auto-86 from stock

    Mark a dish unavailable when its ingredients can no longer cover one portion.

    Planned
  11. Theoretical vs actual variance

    Count sheets compared against the ledger.

    Planned
  12. Par levels and suggested orders

    Reorder points and draft purchase orders.

    Planned
  13. Supplier invoice capture

    Photograph a delivery invoice instead of typing it.

    Planned

Grow

Your website, QR menu, bookings and regular guests.

  1. QR table ordering

    Per-table QR codes, server-priced orders, duplicate-proof submit and a live status page for the guest.

    Limit: Guest status is polled every few seconds, not pushed.

    Available
  2. One availability switch

    Mark a dish 86'd once and both the POS and QR ordering refuse it on the server.

    Limit: Manual toggle only; restaurant-wide, not per branch; open guest menus are not pushed an update.

    Partial
  3. Restaurant website from your menu

    A public page and menu read straight from the live menu database.

    Limit: Browse-only today: no opening hours, content editor or checkout.

    Partial
  4. Reservations

    Branch bookings with server-side overlap checks.

    Limit: Staff-side only. No public booking or deposits yet.

    Partial
  5. Guest profiles

    Customer records with visit history and lifetime spend.

    Limit: No segments or marketing-consent tracking yet.

    Partial
  6. Loyalty points

    Earn and redeem with an explicit tax mode (discount vs tender), reversed on refund, safe under concurrency.

    Limit: No tiers or expiry yet.

    Available
  7. Online ordering (pickup and delivery)

    Web checkout on the same order pipeline as the POS.

    Planned
  8. Public reservation booking

    Guests book from your website.

    Planned
  9. Promotions and campaigns

    Rule-based offers, SMS and email to guest segments.

    Limit: Manual discounts only today.

    Planned
  10. Gift cards

    Stored value on the payment ledger.

    Planned

Understand

Sales, costs and branch figures from the same records.

  1. Sales, tax and end-of-day

    Timezone-correct daily reports with refunds netted out.

    Available
  2. Profit and loss

    Revenue net of tax, service charge and refunds, against COGS, waste, purchases and expenses.

    Available
  3. Product and staff performance

    What sold, who sold it, by hour.

    Available
  4. CSV export

    Every report exports, with spreadsheet formula injection neutralised.

    Available
  5. Branch reporting

    Tenant → restaurant → branch, with per-branch reports.

    Limit: The menu is restaurant-wide: no per-branch menu or prices yet.

    Partial
  6. Menu engineering

    Margin × popularity for every dish. The data already exists.

    Planned
  7. Branch comparison dashboard

    Side-by-side branch performance.

    Planned
  8. Labour cost

    Labour % once the time clock exists.

    Planned
  9. Channel profitability

    Margin by channel, net of aggregator commission.

    Planned

Connect

Payment methods, printers and devices you already use.

  1. Record any tender

    Cash, card, wallet or QR recorded against the bill with idempotent, concurrency-safe writes.

    Limit: Payments are recorded, not processed: you run the card on your own terminal.

    Available
  2. No processor lock-in

    Use any acquirer or wallet; a provider seam is in place for integrated processing later.

    Available
  3. Fonepay dynamic QR

    A unique QR per bill, confirmed by callback. Needs a Fonepay partner agreement.

    Planned
  4. Online checkout (Khalti, eSewa, Stripe)

    Guests pay QR orders online; recorded only after the provider confirms the amount. Needs your merchant account; not yet verified against live accounts.

    Limit: In-store cards are still run on your own terminal.

    Partial
  5. Card terminal integration

    Push the amount to the terminal instead of keying it twice.

    Planned
  6. Printers

    Network, USB and Bluetooth printers modelled per station.

    Limit: No device driver yet.

    Partial
  7. Accounting export

    CSV today; journal export for Xero, QuickBooks and Tally-style ledgers later.

    Limit: CSV exports only.

    Partial
  8. Public API and webhooks

    Scoped API keys and signed webhooks for order, menu, stock and payment events, not gated by plan.

    Planned
  9. Delivery aggregator orders

    Inbound adapters where platforms offer an API; a manual lane where they do not.

    Planned

Comply

VAT invoices, credit notes and an audit log of sensitive actions.

  1. VAT-inclusive and exclusive prices

    Inclusive prices have their VAT extracted and reported, not shown as zero.

    Available
  2. Per-item tax rate

    Override the restaurant rate for an individual item.

    Available
  3. Service charge

    Configurable percentage, kept out of revenue in the P&L.

    Available
  4. Decimal money everywhere

    No floating point in any monetary path.

    Available
  5. Audit log

    Sensitive actions (voids, refunds, discounts, permission changes) are recorded.

    Limit: Login/logout coverage still being checked; the retention job can delete old audit rows, which a Nepal deployment must disable.

    Partial
  6. Data retention and anonymisation

    Configurable retention; dormant customers are anonymised.

    Available
  7. Currency and timezone per restaurant

    Each restaurant carries its own currency and timezone.

    Available
  8. Nepal fiscal invoice

    PAN on the bill, fiscal invoice numbering, Bikram Sambat dates, "Copy of Original" on reprint, credit notes, IRD-format sales register.

    Available
  9. CBMS real-time reporting

    Invoices and credit notes reported to IRD CBMS with automatic retry.

    Limit: Implemented; awaiting validation with IRD. DataRestro is not yet IRD-approved.

    Partial
  10. CBMS transmission

    Real-time invoice sync to IRD through a retrying outbox.

    Limit: Not certified or approved by IRD. Certification is a separate approval.

    Planned

Need something that isn’t listed? Tell us what it is.