> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atlios.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Severity

> How Atlios helps teams prioritize catalog issues.

Severity helps teams decide what to review first. It is a prioritization signal
attached to each [issue](/concepts/issues), not a judgment that every store must
resolve every issue in the same way.

Higher-severity issues usually have a stronger chance of affecting operations,
storefront quality, or customer trust. Lower-severity issues may still matter,
but they are less urgent.

## Severity levels

Atlios uses four severity levels:

* **Critical.** Catalog problems that should be reviewed first, such as
  conditions that block product readiness or signal data corruption.
* **High.** Important issues that affect operations or customer-facing
  product content.
* **Medium.** Issues worth addressing in batches as part of a regular
  review.
* **Low.** Informational findings or minor inconsistencies.

## How to use severity

Use severity to plan review order:

* Start with the highest-severity issues in a new scan.
* Fix issues that block product readiness or storefront confidence.
* Review lower-severity issues in batches.
* [Suppress](/concepts/suppressions) intentional exceptions so future scans stay focused.

## Severity and business context

Your team's context still matters. A missing barcode may be urgent for one
operation and less important for another. Atlios gives you the signal; your
team decides the right catalog action.

## Severity can change

As Atlios adds checks and learns more about catalog workflows, severity
definitions may become more precise. Treat severity as a practical review aid,
not as a permanent taxonomy.