Skip to the brief

ONE TOUCH TECHNOLOGY SOLUTIONS

Proposal · September 2026 · Not a quotation

QR ordering for the F&B floor

Scan the code on the table. Order. Pay. Leave a review. One screen, and the operating platform behind it.

  1. 01

    Scan

    The code already knows this table.

  2. 02

    Order

    The priced card, add-ons included.

  3. 03

    Kitchen

    The same list, as a station ticket.

  4. 04

    Pay · Review

    One screen. Then one question.

If the room is full

24.3%

Extra sales in a busy month. About ₹39.6 L in year one.

If seats stay empty

15.5%

Same cafe, no extra turns. About ₹24.6 L in year one.

The example

One cafe, 140 covers, ₹420, 26 days. Change every figure in Numbers.

Not a price. Not a promise of extra sales.

01 · Why

No waving. Just the menu.

One menu. One order. One bill. The kitchen cooks what the guest tapped.

01

One menu

Website and table show the same dish and the same sold-out.

02

The code knows the seat

Scan opens this table. Not a list of cafes.

03

One order

Pay, kitchen, and status stay on that order.

04

A real bill

Tax, discount, and refund need a reason and a permission.

05

Kitchen stations

The ticket goes to the station that cooks it.

06

Stock later

Only after recipes exist. Until then it stays manual.

02 · Lost sales

Where a full cafe still loses money.

Nothing here is theft or laziness. It is a spoken menu shedding a little of every order.

What the table would buyWhat the menu said out loudWhat the kitchen was toldWhat the bill listedPaid

Leaks out

Reaches the bill

  1. 01

    The menu is spoken.

    Guests order what they heard. The second samosa never comes up.

  2. 02

    The order is rewritten.

    Each handoff drops an add-on. The kitchen should cook the tap.

  3. 03

    The table waits to pay.

    The food is done. The seat earns nothing until the bill arrives.

  4. 04

    Nobody asks for a review.

    They will tap once on the receipt. They will not hunt from the car.

  5. 05

    A busy day is not closed.

    Discounts, refunds, and stock need one record. Or the morning is a guess.

The second samosa is the sale a spoken menu forgets.

03 · The visit

Scan. Order. Pay. Review.

Four taps for the guest. One record for the cafe.

  1. 01

    Scan

    The table is the link

    The code already knows this table.

  2. 02

    Order

    The full menu

    Prices, add-ons, and what is sold out.

  3. 03

    Pay

    UPI, card, or wallet

    They pay on the same screen. We do not store card numbers.

  4. 04

    Review

    Still at the table

    5 stars can go to Google. Then the cafe’s scratch card.

In the room

The same four taps, on the floor.

  1. A guest at a cafe table, his phone beside his hand.

    01

    Point the phone

    Opens this cafe’s menu. No waiting to be noticed.

  2. A shared Indian plate of pakora, butter naan, and bowls of gravy.

    02

    Tap the food

    The price on the screen is the price on the bill.

  3. An Indian chef in a restaurant kitchen.

    03

    Kitchen gets a ticket

    The chef cooks the tap. Not a shout.

  4. An iced coffee and a phone sitting together on a cafe table.

    04

    Pay, then review

    Then one question about the food.

On the guest’s phone

Four screens. The whole visit.

  1. 01

    Point the phone

    The cafe’s card opens on the table. No waiting to be noticed.

  2. 02

    Tap the food

    Add-ons are priced on the screen, so the bill holds no surprises.

  3. 03

    Watch it cook

    The kitchen accepted the ticket. The table can see where it is.

  4. 04

    Pay, then review

    One screen for payment. Then one question about the food.

Table 07 · Dine-in

A Jaipur table

  • Masala chai₹60
  • Cold coffee₹160
  • Pav bhaji₹180
  • Samosa plate₹90
Items
₹510
CGST 2.5%
₹13
SGST 2.5%
₹13
To pay
₹536

Sample. Tax extra. The kitchen gets this list.

Grill · KOT 1842

Table 07

  • Pav bhaji
  • Samosa · mint chutney
  • Masala chai

Same order. Cold coffee goes to the bar ticket.

Start86 item

Paid · Table 07

How was it?

Tap the stars. Five opens the Google card.

Tap the add-ons. Tap 5 stars for the Google card.

Sketch · the system

How one visit runs.

  1. 01

    Scan

    The code knows this table.

  2. 02

    Order

    Chai, pav, samosa. Price included.

  3. 03

    Kitchen

    The same list, as a station ticket.

  4. 04

    Pay

    UPI, card, or wallet, on the phone.

  5. 05

    Five stars

    A public review, on Google.

  6. 06

    Scratch

    The cafe’s offer. This meal, or the next.

Sketch · the rating

How five public stars help the cafe.

  1. Five

    They say it on Google

    Only a full five. Lower scores stay private, with the manager.

  2. Maps

    New people find the cafe

    A public star is how the next guest chooses where to sit.

  3. Room

    More tables fill

    The review does the inviting. The QR takes the order.

  4. Back

    The card brings them again

    A free chai or a rupee-off, set by the cafe.

