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

# Plan new and replacement items with Item Links

> Use a previous or similar item's demand to plan a new product. Choose between Replacement and Reference, set the percentage, and review the forecast.

A new item can have little sales history even when you already know who will
buy it. It might replace a model you have sold for years, or be similar to an
established product. **Item Links** lets Lantern use that existing demand when
planning the new item, so you do not have to wait for it to build a history
from scratch.

## When should I use an item link?

* **A product is being replaced.** Customers will buy the new model instead
  of the old one. Use **Replacement** to move the relevant demand to the new
  item.
* **A new product needs a starting point.** An existing equivalent item is a
  useful guide, and you will continue selling it too. Use **Reference** to
  plan the new item from that demand without taking it away from the existing
  product.

Choose a source that reflects the customers and buying pattern you expect.
A similar description alone does not mean two products will sell the same way.
If you need a specific stock target for a short event instead, use a
[temporary override](https://docs.lanternhq.com/guides/overrides-and-boundaries.md).

## Choose Replacement or Reference

In the link form, **Source** is the item demand comes from. **Target** is the
item demand goes to.

| Choice | What happens to demand | Typical use |
| - | - | - |
| **Replacement** | Moves the chosen share from source to target. The source keeps any remaining share, and the target keeps its own demand too. | An old SKU is being replaced by a new model. |
| **Reference** | Copies the chosen share to the target. The source keeps its demand. While the link is active, the target uses the referenced demand **instead of its own**. | A new item uses an established equivalent as its starting point. |

For example, **100% Replacement** moves all of the old item's demand to the
new item. **50% Replacement** moves half and leaves half with the old item,
which can help when demand is expected to split during a transition.

With **50% Reference**, the new item uses half of the reference item's demand
as its planning history. The reference item still keeps all of its demand.
Review this choice as the new product develops its own sales pattern.

Link items with the same unit of measure. The percentage controls how much
demand to use; it does not convert packs into individual units.

## Create a link

If **Item Links** is missing from your sidebar, ask your Lantern admin to add
the page to your account.

**1. Choose the two items**

Open **Item Links** and select **Add Link**. Search for the **Source**
item with the useful history, then the **Target** item you want to plan.
For a replacement, the old item is the source and the new item is the target.

**2. Choose where the link applies**

Use **All locations** for a product relationship that applies throughout
your business. Use **Specific locations** to choose the **Source location**
and **Target location** for a local change.

A location-specific link takes priority over all-location links for the
same source item at that source location.

**3. Choose the relationship and percentage**

Select **Replacement** or **Reference**, then enter **Percentage moved**
or **Percentage copied**. Use 100% for the full demand or a smaller
percentage for a share. If one source has several replacements, their
combined percentage cannot exceed 100%.

**4. Record why you are linking the items**

Choose **Permanent** or **End date** under **Duration**. Enter a **Link
reason** that another buyer will understand, such as the model transition
or why this product is a useful reference.

**5. Review and create**

Check the items, locations, direction, and percentage in **Live Preview**.
Resolve any message about an incompatible or conflicting link, then select
**Create link**.

## Import links from a file

Use a CSV or Excel file when you have many links to add or update together,
such as a product line moving to new item numbers. Drop the file on the
**Item Links** table, or on the empty page before you have any links. 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 |
| - | - |
| **Source Item ID** | The item demand comes from. Required. |
| **Target Item ID** | The item demand goes to. Required. |
| **Source Location** | For a location-specific link, provide both locations. Leave both blank, or use **All locations** in both, for a link at all locations, the default. A row with only one location fails. |
| **Target Location** | Provide it together with **Source Location**, or leave both blank. |
| **Relationship** | `Replacement` or `Reference`. Optional; the default is **Replacement**. |
| **Weight (%)** | The share of demand, from 0.01 to 100, written as `50` or `50%`. Use a column or one value for all rows; the default is **100%**. |
| **Reason** | Why the items are linked, from a column or one reason for all rows. Required. |
| **Expiration** | An end date from a column, or **Permanent** or **Specific date** for all rows. Required. |

Each row adds a link, or updates the active link with the same source item and
location and target item and location. Both items must exist in Lantern with
the same unit of measure.

Lantern checks the whole file against your existing links, using the same rules
as **Add Link**. A source item's Replacement links from one source location,
including the ones already in Lantern, cannot move more than 100% of its demand
in total. If rows would take a source over 100%, those rows fail and the rest of
the file still applies. Lower or remove an existing link first when you want to
move that share to a new target.

To change many existing links, select **Export**, edit the rows you want to
change, and import the workbook. Before exporting, make sure **Source
Location**, **Target Location**, **Relationship**, **Weight**, **Reason**, and
**Expiration** are visible, because the export includes only visible columns. Delete rows for
expired links, which fail because their date has passed.

A row that matches an existing link exactly changes nothing, though it is
counted as **Updated**, so re-uploading an unedited export leaves your links
as they are.

### Links from your ERP

Links imported from your ERP show **ERP** as their **Origin**. In a file:

* A row that matches an ERP link exactly leaves it as an ERP link.
* A new or changed row replaces these ERP links from its source item, as
  **Add Link** does:

  * the ERP link between the same two items and locations;
  * for a Replacement, the source's other ERP Replacement links at that source
    location;
  * when the row's source location is all locations (the default), every
    location-specific ERP link from that source item, including References.

  Lantern saves your row as a manual link, and later ERP imports do not bring
  back the links it replaced while it is active.
* To keep one of those other ERP links, include its row unchanged in the same
  file. Lantern keeps it as a manual link with the changed row's reason.

## Check the result

Confirm the relationship in **Item Links**, then open the affected item's
[demand forecast](https://docs.lanternhq.com/guides/forecast.md). The forecast shows associated item links
and the demand coming from or moving to other items.

Recommendations can take time to update after a link is saved. When the updated
targets are ready, review the affected items in **Min/Max** and
[apply the reviewed targets](https://docs.lanternhq.com/guides/min-max.md#apply-reviewed-targets).

## Review the link as the products change

Use **Edit** on an active manual link to change the relationship, percentage,
duration, or reason, then select **Save changes**. Use **Remove** when the link
is no longer appropriate. Check the forecast and targets again after a change.

For a Reference, ask whether the new item's own history is now a better guide.
For a Replacement, check whether the expected split between old and new
products still makes sense. Revisit temporary links at their end date and
confirm the resulting forecast.

For links imported from your ERP, make lasting changes in the ERP. A link
removed only in Lantern can return when it is imported again. A manual link
that [replaces an ERP link](#links-from-your-erp) stays in place.

## FAQs

### Can I use an old or similar item's demand for a new product?

Yes. Use **Replacement** when customers will buy the new item instead of the
old one. Use **Reference** when an existing item is a useful starting point
and will continue selling too. See [choose Replacement or Reference](#choose-replacement-or-reference)
for what happens to each item's demand.

### Does an item link move stock or change open orders?

Links change the demand used for planning. Use your normal purchasing or
transfer process to change open orders or move physical stock.


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