> For the complete documentation index, see [llms.txt](https://docs.spiroq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spiroq.com/en/guides/navody/everyday-operation/wolt.md).

# Wolt in the Hub

The customer orders goods from the machine in the Wolt app. The machine layout and stocking decide which products are available for Wolt — only products that are in the slots of that machine, have enough stock, and have an **SKU** code.

Connecting the Wolt account technically is covered in the [technical documentation](https://github.com/PixelDev-CZ/spiroq-docs/tree/main/en/technicke/wolt.md). This is the work in the Hub, once the connection is running.

## What has to match

* The product has **SKU** filled in. The same SKU is on the item in Wolt. When SKU is missing, EAN is used.
* The product is assigned in a slot and is active.
* There is at least one item in the slot. An empty slot is sent to Wolt as unavailable.
* One machine belongs to one Wolt venue. Do not enter the same venue on two machines.

## In the machine detail

After a slot layout change, a **Wolt catalog update pending** bar can appear above the detail. The catalog is sent by itself, usually within a quarter of an hour. The **Sync Wolt menu** button sends it immediately. The whole menu can be sent at most once every 15 minutes — on the next attempt the Hub says how long until it can be done again.

The product quantity is sent to Wolt actively.

An order that Wolt sends is dispensed on the machine as a normal sale. When the SKU does not match or the item is not in stock, the order is rejected.