> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/stock/demand-forecast/stock-runway-and-lead-time.md).

# Stock Runway and Lead Time

<figure><img src="https://1925381409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5cJdZdmiiIn3u107Grmv%2Fuploads%2FvCz06kkHgRLJihGWOELR%2Fimage.png?alt=media&amp;token=fe701720-e15d-4908-b422-f262b2aa2bff" alt=""><figcaption></figcaption></figure>

## Stock Runway

Stock Runway shows how many days your current stock is expected to last based on the forecast. It highlights products that are likely to run out in the coming days.

When Stock Runway is active, the forecast cells are colour coded:

* **Green** — stock is sufficient to cover that day's expected demand
* **Yellow** -- stock is getting low
* **Red** — stock is expected to run out before or on that day

## Lead Time

When Lead Time is active, it factors in approximate delivery times when showing to give users insight how soon you need to order.

### Updating Lead Time on Stock Item

1. In the [**Admin Portal**](https://admin.gobossit.com/), go to the **group level**.
2. Navigate to **Stock > Items**.
3. Locate and click on the relevant stock item.
4. Set value for **Delivery lead time, days**.

{% hint style="info" %}
This value should be the **average number of days** for lead time.
{% endhint %}


---

# 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.bossithq.com/stock/demand-forecast/stock-runway-and-lead-time.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.
