> ## 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 replenishment lead times

> See how PO history informs lead-time forecasts, review the delivery evidence, and use a temporary override when you know about a change before the data.

**Smart Lead Times** uses purchase-order receipt history to forecast how long
replenishment takes. As supplier performance changes, that history helps
Lantern update the delivery time behind your inventory targets. Longer lead
times can mean your stock needs to cover a longer wait.

You do not need to manually update lead times for every late delivery. One late
PO does not necessarily establish a new delivery pattern. Use the forecast and
its recent POs to understand the recommendation; add an override when you have
information that is not yet reflected.

## Read the recommendation

1. Find the item, supplier, and purchasing location. Use **Supplier Name**,
   **Supplier ID**, and **Location ID** filters to narrow the review.
2. Compare **Current Lead Time (Days)**, **New Lead Time (Days)**, and
   **Lead Time Variance (Days)**.
3. Check whether an active override is holding a chosen value.
4. Select **Forecast** on the row to open **Lead Time Forecast Details**.

A longer forecast is worth investigating, but it does not by itself establish
whether the supplier has a continuing slowdown or a temporary disruption.

## What should I look for in Forecast?

The detail identifies the item, supplier, location, **Lead Time Forecast**, and
**Last PO**. Use the receipt evidence and source explanation together.

* **Most Recent Purchase Orders** can show **PO Number**, **Supplier**,
  **PO Date**, **Lead Time**, and **Status**, with additional receipt or
  location detail where provided.
* **Forecast Based on ERP Standard Lead Time** means the planning supplier's
  forecast uses that standard.

Use the recent POs and the forecast's source explanation to judge whether it
reflects your supply route.

For example, if the forecast increases but your purchasing location has little
receipt history, check the source explanation before replacing it. If you have
a recent supplier notice that the data has not yet captured, an override may
record that exception.

A very long receipt can also reflect an order deliberately placed early for
a later season. Check the PO and business arrangement before treating it as
the supplier's normal delivery performance. Conversely, missing production
time or relevant receipts can make an estimate too short. Bring a concrete PO
example to Lantern when the evidence does not match your experience.

### Which part of a transfer route does this describe?

A supplier's lead time into a distribution center is different from the time
to replenish a branch from that center. For **Transfer** rows, compare
**Replenishment Lead Time** with **Supplier Lead Time into** the source
location. The replenishment value can include transfer and safety days.

Confirm the route before applying a supplier-wide adjustment.

## When should I override a lead time?

Use an override when you know about a change before there is enough PO history
for the forecast to reflect it. For example, a supplier announces a production
shutdown affecting upcoming orders, while recent receipts still reflect normal
delivery times. A temporary override can bridge that initial period.

If slower deliveries are already reflected in the forecast, you can keep
following Lantern's recommendation. An active override holds your chosen value,
so give it a review date and remove it when you want the forecast to guide
planning again.

## Record a one-item exception

1. Select **Override** on the affected row.
2. Choose **Custom** for an exact lead time or percentage adjustment, or
   **Current** to retain the current value.
3. Choose **Temporary (with end date)** for a disruption, set **End Date**,
   and enter an **Override Reason**.
4. Select **Save Override**.
5. Check the displayed value and override history.

Percentage adjustments use **Current Lead Time**, rounded up to whole days.
**Recommended** saves the current recommendation as an override; it does not
remove an override and resume future forecasts.

## Apply the same exception to several items

You can update a group together when the same known change affects several
items. Filter **Supplier Name** or **Supplier ID** and the affected
**Location ID** before opening the toolbar **Override**.

1. Check **Active Filters:**, **Show Details**, and the item count. The action
   includes all filtered items, including other pages. If **WARNING: No Filters
   Applied** appears, cancel and filter the intended group first.
2. Choose **Custom** and enter the total **Lead Time (Days)**, or use **%** /
   **Adjust by percentage** to adjust each item's **Current Lead Time**,
   rounded up to whole days.
3. Choose **Temporary (with end date)**, set **End Date**, and enter an
   **Override Reason** explaining the known change.
4. Select **Apply to All**. Check the applied and skipped counts, then inspect
   a few affected rows and their override values.

An exact value sets the same total lead time on every affected row. A
percentage keeps the differences between rows: an illustrative **+50%**
changes 10 days to 15 and 20 days to 30. Entering an exact **30 days** makes
both rows use 30 days.

For **Transfer** rows, check the replenishment route before applying a
supplier-wide exception. Supplier delivery into a distribution center and
transfer time to a branch are different parts of that route.

## Import lead-time overrides from a file

Use a CSV or Excel file when a known change gives different lead times to many
items. For example, a supplier sends a quote sheet with new lead times for each
item ahead of a production change. Drop the file on the **Smart Lead Times**
table. See [file imports](https://docs.lanternhq.com/reference/file-imports.md) for matching columns,
checking the result, and correcting failed rows.

| Field in Lantern | What to provide |
| - | - |
| **Item ID** | The item's ID in Lantern. |
| **Location ID** | The purchasing location, from a column or one location for all rows. |
| **Supplier ID** | The supplier, from a column or one supplier for all rows. A single supplier's quote sheet does not need a supplier column. |
| **Lead time (days)** | The total lead time to hold, in whole days of 1 or more. |
| **Reason** | The known change, from a column or one reason for all rows. |
| **Expiration** | An end date from a column, or **Permanent** or **Specific date** for all rows. |

Each row saves an exact override for one item, location, and supplier, and
replaces any existing override for that combination. Each row must match an
item, location, and supplier shown on **Smart Lead Times**. As with any
override, choose an end date for a temporary change so the forecast guides
planning again afterward.

After the import, check a few affected rows and their **Override History**,
then [check the inventory impact](#check-the-inventory-impact).

## Return to the forecast

Review the exception at its end date. To end it sooner, open **Override
History** and remove it. For a group, use the same filters, open the toolbar
**Override**, and choose **Remove Overrides**. Review the matching overrides
and confirm removal, then check the lead-time recommendations again.

Saving **Recommended** creates an override at today's forecast value. Use
removal when you want the items to keep following future forecasts.

## Check the inventory impact

Open an affected item in **Min/Max** and select an underlined **New Min** or
**New Max** to inspect the lead time behind the target. Confirm that it reflects
your adjustment before approving; recommendations can take time to update.
Then [apply the reviewed targets](https://docs.lanternhq.com/guides/min-max.md#apply-reviewed-targets)
through your team's export process.

## FAQs

### Does Lantern pick up changes in supplier lead times?

**Smart Lead Times** uses PO receipt history to forecast replenishment time as
delivery patterns change. One late PO does not necessarily establish a new
pattern. If **Forecast** shows **Forecast Based on ERP Standard Lead Time**,
the estimate uses that standard.

An override can bridge new information that is not yet reflected, such as a
newly announced production shutdown. See [when to override a lead time](#when-should-i-override-a-lead-time).


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