A restaurant invitation arrives during service. You open it later, try to continue setup, and hit an error. It is tempting to start again with another email or add the restaurant from scratch. Before doing either, work out which part has stopped: the invitation, your sign-in, or the restaurant’s remaining setup.
Those problems need different next steps. An expired sign-in code can be replaced through sign-in. An expired or already-claimed restaurant invitation needs support. A restaurant waiting for verification needs the action shown in its setup status.
This guide helps you find the right path while keeping the existing restaurant and the work you have already submitted.
Start with the message on the screen
Read the error before requesting another code or opening another link. Write down its wording and what you were trying to do. “I cannot finish setup” is a useful starting point, but “the invitation says it has already been claimed” gives you a much clearer next action.
Use these three questions:
- Can you sign in? If the problem is a missing, expired, or rejected sign-in code, start with your email and the latest sign-in message.
- Does the restaurant invitation report a problem? If it is expired, incorrect, or already claimed, contact support about that invitation.
- Can you open the restaurant’s setup? If so, check its saved status and follow the remaining requirement rather than restarting onboarding.
You may encounter more than one issue. Resolve the one currently blocking you, then check the next screen. A successful sign-in does not tell you whether an invitation is still valid or whether payment verification is complete.
Check the intended email first
If the invitation specifies an email address, use that address. Compare it with the one you are using for sign-in, especially if you have a personal inbox, a business inbox, and a public restaurant contact address.
OmNom’s email guidance separates your login email from your public restaurant contact information. The email printed on your menu or website therefore is not enough to establish which account you used for setup. Use an inbox you control and can reliably access for sign-in and important notices.
If someone helped prepare your restaurant, check which email the invitation was intended for. They can help clarify the original introduction without signing in for you. Keep the sign-in code with the person completing the authorized owner setup.
If the intended address is wrong, or you can no longer access it, contact support. Do not assume a different email will reconnect you to the same setup. Explain the mismatch so support can review the existing record.
Treat sign-in codes separately from invitations
For a missing sign-in email, check the spam folder. If you have requested several codes, use the newest email: requesting a new code replaces the previous one. An older message arriving later can make repeated attempts confusing, so check which request the message belongs to before entering its code.
If the sign-in code or link has expired, request another. If that still leaves you stuck, use OmNom’s support contact details rather than continuing to generate codes indefinitely. These steps come from the current sign-in troubleshooting answer.
A restaurant invitation has its own status. Owner setup invitations can expire or be replaced. OmNom directs owners to support when an invitation is expired, incorrect, or already claimed. Requesting a fresh sign-in code is not a documented fix for those invitation states.
Follow the restaurant invitation guidance: keep the existing restaurant and ask for help with the invitation. Creating another restaurant to bypass the error can leave you with another record to untangle.
Resume the work you successfully submitted
If you previously started onboarding, reopen the app and continue using the same email when sign-in is required. OmNom saves steps when you successfully submit them and move forward. Text entered without submission may not be saved.
That distinction helps explain an interrupted session. If you entered hours and left before submitting, you may need to enter that step again. If you completed a step and advanced, look for the saved progress before rebuilding everything. See the current guidance on finishing setup later.
For owners managing more than one restaurant, check which restaurant is selected. OmNom supports multiple locations and separate businesses; Switch Account in Settings is the documented place to select a restaurant. Match the restaurant and location before making edits. Adding another location makes sense when you actually need another location, not as a recovery step for an invitation error.
Once you are signed in as the verified owner with a restaurant selected, the restaurant assistant can use its saved setup status to explain the next action or waiting reason. Ask a specific question, such as “What is this restaurant waiting on?” The assistant cannot complete protected verification steps for you.
A worked example: two problems in the same session
Imagine an owner returning to a café’s setup after a busy weekend. They have an invitation in their business inbox and several sign-in messages. The first code they try fails. They also remember entering opening hours, but cannot recall submitting them.
The practical sequence is:
- Check the invitation’s intended email and use that inbox for sign-in.
- Use the newest sign-in email, requesting a replacement if its code or link has expired.
- If the invitation then reports that it is expired or already claimed, stop trying to rebuild the café and contact support about that message.
- Once access is resolved, select the café and review the saved setup. Re-enter hours only if that unfinished step still requires them.
This is an illustrative troubleshooting sequence, not a promise that every access problem has the same cause. Its value is keeping each decision tied to the evidence on the screen.
Give support a clear, limited account of the problem
A useful support request identifies the restaurant, the blocked step, and what you have already checked. You do not need to send the contents of a verification form to explain an invitation problem.
For example:
“Hello, I’m setting up [restaurant name and location]. The restaurant invitation shows [exact message]. It was intended for [email address], which I [can/cannot] access. I [can/cannot] sign in. I last successfully completed [step, if known]. I have kept the existing restaurant record. Could you help me continue its setup?”
Adapt the details to what actually happened. If you send a screenshot, remove sign-in codes, passwords, bank information, identity documents, and other sensitive contents. Enter protected information only in the appropriate secure form.
OmNom lists its support email and (402) 875-9960 in its current support guidance. Chat and phone AI can pass unresolved questions to the support team with contact details for follow-up. There is no promised response time.
Finish with the restaurant’s current status
After recovering access, check what the restaurant still needs. Required payment, restaurant, menu, and applicable device checks must pass before ordering can begin. A waiting verification step should be handled through the instructions shown in the app; finishing a form does not guarantee immediate approval.
Also check whether the restaurant is already active. Some setup paths activate automatically once the requirements are satisfied, so do not rely on there always being a separate final launch button.
The useful stopping point is clear: you can access the correct restaurant, see its current status, and understand the next required action or waiting reason. From there, continue the existing setup one submitted step at a time.