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

# Deliveries

> Your own delivery, with zones and fees, and the link to delivery platforms: Wolt, Glovo and Bolt Food.

A restaurant can deliver in two ways: **with your own people**, for orders from your website, or **through delivery platforms**. Both are set up on the restaurant's **Delivery** tab.

## Your own delivery

Turn on **Deliver** under the restaurant's **Settings → What you sell** (see [Restaurants](/en/restaurants#settings)). Then, on **Delivery**, **Delivery zones** → **Add zone**: **Name**, **Radius (km)**, **Delivery fee**, **Minimum order** and, optionally, **ETA (min)**. Distances are measured from the restaurant's coordinates.

<Warning>
  With no zone at all, "every delivery order ships with NO delivery fee". And if the restaurant has no coordinates, zones match no address: set the restaurant's location.
</Warning>

Delivery orders get the **Send Out for Delivery** step in the queue, then **Mark Delivered** — see [Orders and kitchen](/en/restaurants/orders).

## Delivery platforms

**Settings → Delivery** (Integrations group; the **Delivery Platforms** page) lists the platforms: **Wolt**, **Glovo** and **Bolt Food**. Gridbeds holds the integration with each platform, so there are no credentials to enter: no API key, no client secret. The page needs permission to manage integrations and your subscription's integrations module.

<Note>
  Each platform first has to approve Gridbeds as an integration partner and give it access. Until then the platform shows **Not set up yet** and cannot be connected; ask Gridbeds support when it will be. Uber Eats is not offered for now, so it is not on the list.
</Note>

A platform is connected in two steps:

1. **for the organization**, in **Settings → Delivery**: **Enable Platform**. This sends nothing to the platform; it lets the organization's restaurants connect to it;
2. **for each restaurant**, on its **Delivery** tab: **Add Platform**, choose the platform, then follow its steps below. The last step sets **Price Markup** (raises prices on that platform by a percentage), the default prep time, **Auto-accept Orders** and **Automatic Menu Sync**.

### Wolt

1. Choose **Wolt** and continue to the last step, then press **Continue to Wolt**.
2. On Wolt's page, log in with your Wolt merchant account, pick this restaurant's venue and allow Gridbeds.
3. Wolt sends you back to the **Delivery** tab, which says whether it worked, and Gridbeds tests the connection straight away.

The venue is the one you picked on Wolt's page; it is never typed. If Wolt later stops accepting the authorization (it expired, or someone removed it on Wolt's side), the Wolt card shows **Needs attention** and a **Connect with Wolt again** button.

### Glovo

1. Choose **Glovo** and press **Connect Platform**.
2. Gridbeds gives the restaurant a **Store ID for Glovo**, shown on the Glovo card with a copy button. Send it to your Glovo account manager and ask them to link the store to Gridbeds. Glovo does this by hand, so it can take a few days.
3. When Glovo confirms, press **Test connection** on the card.

The store ID is Gridbeds's and cannot be changed. If the store was linked to another system before, Glovo changes it to this ID.

### Bolt Food

1. Ask Bolt Food support for this restaurant's **provider ID**, and ask them to link it to Gridbeds.
2. Choose **Bolt Food**, enter the provider ID, and press **Connect Platform**. Gridbeds tests the connection straight away.
3. While Bolt Food answers for the store but nobody has confirmed it is this restaurant's, the card shows **Waiting for confirmation**. Ask Gridbeds support to confirm it with Bolt Food; the card then shows **Connected**.

A provider ID someone types is a claim, not a link: Gridbeds makes it the restaurant's only once a second signal confirms it. If another organization already claims the same provider ID, the card shows **Needs attention** and Gridbeds support reviews which restaurant it belongs to; nothing of the other claim is overwritten.

### What Test connection tells you

**Test connection**, on each platform's card, asks the platform one read-only question and shows what it found. The card also shows when the last successful check was.

| Card shows | Means | What to do |
| - | - | - |
| **Connected** | The platform accepts the connection and knows the store as linked to Gridbeds. | Nothing. |
| **Waiting for confirmation** | The platform knows the store, and a second signal has yet to confirm it is this restaurant's (Bolt Food). | Ask Gridbeds support to confirm it with the platform. |
| **Not connected** | The connection is not finished: Wolt has not been authorized yet, or there is no store ID. | Finish the platform's steps above. |
| **Needs attention**: the platform no longer accepts the restaurant's authorization | Wolt's authorization expired or was removed. | **Connect with Wolt again**. |
| **Needs attention**: the platform refused Gridbeds's credentials | Something on Gridbeds's side. | Contact Gridbeds support. |
| **Needs attention**: the platform does not know this store, or has not linked it to Gridbeds yet | The store ID is wrong, or the platform has not linked it yet. | Check the ID; ask the platform's account manager to link the store. |
| **Needs attention**: the platform did not answer | The platform was down or busy. Nothing is known to be wrong with your settings. | Test again in a few minutes. |
| **Needs attention**: requests to delivery platforms are switched off for your organization | Gridbeds has not switched delivery platforms on for your organization yet, so nothing was sent. | Ask Gridbeds support to switch them on. |
| **Needs attention**: Gridbeds's integration with the platform is not set up yet | The platform has not approved Gridbeds yet. | Contact Gridbeds support. |

**Disconnect**, on the card's menu, removes the platform from the restaurant and deletes what Gridbeds held for it. For Wolt, also remove Gridbeds from the venue's integrations in Wolt's merchant tools.

<Warning>
  **Connecting is what the screen does for now.** Taking a platform's orders in Gridbeds, opening and closing the store on the platform, marking items sold out and sending the menu come next, one platform at a time, Wolt first. Until then, keep taking the platform's orders on its own tablet or merchant portal.
</Warning>

Platform orders take no tip in Gridbeds.


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