> For the complete documentation index, see [llms.txt](https://docs.flowlity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowlity.com/settings/buffer-policy.md).

# Buffer Policy

The Buffer Policy page lets you define the default safety-stock and buffer parameters applied to products based on their inventory strategy. These defaults are used unless a product-level override is set in [Products](/settings/products.md) > Inventory strategy.

### Policies by strategy

Each inventory strategy has its own set of configurable buffer parameters:

* **MTS Flowlity AI** — Flowlity automatically calculates the optimal safety stock using probabilistic forecasting. You can set a target **service level** (e.g. 95 %) that drives the buffer size.
* **MTS My min** — A fixed minimum stock level you define manually. The buffer is the minimum quantity that should always be on hand.
* **MTS Reorder point** — Classic reorder-point policy. Configure the **reorder point** (stock level that triggers a new order) and the **reorder quantity**.
* **MTS Reorder point + AI** — Same as the standard reorder point, but Flowlity dynamically adjusts the reorder point using AI-based demand signals.
* **MTO** — Make-to-order. No buffer is held; orders are placed against confirmed demand only.

Adjust these defaults to match your organization's risk tolerance and service-level targets. Products that need different parameters can be individually overridden from the [Products](/settings/products.md) settings.

### Learn more

* [Inventory strategies](/concepts/inventory-strategies.md) — The five strategies and when to use each.
* [Buffer policies and safety stock](/concepts/buffer-policies.md) — How buffer parameters, service levels, and the Flowlity Min/Max corridor work.
* [Configure your inventory strategy](/how-tos/configure-inventory-strategy.md) — Step-by-step strategy and buffer policy setup.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flowlity.com/settings/buffer-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.