# Item Comparables

{% hint style="info" %}
**Quick Answer:** When a new or sparse SKU doesn't have enough data to forecast reliably, Mo borrows demand signals from a similar product already in your catalog — called an **Item Comparable**. You assign the comparable in the Product Catalog, and Mo applies it automatically on the next forecast run.
{% endhint %}

## What Are Item Comparables?

**Item Comparables are products in your catalog that share relevant characteristics with a new SKU** — similar product category, sales velocity profile, channel mix, or launch trajectory. When Mo detects that a SKU has insufficient history to forecast reliably, it identifies the mapped comparable and uses its demand patterns as a proxy.

The result is a forecast that reflects realistic demand expectations for the new product — not a zero, and not a guess.

Mo has direct access to your comparable product mappings as part of his context. This means when you ask Mo questions about a new SKU — reorder timing, expected demand, weeks of stock — he factors in comparable item signals automatically, without you needing to prompt him separately.

***

## When Does Mo Apply Item Comparables?

Item Comparables are used as a fallback in two situations:

| Situation                            | Description                                                                                                                                                                                  |
| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **New Product Introductions (NPIs)** | SKUs that have just launched and don't yet have enough sales data for a reliable forecast                                                                                                    |
| **Sparse items**                     | Products that have been in the catalog but have very limited or inconsistent sales history, often because of distribution gaps, seasonal introductions, or channel-specific pipefill effects |

In both cases, Mo applies comparable item data automatically once a comparable is mapped. No additional configuration is required.

***

## How to Set Up Item Comparables

**Time Required:** 2 minutes\
**Difficulty:** Beginner

Comparables are assigned directly from the Product Catalog at the individual item level.

{% stepper %}
{% step %}

### Navigate to the Product Catalog

Go to **Catalog** in the left sidebar and open the item detail page for the SKU you want to configure.
{% endstep %}

{% step %}

### Find the Comparable SKU Field

Locate the **Comparable SKU** field on the item record.
{% endstep %}

{% step %}

### Search and Select a Comparable

Search for and select the comparable product from your catalog.

**Choosing a good comparable:**

* Same product category and price point
* Similar sales velocity and channel mix
* Comparable marketing support and launch trajectory
* Launched in a similar season

{% hint style="success" %}
If you're replacing an outgoing SKU with a new one, map the outgoing SKU as the comparable — this gives Mo the most relevant demand signal available.
{% endhint %}
{% endstep %}

{% step %}

### Save

Click **Save**. Mo will pick up the mapping on the next forecast run.
{% endstep %}
{% endstepper %}

You can also check or manage comparable mappings conversationally through Mo:

* "What comparable SKU is mapped to \[new SKU]?"
* "Which of my new SKUs don't have a comparable assigned yet?"

***

## What to Expect for New Product Introductions

When a new SKU is added to Moselle and doesn't yet have sufficient history, Mo will:

1. **Flag the SKU as a New Product Introduction** internally
2. **Apply the mapped comparable item's demand patterns** to generate an initial forecast across all relevant channels
3. **Refine the forecast progressively** as actual sales data accumulates for the new SKU

This means new launches enter the planning workflow with a usable forecast from day one — rather than sitting at zero and triggering false stockout alerts or missed reorder signals.

***

## How Mo Uses Comparable Data

Mo has visibility into the following for every SKU with a comparable mapped:

**Launch date** — Mo knows when a SKU entered the catalog and adjusts how much weight to give comparable signals versus actual history.

**Comparable product** — Mo knows which SKU is mapped and references it when answering questions about the new product's expected trajectory.

**Channel mix** — Comparable signals are applied per channel. If the comparable SKU sold primarily through DTC, Mo applies that demand pattern to the new SKU's DTC channel specifically.

### The Transition to Actual History

As the new SKU accumulates its own data — typically after 2–3 months — Mo progressively shifts weight away from the comparable and toward the SKU's actual sales history. This transition happens automatically.

***

## Where to Find It in the Platform

| Action                          | Where                                                    |
| ------------------------------- | -------------------------------------------------------- |
| Assign a comparable to a SKU    | Product Catalog → Item Detail → **Comparable SKU** field |
| Check what comparable is mapped | Product Catalog → Item Detail, or ask Mo in chat         |
| View NPI forecast in context    | Forecasting → Active Plan → filter by new SKUs           |

***

## Troubleshooting Common Issues

| Problem                                      | Solution                                                                                                 | Time to Fix |
| -------------------------------------------- | -------------------------------------------------------------------------------------------------------- | ----------- |
| Forecast still shows zero for a new SKU      | Verify a comparable is assigned in Product Catalog → Item Detail → **Comparable SKU** field              | 1 minute    |
| Comparable mapping not reflected in forecast | Mo applies changes on the next forecast run — wait for the next cycle or trigger a new run               | 2 minutes   |
| New SKU forecast looks unrealistic           | Review whether the assigned comparable has clean, representative sales history                           | 5 minutes   |
| Unsure which product to use as a comparable  | Choose the closest category match at a similar price point, or ask Mo: "Suggest a comparable for \[SKU]" | 5 minutes   |

***

## Tips

* For best results, ensure your comparable products are well-represented in Moselle with clean sales history — Mo draws on this data when forecasting new items.
* Item Comparables work across all channels. If a new SKU is launching into multiple channels simultaneously, Mo will apply comparable signals per channel where data is available.
* If a new product is genuinely unlike anything else in your catalog, reach out to your Moselle account team — additional configuration may help Mo identify the best comparable match.

***

## Frequently Asked Questions

### What happens if I don't assign a comparable to a new SKU?

Mo will generate a forecast based on available data. For a true NPI with zero history, this typically results in a near-zero forecast until enough actuals accumulate. Assigning a comparable gives Mo a meaningful starting point from day one.

### Can I assign more than one comparable?

Each SKU supports a single comparable mapping. Choose the product that most closely reflects the new SKU's expected demand profile. If no single product is a perfect match, the closest category match at a similar price point is usually the best choice.

### How long until Mo switches from comparable data to actual history?

Typically 2–3 months after the first meaningful sales data flows in. Mo blends signals progressively — there's no hard cutover. You can ask Mo directly: "How much of \[SKU]'s forecast is based on comparable data versus actuals?"

### Will changing the comparable mid-cycle affect my active forecast?

Yes. Updating the comparable mapping will be reflected on Mo's next forecast run. If you're mid-cycle and want to preserve your current forecast values, review them before making the change.

***

## Related Guides

{% content-ref url="/pages/KXh7MTxw84WmaJhhHp6g" %}
[How Mo's Forecasting Works](/planning-and-execution/forecasting/how-mos-forecasting-works.md)
{% endcontent-ref %}

{% content-ref url="/pages/9RDig5cQWudNgHK0uKRa" %}
[Special Situations](/planning-and-execution/forecasting/special-situations.md)
{% endcontent-ref %}

{% content-ref url="/pages/Thw9NEHchrwLEq8IMSLH" %}
[Edit Item Details](/operations/catalog/edit-item-details.md)
{% endcontent-ref %}

{% content-ref url="/pages/D2BTtZoIEwFaGlVVWPXZ" %}
[Forecast Best Practices](/planning-and-execution/forecasting/forecast-best-practices.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.moselle.io/planning-and-execution/forecasting/special-situations/item-comparables.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.