Why Apron

Built around the service, not just the bill.

The bill is only the last step of a service. Apron is built around all of it: the table, the kitchen, the counter and the count at the end of the shift. When those steps are connected, the whole service runs more smoothly.

01 · Connected handoffs

The kitchen knows the moment the floor does.

When a captain sends an order, each dish's KOT lands on the screen of the station that cooks it. Notes, variants and allergens travel with it, so everyone works from the same order.

In the product: station routing on the kitchen display, with rush, re-fire and overdue tickets highlighted.

Apron's kitchen display: tickets for the main kitchen, beverages and dosa counter, each with its station, age and allergens.

02 · Honest numbers

Nothing is settled before it is.

UPI and card payments recorded by staff stay unverified until they match the bank or terminal settlement. Cashiers count the drawer before they see what the system expects, and variances over the limit need approval.

In the product: payment reconciliation, blind drawer counts and variance approvals.

Reconciling a UPI payment of ₹441.00 in Apron: marked as found in the bank, with the statement line and a note.

03 · Screens for a busy service

Each screen does one job, clearly.

The POS takes orders. The kitchen display cooks them, readable from two metres away. The shift screen counts the drawer. On a phone, the POS fits a captain's hand. The floor and kitchen screens also work in Kannada and Hindi.

In the product: POS, kitchen display, menu, tables, orders and guest QR menu in English, Kannada and Hindi.

Apron's POS on a captain's phone at table T12.

Apron's guest QR menu on a phone, with dish drawings, veg marks and prices.

04 · Visibility

See the day, and what needs you.

The dashboard shows what was billed, what was collected and what needs attention. Suggestions come from rule-based analysis of your own sales, stock and recipes, and nothing changes until you approve it.

In the product: the dashboard, reports with Excel export, and suggestions you can check.

A suggestion on Apron's dashboard: wastage up this week compared with the previous week, with Dismiss and Acknowledge.

05 · Accountability

Who did what, and when.

Price changes, discounts, voids and refunds go to the audit log with the person and the time. Exceptions like a discount over the limit or a cancellation need a manager's PIN, so the record shows who approved it.

In the product: the audit log and manager PIN approvals.

Apron's audit log: today's payment, discount, PIN override and item cancellation events with who and when.

Made for India

Made for how Indian restaurants work.

GST on every bill

CGST and SGST per line, tax-inclusive or not, round-off, service and packaging charges, and numbered credit notes for refunds.

Invoice series

Invoices numbered per outlet, per financial year.

UPI, card and cash

Part payments and equal splits, with UPI matched to the bank.

Your team's language

English, Kannada and Hindi on the floor and kitchen screens and the guest QR menu.

Hosted in India

The service runs on servers in Amazon Web Services' Mumbai region.

Devices you already have

Any current browser on a PC, tablet or phone.

Your data

Your restaurant's data stays your restaurant's.

Separated per businessEvery restaurant's data is kept apart from every other's.
Roles and permissionsRole templates and custom roles decide who can see and do what.
Two-factor sign-inAvailable for every account. Passwords and PINs are stored only as hashes.
An audit logSensitive actions are recorded with who did them, and when.

Good service should feel this connected.

Book a demo Explore the product