Skip to content
DataRestro

Integrations

What DataRestro connects to

Kitchen display, QR ordering, inventory and loyalty are part of DataRestro rather than separate products to connect. This page lists the outside services it works with today and the ones that are planned.

Try it in the demoGet started

Filter to “Available now” to see what works today. Planned integrations have no dates until they are built.

Shared records

DataRestro

Menu, stock, orders and payments in one record. Everything plugs into that record, not into each other.

Payments

  • Card on your own terminal

    Any acquirer; approval code recorded

    Available

  • Cash, drawers, shifts

    Float, paid-outs, counted close

    Available

  • Bank transfer

    Recorded by transfer reference

    Available

  • Integrated card terminal

    Via the provider seam

    Planned

Nepal wallets & QR

  • Fonepay · eSewa · Khalti

    Recorded by wallet transaction ID

    Available

  • Fonepay dynamic QR

    A QR per bill, confirmed by callback

    Planned

  • eSewa & Khalti online checkout

    Guests pay QR orders online; confirmed with the provider before it is recorded

    Partial

Accounting

  • CSV exports

    Sales, payments, refunds, tax, products, staff

    Available

  • Expenses

    Captured in-app, flowing into the P&L

    Available

  • Journal export

    Xero, QuickBooks, Tally-compatible

    Planned

Hardware

  • Any browser device

    Tablet, laptop, touchscreen

    Available

  • Kitchen display

    Any screen with a browser

    Available

  • Receipt printing

    Through the browser print dialog

    Available

  • ESC/POS thermal printers

    Network, USB, Bluetooth; routing is modelled, driver pending

    Partial

Delivery

  • Delivery orders at the POS

    Own riders or re-keyed aggregator orders

    Available

  • Foodmandu

    No public POS API found yet

    Planned

  • Pathao Food

    No public POS API found yet

    Planned

  • Menu & 86 push

    Where aggregator APIs allow

    Planned

Built-in channels

  • QR table ordering

    Same order pipeline as the POS

    Available

  • Restaurant website

    Live menu page; browse-only today

    Partial

  • Online ordering

    Pickup and delivery checkout

    Planned

  • Kiosk

    Self-order on the QR flow

    Planned

API & webhooks

  • Public API keys

    Scoped keys for your own tools

    Planned

  • Signed webhooks

    Order, menu, stock, payment events

    Planned

Migration

  • CSV import

    Menu, customers, ingredients

    Planned

  • Your data out

    Every report exports to CSV

    Available

Keep your own card terminal

DataRestro records payments; it doesn’t process them. You run the card on your own terminal, from whichever bank you choose, then record the approval code against the order. Fonepay, eSewa and Khalti payments are recorded the same way, by transaction ID.

  1. 1You can change card provider without changing anything in the POS.
  2. 2Card numbers never reach DataRestro.
  3. 3Online checkout through Khalti, eSewa and Stripe for QR orders, on your own merchant account.
GET /api/v1/payments/providerAvailable
{
  "name": "external-terminal",
  "processesPayments": false,
  "processesRefunds": false,
  "supportedMethods": [
    "CASH", "CARD", "BANK_TRANSFER",
    "DIGITAL_WALLET", "LOYALTY", "OTHER"
  ],
  "summary": "Card payments are recorded, not processed."
}

The server says what it can do, and the till reads it. When a real provider is added, every screen changes its wording at once, with no app update needed.

Foodmandu and Pathao Food orders

We found no public POS integration API for Foodmandu or Pathao Food. Today, staff enter their orders in the POS as delivery orders, so they still reach the kitchen, deduct stock and appear in reports.

Where an aggregator offers an API, we plan to receive its orders automatically and send menu and sold-out changes back.

Today

Available

  1. Aggregator tablet pings

  2. Re-key as a Delivery order at the POS

  3. Kitchen ticket, stock deduction, reports

Planned

Planned

  1. Order arrives through an adapter

  2. Lands on the same order pipeline

  3. Menu & 86 pushed back out

Only where the aggregator offers an API.

API and webhooks (planned)

Today the REST API is internal: our own apps use it, signed in with staff accounts. Scoped API keys and signed webhooks for order, menu, stock and payment events are planned.

POST https://your-app.example/hooksPlanned
X-Restro-Signature: t=…,v1=…

{
  "type": "menu.availability",
  "data": {
    "item": "Jhol Momo",
    "available": false
  }
}

Design preview · not available yet

How it connects

Where outside systems connect

Because the POS, kitchen, stock and guest records are one system, there are few things left to connect. These are the points where outside systems meet it.

Feeds in

Integrations

Where outside systems meet the menu, stock, orders and payments. Today by recorded references and CSV; by API and webhooks later.

Feeds out

Integrations

Partial means it works today with the limit stated. Planned means it is not built yet.

Available
Available
Partial
Partial
Planned
Planned

  • Any acquirer

    Available

    Cards run on your terminal and are recorded with the approval code.

  • Nepal wallets

    Available

    Fonepay, eSewa and Khalti recorded by transaction ID.

  • Khalti, eSewa & Stripe checkout

    Partial

    Guest online payment for QR orders, verified with the provider. Not yet verified against live merchant accounts.

  • Nepal IRD CBMS

    Partial

    Real-time invoice reporting with retry, using the business’s own CBMS credentials. Awaiting validation with IRD.

  • Fonepay dynamic QR

    Planned

    A QR per bill, confirmed by callback instead of a typed reference. Needs a partner agreement with Fonepay.

  • Any browser device

    Available

    No proprietary terminal or screen to buy.

  • Thermal printers

    Partial

    Network, USB and Bluetooth printers and routes are modelled. The ESC/POS driver is pending, so receipts use browser print for now.

  • CSV export

    Available

    Every report, for your accountant or a spreadsheet.

  • Accounting sync

    Planned

    Journal export to Xero, QuickBooks and Tally-compatible formats.

  • Delivery aggregators

    Planned

    Inbound orders and menu/86 push where APIs exist.

  • Public API

    Planned

    Scoped keys. The current REST API is internal and staff-authenticated.

  • Webhooks

    Planned

    Signed events for orders, menu, stock and payments.

  • CSV import

    Planned

    Bring your menu, guests and ingredients across in one go.

  • Time clock & payroll

    Planned

    Not built, and no payroll integrations yet.

Integration questions

Do you integrate with Foodmandu or Pathao Food?
Not yet. We found no public POS integration API for either. Today their orders are keyed in as delivery orders. An adapter is planned wherever an API becomes available.
Can I keep my current card terminal?
Yes. DataRestro records the payment and your terminal processes it. You can change card provider whenever you like.
Is there a public API?
Not yet. The REST API is used by our own apps and signs in with staff accounts. Scoped API keys and signed webhooks are planned.
What printers work?
Anything your browser can print to works for receipts today. Direct ESC/POS printing to network, USB and Bluetooth thermal printers is being built. The printer and kitchen-routing setup is already in the product.

Try the demo

A sample restaurant in your browser. Take an order, send it to the kitchen, mark it ready and take payment. No account needed.

Try the live demoGet started
Next featureRunPOSCounter and table orders, bills, payments and cash shifts. Keeps taking orders offline.