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

# Classify products for inventory planning

> Group products using business criteria so you can review them and choose service-level targets by class.

Which products matter most to keep available? A costly item sold once for a
project can lead a revenue ranking. A low-cost fitting bought repeatedly by many
customers may matter more to everyday service. Your classification criteria
determine which of those signals the plan emphasizes.

Product classification groups your catalog using the business measures you
choose. Your team then sets a service-level target for each class, connecting
that ranking to the inventory investment you are willing to make.

Use **Product Classification** to understand an item's class. Your organization
can then use class-based [service-level targets](https://docs.lanternhq.com/guides/safety-stock.md) to make
different inventory choices for different groups of products.

**Buyers** review how items are classified. **Admins** choose the shared ranking
criteria and class distribution. If a group looks misclassified, bring your
admin a few item examples and explain which business priority the ranking misses.

## Understand the ranking criteria

| Criterion | Measure |
| - | - |
| **Invoice Hits** | Number of invoice occurrences |
| **Volume (Units)** | Quantity sold in the item's base unit of measure |
| **Customer Count** | Number of unique customers |
| **Profit Margin (\$)** | Profit dollars, rather than a margin percentage |
| **Revenue (\$)** | Revenue dollars |

For example, ranking by revenue can produce a different group of A items than
ranking by customer count. Choose criteria that reflect the decision your team
wants the classes to support.

A Lantern class can differ from the ABC class in your ERP when the criteria,
weights, analysis period, or ranking scope differ. Compare those choices before
treating the difference as an error.

## For admins: configure classification

Open **Classification Settings** to change shared ranking criteria. Review the
scope before applying them; a filtered dashboard view does not necessarily
limit the ranking population.

> [!WARNING]
>
> Changing classification mode can clear existing classification overrides
> affected by the change. The dialog requires acknowledgement. Switching back
> does not restore the cleared overrides.

1. Open the classification settings and review **Ranking Criteria**. When
   combining criteria, make the weights total 100%.
2. Choose the **Classification mode**: **Item** assigns a shared class across
   locations; **Item-location** ranks items within each location.
3. Set **Analysis Period** in months, **Number of Classes**, and
   **Class Distribution (%)**. The distribution specifies the percentage of
   products assigned to each class and must total 100%.
4. Select **Show Impact Preview** and inspect how assignments would change.
   Read the scope information alongside the impact counts.
5. Review any mode-change warning, then select **Apply Changes**. With unchanged
   settings, the available action is **Classify**.

## Check the planning result

Inspect a few representative items after classification. Do their classes fit
the criteria and location scope you chose? Then review the service-level targets
assigned to those classes in **Safety Stock**.

A class change and a service-level decision are connected, but they answer
different questions. The class expresses your chosen ranking; the service-level
target expresses how much availability you want to plan for that class.


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