Skip to content
BuilderSoft
Restaurant Point of Sale SoftwareLive product

Run the floor, the kitchen, and the till from one system.

RPOS is a multi-tenant restaurant platform: order taking on the floor, a live kitchen display, billing with splits and credit, and an admin portal for menu, staff, and reporting — built to keep working even when the internet doesn't.

Sign in to RPOSBook a demoRead the docs

The problem

The till, the kitchen, and the floor were never talking to each other.

Most restaurants run order pads, a kitchen printer, a separate billing machine, and a notebook for credit customers — reconciled by hand at the end of the night, if at all.

  • Orders scribbled on paper get lost between the table and the kitchen
  • The kitchen has no idea how long a ticket has actually been waiting
  • Billing and the floor disagree on what a table actually ordered
  • A dropped Wi-Fi signal means the floor stops taking orders entirely
  • Credit customers are tracked in a notebook nobody reconciles
roles routed to the right screen automatically
4
orders lost to a dropped connection
0
ways to split a single bill
20
portal running every restaurant on the platform
1

9 modules, all included

Every module a restaurant actually needs.

Not a toolkit you assemble — a complete operating system. Each module is included on every plan and connected to all the others.

Module 1 of 9

Floor & Order Taking

Waiters work a live floor plan — table status, menu search, add-ons, and notes — with orders queued and synced automatically if the connection drops.

  • Colour-coded floor grid: Free, Occupied, Bill requested, Cleaning
  • Dine-in tables and takeaway orders from the same screen
  • Menu search, category tabs, and a one-tap Top sellers view
  • Add-ons, sizes, and per-item notes with quick-note chips
  • Table transfer, bill requests, and void workflows with reasons
  • Offline order capture with automatic sync once reconnected

Module 2 of 9

Kitchen Display System

A full-screen ticket board for Kitchen and Bar stations that flags slow tickets before a guest has to ask.

  • Separate Kitchen / Bar views with unread-ticket counts
  • Per-item status: Sent → Cooking → Ready, tapped by the cook
  • Colour escalation on tickets that pass configurable wait thresholds
  • New-ticket chime and flash, mutable per station
  • One-tap bump off the board once every item is ready
  • Reprint to the station printer without re-sending the order

Module 3 of 9

Billing & Payments

Cashiers bill any open order, take payment in any mix of methods, and print or send the receipt in one flow.

  • Shift open/close with counted cash drawer and variance report
  • Bill now, or bill-and-collect cash in a single tap
  • Cash, card, eSewa, Fonepay, Khalti, and credit, with partial payment
  • Split a bill equally or by item, into 2–20 separate bills
  • Cash in/out logging for drawer movements mid-shift
  • Print, browser-print, or send receipts by email and WhatsApp

Module 4 of 9

Discounts, Voids & Refunds

Every exception on a bill — discount, void, or refund — is reason-coded and written to the audit log automatically.

  • Quick-pick and custom discounts with a mandatory reason above a configurable threshold
  • Item voids on sent orders, restricted to admins and cashiers by default
  • Admin-only refunds against any paid bill, reason required
  • Struck-through voided items excluded from kitchen prep and the bill
  • Every discount, void, and refund logged with who, when, and why

Module 5 of 9

Customers & Credit

Run a tab for regulars with a real ledger, credit limits, and statements — instead of a notebook behind the counter.

  • Customer records with phone, email, and a per-customer credit limit
  • Running ledger of credit sales and payments per customer
  • Admin approval to go over a customer's credit limit at billing time
  • One-click statements and reminders by email, WhatsApp, or PDF
  • Bulk monthly statement run for every customer with a balance

Module 6 of 9

Menu & Catalog

Categories, items, add-ons, and pricing — editable in place, with an import path for getting a full menu in fast.

  • Drag-to-reorder categories; items stay put if a category is deleted
  • Per-item station routing (Kitchen or Bar) that drives ticket printing
  • Add-ons with their own pricing and single-choice rules (e.g. sizes)
  • In-place price edits that apply only to new orders, not open ones
  • Instant sold-out toggle per item
  • Spreadsheet import with validation of flagged rows before commit

Module 7 of 9

Staff, Roles & Shifts

PIN login for the floor, email and password for admins, and role-scoped access for everyone in between.

  • Four roles — Admin, Cashier, Waiter, Kitchen — each landing on their own screen
  • 4-digit PIN login for staff; PIN reset and deactivation from the staff list
  • Email and password login for Admin accounts
  • Switch-user and full-logout controls on every screen
  • Per-restaurant staff list with role changes and deactivation, not deletion

Module 8 of 9

Reports & Audit Log

Sales, collections, and voided-item reporting for any date range — plus a full audit trail of every sensitive action.

  • Sales, bill count, average bill, and sales-by-hour/day for any date range
  • Top items, categories, payment-method mix, and waiter performance
  • Credit given/collected and voided-item reporting
  • CSV export on every report table
  • Audit log of voids, discounts, refunds, reprints, transfers, and shift closes — who, when, why

Module 9 of 9

Multi-restaurant Platform Admin

One operator portal runs every restaurant on the platform — provisioning, feature flags, and branding, without touching any single restaurant's data.

  • Create a new restaurant with its own slug, web address, and first admin
  • Toggle any restaurant active or inactive
  • Enable or disable features per restaurant: credit, kitchen display, notifications
  • Per-restaurant brand colour, logo, and generated web address
  • New restaurants land straight into the first-time setup wizard

How it works

From table to ticket to till, one connected order