The cafe loads the card

  • This meal · ₹40 off the bill
  • Next visit · free kulhad chai

Examples only. The manager turns prizes on or off.

Who gets one

A public 5-star Google review. Four stars and below stay with the manager.

The discount is the cafe’s cost, paid to earn the public star.

One order, four desks

  1. 01

    The phone

    Menu, add-ons, pay, review.

  2. 02

    The kitchen

    Those same items, as a ticket.

  3. 03

    The bill

    Tax and payment. Not a second list.

  4. 04

    The morning

    That order is already in the books.

Nothing is copied by hand between these four. That is the product, in one line.

What the review is about

What they review.

  • Clay cups of masala chai on a tray.
    “Second kulhad, still hot. I did not have to catch anyone’s eye.”

    Kulhad masala chai

    Sample. Not a real review.

  • A basket of samosas with lemon, chutney, and glasses of chai.
    “Two samosas and the green chutney. We paid before we stood up.”

    Samosa, mint chutney

    Sample. Not a real review.

  • Pav bhaji with buttered pav, onion, coriander, and lime.
    “Extra butter, extra onion. It arrived the way we ticked it.”

    Pav bhaji

    Sample. Not a real review.

  • Two masala dosas on a banana leaf with chutneys and podi.
    “Dosa, podi, and both chutneys. The chutney was a choice on the card, not a surprise at the table.”

    Masala dosa

    Sample. Not a real review.

  • Chicken biryani on a plate with raita and a red chutney.
    “One biryani for the table. One order. One bill. Nobody retyped it.”

    Chicken biryani

    Sample. Not a real review.

  • A barista pouring latte art into a cup of coffee.
    “The review sat on the receipt, not on a sticker by the door.”

    Cappuccino

    Sample. Not a real review.

04 · The system

One menu. Three places.

The website, the guest’s phone, and the staff screens read the same menu and write to the same order.

A cafe interior with wooden tables and the service counter.

Website

The cafe online

Menu, locations, offers. Same prices as the table.

A guest at a cafe table, his phone beside his hand.

Guest phone

The table

Scan, order, pay, review. No app to install.

An Indian chef in a restaurant kitchen.

Staff

Kitchen and counter

The same order. Nobody types it again.

Who can touch it

  • Owner

    Settings and reports.

  • Manager

    The day’s floor.

  • Cashier

    Bills, discounts, refunds.

  • Floor

    Tables and service.

  • Kitchen

    Tickets and sold-out.

  • Store

    Purchases and waste.

  • Finance

    Tax, payments, refunds.

  • Guest

    Menu, order, pay.

  • Admin

    Access and setup.

What happens, in order

  1. 01Scan knows the cafe and the table.
  2. 02Guest picks food, add-ons, and notes.
  3. 03Price and sold-out are checked. The order exists once.
  4. 04They pay the way you set.
  5. 05Kitchen and counter get the same ticket.
  6. 06Status updates. The table closes when you say so.
A man working on a laptop.
The day should already be a record — not something the office reconstructs the next morning.

05 · Money

Four ways the bill grows.

Each one is small. None of them needs a new guest walking through the door.

  1. +16%

    Bigger orders

    On the orders that move to QR.

  2. +8%

    More turns

    Only if the room is already full.

  3. 1.8%

    Bills that match

    Charged what the kitchen sent.

  4. Month 3

    Reviews

    Not counted in the first two months.

Sketch · the month

The business you have, and the slice the table adds.

  • Larger tickets₹1,58,995
  • Extra turns₹1,35,024
  • Reviews₹50,634
  • Recovered billing₹27,518

One cafe, 140 covers a day, a ₹420 average bill, 26 open days — month twelve, with the room full. The base column is the business you already have: ₹15,28,800 a month. Change any of it in Numbers.

Today

  1. 01Wait to be noticed
  2. 02Hear a partial menu
  3. 03Order from memory
  4. 04Wait again to be billed
  5. 05Leave without a trace
  6. 06The office reconstructs the day

With the QR

  1. 01Scan a code that knows the seat
  2. 02See the card, including what is out
  3. 03Send a priced ticket
  4. 04Pay when the meal is finished
  5. 05Review on the receipt
  6. 06The day is already the record
  1. 01

    A bigger bill

    The extra chai and the chutney are on the screen, so more people take them.

  2. 02

    A faster table

    They order and pay without waiting. Extra turns count only if the room is full.

  3. 03

    The right bill

    What left the kitchen is what was charged.

  4. 04

    Reviews that arrive

    Asked on the receipt. Counted from month three, not from day one.

  5. 05

    Staff time back

    Waiters stop being a walking menu.

  6. 06

    The next cafe

    Same system. New outlet. Not a second set of books.

06 · Numbers

Try your own numbers.

Move the sliders. Extra turns count only if guests are waiting for a table.

An example, not a forecast. Put in your own cafe. Prices are before GST.

