> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lanternhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Review safety stock and service levels

> Choose inventory buffers with a clear view of the tradeoff between availability and inventory investment.

Some products need to be ready when the customer walks in. Others can wait for
the next delivery. Safety-stock settings let your team make that availability
decision with a view of the inventory it requires.

Safety stock adds protection when demand or replenishment differs from the
baseline expectation. Giving every item the same extra percentage can leave
too much stock on predictable items and too little protection on uncertain ones.
The buffer depends on uncertainty as well as your chosen service target.

A service-level target expresses the availability you want to plan for. Higher
targets generally require more inventory investment to reduce stockout risk.
They are planning targets, not a guarantee that every future demand will be met.

## Choose the availability you need

Start with the business consequence of running out. A small fitting can hold up
a customer's whole order even if the fitting itself costs little. A large,
infrequently ordered item can have a different service expectation and space
constraint.

Use [product classes](https://docs.lanternhq.com/guides/product-classification.md) to group items according
to your priorities, then preview the service targets for those classes. A
higher target generally adds protection and inventory, but the same target
does not imply the same buffer on a predictable and a volatile item.

The preview gives buying, sales, and finance a common way to discuss the
tradeoff: which availability objective are we choosing, and what inventory
commitment does it imply?

## For buyers: review an item's buffer

Open **Safety Stock** and confirm the item and location. Review its product
class, service-level target, and displayed safety-stock context.

When a buffer looks unexpected, ask two questions: does the product have the
intended class, and does that class have the intended service-level target?
Check [Product Classification](https://docs.lanternhq.com/guides/product-classification.md) before changing
the buffer to compensate for a classification decision.

For a change affecting a whole class, ask your Lantern admin to preview a new
service-level target. Include the class, a few example items, and why the current
availability target needs to change. For one item, use the
[item-specific exception](#handle-an-item-specific-exception) below.

### Handle an item-specific exception

Use a class-level setting when the policy should apply to the class. Use an
item exception when you have a reason specific to the affected item or location.

For example, one product may need greater availability for a customer
commitment even though its class has a lower service target.

1. In **Safety Stock**, select **Override** on the item's row and confirm the
   item and location.
2. Choose **Set service level** to enter a target percentage and preview the
   resulting safety-stock quantities. Choose **Custom** when you want to set
   the buffer quantities yourself, and enter the Min and Max safety stock in units.
3. Choose **Temporary (with end date)** for a time-limited exception, or
   **Permanent** for an ongoing decision. Enter an **Override Reason**.
4. Select **Save Override**.
5. Check the saved adjustment, duration, and resulting buffer on the item.

To change a group together, filter the table and use the toolbar **Override**.
Check the item count before selecting **Apply to All**. **Set service level**
uses each item's own demand to work out its buffer; an exact **Custom** entry
sets the same quantities across the group.

## For admins: set class service levels

Admins set the shared availability target for each product class in
**Service Level Settings**. Review the classes and items affected by a change.

1. Open **Service Level Settings**.
2. Review the target for each configured product class and change the values
   your team intends to use.
3. Select **Show Impact Preview** to inspect the scenario before applying it.
4. Compare **Lead Time Impact**, **Demand Safety Stock**, and **Financial
   Impact** with the availability objective. Keep days, units, and inventory
   dollars separate when reading the preview.
5. Select **Apply Changes** to save changed targets. With unchanged settings,
   the available action can be **Calculate Safety Stock**.

For example, you might investigate a higher target for a strategically important
class. Use the preview to understand the inventory commitment rather than
treating the highest target as automatically the best choice.

If many items seem to carry the wrong buffer, review the class policy and a
few representative items first. An item-by-item Min/Max override can
hide a shared setting that needs attention.

## Check the result

When the updated recommendations are ready, inspect a few items. Check that the class, target, and
resulting buffer reflect the policy you intended.

Follow your team's [export process](https://docs.lanternhq.com/guides/min-max.md#apply-reviewed-targets)
to apply the reviewed targets in your ERP.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.