Every screen reads and writes the same order. Nothing is re-typed between the floor, the kitchen, and the bill.

  1. 1

    Seat and order

    A waiter opens a table or takeaway and builds the cart with add-ons and notes from the live menu.

  2. 2

    Send to the right station

    Each item routes to Kitchen or Bar automatically, and its status is visible back on the floor the moment it changes.

  3. 3

    Cook against a live board

    Kitchen staff cycle tickets Sent → Cooking → Ready. Slow tickets escalate colour automatically, before a guest has to ask.

  4. 4

    Ask for or take the bill

    The table is flagged “Bill requested” for a cashier, or billed directly by whoever on the floor has permission.

  5. 5

    Collect in any mix

    Cash, card, QR wallet, or credit — in full, in part, or split across methods and across guests.

  6. 6

    Close out and reconcile

    The shift closes against a counted drawer, and every report and audit entry from the night is already there.

Built for every seat

One platform, every role covered.

  • Owner / Admin

    Before
    Finds out how today went from tomorrow's notebook tally.
    After
    A live dashboard — sales, payment mix, voids, waiter performance — for any date range, every morning.

  • Waiter

    Before
    Loses track of what a table ordered the moment the floor gets busy.
    After
    A floor screen with live order status per table, working even if the Wi-Fi drops.

  • Cashier

    Before
    Reconciles cash, card, and QR payments by hand at the end of the night.
    After
    One shift summary across every payment method and cash movement, with a counted close and a variance figure.

  • Kitchen staff

    Before
    Works off a printer with no sense of how long anything has been waiting.
    After
    A ticket board that escalates colour the longer something sits, so nothing gets forgotten.

  • Platform operator

    Before
    Supporting multiple restaurants means logging into each one separately.
    After
    One operator portal to provision, configure, and monitor every restaurant on the platform.

Connected stack

Plays well with the systems you already run.

RPOS is the operational core — and it connects outward to the tools around it, so nothing gets typed twice.

  • Payments

    • Cash
    • Card
    • eSewa
    • Fonepay
    • Khalti
    • Credit accounts

  • Printers

    • Kitchen station printer
    • Bar station printer
    • Cashier bill printer
    • Browser print fallback

  • Messaging

    • Email receipts & statements
    • WhatsApp receipts & reminders

  • Data

    • Spreadsheet menu import
    • CSV report export
    • PDF customer statements

Security, control & compliance

Enterprise controls, whatever your size.

  • Role-based screens

    Admin, Cashier, Waiter, and Kitchen each see only their own screen and permissions, enforced from first login.

  • Complete audit trail

    Every void, discount, refund, reprint, transfer, and shift close is logged with who did it, when, and the reason given.

  • Offline-safe order capture

    Floor orders taken offline are queued on the device and synced automatically — nothing is lost to a dropped connection.

  • PIN and password separation

    Floor staff log in with a 4-digit PIN; admin accounts use email and password, reset only by another admin.

  • Per-restaurant data isolation

    Each restaurant's menu, staff, customers, and reports are scoped to its own tenant, even though the platform is shared.

  • Reason-coded exceptions

    Large discounts, voids, and refunds require a typed reason before they're allowed to go through.

Getting started

Live in weeks, not quarters.

  1. Step 1

    Restaurant profile

    Name, PAN/VAT, address, receipt footer, and logo — everything that prints on a bill.

  2. Steps 2–3

    Tax & floor plan

    VAT and service charge rules, rounding, and your floor: sections and tables, bulk-added by name prefix.

  3. Steps 4–5

    Menu & staff

    Menu imported from a spreadsheet, staff added with roles and PINs — the same import path used later from Admin → Menu.

  4. Step 6 onward

    Printers & go live

    Kitchen, Bar, and Bill printer addresses set once. Every step can be skipped and finished later from the Admin sidebar.

We built RPOS because the floor, the kitchen, and the till kept drifting apart the moment a restaurant got busy. A shared order state fixes that by construction, not by discipline.
BuilderSoft Product TeamFrom the RPOS design notes
Offline support wasn't a nice-to-have — a waiter mid-order when the Wi-Fi blinks can't lose that ticket. That constraint shaped the whole floor screen.
BuilderSoft EngineeringOn designing the offline floor

Questions

RPOS FAQ

Something not covered here? Email info@buildersoft.ca — a human answers within one business day.

What is RPOS?

RPOS is BuilderSoft's cloud-based restaurant point-of-sale platform covering floor order-taking, a live kitchen display, billing and payments, customer credit, menu and staff management, and reporting — all from one shared, multi-tenant app.

Does RPOS work if the internet drops?

The Floor screen is built to keep working offline: a waiter can still open a table and add items, with a banner confirming the order is saved and will sync automatically once the connection returns. Kitchen, Billing, and Admin need a live connection.

Can RPOS handle split bills and multiple payment methods?

Yes. A bill can be split equally (2–20 ways) or by item, and any bill can be paid across a mix of cash, card, eSewa, Fonepay, Khalti, and credit in partial amounts.

Can I run customer credit accounts?

Yes. Each customer gets a credit limit and a running ledger of credit sales and payments, with admin approval required to exceed their limit at billing time, and one-click statements by email, WhatsApp, or PDF.

How do kitchen tickets avoid getting forgotten?

Tickets change colour the longer they wait, using amber and red thresholds your admin sets in Settings — so a slow ticket is visible on the board well before a guest has to ask.

Can RPOS host more than one restaurant?

Yes — RPOS is one shared application that hosts many restaurants, each at its own web address and slug. A platform operator provisions new restaurants from a separate superadmin portal.

Is there an audit trail for discounts, voids, and refunds?

Yes. Every discount above a configurable threshold, item void, refund, reprint, table transfer, and shift close is logged with who performed it, when, and the reason given.

See your work running in RPOS this week.

A 30-minute demo with your own project structure — no slideware.

Book a demo