Before a new restaurant location page goes public, have a confirmed address, an accurate opening status, a contact method someone monitors, and a clear plan for keeping the page current. Add hours and a menu only when they apply to that location. Link ordering or reservations only when guests can use them for the new restaurant.
A page can be useful before opening day without pretending the doors are already open. The key is to separate what is confirmed from what is still being decided, then give one person responsibility for changing the page as plans firm up.
Confirm opening status and contact facts
Start with the question a guest is most likely to have: Can I visit yet? Put the answer near the top of the page, not only in a footer or a social post. Use a specific status such as “Opening soon,” “Opening October 12,” or “Now open” only when the person managing the launch has approved it.
If the opening date is uncertain, leave out the date rather than publishing a guess. A short note such as “Opening date to be announced” sets a clearer expectation. Avoid taking reservations for a date the team is not ready to honor.
Gather these details from the people who can confirm them:
- Location manager or launch lead: opening status, planned services, and the date each detail was last confirmed.
- Operations lead: street address, suite or unit number, entrance instructions, parking information, and any access notes guests need.
- Customer service or front-of-house lead: the phone number or email address guests should use, who monitors it, and when guests can expect a response.
- Website owner: the person who can make edits, approve publication, and remove an incorrect detail quickly.
Check that a phone number shown before opening actually reaches a useful contact. If the new location's phone is not staffed, a central contact may be more useful, provided the team answering it can handle questions about the new site. Do not list a number simply because it has been assigned.
Make the location easy to distinguish from existing restaurants. Use the neighborhood or city in the page heading, show the full address, and check that directions point to the right entrance. If a map or directions link is present, open it and inspect the destination. For a shopping center, a suite number or a brief entrance note can save guests an unnecessary call.
Also decide who controls the domain and who has access to the website account. A new location often involves several people, and the person who supplied the address may not be the person who can correct it. This guide to restaurant website domain ownership covers questions to ask before handing that control to a provider.
Publish only verified menu and hours
A menu copied from another location can create the wrong expectation. Ask the kitchen and operations teams to approve the items, prices, service periods, and any differences that apply to the new restaurant. If the menu is still being finalized, say so and wait to publish the detailed version. A representative menu should be clearly labeled and should not imply that every item will be available on opening day.
Hours need the same care. Confirm regular hours separately from opening-day hours, soft-opening hours, and special events. If those schedules differ, label the dates they cover. Give an end date for temporary hours or assign someone to remove them as soon as they no longer apply.
Consider this hypothetical example: A restaurant expects to open on a Friday, but the kitchen has approved only a limited opening-week menu. The launch manager confirms that dine-in service will start at 4 p.m. Friday; regular hours are still being finalized. The useful page says when Friday service starts and identifies the limited menu as applying to opening week. It does not display unapproved regular hours or a full menu borrowed from another branch.
That choice may mean the page has less information for a few days. It also means the team has fewer promises to correct if the schedule or menu changes. Keep a dated internal copy of the approved details so the website editor knows which version to use.
Read the page on a phone before publishing. Check that the address, status, hours, and menu are easy to find without pinching to zoom. If a menu is a separate document, open it on a phone too. A guest should be able to read it and return to the location page without losing their place.
Link ordering and booking when available
Decide what each button should do at each stage. Before opening, a guest may need directions or a contact method. Once the restaurant is ready, the same page might offer ordering or reservations. A button that leads to a different location's checkout or booking calendar is worse than no button at all.
Ask the ordering provider how the new location is identified, who sets its service hours, and how the team can pause ordering if the kitchen is not ready. For reservations, ask how guests choose the new location, which dates and party sizes can be booked, and who controls availability. If Google bookings matter to you, ask whether and how they are available for this location.
Use a simulation before a live service pilot. In the hypothetical opening above, the team could inspect the ordering flow with a practice configuration or a provider-supported test mode: select the new location, review the displayed menu and pickup times, and stop before submitting anything. For reservations, inspect the location and date selection in a practice environment if one is available. A simulation must not charge a card, send a guest message, or dispatch a courier.
If a safe test mode is unavailable, ask the provider how to inspect the flow without triggering those actions. A visual check alone cannot prove that an order will reach the kitchen or that a reservation will appear in the staff's workflow. Plan a separate, controlled live service pilot when the location is ready, with staff assigned to monitor and handle real activity.
If you already have a site, ask whether an ordering button or link can connect guests to the right location rather than assuming you need to rebuild everything. Fleksa offers options for keeping an existing site with an online ordering link or button. Confirm the available setup for your location and when it can be activated.
Use a readiness checklist and review after opening
Before publishing, work through the checklist below with the launch lead and the person who can edit the page. “Ready” means the detail is approved and the team knows who maintains it; it does not mean every future service must already be offered.
| Page item | Ready to publish when | Owner to confirm |
|---|---|---|
| Opening status | The wording and any date match the approved launch plan. | Launch lead |
| Address and directions | The full address, entrance notes, and any directions link point to the new site. | Operations lead |
| Contact | The number or inbox is monitored and the team can answer location questions. | Front-of-house lead |
| Hours and menu | Each applies to this location; temporary details have a review date. | Operations and kitchen leads |
| Ordering and reservations | Available actions point to the right location and have an activation plan. | Service and website leads |
| Page upkeep | An editor has access, approval authority is clear, and the next review is assigned. | Website owner |
The table is a release check, not a requirement to publish every feature at once. For example, an accurate “opening soon” page with a monitored contact can go live while the menu and ordering setup are still being finalized. Keep those unavailable actions off the page until they are ready, rather than using buttons that lead nowhere.
Set a review for opening day and another after the first service period. Compare the page with what staff are actually offering: Is the entrance easy to find? Are the published hours still right? Does the menu reflect current service? Check ordering and booking links again whenever their settings change.
Give staff a simple way to report errors to the editor. A shared list with the issue, the person responsible, and the date corrected is enough to prevent an old change request from getting lost. Update other places where the location appears as well, including your existing location directory and any profiles you manage, so guests are not seeing conflicting hours.
Use the checklist to assess your current setup, then ask Fleksa about a restaurant website and verified availability for your US location.
Frequently asked questions
Can a location page go live before the restaurant opens?
Yes. State that the location is not yet open, publish confirmed contact and address details, and add an opening date only after it is approved. Leave unavailable ordering and reservation actions off the page.
Should the new location use another branch's menu?
Only if the kitchen and operations teams confirm that it applies to the new location. Otherwise, wait for the approved menu or clearly label a representative menu so guests know details may differ.
How often should the page be checked after opening?
Check it on opening day, after the first service period, and whenever hours, menu, contact details, or service availability change. Assign an editor so corrections do not depend on someone noticing them by chance.
