Choose an ordering URL that guests can recognize, your staff can update, and your restaurant can keep using if you change ordering providers. A branded address under a domain you control may give you more control over the link. A provider-hosted address may be simpler to launch, but you need to understand what happens to it when the relationship ends.
Before deciding, ask both your website manager and ordering provider how the address connects to the ordering page. The decision is not just about buying a domain. It is about who controls the ordering endpoint, where guests land, and how that handoff can be changed later.
Compare branded and provider-hosted links
A branded ordering address might look like order.example.com, using a subdomain of the restaurant's domain. A provider-hosted address might look like provider.example/restaurant. These are hypothetical formats, not addresses for real services.
With the branded option, the restaurant can keep the same guest-facing address while changing where it points, provided the new provider supports the necessary setup. That does not mean a move will be automatic: the new provider must accept the address, and someone must make and check the configuration changes.
A provider-hosted link can be useful when the restaurant wants fewer domain setup steps. Ask whether the address includes your restaurant name, whether it can change, and whether it remains available after cancellation. If the provider controls the address, your ability to send it somewhere else may be limited.
Start with these inputs:
- Restaurant owner: Which name should appear on menus, receipts, signs, and public profiles? Who should approve changes?
- Domain or website manager: Who has the domain account and the ability to change its settings? Is there already an ordering subdomain?
- Ordering provider: Does the service support your preferred address? What setup, recurring, or change fees apply?
- Front-of-house and marketing staff: Where is the current link printed or published, and who can update each location?
For a restaurant with an established domain and access to its settings, a supported branded subdomain is often worth considering because the restaurant can retain the address. For an owner who needs a quick launch and has no one available to manage domain settings, a provider-hosted link may be a reasonable starting point. Record the places it appears so a later move is manageable.
The address is only one part of the purchase. Use the online ordering buying guide to compare the ordering workflow and other operating needs as well.
Check control, certificates, and portability
Ownership has several layers. Your restaurant may own its domain but still rely on a provider to operate the ordering page. A web agency may have built the site yet hold the account credentials. Get the details in writing rather than assuming that a branded-looking address is under your control.
Use this worksheet in a provider conversation. The third column describes the decision or evidence to seek; it is not a promise that every provider offers that arrangement.
| Item | Question to ask | Useful answer to record |
|---|---|---|
| Domain account | Who is the account holder and who can renew it? | Restaurant-controlled account, renewal contact, and recovery method |
| Ordering address | Who can change where the link points? | Named person or company with access and an approval process |
| Secure connection | Who supplies and renews the HTTPS certificate? | Responsible party, renewal process, and support contact |
| Exit | What happens to the link and ordering data after cancellation? | Written end date, available exports, and any transition charges |
The domain account and its settings are not always in the same place. Ask for the account names and authorized contacts for both. Keep credentials in the restaurant's approved password manager, not in an employee's personal inbox. If an agency manages access, agree on how the restaurant can regain control if that relationship ends.
HTTPS is the secure connection indicated by the lock or security information in a browser. Ask who sets up the certificate for the ordering address, who renews it, and what happens if renewal fails. Also ask whether the provider needs access to your domain settings or can give your manager instructions instead.
Portability has two separate parts: keeping the address and moving the operation behind it. Keeping a branded URL does not automatically transfer menu items, guest records, order history, payment settings, or integrations. Ask what can be exported, in what format, and whether the next provider can use those files. Have a qualified adviser review contract terms if ownership or termination language is unclear.
Check the path from public links to checkout
A clear address is useful only if guests reach the right ordering page. List every place the link appears: the order button on your restaurant website, public business profiles, social accounts, email templates, QR codes, printed menus, and signs. Include links held by an outside agency or printing company.
Hypothetical example: A neighborhood restaurant uses a branded order link on its website and a provider-hosted link in its public business profile. Both currently lead to the same ordering page. The owner wants to keep the branded link for a future provider change.
The owner can first check the website button and profile link on a phone and a desktop browser. For each path, note the address shown, whether the correct restaurant and location appear, and whether pickup or delivery choices match the intended service. If the page sends guests elsewhere, record the final destination as well as the original link.
Then ask the provider for a safe practice environment or a way to check the remaining steps without placing a live order. A simulation must not charge a card, send a guest message, or dispatch a courier. Check the menu, location, fulfillment choice, and displayed totals up to the point the practice setup allows. Do not enter real payment details or submit a live order as a practice check.
A simulation cannot prove that live payments or order notifications will work during service. If a live pilot is needed, agree on its scope with the provider and staff in advance, including how a real order will be identified and handled. Check each public link again after the change; updating the website button does not update an old QR code or a profile link.
Document the migration before you need it
A move is easier when the restaurant has a short handoff record before giving notice to an existing provider. Keep the record somewhere the owner and an authorized backup can reach. It should cover the address, accounts, contacts, and public links, but it should not contain passwords in plain text.
- Inventory the current path. Record the ordering URL, where it points, who operates the page, and every public placement. Include printed materials that cannot be edited remotely.
- Confirm control. Identify who can access the domain account, change its settings, renew the certificate, and approve updates. Verify the backup contact with each party.
- Agree on the new setup. Ask the incoming provider whether it supports the existing branded address, what configuration it requires, and who will perform each step. Obtain written setup and transition quotes.
- Plan the handoff. Agree on a change window, support contacts, a way to check the new destination, and a fallback if something is wrong. Do not assume the old provider's address can be redirected after cancellation.
- Update and recheck placements. Change editable links and arrange replacements for printed codes. Monitor for reports of broken links or orders reaching the wrong destination, and assign someone to resolve them.
- Close the old account deliberately. Confirm the end date, retrieve agreed exports, and understand when access to the old page and records ends.
Ask for an operational quote that separates one-time setup and change fees from recurring charges, and identifies any transition or early-exit fees. Also ask what support is included if a link or certificate fails. A lower setup quote may not be the better choice if the restaurant cannot control the address or get help during a change.
No handoff plan can guarantee uninterrupted service or that no order will be missed. The practical goal is to make responsibilities visible, reduce avoidable confusion, and give staff a clear response if a guest reaches an old or unavailable page.
Use the worksheet to review your current setup, then ask Fleksa about restaurant online ordering, whether your preferred URL arrangement is supported, and current availability for your US location.
Frequently asked questions
Should the ordering link use my restaurant's domain?
A branded subdomain can help guests recognize the address and may give you more control over where it points. Confirm that your ordering provider supports it and that the restaurant controls the domain settings.
Can I keep my ordering URL when I switch providers?
Possibly. A restaurant-controlled branded address may be usable with a new provider if that provider supports the setup. A provider-hosted address may remain under the old provider's control. Confirm both arrangements before making a change.
Does moving the link also move my menu and customer data?
No. The address and the information behind it are separate. Ask the current provider what it can export and the incoming provider what it can import, including any fees and limits.
