A list that builds itself
No import, no data entry, no nightly spreadsheet ritual. Each order adds to the customer's record, and the list is sorted by what matters — how often they order and how much they have spent — so the regulars surface on their own.
What you get from it
Visits, lifetime spend and average order value per customer, built from real orders rather than a loyalty card nobody stamps.
A call comes in and the number is recognised: search by phone or name and see what they usually order.
Open a customer to see their orders — useful when a regular asks what they had last time, or when a complaint needs context.
The filtered list downloads as CSV for accounts, a festival message list, or any tool that is not this one.
Each customer's promotional consent is stored with them, and campaigns only message those who opted in.
Contact details sit behind sign-in, apart from the order data a QR menu needs. See privacy for the data flows.
From list to repeat visits
QR table orders, phone and WhatsApp orders all record the customer the same way — no extra step for staff.
Sort by orders or spend. The top of that list is the audience a win-back or a new-menu announcement should start with.
First-order offers, coupons and the occasional campaign — built in the same dashboard that sees the orders.
Repeat visits show up in reports as orders and average ticket, not as "messages sent".
Coupons are created in the discount engine the POS uses, so a code in a message is a code the counter accepts.
Customer book vs a phone full of contacts
| Contacts app / notebook | FoodHubbie customer book | |
|---|---|---|
| Entered how | Manually, if at all | Automatically, from orders |
| Order history | Not available | Every order, per customer |
| Spend and visits | Unknown | Lifetime totals, average ticket |
| Consent for offers | Assumed | Recorded per customer |
| Who can read it | Whoever holds the phone | Signed-in staff only |
Customer database questions, answered plainly
Do I have to import my customer list?
No. The book builds itself from orders — each order records the phone, name and amount, and repeat orders are grouped under the same customer with a running visit count and lifetime spend. An existing list can be exported, but a fresh outlet needs no import to start.
What can I see about a customer?
Number of orders, lifetime spend, average order value and the order history, reached from the customer's row. Search works by name or phone number.
Is there a loyalty points system?
No. There are no points or wallet balances. Repeat business is encouraged with first-order offers, coupons and win-back campaigns instead, and each customer records whether they agreed to promotional messages.
Who can see phone numbers?
Only signed-in staff of the outlet. Customer contact details are stored separately from publicly readable order and table data, so a QR menu visitor cannot read the customer book.
Turn orders into regulars
The customer book is included; campaigns cost ₹1 a message. See pricing.
Start free trial → WhatsApp us