> For the complete documentation index, see [llms.txt](https://broadcast.presidiocreative.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broadcast.presidiocreative.com/product-theme-blocks/inventory-countdown.md).

# Inventory countdown

Use an I**nventory countdown** block to display the remaining quantity of items in stock. It helps businesses and customers easily see how many products are available before they run out.

> Only one Inventory countdown block is allowed per section (`limit: 1`).

<figure><img src="https://2636770384-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsD7BEEDU3B7WiEJlN0F7%2Fuploads%2F4gmFcfd50JCf1nA9H29r%2FUntitled%20image%20(36).png?alt=media&amp;token=01dd4005-7c30-4fa7-a659-ef58349cfd4b" alt="Picture depicting the Inventory countdown block settings of the product pages section"><figcaption></figcaption></figure>

{% hint style="success" %}
Create a sense of urgency and encourage customers to purchase before the item is sold out.
{% endhint %}

<table><thead><tr><th width="214.02166748046875">Settings</th><th width="126.42095947265625" align="center">Type</th><th>Description</th></tr></thead><tbody><tr><td>Show notice</td><td align="center"><code>select</code></td><td>Choose when the inventory notice appears. Options: <code>Always</code> or only when stock is <code>Low inventory</code>.</td></tr><tr><td>Low inventory threshold</td><td align="center"><code>range</code></td><td>The maximum stock level (1-50) at which the low inventory message will appear. </td></tr><tr><td>Hide inventory counter</td><td align="center"><code>checkbox</code></td><td>Hides the actual number of items in stock if enabled. </td></tr><tr><td>Icon size</td><td align="center"><code>range</code></td><td>Controls the size of the stock icon.</td></tr><tr><td><strong>Colors</strong></td><td align="center"></td><td></td></tr><tr><td>In stock</td><td align="center"><code>color</code></td><td>Icon and text color when the item is in stock.</td></tr><tr><td>Low stock</td><td align="center"><code>color</code></td><td>Icon and text color when item hits the low stock threshold.</td></tr><tr><td>Out of stock</td><td align="center"><code>color</code></td><td>Icon and text color when the item is sold out.</td></tr><tr><td><strong>Padding</strong></td><td align="center"></td><td></td></tr><tr><td>Bottom</td><td align="center"><code>range</code></td><td>Adds spacing below the block.</td></tr></tbody></table>

## Notes

* The block uses live product inventory data.
* When 'Hide inventory counter' is enabled, the stock quantity is not shown, but the message will still be displayed.
* Color settings allow for full customization of inventory status indicators to match your store’s branding.


---

# 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://broadcast.presidiocreative.com/product-theme-blocks/inventory-countdown.md?ask=<question>&goal=<user_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.
