01
One menu
Website and table show the same dish and the same sold-out.
ONE TOUCH TECHNOLOGY SOLUTIONS
Proposal · September 2026 · Not a quotation
Scan the code on the table. Order. Pay. Leave a review. One screen, and the operating platform behind it.
01
The code already knows this table.
02
The priced card, add-ons included.
03
The same list, as a station ticket.
04
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
One menu. One order. One bill. The kitchen cooks what the guest tapped.
01
Website and table show the same dish and the same sold-out.
02
Scan opens this table. Not a list of cafes.
03
Pay, kitchen, and status stay on that order.
04
Tax, discount, and refund need a reason and a permission.
05
The ticket goes to the station that cooks it.
06
Only after recipes exist. Until then it stays manual.
02 · Lost sales
Nothing here is theft or laziness. It is a spoken menu shedding a little of every order.
Leaks out
Reaches the bill
01
Guests order what they heard. The second samosa never comes up.
02
Each handoff drops an add-on. The kitchen should cook the tap.
03
The food is done. The seat earns nothing until the bill arrives.
04
They will tap once on the receipt. They will not hunt from the car.
05
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
Four taps for the guest. One record for the cafe.
The table is the link
The code already knows this table.
The full menu
Prices, add-ons, and what is sold out.
UPI, card, or wallet
They pay on the same screen. We do not store card numbers.
Still at the table
5 stars can go to Google. Then the cafe’s scratch card.
In the room

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

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

03
The chef cooks the tap. Not a shout.

04
Then one question about the food.
On the guest’s phone
01
The cafe’s card opens on the table. No waiting to be noticed.
02
Add-ons are priced on the screen, so the bill holds no surprises.
03
The kitchen accepted the ticket. The table can see where it is.
04
One screen for payment. Then one question about the food.
Table 07 · Dine-in
A Jaipur table
Sample. Tax extra. The kitchen gets this list.
Grill · KOT 1842
Table 07
Same order. Cold coffee goes to the bar ticket.
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
The code knows this table.
Chai, pav, samosa. Price included.
The same list, as a station ticket.
UPI, card, or wallet, on the phone.
A public review, on Google.
The cafe’s offer. This meal, or the next.
Sketch · the rating
Five
Only a full five. Lower scores stay private, with the manager.
Maps
A public star is how the next guest chooses where to sit.
Room
The review does the inviting. The QR takes the order.
Back
A free chai or a rupee-off, set by the cafe.
The cafe loads the card
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
01
Menu, add-ons, pay, review.
02
Those same items, as a ticket.
03
Tax and payment. Not a second list.
04
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

“Second kulhad, still hot. I did not have to catch anyone’s eye.”
Kulhad masala chai
Sample. Not a real review.

“Two samosas and the green chutney. We paid before we stood up.”
Samosa, mint chutney
Sample. Not a real review.

“Extra butter, extra onion. It arrived the way we ticked it.”
Pav bhaji
Sample. Not a real review.

“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.

“One biryani for the table. One order. One bill. Nobody retyped it.”
Chicken biryani
Sample. Not a real review.

“The review sat on the receipt, not on a sticker by the door.”
Cappuccino
Sample. Not a real review.
04 · The system
The website, the guest’s phone, and the staff screens read the same menu and write to the same order.

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

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

Staff
The same order. Nobody types it again.
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.

05 · Money
Each one is small. None of them needs a new guest walking through the door.
+16%
On the orders that move to QR.
+8%
Only if the room is already full.
1.8%
Charged what the kitchen sent.
Month 3
Not counted in the first two months.
Sketch · the month
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
With the QR
01
The extra chai and the chutney are on the screen, so more people take them.
02
They order and pay without waiting. Extra turns count only if the room is full.
03
What left the kitchen is what was charged.
04
Asked on the receipt. Counted from month three, not from day one.
05
Waiters stop being a walking menu.
06
Same system. New outlet. Not a second set of books.
06 · 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.
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 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.
Twelve months
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.
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
Guests can order while recipes are still being written. Stock waits for real recipes.
Start at 00 · stock waits for 03
00
Menu, tables, tax, and who can refund. Then a price. This page is not a quote.
01
Menu, QR, order, pay, review, and a kitchen ticket.
02
Bills, discounts, receipts, and refunds on that same order.
03
Not before. A stock screen without recipes is fiction.
04
A second outlet on the same system. An app only if you want one.
The guest loop
Start here
When recipes are real
Done means a stranger can order, the kitchen can cook it, and the bill matches.
08 · Contact
Tables, food orders, stock, and payments. That is the work behind this proposal.
Bring these
Sales
Lashika Kaushik
Sales Director
One Touch Technology Solutions
+91 95213 33881sales@onetouchsoft.comWeb
onetouchsoft.comLinkedIn, Instagram, and Facebook are on the site.
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