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

# Fix

> How to review, filter, and act on issues in Atlios.

**Fix** is where you review the catalogue issues Atlios found in your store. It
sits in the sidebar with a count of the problem types that are open, so you can
open it in one click from anywhere. Your store home also links into it, already
filtered to the work it describes.

Use it to decide what needs a fix, what needs manual review, and what can be
ignored as an intentional exception.

## The Fix page

Fix is one page, from top to bottom:

* **Start here** is a card for the problem type to work on next. It says why it
  matters and shows how many products it affects, how many Atlios can fix
  (**I can fix**), and how many need you (**Need you**). Its one button opens
  that problem type's page.
* **Your pins** is a slim row with the pins you have earned, and empty circles
  for the ones still to earn.
* The list holds every problem type with something open, grouped by priority,
  such as **High priority**. Under each name, a short line says who does what,
  such as "I can fix 34, and 6 need you". Each row has a **Status** word:
  **I can fix**, **Needs you**, or **Ready for your review**.

At the top of the list, the chips **All**, **I can fix**, **Needs you**, and
**Ready for your review** narrow it, and a search box finds a problem type by
name. **Group by** switches the groups between **Priority** and **Area**, such
as Images or Content. Choose
**Ask Lio** at the top of the page to ask about what you see.

Open a problem type to see examples of what Atlios would change and what it
costs. Choose **Prepare** followed by the number of fixes to start. Then open the fix job to review the
changes. Nothing goes live until you approve it, and you can undo a fix from
Activity. To work through one problem type from start to finish, see
[Fix a problem type](https://docs.atlios.io/guides/fix-a-problem-type.md).

### Keys on the list

On a computer, the list also works from the keyboard. A reminder sits at the
bottom of the list.

| Key | What it does |
| - | - |
| `J` | Moves down to the next problem type. |
| `K` | Moves up to the previous problem type. |
| `X` | Ticks or unticks the problem type you are on. |
| `Enter` | Opens the problem type's page. |
| `F` | Opens the problem types you ticked one after another, like **Review fixes** on the bar at the top of the list. |

`X` only works on a problem type where Atlios can prepare the fixes and none are
being prepared right now. `Enter` leaves a focused button or link to do its own
job. The keys do nothing while you type in a box or have a
menu or dialog open, or while you hold Ctrl, Cmd, or Alt. The reminder is hidden
on a phone.

## The full problem list

To see every problem, product by product, choose **See every problem, product by
product** under the list. The same list opens whenever a link or a filter
names the work you want, such as a link from your store home.

The full list shows active issues by default. The columns are **Product**,
**Problem**, **Priority**, **Status**, **Action**, **Source**, and **Detected**.

Issues from [Google Merchant Center](https://docs.atlios.io/product/google-merchant-center.md) appear here
too, prefixed `GMC:`. Account-level GMC warnings are not in this list. They show
on the Google Merchant Center card on **Integrations**.

The summary at the top shows how many issues are **Open** and how many were
**Resolved 7d**, meaning in the last 7 days.

Beside the list, **Problem types** opens the issue settings, and **More** lets
you export issues and open **Ignored problems**.

## Find the right issues

Use the controls above the full list to narrow it:

* **Search** by product title, rule name, or issue message.
* **Status** to show open, in progress, waiting for Google, resolved, or ignored
  issues.
* **Priority** to focus on critical and high-severity work first.
* **Problem type** to review one type of issue at a time.
* **Source** to focus on issues from Google, Shopify, or the live page.
  An issue flagged by both shows a badge for each and appears once.
* **Group by** to organise the list by problem area, priority, problem type,
  product, item type, product detail, or Google's message. **Problem area** is
  the nine-way breakdown of what kind of problem it is.

**Group by Google's message** puts each issue under the reason Google gave for
it, in Google's own words. The option appears only while the current view
contains Google Merchant Center issues. An issue flagged by both Google and
Atlios is grouped under Google's message, not your check, and anything Google
did not flag collects in one "Not from Google" section at the bottom, so nothing
is hidden. Rows Google flagged also show the markets affected, so you can read a
reason's reach without opening it.

> [!TIP]
>
> For routine reviews, start with active critical and high-severity issues. Then
> move into medium and low-severity batches.

## Open an issue

Open an issue to see:

* The affected product or variant.
* Why Atlios flagged it.
* Which sources flagged it. When more than one source flagged the same field, a
  **Flagged by** section lists each source, with a link to open the issue in
  Google Merchant Center where relevant.
* The most useful details for that check.
* Any available fix action.
* A way to ignore it.
* Recent activity, such as fixes, ignored problems, or reopens.

Some issues also show extra context, such as duplicate products or variants,
off-spec images, or tag patterns that may explain the issue.

## Work through issues

**1. Start with the highest impact issues**

Use the priority and problem type filters to focus the list.

**2. Open the issue**

Read the issue message, affected product, and details.

**3. Choose an action**

Apply a supported fix, review a proposed fix, enter a required value, open
the product for manual editing, or ignore a valid exception.

**4. Let Atlios confirm**

After fixes or Shopify edits, Atlios re-checks the affected products
automatically and resolves issues that no longer apply.

## Available actions

Each issue can show different actions depending on the issue type and status.

> [accordion] Apply or review a fix
>
> Use this when Atlios can prepare a safe change. Some fixes can start
> directly, while others require review before applying.

> [accordion] Enter a value
>
> Use this when Atlios needs a value from you, such as SKU, barcode, or price.

> [accordion] Open an image workflow
>
> Use this for image template mismatch issues that need generated image review
> before publishing.

> [accordion] Generate more images
>
> Use this on a product flagged for too few images to generate extra angles
> for review before publishing.

> [accordion] Ignore an exception
>
> Use **Ignore** when the catalogue state is intentional and should not keep
> appearing as active work. Ignored problems are listed under **More**, then
> **Ignored problems**.

> [accordion] Open product
>
> Use this when the issue is inspect-only or needs a manual Shopify edit.

## Bulk actions

Use bulk actions when several selected issues can be handled the same way.
Atlios shows which issues were started and which ones need individual review.

> [!NOTE]
>
> Some issues cannot be fixed in bulk because they require a decision, a custom
> value, or manual review in Shopify.

Bulk actions can exclude selected issues that are already waiting (verifying),
resolved, ignored, inspect-only, manual-input only, or review-required.

For a focused walkthrough, see [Use bulk issue actions](https://docs.atlios.io/guides/use-bulk-issue-actions.md).


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