Skip to main content
Open a forecast when you want to understand why Lantern expects an item to sell more or less. Sales history tells you what happened. The forecast estimates what is ahead, so it can differ from a simple average of past usage. Your review connects that estimate to the customers and events you know. A seasonal pattern, a completed project, and a customer moving business to another supplier can call for different decisions even when their recent sales totals look similar.

Why not just use average sales?

An average spreads historical sales across a period. That can hide when the demand occurs and whether it is changing. For a seasonal item, compare the forecast with the relevant season as well as the latest months. A forecast can be lower than summer demand and still be higher than last winter. Use the displayed history to challenge the forecast. An unusual order is not automatically a mistake, and a model cannot be assumed to know whether a customer’s project will repeat.

Inspect an item’s demand

  1. On the recommendations page, find the item and location, then select Forecast.
  2. In Demand Forecast Details, confirm the item and the location being shown.
  3. Compare historical demand with the forecast over the periods displayed.
  4. Use the Location and Company views to compare the selected location with the wider demand you are authorized to see.
Start with the location where you are making the stocking decision. Company-wide demand adds context, but a strong company-wide trend may be concentrated at other locations.

Is the forecast the amount I should keep on the shelf?

No. Read the series labels shown in your chart: The service-target estimate is not the complete inventory target. Lead-time buffers, replenishment coverage, boundaries, and overrides can also affect Min/Max. Select an underlined New Min or New Max to see how those factors shape the target. For example, quick replenishment can support a target below a month’s demand because the stock is replaced during that month. Conversely, a low baseline forecast does not mean Lantern has planned no buffer. Compare both the demand and the coverage before deciding whether the target is too high or too low.

Look for an explanation

Was the demand one customer or a broad pattern?

Select historical sales activity in the chart to open Customer Analysis where that detail is available. Some points open Committed orders first; use View customer sales to continue to customer activity. Confirm the period and location in the analysis header. All Locations is broader than the one branch you may be deciding for. Use All Customers when you need the full list. Check whether demand is concentrated in one project or spread across regular customers before deciding on an override.

Plan a new or replacement item

If the item has little history because it is new or replaces another product, use Item Links to bring in relevant demand. Choose Replacement when demand is moving to the new product, or Reference when an existing equivalent is a useful starting point and will continue selling.

Bring in business context

If customer information changes the inventory decision, record a temporary target override with a reason and review date. If the concern affects many items, investigate the shared input with Lantern. The adjustment records your chosen target; the forecast remains evidence for the review.

Check the full recommendation

Demand is one input. A target can also change because replenishment takes longer, your ordering interval changed, or a different buffer is needed. Review lead times, order frequencies, and safety stock when demand alone does not explain the result. Before returning to your shortlist, be able to explain the demand pattern you observed and whether you need an adjustment or further investigation.