# Triage Catalog Issues

The Catalog Issues page helps you identify missing data that affects forecasting and planning. Issues are categorized as **blocking** or **non-blocking** based on their impact on Moselle's ML forecasting models.

## Why Catalog Data Quality Matters

Moselle's AI forecasting models rely on complete, accurate catalog data to generate predictions. Missing fields can:

* **Prevent forecasts from being generated** (blocking issues)
* **Reduce forecast accuracy** (non-blocking issues)
* **Limit filtering and reporting capabilities**

{% hint style="warning" %}
**Rebuild forecasts after fixing issues.** If you have active forecasts or production plans, regenerate them after resolving catalog issues to incorporate the updated data.
{% endhint %}

## Access Catalog Issues

1. Go to **Catalog** from the dashboard
2. Select the **Issues** tab
3. Toggle between **Blocking** and **Non-Blocking** views

## Blocking Issues

Blocking issues **prevent forecasts from being generated** for affected items. These must be resolved before Moselle can create predictions.

| Issue                     | Description                               | Why It Blocks Forecasting                                                                                                                |
| ------------------------- | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| **Missing Unit Price**    | No selling price set                      | Top-down forecasts convert revenue to units using price. Without a price, revenue cannot be translated into unit projections.            |
| **Missing Sales Listing** | No channel listings linked                | Bottom-up forecasts analyze historical sales data. Without linked listings, there's no sales history to learn from.                      |
| **Missing Comparables**   | No comparable products set (for new SKUs) | New products have no sales history. Moselle uses comparable products to bootstrap forecasts for items launched within the last 2 months. |

### Missing Unit Price

**Impact on forecasting:**

Top-down forecasting models (like Bombay) convert revenue targets into unit projections using Average Selling Price (ASP). Items without a unit price cannot be included in revenue-to-unit calculations.

{% hint style="danger" %}
You cannot create a top-down forecast until all unit prices are set in your product catalog.
{% endhint %}

**How to fix:**

1. Click on the item in the Missing Unit Price table
2. Enter the unit price on the item details page
3. Price saves automatically

### Missing Sales Listing

**Impact on forecasting:**

Bottom-up forecasting models (like Rome, Athens, Venice, Hong Kong, London) analyze historical sales patterns at the SKU level. Items without linked channel listings have no sales data for the models to learn from.

**How to fix:**

1. Click on the item in the Missing Sales Listing table
2. Go to **External Listings** on the item details page
3. Click **Link Listings** and connect listings from your sales channels

See [Link a Store Listing](/operations/catalog/edit-item-details.md#link-a-store-listing) for detailed instructions.

### Missing Comparables

**Impact on forecasting:**

New products (launched within the last 2 months) have insufficient sales history for ML models to generate accurate predictions. Moselle uses comparable products as proxies to forecast demand for new items.

{% hint style="info" %}
**Comparable required for new SKUs.** Set a comparable so forecasts can be generated for recently launched items.
{% endhint %}

**How to fix:**

1. Click on the item in the Missing Comparables table
2. Go to **Adjust Forecast** tab on the item details page
3. Under **Product Comparables**, search for similar SKUs
4. Select one or more comparable products

See [Product Comparables](/operations/catalog/edit-item-details.md#product-comparables) for detailed instructions.

## Non-Blocking Issues

Non-blocking issues **reduce forecast quality or limit functionality** but don't prevent forecasts from being generated.

| Issue                         | Description                              | Impact                                                      |
| ----------------------------- | ---------------------------------------- | ----------------------------------------------------------- |
| **Missing Unit Cost**         | No cost per unit set                     | Cannot calculate margins, COGS, or production costs         |
| **Missing Product Line/Type** | No product line or product type assigned | Limits filtering, grouping, and reporting capabilities      |
| **Missing Supplier**          | No supplier linked                       | Cannot generate purchase orders or compare supplier pricing |

### Missing Unit Cost

**Impact:**

* Margin analysis unavailable
* Cost of goods sold (COGS) cannot be calculated
* Production planning cost estimates incomplete

**How to fix:**

1. Click on the item in the Missing Unit Cost table
2. Enter the unit cost on the item details page

### Missing Product Line/Type

**Impact:**

* Cannot filter by product line or type in forecasting views
* Limited grouping options in reports
* AI SKU grading may be less accurate

**How to fix:**

1. Click on the item
2. Add **Product Line** and **Product Type** as custom attributes, or
3. Update these fields directly on the item details page

### Missing Supplier

**Impact:**

* Cannot generate purchase orders for this item
* Supplier price comparison unavailable
* Replenishment recommendations incomplete

**How to fix:**

1. Click on the item
2. Go to the **Suppliers** tab on the item details page
3. Click **+ Add Supplier Price** and link a supplier

See [Suppliers](/operations/catalog/edit-item-details.md#suppliers) for detailed instructions.

## Best Practices

### Prioritize Blocking Issues First

Focus on blocking issues before non-blocking ones. Items with blocking issues are excluded from forecasts entirely.

### Fix Issues Before Generating Forecasts

Resolve catalog issues **before** creating new forecasts or production plans. Fixing issues after forecast generation requires regenerating the forecast.

### Regular Catalog Audits

Check the Issues page regularly, especially:

* After importing new items
* Before major planning cycles
* When onboarding new sales channels

### Bulk Updates via CSV

For many items with the same issue, use CSV import to update in bulk:

1. Export your catalog
2. Fill in missing fields
3. Re-import with **Overwrite** enabled

See [Import Items via CSV](/operations/catalog/import-your-items.md) for instructions.


---

# 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/operations/catalog/triage-catalog-issues.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.