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

# Deliverect Troubleshooting

> Troubleshoot Deliverect connections, menu publications, availability, busy mode, payment settings and orders in storekit.

Use these checks to identify the setting or Deliverect action behind a missing menu update, unavailable order or unexpected store status.

## Connection

### Deliverect is missing from Integrations

Go to **Stores** → your store → **Settings** → **Integrations**. Before the connection is complete, the entry is **EPOS**, not **Deliverect**. Open **EPOS**, then **EPOS Integration** → **Details**, and click **Integrate your EPOS**. This opens live chat with storekit support, who set up the connection together with Deliverect.

After Deliverect links the store to a channel and sends its channel-status callback, **Deliverect** appears and shows **Connected**.

## Menu

### The menu is not updating

Publish the menu in Deliverect. There is no storekit sync button for Deliverect menus; storekit receives the Deliverect webhook and processes it asynchronously. An item appears only if it is in the newly published Deliverect menu.

### Items disappeared after a publication

storekit removes anything absent from the newly published Deliverect menu. Add the category or product in Deliverect and publish the menu again. Do not try to create it in the storekit editor: it shows “You can't add a new category here. Please create new items in your POS”.

## Availability

### The store went offline unexpectedly

Deliverect can send `PAUSED`, `ONLINE` and `BUSY` busy-mode statuses. `PAUSED` takes the storekit store offline and `ONLINE` brings it back online. On **Deliverect Integration**, turn on **Disable Busy Mode** to make storekit ignore Deliverect busy-mode statuses.

**Menu Sync Only** also ignores busy mode, but it additionally stops orders, cancellations and courier updates being sent to Deliverect.

### A product is still unavailable

If Deliverect snoozed the product, click **Unsnooze** in the storekit menu editor to clear the local snooze. For a lasting change, update availability in Deliverect and publish the menu. The next publication can overwrite storekit availability.

There is no stock-level sync from Deliverect. Inventory counts are not sent to storekit.

### Opening hours were overwritten

Check **Use Deliverect opening hours** on **Deliverect Integration**. When it is on, availability hours in a Deliverect menu update overwrite the store's opening hours. Turn it off if storekit should keep its own opening hours.

## Orders

### Orders are not reaching Deliverect

Check these in order:

* **Menu Sync Only** may be on. When it is enabled, orders are dispatched to a different POS.
* The order may be a buffered pre-order. Check **Buffer Orders** and **Buffer Delay (in minutes)** on **Deliverect Integration**.
* The dispatch may have failed. Open the order and read its POS failure notification. If it has no POS receipt, use **Resend order to POS**. Use **View in Deliverect** to open the corresponding Deliverect order.

storekit refuses **Resend order to POS** when the order was already accepted by the POS, to avoid a duplicate.

### Cash orders are unpaid in the POS

Turn on **Send Cash as Paid** on **Deliverect Integration**. Without it, cash orders are sent as unpaid. Card, other payment types and £0 orders are always sent as paid.

### The tip is missing or combined with the service charge

Turn on **Split Service Charge and Tip**. When it is off, storekit adds the customer tip to the service charge and sends one combined amount to Deliverect.

### The order was sent too early or too late

Check **Buffer Orders** and **Buffer Delay (in minutes)**. Scheduled orders are sent the configured number of minutes before their requested time; ASAP orders are never buffered. If the scheduled send time has passed, storekit sends the order immediately.

### The order has the wrong table

For in-store orders, storekit sends **POS ID** when it is set, otherwise **Name**. Open **Tables** in the left-hand menu, then set the correct **POS ID** or **Name**.

### The customer has not received a ready-for-pickup notification

Set **Ready for Pickup Status Code** to the numeric Deliverect code that should mark the order ready. The usual code is `70`; the field placeholder is `eg 70`.

## Still Need Help?

If the issue persists, [contact storekit support](/docs/getting-started/contact-support) with the store name, order code or Deliverect channel link ID and the time of the failed action.


## Related topics

- [Deliverect](/docs/guides/integrations/pos/deliverect/overview.md)
- [Troubleshooting](/docs/guides/integrations/pos/comtrex/troubleshooting.md)
- [Connecting Deliverect](/docs/guides/integrations/pos/deliverect/connect.md)
- [Deliverect Orders](/docs/guides/integrations/pos/deliverect/orders.md)
- [Webhook Troubleshooting](/docs/developers/webhooks/troubleshooting.md)