> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/whatsapp-commerce/logistics-integration/logistics-core-module/delivery-slots.md).
# Delivery Slots
Configure customer delivery days, time windows, booking lead time, and capacity.
### Overview
Delivery Slots let customers choose a delivery date and time at checkout.
Use this feature to offer only times your store can fulfil.
### Before you start
Open **Ecommerce** → **Catalogs**. Select your catalog and click **Edit**. Then open **Delivery Settings**.
For the full navigation, see [Access delivery settings](/whatsapp-commerce/logistics-integration/logistics-core-module/access-delivery-settings.md).
### Enable delivery slots
Enable **Delivery Slots** to require a delivery date and time selection at checkout.
Disable it to hide delivery-slot selection from customers.
Click **Save Delivery Settings** after making changes.
### Configure delivery days
Select the days when deliveries are available.
* Select **All** to enable every day.
* Select individual days for a limited schedule.
For example, select Monday through Saturday and leave Sunday unselected.
### Add time slots
Time slots define the delivery windows customers can select.
For each slot, enter:
* **Slot Name**, such as `Morning` or `Evening`
* **Start Time**
* **End Time**
For example:
| Slot | Time |
| ------- | ---------------- |
| Morning | 9:00 AM–11:30 AM |
| Noon | 12:00 PM–3:30 PM |
| Evening | 4:00 PM–6:30 PM |
Customers can select one available slot during checkout.
#### Add or insert a slot
Click **Add Time Slot** to add another delivery window.
Use the **+** button beside a slot to insert one directly below it.
{% hint style="warning" %}
Do not create overlapping time slots. Overlaps can create unclear delivery commitments.
{% endhint %}
For example, `9:00 AM–11:30 AM` and `11:00 AM–2:00 PM` overlap between 11:00 AM and 11:30 AM.
### Set booking thresholds
Thresholds control when customers can book a delivery.
#### Start threshold
The **Start Threshold** is the minimum preparation time before a slot is available.
Set it in minutes, hours, or days. This gives your team time to prepare, pack, and dispatch an order.
If the threshold falls within an existing slot, that slot remains selectable.
For example, at 10:00 AM with a four-hour threshold:
* `9:00 AM–11:30 AM` is unavailable.
* `12:00 PM–3:30 PM` is available because 2:00 PM falls within it.
* `4:00 PM–6:30 PM` is available.
With a two-day threshold on Monday, the earliest available date is Wednesday. This depends on your selected delivery days and time slots.
#### End threshold
The **End Threshold** limits how far ahead customers can book.
For example, an end threshold of 20 days on 1 July allows bookings through 21 July. Customers cannot select 22 July until it falls within the booking window.
### Set a slot limit
**Slot Limit** controls how many orders each delivery slot accepts.
Leave it empty for unlimited bookings. Enter a number to cap bookings for each slot.
For example, with a slot limit of 50, the Morning slot becomes unavailable after 50 bookings.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.pickyassist.com/whatsapp-commerce/logistics-integration/logistics-core-module/delivery-slots.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.