Custom Domain for Restaurant Chains: Ordering at Your Own Web Address

Running restaurant ordering on an own-domain address means your customers order at order.yourbrand.in instead of at a platform link, and for a chain it means one address for every branch. The customer types the name they know, enters their address, and the order goes to the nearest outlet. The menu, the zones, the payments and the dashboard are the same Tezzu store underneath; only the address on the door changes.

This post is for owners of a brand with two or more outlets. It covers why the domain matters more for a chain than for a single shop, how one domain serves every branch, which address to pick, the DNS step, what happens at payment on a custom domain, and how to roll the new link out across outlets without breaking anything already printed.

Why a chain should take orders at its own address

A single restaurant can live with a platform link. A chain cannot, for three reasons.

Print. A chain prints the ordering link on menus, table cards, packaging stickers and shop boards across every outlet. A short address with the brand name in it, order.yourbrand.in, is what staff can say aloud and customers can remember. A long platform address is neither.

Ownership. The domain belongs to you. If the brand ever changes tools, the printed links keep working because the name moves with you. Over a five-year horizon with ten outlets' worth of print, that matters.

One link for everything. Without a shared domain, chains end up with a different link per branch, and customers save the wrong one. A customer who moves from Indiranagar to Whitefield keeps ordering from the Indiranagar link, the order goes to the wrong kitchen, and someone has to call. One brand address with routing behind it removes that whole category of problem.

One domain, many branches: what happens behind the address

Here is the flow when a customer opens order.yourbrand.in in a city where you have three outlets.

1. The store page opens with the brand's menu, photos and promo banners.
2. The customer enters a delivery address, or shares a location pin if they came in through WhatsApp.
3. Tezzu checks which outlets have a delivery zone covering that address and picks the nearest.
4. The customer sees that outlet's prices, delivery charge and minimum order before confirming. The confirmation names the outlet.
5. The order lands in that outlet's dashboard and staff app. Other outlets never see it.

The domain is the front door; nearest-outlet routing is what happens inside. The routing itself, including overlapping zones and what happens to an address outside every zone, is covered in nearest-outlet routing for biryani chains. The master menu with outlet-level prices, so the same item can cost ₹260 in the old city and ₹290 in the IT park, is in managing multiple outlets on one WhatsApp number.

Which address to use

You own a domain or will buy one. A .in or .com domain typically costs a few hundred to a little over a thousand rupees a year. Then decide where the store lives.

For most chains the subdomain is right, because a chain usually has a brochure site with outlet addresses and a careers page at the root. Keep the address short, lower case, with no hyphens, and use the same one on every outlet's print.

Connecting the domain: the steps

1. Finish the store first. Master menu entered, every outlet added with its zones and hours, payments active. A domain in front of an empty store helps nobody.
2. In the Tezzu dashboard store settings, enter the exact address you will use. The dashboard shows the DNS record to create.
3. At your domain registrar, open DNS settings and add that record exactly as shown. For a subdomain this is one record. Get the registrar login now if a web designer holds it; this is the step that stalls most setups.
4. Wait. DNS changes take from minutes to a few hours to spread. The dashboard shows the domain as pending until it sees the record, then active.
5. Open the store on a phone on mobile data, not shop Wi-Fi, confirm it loads securely at your address, and place a full test order from an address in each outlet's zone.

The old tezzu.in/store address keeps working alongside the domain, so nothing already printed breaks. The single-outlet version of this setup, with the registrar screens described, is in custom domain for your ordering store.

What happens at payment on your own domain

This is the one part that surprises people, so it is worth understanding before you go live. Razorpay's risk checks block a payment window opened from a website that is not registered on the Razorpay account whose key opened it. Tezzu's store on tezzu.in is registered; your domain is not, because it is yours.

So on a custom domain with the default payment setup, when the customer reaches payment, Tezzu opens the payment page at tezzu.in/pay for that order, the customer pays by UPI or card there, and is sent back to your domain with the order confirmed. The hand-off link is tied to that one order and expires after a short window. Confirmation does not depend on the customer coming back; Razorpay tells Tezzu the payment succeeded, and the order is confirmed on WhatsApp either way. Cash on delivery orders are not affected at all.

If you want the entire flow to stay on your domain, connect your own Razorpay account. Then the key is yours, your domain is registered on your account, and checkout runs on your address with no hand-off. For a chain this is often the right choice anyway, because it also removes the platform fee on online payments; the trade-offs are in bring your own Razorpay.

What this looks like on Tezzu

In the dashboard, the custom domain lives in the brand's store settings: the address you entered, the DNS record to add, and a status that moves from pending to active. It is set once for the brand, not per outlet. Everything else in the dashboard is unchanged: the store switcher at the top still moves you between outlets, each outlet still has its own orders, zones, prices, staff and earnings, and the master menu is still edited at brand level.

For the customer, your domain opens the storefront with your logo, banner and promo banners, the menu with photos, and the delivery, pickup or dine-in choice. When they enter an address, the quote they see is from the outlet that will cook the order: that outlet's prices, delivery charge by zone, and free-delivery threshold. Pickup shows your outlets as collection points with a collection time. At payment, the hand-off described above runs, or checkout stays on your domain if you have connected your own Razorpay account.

Orders arrive in the right outlet's live dashboard and staff app, with the usual alerts and spoken announcements, and KOTs print in the right kitchen. WhatsApp confirmations and status updates still come from the one brand number. Campaigns sent from that number can carry the domain as the order link, so every offer points customers at the same address. Which plans include custom domains and multi-outlet is on the pricing page, and the complete list of what the storefront does is on the features page.

Rolling the link out across outlets

Once the domain is active, change the link everywhere, in this order. The Instagram bio and any pinned posts. The order button on each outlet's Google Business Profile, which is where the branch-level "order online" clicks come from. The WhatsApp business profile. Templates for campaigns. Then print: new table cards, packaging stickers and shop boards on the next run, with one QR code that opens the domain. Old QR codes keep working, so there is no rush to pull them.

Give outlet managers the same one-line answer for customers who ask where to order: the domain, spoken the same way at every branch. A week after go-live, search the brand name and check that the domain shows up; if a site builder or a directory still shows an old link, fix it there. How those buttons are usually configured is covered in restaurant website builders with ordering built in.

Frequently asked questions

Can a restaurant chain use one website address for ordering at all branches?

Yes. On Tezzu, a brand connects one custom domain to its store, and nearest-outlet routing decides which branch cooks each order from the customer's address or location pin. The customer sees one brand and one link; each outlet sees only its own orders. Pickup customers choose the outlet they want to collect from.

Do I need a developer to put ordering on my own domain?

No. You need a domain you own, access to its DNS settings at the registrar, and a finished store. You enter the address in the dashboard, add one DNS record exactly as shown, and wait for it to resolve. The registrar login is the only thing that usually needs chasing, if someone else bought the domain for you.

Why does payment on my custom domain open a tezzu.in page?

Because Razorpay only allows its payment window on websites registered to the account whose key opened it, and your domain is registered to you, not to Tezzu. So the default setup hands the customer to tezzu.in/pay for that one order and returns them with it confirmed. Connect your own Razorpay account and checkout stays entirely on your domain.

Does a custom domain change how orders reach the kitchen?

No. Orders from the domain appear in the same live dashboard and staff app as orders from WhatsApp or the tezzu.in link, routed to the nearest outlet in the same way, with the same alerts, status updates and KOT printing. The domain changes the address customers see and nothing about how the outlets run.