Managing multiple restaurant locations starts with a small but important check: which restaurant are you working on right now? A correct menu edit in the wrong location is still a mistake. So is asking one branch to investigate an order that belongs to another.
OmNom supports multiple locations under one business as well as separate restaurant businesses. Its current location guidance points owners to Settings → Switch Account to select a restaurant or start adding another.
The practical routine is simple: identify the location, select it, complete one task, and verify the result before moving on. Use the checklist below whenever you work across branches or hand unfinished work to another person.
1. Select the location before starting the task
Open Settings, choose Switch Account, and select the restaurant you intend to work on. Check the selection before making an edit or investigating an order, even if you used that location earlier.
Your physical location is not a reliable reminder of the restaurant selected in the app. You might be standing at the north branch while still finishing yesterday’s work for the downtown branch. Returning after a phone call or interruption is another good moment to check again.
Keep a short location reference in your own operating notes:
- Restaurant or business name
- Branch name and street address
- The corresponding restaurant selection in OmNom
- The person responsible for confirming changes at that branch
Use enough detail to distinguish similar names. “Downtown” may be clear to a long-time manager but unclear to someone covering a shift. Pairing it with the street address gives both people the same reference.
This is a team checklist you maintain, not a promise of a particular OmNom account-management feature.
2. Turn a general request into a location-specific worklist
“Update the special” is incomplete when two branches offer different specials. Before opening the app, write down the restaurant, the exact intended change, and which locations should remain unchanged.
For work that applies to several branches, give each location its own line. Track completion separately rather than writing “all stores done” after checking only one.
Here is a hypothetical worklist for a two-location café business:
- Market Street: Correct the description of the lunch special after the local manager confirms the wording
- Station Road: Leave its lunch-special description unchanged because it uses a different recipe
- Both locations: Check the final result separately and record who reviewed each one
The distinction matters even when the branches share a brand. Similar menus and names do not prove that an identical edit belongs everywhere.
Do not assume that switching restaurants synchronizes changes between them. The documented Switch Account function lets you select a restaurant; it does not establish a bulk-editing workflow. Work from each location’s actual requirements and verify its own result.
3. Finish and verify one location before switching
Keep the work sequence narrow. Select the first restaurant, make the intended change using the available controls, complete the save or submission step, and review what is actually saved.
Before switching away, ask:
- Am I still working on the intended restaurant?
- Does the saved result match the request for this branch?
- Is there any unfinished work or uncertainty someone else needs to know about?
- Have I recorded this location as checked, rather than merely attempted?
Where relevant, check the customer-facing result too. Open the ordering page you intend to inspect and confirm its restaurant identity before judging whether the change appears correctly. A saved edit and a check of the wrong branch’s page can otherwise create false confidence.
If the result is unclear, keep that location marked as unresolved. Repeating the same edit across other restaurants before understanding the first result makes it harder to reconstruct what happened.
After an interruption, restart with the location check. You do not need to redo completed work; you need to establish where you are before continuing.
4. Put the location first in every operational handoff
A handoff between people should carry the restaurant identity along with the task. This applies to menu changes, setup questions, and order investigations.
A useful hypothetical note is:
“Market Street, [street address]: lunch-special description corrected and checked at 10:15. Station Road was intentionally left unchanged. Please confirm the Market Street wording with the opening manager.”
For an order question, include the location and relevant order number through your normal authorized team channel. Ask the receiving person to confirm the restaurant before taking action. Share only the order details needed to resolve the issue.
Treat this as a communication handoff, not a request to move an order between restaurants. If a guest or team member appears to be at the wrong branch, establish which restaurant the order belongs to before making promises about how it will be handled.
5. Stop and clarify when the restaurant identity is uncertain
If you cannot find the expected restaurant, do not select the closest-looking name and continue. Check your location reference and whether you are signed into the intended account.
If that does not resolve it, contact OmNom support. Include a short description, the account email, the relevant restaurant name and location, and an order number when the problem concerns an order. Explain what you expected to see and what you saw instead. Keep sign-in codes and sensitive payment information out of the message.
Adding another restaurant should be a deliberate setup task for an additional location or business. First clarify the existing restaurant’s identity when you are trying to resume work already underway.
For day-to-day multi-location management, use one repeatable rule: select, act, verify, then switch. It gives every branch a clear completion check and makes the next person’s starting point easier to understand.