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

# How Lantern fits into buying

> See how Lantern keeps your inventory plan current, where your judgment matters, and how reviewed recommendations reach your buying workflow.

Keeping the plan current for thousands of items is difficult when customers,
suppliers, and branch needs keep changing.

Lantern uses your business data to forecast demand and replenishment time, then
recommends inventory targets. Your team sets the planning policy and reviews
the changes that need judgment. The targets reach your buying workflow through
your configured ERP export.

## Three decisions behind the plan

| Buying decision | What to consider in Lantern |
| - | - |
| **Should we routinely stock this item?** | Demand history, customer needs, and your stocking policy. A product ordered only for a specific job can need a different approach from a shelf item. |
| **How much coverage does it need?** | Expected demand, replenishment lead time, time between orders, and the buffer chosen through your service policy. |
| **Where should we hold it?** | The location serving the demand and its replenishment route. A branch supplied by a nearby DC faces a different wait from a DC buying from the manufacturer. |

These questions explain why the same item can need different targets at two
locations. A healthy company-wide total can still leave the branch that serves
the customer short.

Read [understand Min/Max](https://docs.lanternhq.com/concepts/inventory-targets.md) for a worked example of
coverage and [lead times](https://docs.lanternhq.com/guides/lead-times.md#which-part-of-a-transfer-route-does-this-describe)
for the difference between supplier and branch replenishment.

## What Lantern handles, and what you add

Lantern keeps recommendations up to date across your catalog, so buyers can
focus on the decisions that need their knowledge rather than reviewing every
item by hand.

You bring the information and decisions that the history may not contain:

* **A major customer has stopped buying.** Investigate the forecast and use a
  temporary adjustment when you need the target to reflect that change now.
* **A low-cost fitting must stay available.** Review its class and service
  policy, or use a boundary for an item-specific inventory floor.
* **A supplier announces a change before your PO history reflects it.** Review
  the [lead-time forecast](https://docs.lanternhq.com/guides/lead-times.md) and use a temporary override if
  the known change needs to affect planning now.
* **A new item replaces an established product.** Use [Item Links](https://docs.lanternhq.com/features/item-links.md)
  to carry the relevant demand to the replacement.
* **A whole product group looks wrong.** Check the shared inputs and policy
  with Lantern rather than maintaining a separate override on every item.

The [override guide](https://docs.lanternhq.com/guides/overrides-and-boundaries.md) helps you choose between
an exact exception, a boundary, and a change to a planning input.

## Your first review establishes the baseline

Review every item at least once to confirm that the plan fits your business
and establish the targets your team accepts. Work through suppliers or product
groups in manageable batches, starting with some items you know well.

Many recommendations involve small changes. Use the table's variance filters
to group changes you are comfortable accepting, then
bulk approve that group. This leaves more of your review time for the big
differences, stocking decisions, and business exceptions where you can make
the greatest impact. Resolve unexplained patterns before extending the rollout.

Manual approval records the reviewed target used as the baseline for ordinary
auto-approval. [Approval rules](https://docs.lanternhq.com/guides/approval-rules.md) can then accept qualifying
changes within the tolerances your team chooses. Approval and
[applying the targets in your ERP](https://docs.lanternhq.com/guides/min-max.md#apply-reviewed-targets) are separate
parts of the process.

Follow [your first inventory review](https://docs.lanternhq.com/getting-started/first-review.md) for the
filtering, bulk-approval, and closer-review steps.

## The ongoing routine focuses on exceptions

After the initial review, use [Priority Center](https://docs.lanternhq.com/guides/priority-center.md) to
find changes requiring attention. Investigate the items outside your approval
policy, check expiring exceptions, and add new customer or supplier information.

For example, an item you approved last time can return when its proposed
maximum moves beyond the allowed change from your last manual approval. That
is a new decision about the plan, rather than a reason to repeat the entire
catalog review.

Your team's recommendation and export schedules determine when changes appear
and reach the ERP. Agree on that routine with your Lantern contact during setup.

## Where do purchase orders happen?

If your team buys in the ERP, continue that purchasing process using targets
applied through the configured export.

Min and Max describe a replenishment policy. They are different from an order
quantity: what you buy also depends on stock, open supply, commitments, and
purchasing constraints. Approving a target does not create a purchase order.


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