> 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/stock-countdown/overview.md).

# Stock countdown overview

Show how little stock is left of a product, with a message and an optional scarcity slider.

A stock countdown is the one type that doesn't count time. It counts inventory — "🔥 This product is almost sold out. Hurry up to order! 7 items left in stock." — optionally with a slider that shows how far the stock has been drawn down.

It works on scarcity rather than deadline, which makes it a good fit for products that genuinely sell out: limited runs, seasonal lines, one-off pieces.

<figure><img src="https://855148666-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaOJwtwIUCsbYLCDqZD0u%2Fuploads%2Fgit-blob-df4207db5ea6f7693a712b88df3cd3123d1a4f35%2Fscreenshot-storefront-stock-product-page.png?alt=media" alt="A storefront product page showing the stock message and scarcity slider below the Add to cart button"><figcaption><p>A stock countdown on a product page: message and slider.</p></figcaption></figure>

## What it's made of

| Part                          | What it does                                                                  |
| ----------------------------- | ----------------------------------------------------------------------------- |
| **Message**                   | The sentence shoppers read, with `{stock_number}` replaced by the real figure |
| **Inventory tracking method** | Where the number comes from — the variant, the product, or an estimate        |
| **Stock quantity threshold**  | Hides the countdown until stock drops below a number you set                  |
| **Stock slider**              | A bar showing remaining stock against a total you define                      |
| **Design**                    | Alignment, colors, animation, and custom CSS                                  |

## Where to start

New to it? [Create a stock countdown](/samita-countdown-timer-bar/stock-countdown/create.md) runs from creating the countdown through to checking it on your storefront.

Already have one and want to tune what it reports? [Inventory tracking and the stock slider](/samita-countdown-timer-bar/stock-countdown/inventory.md) covers the three tracking methods, the threshold, and the slider in detail.

## An honest number is a better number

The app can show a real inventory figure or an estimated one. The real figure is the one worth using wherever you can:

* Shoppers who see "3 left", buy, and get the product build trust.
* Shoppers who see "3 left" for weeks learn to ignore every scarcity signal on your site.

Shopify's App Store rules expect urgency features to reflect genuine conditions. If you're not tracking inventory in Shopify, the estimated mode exists — but set it to something defensible.

## Next steps

* [Create a stock countdown](/samita-countdown-timer-bar/stock-countdown/create.md)
* [Inventory tracking and the stock slider](/samita-countdown-timer-bar/stock-countdown/inventory.md)
* [Display conditions](/samita-countdown-timer-bar/where-countdowns-appear/conditions.md)
* [Countdown types](/samita-countdown-timer-bar/countdowns/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/stock-countdown/overview.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.
