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

# Run your first inventory review

> Review your catalog once, approve straightforward changes in groups, and focus your close review on the target changes and stocking decisions that matter most.

Your team's first review covers every item at least once. It helps you confirm
that Lantern's targets fit how you buy and serve customers, and records the
targets your team accepts as the baseline for future changes.

Work through a familiar supplier or product group at a time. Check some items
you know, use filters to approve straightforward changes in groups, then give
the bigger differences a closer look. Each item gets a review decision, while
the depth of investigation reflects the decision's impact.

Use **Min/Max** or **Order/Line Points** for this review. If you are new to the
terminology, read [understand your inventory targets](https://docs.lanternhq.com/concepts/inventory-targets.md)
first. Approval records your review; [export](https://docs.lanternhq.com/guides/min-max.md#apply-reviewed-targets)
is the separate step that applies the targets to your buying process.

## 1. Choose a focused view

Open the recommendations page. Choose the location you want to review, then
narrow the table to a supplier or product group you know well.
Open **Columns** if you need to show the relevant variance or stocking-status
fields.

Choose filter values or a sort direction in the column header's dialog, then
select **Apply**. Keep the **Current** and **New** target columns visible together.
In **Order/Line Points**, these are **Current Order Point**, **Current Line Point**,
**New Order Point**, and **New Line Point**. Current values are the imported
targets; New values include applicable saved overrides and boundaries.

Starting with a small group makes it easier to compare Lantern's recommendation
with your own knowledge of customers and suppliers.

## 2. Approve small changes in groups

Once you have checked some familiar recommendations, use the table to group
the changes you are comfortable accepting together. Many items need only a
small adjustment, so you can often clear a large part of the review list here.

1. Open the **Actions** column filter, choose **Unapproved**, then select
   **Apply** to focus on work still awaiting a decision.
2. Agree on the percentage changes your team is comfortable accepting.
   In **Max Variance (%)**, use **Between** to set that range, then select
   **Apply**. In **Order/Line Points**, use the percentage **Line Point Variance**
   column. Include small increases and decreases. Where your table provides
   **Max Variance (\$)** or dollar **Line Point Variance**, add a dollar range
   to narrow the group.
3. Review the filtered group against its **Current** and **New** targets.
   Where **Stocking Status** is shown, filter out **Discontinue** and
   **Start Stocking** for this batch. Keep known business exceptions for
   separate review.
4. Select the toolbar **Approve** and choose **Filtered** in the dialog.
   Confirm the group and item count, then select **Approve \[n] Items**.
5. Check the approval result. Clear the batch's variance and stocking-status
   filters, keeping **Unapproved** and the supplier or location you are reviewing,
   to see the decisions that remain.

A small percentage change can still be expensive on a high-value item. Give
higher-cost items a closer review before including them in a bulk approval.
The ranges are review choices for this batch; [auto-approval rules](https://docs.lanternhq.com/guides/approval-rules.md)
set the policy for future changes.

## 3. Focus on the biggest differences

Work through these three groups. Each surfaces a different decision.
If your workspace does not include **Stocking Status**, start with target
variances and follow your team's process for reviewing stocking changes.

| Review group | How to find it | What you are deciding |
| - | - | - |
| Largest target changes | Sort **Max Variance (%)**, or **Max Variance (\$)** where shown. In Order/Line Points, use the corresponding Line Point columns. Inspect increases and decreases, applying each sort choice. | Does the size of the change make sense given demand, supply, and inventory investment? |
| Discontinue recommendations | Filter **Stocking Status** to **Discontinue**. | Is it appropriate to stop routinely stocking the item, or is there business context that supports continuing? |
| Start-stocking recommendations | Filter **Stocking Status** to **Start Stocking**. | Does the demand justify holding inventory at this location? |

A large percentage change can have a small dollar impact on a low-value item.
A modest percentage change on an expensive item can matter more to your working
capital. Consider the size of the change and the item's cost when choosing
what deserves your attention.

Include a familiar, ordinary item alongside the largest changes. The top of a
variance sort can concentrate unusual project items and old exceptions; it is
useful for finding risk, but does not represent every recommendation.

**Discontinue** asks whether the item should stop being routinely stocked at
this location. It does not mean dispose of the existing units or delete the
product. A 0/0 target ordinarily means no standing Min/Max stock target; check
your team's customer-order process and any separate ERP stocking statuses.

**Start Stocking** asks whether holding stock is justified. An item can already
have units on hand without an ongoing replenishment target, so this label does
not mean that no inventory exists.

## 4. Inspect one item's forecast

Choose an item from your shortlist and select **Forecast**. Start with the
location you are reviewing before using the **Company** view for wider context.

You can also select an underlined **New Min** or **New Max** in the table to
see how Lantern arrived at the target. Check any override indicator before assuming the
displayed New value is an untouched recommendation.

Look for a reason behind the change:

* Is recent demand recurring, seasonal, or concentrated in a one-off order?
* Do you know about a customer starting or ending a project?
* Would a supplier disruption or a longer replenishment time explain the target?
* Is an existing override or boundary affecting the result?

For example, two items can sell the same total quantity while telling different
stories. One large project order raises the question of whether that job will
repeat. Smaller orders spread across months and customers suggest a different
pattern. Open the customer activity behind the history before treating equal
sales totals as equal future demand.

Use [review demand forecasts](https://docs.lanternhq.com/guides/forecast.md) for a closer walkthrough. A
forecast is evidence for the decision; your customer and supplier knowledge
can add context the available data does not contain.

## 5. Make a decision you can explain

Choose the next action based on what you learned:

| Your conclusion | Next action |
| - | - |
| The recommendation fits the evidence and your business context. | Approve the item as described below, then [apply the reviewed targets](https://docs.lanternhq.com/guides/min-max.md#apply-reviewed-targets). |
| You have a specific reason to use a different target. | Apply an [override or boundary](https://docs.lanternhq.com/guides/overrides-and-boundaries.md) with an appropriate duration and reason. |
| The same concern appears across a product group. | Check shared lead times, ordering cadence, classification, and service policy before overriding items individually. |
| You cannot explain the recommendation yet. | [Investigate its inputs](https://docs.lanternhq.com/guides/min-max.md#understand-an-unexpected-target) and bring the specific example to your Lantern contact. |

For example, if an unusually large customer project has ended, a recent sales
spike may not represent recurring demand. Use that fact to investigate the
forecast and decide whether a temporary adjustment is justified. Do not assume
every spike is a mistake or every large recommendation needs an override.

## 6. Check your result and continue

Confirm the intended target, active adjustment, and approval state before moving
on. If you made an adjustment, check the displayed value and its history.

If the item needs manual review and its row shows **Approve**, select that
row's **Approve** button after completing the review and intended adjustments.
Check the resulting approval state. **Auto-Approved** indicates the tolerance policy applied.
An active override can also give an item an approved status; that is separate
from a manual approval snapshot. Check **Last Manual Approved**, when shown,
to inspect the last manually reviewed targets.

Continue with [apply reviewed targets](https://docs.lanternhq.com/guides/min-max.md#apply-reviewed-targets)
to apply reviewed targets through your export path.

Work through the rest of the catalog in manageable groups until every item has
been reviewed. Approve straightforward groups together and investigate the
remaining big differences or exceptions individually.

After that, [Priority Center](https://docs.lanternhq.com/guides/priority-center.md) and
[auto-approval rules](https://docs.lanternhq.com/guides/approval-rules.md) help you focus on changes needing
attention. See [the ongoing buying routine](https://docs.lanternhq.com/getting-started/how-lantern-fits.md#the-ongoing-routine-focuses-on-exceptions).


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