Why restaurants must own their customer data

Ask most restaurant owners who their customers are, and you’ll get a warm, human answer: the couple who come in every Friday, the office crowd that clears out the lunch counter, the family that always orders the same biryani. Ask them for those customers’ phone numbers, order histories, or last visit dates, and the answer changes. They don’t have them. Someone else does.

That someone is usually a delivery marketplace. And it is the single most expensive fact in the restaurant business.

The relationship you’re actually renting

When an order comes through an aggregator, the restaurant does the hard part. It sources the ingredients, staffs the kitchen, cooks the food, and packs it well enough to survive a delivery ride. In exchange, it pays 20–30% commission — and gets an order. What it does not get is the customer.

The name, the phone number, the delivery address, the order history, the frequency, the preferences — all of it stays with the platform. The restaurant is a fulfillment vendor for a relationship it will never see. Worse, the platform then uses that data to advertise competing restaurants to the very customer the kitchen just fed. You paid a commission to acquire a customer, and the acquisition went to someone else.

This is the difference between revenue and ownership. A marketplace order is revenue today. A customer you can reach directly is revenue for years.

Why first-party data is the asset

First-party data — information a customer gives you directly, with consent — is the foundation of every durable customer relationship. For a restaurant, it means knowing:

• Who your customers are (phone-first identity, no login required)
• What they order (favorite dishes, dietary preferences, average order value)
• When they visit (frequency, last order date, day-part patterns)
• How much they’re worth (lifetime value, not just this ticket)

With that, you can do things a marketplace will never let you do. You can send a reorder reminder featuring someone’s usual order after two quiet weeks. You can wish a regular a happy birthday with a coupon. You can notice that a weekly customer hasn’t been in for a month and win them back before they’re gone for good. None of this is possible when the data lives on someone else’s server.

There’s a regulatory tailwind here, too. India’s Digital Personal Data Protection (DPDP) Act and Europe’s GDPR are pushing the whole economy toward explicit consent and first-party relationships. Businesses that already collect data properly — with opt-in, a consent ledger, and honest data practices — are ahead of the curve. Those relying on third-party data brokers are increasingly exposed.

The repeat-customer math

Here’s the part owners underrate. A repeat customer is worth far more than a new one — not by a little, but by a multiple. New-customer acquisition is expensive and getting more so; retaining an existing customer costs a fraction and compounds over time. Every study of restaurant economics lands in the same place: the second visit is where profit lives, and the fifth visit is where loyalty does.

But you cannot drive a repeat visit if you can’t reach the customer. Repeat business isn’t a happy accident; it’s the result of a message sent at the right moment to someone you can identify. No data, no repeat lever. It’s that simple.

What owning your data actually looks like

Owning your customer data doesn’t require a data science team. It requires a channel where every interaction builds a profile you control. WhatsApp is that channel for most restaurants: customers already use it, no app download is needed, and every conversation can — with consent — enrich a first-party CRM record that belongs to the restaurant.

The practical starting point is small:

1. Give every order a front door you own. A QR code on the table, the counter, and the packaging that opens a WhatsApp conversation. Now the first order creates a profile instead of vanishing into an aggregator.
2. Capture consent once, honestly. A clear opt-in at the first message, stored in a consent ledger. This is both good ethics and good compliance.
3. Let the profile build itself. Every order, reservation, and feedback response lands on one timeline automatically — no data entry.
4. Use it to bring people back. Reorder nudges, birthday offers, win-back campaigns. The data only matters when it drives a message that drives a visit.

The bottom line

Delivery apps solved discovery, and for that they earned a place. But discovery is a one-time service, and they’re charging you rent on it forever — while keeping the asset that would let you stop paying. The restaurants that will thrive over the next decade are the ones that treat their customer relationships as something to own, not rent.

You already earned those customers. The only question is whether you get to keep them.