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

# Issues

> What issues are and how teams use them in Atlios.

An issue is a catalog or storefront problem that Atlios found during a scan.
Issues are the main review surface for catalog quality work.

Instead of asking teams to inspect raw scan output, Atlios turns findings into
issues with context: what was found, where it was found, how important it is,
and what action may be available.

## What an issue includes

An issue usually answers:

* What needs attention.
* Which product, variant, image, or storefront page is affected.
* How severe the problem is.
* Whether a guided fix is available.
* Whether the issue has been suppressed for a valid exception.

## One issue per problem

When more than one source flags the same field on the same product, for example
your Shopify scan and [Google Merchant Center](/product/google-merchant-center),
Atlios shows it as a single issue with a badge for each source. It is counted
once across the inbox, the dashboards, and the agent, so your numbers reflect
real problems rather than duplicate detections.

## Where to review issues

Use the [issue inbox](/product/issue-inbox) to filter, group, open, and act on
issues. The inbox starts with active issues so your team can focus on current
work.

## How to work through issues

Start with higher-[severity](/concepts/severity) issues, then move through
lower-severity ones. Some issues can be [fixed directly in Atlios](/guides/fix-product-issues). Others
require manual updates in Shopify followed by another scan.

For status definitions, see [Issue lifecycle](/concepts/issue-lifecycle).

## Issues are not always mistakes

Some issues represent store-specific exceptions. If your team intentionally
allows a condition for a product or store, use a
[suppression](/concepts/suppressions) rather than changing the catalog only
to satisfy a rule.