The floor
What the table changes
What you keep
Payback, if you name a cost

Not a price. Pick a cost to see how fast it pays back.

Full room · year 1

₹39.6 L

Extra sales over a baseline of ₹1,83,45,600. Mature month runs 24.3% above today (₹3,72,171 on ₹15,28,800).

Gross profit, year 1
₹28.8 L
Payback
Add a cost to see payback

Gross profit is new sales after food cost, plus recovered billings, plus hours returned, minus a gateway fee only if you switched one on. It is not net profit. Rent, royalty, and depreciation stay where they are.

  • Larger tickets₹1,58,995
  • Extra turns₹1,35,024
  • Reviews, this month₹50,634
  • Recovered billings₹27,518
  • Labor returned₹7,800
  • Gateway fee₹0

Twelve months

Extra sales only, from zero

The cafe you already run is not in this chart. The bars are the lift. Month 1 is 40% adopted. Reviews begin in month 3.

  • Larger tickets
  • Extra turns
  • Reviews
  • Recovered billing
How a month is calculated

Baseline = outlets × covers × average check × open days.

Larger tickets = baseline × QR share × ticket lift × adoption. Extra turns, full-room only = baseline × turn lift × (1 + QR share × ticket lift) × adoption.

Recovered billing = baseline × leakage × adoption, with no food cost deducted. Reviews add covers from month 3 and reach the full rate by month 8.

Gross profit = (tickets + turns + reviews) × (1 − food cost) + recovered billing + hours × loaded rate − gateway fee.

07 · The plan

Table first. Stock later.

Guests can order while recipes are still being written. Stock waits for real recipes.

  1. 00
  2. 01
  3. 02
  4. 03
  5. 04

Start at 00 · stock waits for 03

  1. 00

    A working session

    Menu, tables, tax, and who can refund. Then a price. This page is not a quote.

  2. 01

    The table works

    Menu, QR, order, pay, review, and a kitchen ticket.

  3. 02

    The counter works

    Bills, discounts, receipts, and refunds on that same order.

  4. 03

    Stock, when recipes are real

    Not before. A stock screen without recipes is fiction.

  5. 04

    The next cafe

    A second outlet on the same system. An app only if you want one.

The guest loop

Tableline

  • Public menu and outlet pages
  • Table QR with outlet and seat context
  • Options, notes, sold-out
  • Payment step and receipt
  • Status on the guest’s screen
  • Review after payment
  • 5-star Google review, then a scratch card the cafe fills
  • One menu admin for every channel

Start here

Floorline

  • Everything in Tableline
  • Counter POS and service modes
  • Discounts inside permission
  • Kitchen by preparation station
  • Table status for the floor
  • Refunds with a reason
  • Receipt print or share
  • Cashier, floor, kitchen, manager

When recipes are real

Estateline

  • Everything in Floorline
  • Suppliers and purchase receipts
  • Recipe consumption on a qualifying sale
  • Waste, counts, approved variance
  • Low-stock and availability alerts
  • Reports that reconcile
  • Further outlets on the same configuration

Kept safe

  • Logins expire. Secrets stay stored properly.
  • Card numbers stay with the payment company.
  • Tax inside the price, or added on. Your choice.
  • GST fields for an Indian cafe.
  • Refunds and stock changes leave a record.
  • A double tap does not create two orders.

Not included

  • Delivery drivers and routes
  • Payroll and full accounts
  • Franchise settlements
  • Gift cards and memberships, unless you ask later
  • Writing your menu or typing your daily sales
  • Buying or installing hardware

Done means a stranger can order, the kitchen can cook it, and the bill matches.

08 · Contact

Built in Jaipur.

Tables, food orders, stock, and payments. That is the work behind this proposal.

  • TableTrack. Tables and reservations.
  • MH Food and Made By Maa. Ordering on the phone.
  • KS Mart. Stock and customers.

Bring these

Ninety minutes. Then a price.

  • The menu, with prices
  • How many tables, and when you turn people away
  • Tax inside the price, or added on
  • Who may discount, and who may refund
  • The payment account you already use
Download this proposal

Disclaimer

Every figure in this document is hypothetical and published for reference only. The revenue projections, percentages, rupee amounts, and timelines are illustrative models calculated from the example inputs shown in Numbers — one sample cafe — and not measurements taken from your business. They are not a forecast, an estimate, or a representation of what your cafe will earn or save.

Actual results depend on your menu, pricing, footfall, staffing, payment mix, and local market conditions, and may differ substantially or be negative. Nothing here is a quotation, an offer, a warranty, or a guarantee of performance, and nothing here creates any contractual, financial, or other legal obligation on One Touch Technology Solutions or on the reader. Scope, pricing, and commercial terms are agreed separately in writing.

Dish names, prices, bills, ticket numbers, table numbers, reviews, and reviewer names shown in the screens and graphics are fictional samples used to demonstrate the interface. Any reliance placed on the contents of this document is strictly at the reader’s own risk.

One Touch Technology Solutions · Jaipur · September 2026