> 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/variables.md).
# Delivery variables
The seven tokens you can drop into a delivery message, and what each one renders.
A delivery message isn't fixed text. Anywhere you write one of these tokens, the app replaces it with a real value when the page loads — a calculated date, a live countdown, or the shopper's own country.
Open the **Variables** list from the message editor to insert one, or type it by hand — they're just text in curly braces.
The Variables panel, opened from the delivery message editor.
## The seven variables
| Variable | Renders |
| ----------------------- | ------------------------------------------- |
| `{delivered_min_date}` | The estimated order delivery minimum date |
| `{delivered_max_date}` | The estimated order delivery maximum date |
| `{dispatched_min_date}` | The estimated order dispatched minimum date |
| `{dispatched_max_date}` | The estimated order dispatched maximum date |
| `{cutoff_time}` | A live countdown to today's cut-off time |
| `{country_flag}` | The flag of the visitor's detected country |
| `{country_name}` | The name of the visitor's detected country |
## Dates
The four date variables come straight out of your [date range settings](/samita-countdown-timer-bar/estimated-delivery-date/date-range.md), formatted with the **Date format** you chose there.
Pair the min and max of the same stage to express a window:
```
Delivery between {delivered_min_date} and {delivered_max_date}
```
Use a single one when you want to sound definite rather than hedged:
```
Get it by {delivered_max_date}
```
{% hint style="info" %}
The dispatch variables are the less useful pair for most stores — shoppers care when it lands, not when it leaves. They're worth showing if your dispatch speed is itself a selling point.
{% endhint %}
## Cut-off countdown
`{cutoff_time}` renders as a running countdown to today's deadline, formatted with the **Time format** you chose. It's what makes a delivery message act like a countdown:
```
✅ Order within the next {cutoff_time} for delivery between {delivered_min_date} - {delivered_max_date}
```
{% hint style="warning" %}
With the default 23:59 cut-off this reads as most of a day, which persuades nobody. Set a real cut-off before relying on it — see [Cut-off time](/samita-countdown-timer-bar/estimated-delivery-date/cutoff-time.md).
{% endhint %}
## Country flag and name
`{country_flag}` renders a small flag image and `{country_name}` the country's name — both for the country the app detects for that visitor.
```
🚚 Free shipping to {country_flag} {country_name}
```
The country is detected from the visitor's IP address at the time they browse, not from an address on their account. Two consequences worth knowing:
* A shopper on a VPN sees the country their VPN exits from.
* The detection isn't infallible, so don't attach a promise to it that would be expensive to get wrong.
{% hint style="info" %}
"Free shipping to {country\_name}" is only true if it's true everywhere you sell. If your shipping rules vary by country, either soften the wording or use [display conditions](/samita-countdown-timer-bar/where-countdowns-appear/conditions.md) to show a different delivery message per country.
{% endhint %}
## Writing a good message
The default message is a reasonable model: a shipping statement, then a deadline, then a window.
> 🚚 Free Shipping to **{country\_flag} {country\_name}** ✅ Order within the next **{cutoff\_time}** for delivery between **{delivered\_min\_date} - {delivered\_max\_date}**
A few things that help:
* **Colour and bold the dates**, not the whole sentence. The editor supports both.
* **Keep it to two lines.** It sits near the Add to cart button, where it competes for attention.
* **Check it on mobile.** A message that reads well on desktop can wrap badly on a phone.
## Next steps
* [Cut-off time](/samita-countdown-timer-bar/estimated-delivery-date/cutoff-time.md)
* [Date range settings](/samita-countdown-timer-bar/estimated-delivery-date/date-range.md)
* [Translate countdown text](/samita-countdown-timer-bar/design-and-translation/translate.md)
* [Create an estimated delivery date](/samita-countdown-timer-bar/estimated-delivery-date/create.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/variables.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.
