What are the main use cases?
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.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.
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.- Select the row or toolbar Override, then open the Boundary tab.
- Under Min limits or Max limits, enable the Lower Bound or Upper Bound you intend to set and enter the quantities.
- Review the scope, duration, and reason. Select Save Boundaries for one item, or Apply to Selected / Apply to All for a bulk change.
- Check the resulting target and Boundary History.
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.