> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/samita-countdown-timer-bar/estimated-delivery-date/date-range.md).
# Date range settings
Set dispatch and delivery day ranges, working days, holidays, and date formats.
The **Date range setting** section on the **Settings** tab is where the delivery window actually comes from. Everything a shopper sees as a date is calculated from these fields.
Dispatch and delivery are configured separately, each with its own working days.
## Two stages, configured separately
The window is built in two steps, and each has its own settings.
### Order dispatched days range
How long it takes you to get the order out of the door.
| Field | Meaning | Default |
| ------------ | ---------------------------- | ------------- |
| **Min days** | Fastest you'd dispatch | 1 |
| **Max days** | Slowest you'd dispatch | 3 |
| **Days** | The weekdays you dispatch on | Monday–Friday |
These feed the `{dispatched_min_date}` and `{dispatched_max_date}` variables.
### Order delivered days range
How long the carrier takes after dispatch.
| Field | Meaning | Default |
| ------------ | --------------------------------- | --------- |
| **Min days** | Fastest delivery | 3 |
| **Max days** | Slowest delivery | 5 |
| **Days** | The weekdays deliveries arrive on | Every day |
These feed `{delivered_min_date}` and `{delivered_max_date}`.
{% hint style="info" %}
The two ranges stack. With the defaults, the earliest delivery is 1 + 3 = 4 working days out and the latest is 3 + 5 = 8 — before weekends and holidays are skipped, which usually pushes both later.
{% endhint %}
## Working days matter more than you'd think
The **Days** checkboxes aren't decoration — days you don't tick are skipped entirely when counting.
Leave dispatch on Monday–Friday and an order placed on Saturday starts counting from Monday. Untick Sunday for delivery and a window that would have landed on Sunday moves to Monday instead.
Set these to match reality:
* **Dispatch days** — the days someone is actually in your warehouse packing orders.
* **Delivery days** — the days your carrier actually delivers in your main market.
## Holidays
The **Holiday** field takes a list of dates to exclude from the calculation entirely, described in the app as "These dates will be excluded from the estimation."
Add your public holidays and any days you're closed. A store that adds its December closure in November stops promising deliveries that can't happen.
{% hint style="info" %}
Holidays are a plain list of dates, so they don't repeat automatically. Add next year's when you add next year's calendar.
{% endhint %}
## Date & time settings
Two formatting controls decide how the calculated values are written out.
### Date format
Two dozen formats, from short to fully spelled out:
`MM/DD/YY` · `MM/DD/YYYY` · `DD/MM/YY` · `DD/MM/YYYY` · `YY/MM/DD` · `DD.MM.YY` · `YY.MM.DD` · `YYYY-MM-DD` · `DD MMM, YYYY` · `DD MMMM, YYYY` · `MMMM DD` · `MMM DD` · `DD MMMM` · `dddd` · `dd` · and several long forms such as `dddd, MMMM DD, YYYY`
The default is `MMM DD` — "Mar 14".
{% hint style="warning" %}
Numeric formats are ambiguous across countries: `03/04` is 3 April to a British shopper and 4 March to an American one. If you sell internationally, a format with a month name removes the guesswork.
{% endhint %}
### Time format
How the `{cutoff_time}` countdown is written:
`Hrs, Mins, Secs` · `Hrs, Mins` · `Hours, minutes, seconds` · `Hours, minutes` · `hours, minutes, seconds` · `H, M, S`
Short forms suit a compact product page; long forms suit a wide banner.
## Checking your setup
The builder preview updates as you change these fields, so you can see the effect immediately. Two things are worth checking deliberately:
1. **Set a dispatch day range with a weekend in the middle** and confirm the dates skip it.
2. **Add today as a holiday temporarily** and confirm the window moves. Remove it afterwards.
## Next steps
* [Cut-off time](/samita-countdown-timer-bar/estimated-delivery-date/cutoff-time.md)
* [Delivery variables](/samita-countdown-timer-bar/estimated-delivery-date/variables.md)
* [Create an estimated delivery date](/samita-countdown-timer-bar/estimated-delivery-date/create.md)
* [Estimated delivery date overview](/samita-countdown-timer-bar/estimated-delivery-date/overview.md)
---
# 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://docs.samita.io/samita-countdown-timer-bar/estimated-delivery-date/date-range.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.
