> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eat-now.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Close a restaurant

> How to close a restaurant on EatNow — the difference between pausing bookings and closing the account, the checklist to follow before closing, and what happens afterwards.

Closing a restaurant (end of contract, a venue that stops trading, one restaurant leaving a group…) is **done by the EatNow team**. There is no "close my account" button in the dashboard: contact EatNow support and tell us which restaurant to close and from which date.

Before you ask, go through the [checklist](#before-closing-the-checklist) below. **Once the restaurant is closed, your team can no longer export, disconnect or change anything.**

***

## Pause or close?

You may not need to close at all. If you only want to stop taking bookings for a while (renovation, seasonal closure), pause instead — you keep full access and can restart whenever you like.

| | **Pause** (you do it) | **Close** (EatNow does it) |
| - | - | - |
| How | Set your services to **Inactive** — see [Shift visibility](/shifts/visibility). For a few days only, use [Block reservations](/shifts/block-reservations). | Ask EatNow support. |
| Online bookings | Stopped for the paused services | Stopped everywhere |
| Your booking page | Still online | Shows **Page not found** |
| Your team | Keeps full access to the dashboard and the app | Loses access (only invoices stay visible) |
| Reminders and automatic messages | Keep running for existing reservations | Stop |
| Restarting | Set the services back to Active | Ask EatNow support |

***

## Before closing: the checklist

Do these steps **yourself, before the closing date**. They need an owner or a team member with the right permissions.

<Steps>
  <Step title="Deal with upcoming reservations">
    After the closure, guests can no longer open their booking page (to view, change or pay) and stop receiving reminders. Cancel or move any reservation planned after the closing date, and let those guests know.
  </Step>

  <Step title="Export your data">
    * **Reservations** — [Export your reservations](/reservations/export). Use **Settings → Integrations → Export** to download a whole period at once.
    * **Customers** — [Export your customer base](/customers/export).

    Keep the files: once the restaurant is closed, you can no longer download them yourself.
  </Step>

  <Step title="Stop what goes out to your guests">
    * **Marketing** — cancel any scheduled campaign ([Campaigns](/marketing/campaigns)).
    * **Waitlist, activities, privatization, menus** — turn them off if you no longer want them reachable ([Waitlist setup](/waitlist/setup), [Activities on the portal](/portal/activities), [Privatization](/portal/privatization), [Menus](/menus/overview)).
  </Step>

  <Step title="Remove your booking links">
    Take the EatNow booking link off your website, Instagram, Google listing and any other channel: after the closure, it leads to a **Page not found** page. See [Share and embed](/portal/share-and-embed) for the places you may have put it.
  </Step>

  <Step title="Disconnect your integrations">
    In **Settings → Integrations**, disconnect what you no longer need:

    * **WhatsApp** — click **Disconnect** on the WhatsApp card. Otherwise guests can keep writing to the number and the AI agent keeps answering, without being able to book. If you use the same number in the WhatsApp Business app (coexistence), also remove the **EatNow / Meta** device in the app (**Settings → Linked devices**).
    * **Reserve with Google** — disconnect the Google card ([Reserve with Google](/integrations/google-reserve)).
    * **POS and other tools** — [Lightspeed](/lightspeed/reservation), [NowOS](/nowos/connect), payments, tracking: see [Integrations](/integrations/overview).
    * **API and webhooks** — revoke your [API keys](/integrations/api) and delete your [webhooks](/integrations/webhooks).
  </Step>

  <Step title="Remove your team">
    Delete the collaborators who no longer need access ([Manage collaborators](/collaborators/manage)). Owners can't be deleted this way.
  </Step>

  <Step title="Settle your billing">
    Check your invoices in **Billing** and settle any that are still open. Ask EatNow support for the end date of your subscription.
  </Step>

  <Step title="Ask EatNow to close the restaurant">
    Contact EatNow support with the restaurant's name and the closing date.
  </Step>
</Steps>

***

## What happens after the closure

* **Guests** — your booking page, your existing guests' booking pages, your menus and your waitlist all show **Page not found**. New bookings are refused everywhere, including through Google and the [EatNow API](/api-reference/errors).
* **Your team** — when they log in, the dashboard and the app show **Restaurant suspended**. Members with access to billing can still see the invoices. If someone works in several restaurants, they can switch to the others, which are not affected.
* **Automations** — reminders, follow-up and review requests, scheduled reports and automatic no-shows stop. Marketing campaigns that fall due, or are still sending, are paused.
* **Your data** — reservations, customers and settings are **kept, not deleted**. To have data deleted, ask EatNow support.

***

## Closing one restaurant of a group

A closure applies to **one restaurant**. The other restaurants of your organization keep working normally. To close several, list them all in your request.

***

## Reopening

A closed restaurant only reopens when the EatNow team reopens it. Contact EatNow support: everything comes back as it was — reservations, customers, services and settings. Reconnect the integrations you disconnected and put your booking links back.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.