> ## 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.

# When should I use an override?

> Set a temporary stock target for a customer commitment, use boundaries to keep a floor or ceiling, and return to Lantern's recommendations later.

An **override** tells Lantern to use your chosen value instead of its
recommendation for a period of time. Use one when you know something that the
planning data does not yet represent, or when you have made a deliberate
business commitment that the recommendation should respect.

For example, a major customer's project is ending next month.
Recent sales still show the old buying pattern. A temporary target override
can bridge that gap while you review what stock is needed and when the
exception should end.

## What are the main use cases?

| Your situation | Useful action |
| - | - |
| A promotion or customer commitment needs a particular inventory target until a known date. | Set a temporary Min/Max override with an end date matching the event. |
| Your team has decided to retain an item's current targets. | Choose **Current** to hold its current values. |
| You have already chosen different targets for many items in a spreadsheet. | **[Upload the Min/Max targets](https://docs.lanternhq.com/guides/upload-min-max.md)** together as overrides. |
| A target must stay above a floor or below a ceiling while recommendations change. | Set a **Boundary** instead of holding one exact value. |
| A new item replaces an old product or needs a similar item's demand history. | Use **[Item Links](https://docs.lanternhq.com/features/item-links.md)** to plan from that demand. |
| A general policy should change for a whole product class or the business. | Review the relevant planning settings, rather than maintaining many unrelated item exceptions. |

A surprising recommendation is a reason to investigate first. Open **Forecast**,
or select an underlined **New Min** or **New Max** to see why it is recommended.
An existing override or boundary can already be affecting that displayed value.

### One exception or a pattern?

If a single item needs different treatment because of a known event, record
that exception with a reason and review date. If the same concern appears
across a supplier or product group, inspect the shared input or policy first.
For example, a long order interval can explain high Max values across a line;
a service-level choice can explain buffers across a class.

If history appears missing or the explanation still does not fit, bring the
examples to Lantern. An override can handle the immediate business need while
you investigate the cause together.

## Set a temporary Min/Max override

This procedure is on **Min/Max**, also called **Order/Line Points** in some
workspaces. For an exception to replenishment time, see
[when to override a lead time](https://docs.lanternhq.com/guides/lead-times.md#when-should-i-override-a-lead-time).

**1. Open the affected item**

Confirm the item and location, then select **Override** on
the row. Compare the **Current** and **Recommended** values before deciding
which quantity you want to hold.

**2. Choose the value**

Choose **Custom** to enter an exact Min and Max. Choose **Current** if your
intent is to retain the current pair. See the [value choices](#override-value-choices).

**3. Choose an end date and explain the exception**

Under **Override Duration**, choose **Temporary (with end date)** and set
**End Date** to the end of the commitment or disruption. Enter an
**Override Reason** explaining what changed and why this value is needed.

**4. Save and check the target**

Select **Save Override**. Check the new target and its override indicator.
Use the indicator or **Override History** to inspect the saved values,
reason, and expiration.

## When should I use a boundary instead?

A boundary lets Lantern adjust the target within a range. For example,
your team may want a Min of at least one unit for an important fitting. A
**Lower Bound** of one for Min sets a floor while allowing the
target to rise to two or more as demand changes. An exact override of one
would hold that chosen value instead.

ERP stocking restrictions can still keep both targets at zero despite a saved
boundary or override. If the floor does not change the target, check the item's
ERP stocking status with your administrator.

This is a limit on the planning target; keeping that unit physically available
still depends on replenishment and actual demand.

1. Select the row or toolbar **Override**, then open the **Boundary** tab.
2. Under **Min limits** or **Max limits**, enable the **Lower Bound** or
   **Upper Bound** you intend to set and enter the quantities.
3. Review the scope, duration, and reason. Select **Save Boundaries** for one
   item, or **Apply to Selected** / **Apply to All** for a bulk change.
4. Check the resulting target and **Boundary History**.

An **ERP lock in effect** message identifies a separate constraint. Removing a
local boundary does not remove that ERP lock.

## What happens later?

An override holds your chosen value until it ends or you remove it.

* **Temporary:** the override stops being active after its end date. Check
  the recommendation that follows.
* **Permanent:** the chosen value remains until changed or removed. Use it for
  a continuing decision that your team intends to maintain.
* **Return to Lantern's recommendations:** open the active adjustment and use **Remove
  Override**. Check the resulting target and history.

Use **Override History** or **Boundary History** to inspect who made a change,
its reason, and its expiration. History also provides **Edit** and **Remove**
actions.

When the targets are ready, review them in Min/Max and
[apply the reviewed targets](https://docs.lanternhq.com/guides/min-max.md#apply-reviewed-targets).

## FAQs

### What do Recommended, Current, Custom, and % do?

| Choice in the Min/Max override form | Result |
| - | - |
| **Recommended** | Saves the current recommendation as an override. |
| **Current** | Saves the item's current targets as an override. |
| **Custom** | Saves the exact quantities you enter. |
| **%** / **Adjust by percentage** | Adjusts each item's **Current Min/Max**, with results rounded up to whole units. It does not use New Min/Max as its baseline. |

### Can I change several items at once?

Select the items or filter the table, then use the toolbar **Override**.
Check the item count and whether you are applying to selected or all filtered
items before confirming.

**Current** and **Recommended** use each affected item's own values. An exact
**Custom** pair applies the same quantities across the affected set, so use it
only when that is your intent. A percentage change adjusts each item's own
current targets.

If you have a different Min/Max pair for each item in a spreadsheet,
[upload the targets together](https://docs.lanternhq.com/guides/upload-min-max.md) instead of entering them
one by one.

### Do overrides keep following new recommendations?

An exact override holds the chosen value until it ends or you remove it.
Saving **Recommended** also holds the value at the time you save. Use
**Remove Override** to follow future recommendations again, then check the
result. See [duration and removal](#what-happens-later).


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