Help centre

Any device with a modern browser: a tablet or laptop at the counter, a phone for floor staff, a screen per kitchen station. There is no proprietary terminal. Keep your existing card terminal: DataRestro records card payments, it does not process them.

Create categories, then items with variants (half/full) and modifier groups (spice level, add-ons). Import from a spreadsheet is on the roadmap, so today menus are entered in the app. For a typical 60-80 item menu, plan an afternoon.

Yes. The live demo runs a full service in your browser against sample data.

Yes: tax settings, staff roles, a mock service and a network-pull test, a week out.

The POS keeps taking orders. They queue on that terminal with a stable idempotency key and replay once the connection is back, so nothing is duplicated. Offline mode covers order taking only: recording payments and the kitchen display need the network. The queue lives on the device that created it, so do not clear or wipe a terminal that still has queued orders.

Yes. Split by item or evenly; splits always add up exactly to the total. Tables can be merged into one bill.

A void cancels something that has not been paid for. A refund returns money on a paid order. A paid order cannot be voided or edited, so the record of what was paid never changes after the fact.

For refunds, voids after the kitchen has the ticket, price overrides and cash adjustments, a manager can approve on the same screen by entering their own credentials. The cashier stays signed in, and the approval is written to the audit log.

Not yet. Printers can be set up per station (network, USB or Bluetooth) and routing by category is modelled, but a printer driver has not shipped. Today the kitchen works from the live kitchen display, and customer receipts print through the browser.

Items are routed by station on the kitchen display, which updates live. Cancellations reach the station screen too.

No. The kitchen display needs a connection to the server. A local-network fallback, so POS and kitchen keep talking during an internet outage, is on the roadmap.

The kitchen display is a web page, so any screen with a browser can run it. There is no per-screen fee for kitchen displays.

From recipes, when an order completes. Units are converted (a recipe in grams against stock in kilograms), and the deduction is atomic, so two orders at once cannot lose one.

Because more was used than was recorded as received, usually a delivery not entered, a recipe quantity that is off, or a missed count. DataRestro shows the negative rather than hiding it at zero, so you know to check.

Not automatically yet. You can mark an item unavailable and both the POS and QR ordering will refuse it. Auto-86 from stock levels is on the roadmap.

Each delivery you receive against a purchase order updates the ingredient’s cost as a weighted average. Stock moves on receipt, never when the PO is raised.

No. Payments are recorded, not processed. Run the card on your own terminal first, then record the payment in the POS. You keep your own acquirer and your own rates, and you reconcile against your processor’s statement.

At the till, take any of them and record the payment against the bill. For QR orders, guests can also pay online through eSewa or Khalti once you connect your merchant account; the payment is recorded only after the provider confirms it. Fonepay dynamic QR is not available yet.

Every payment carries an idempotency key, so a retry, a double tap or an offline replay records once. Concurrent payments on the same bill cannot lose or duplicate money.

Close the shift, enter the counted amount, and DataRestro shows expected, counted and the difference. Pay-ins, pay-outs and adjustments each require a reason.

Not yet approved. DataRestro issues fiscal invoices built to IRD’s published rules (fiscal-year numbering, PAN, BS dates, copy marking, credit notes, sales register) and has a CBMS reporting client, but it is not approved or listed by Nepal’s Inland Revenue Department and its CBMS reporting is awaiting validation. If you are required to use approved billing software, keep using it for tax invoices until DataRestro is approved.

Yes. Set prices to tax-inclusive and the VAT is extracted from each price and reported, not shown as zero. Tax-exclusive prices are supported too.

Yes. The restaurant has a default rate, and any item can override it.

No. Service charge and tax are kept out of revenue in the profit and loss report. Whether VAT applies to your service charge is a question for your tax advisor; the setting follows your configuration.

Built-in roles cover Owner, Admin, Manager, Cashier, Waiter, Chef, Inventory Manager and Accountant. Permissions are enforced on the server for every request, not just hidden in the interface.

On their next request. They do not keep access until a token expires.

Use “Forgot password” on the sign-in page. The reset link is emailed to you.

Retention is configurable. By default transactions are kept for seven years (84 months) for the tax record, and personal details of customers dormant for two years are anonymised. Nepal deployments need deletion of fiscal records switched off; talk to us before going live.