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

# Supported fixes

> How Atlios prepares, reviews, applies, and skips fixes for supported issue types.

Atlios offers a fix action only when it can prepare a safe next step for the
issue type. Some fixes update Shopify after you approve them. Others ask you
for a value, send you to the image workflow, or keep the issue as manual
review.

<Warning>
  Review proposed catalog changes before applying them. Fixes can update live
  product, variant, image, and metafield data in Shopify.
</Warning>

## Fix modes

<AccordionGroup>
  <Accordion title="Direct apply">
    Atlios can prepare a deterministic change and start it from the issue. The
    change is still previewed before Shopify is updated.

    Used for issues such as missing featured images, weak image filenames, and
    invalid compare-at prices.
  </Accordion>

  <Accordion title="Review optional">
    Atlios can prepare a suggested change, and you can either apply it directly
    or review the suggestion first.

    Used for AI copy suggestions, metafield assignment fixes, allowed-value
    normalization, and whitespace-only metafield format fixes.
  </Accordion>

  <Accordion title="Review required">
    Atlios can build a patch, but you must review it before applying. This is
    used when the change may affect merchandising intent.

    Product tag anomaly patches use this mode.
  </Accordion>

  <Accordion title="Manual input">
    Atlios needs a value from you before it can apply the change. Use this for
    identifiers and prices that Atlios should not invent.

    Missing SKU, missing barcode, duplicate SKU, duplicate barcode, and zero
    price issues use this mode.
  </Accordion>

  <Accordion title="Image workflow">
    Image template mismatch issues use the image workflow instead of the normal
    fix engine. Atlios builds an image job so you can review generated image
    changes before publishing them back to Shopify.
  </Accordion>

  <Accordion title="Inspect only">
    Some issues do not have a fixer by design. Review the context, update the
    product, variant, Shopify inventory, glossary, or rule settings, then run a
    new scan.
  </Accordion>
</AccordionGroup>

## What Atlios can update

Supported fixes can write these Shopify fields after approval:

* Product title.
* Product description and, when enabled, SEO description.
* Product tags.
* Product vendor or product type when a supported bulk action uses those
  fields.
* Product featured media.
* Variant price and compare-at price.
* Variant SKU and barcode.
* Product and variant metafields.
* Product image alt text.
* Product image filenames.
* Image workflow output for template mismatch issues.

## When a fix is skipped

A skipped fix is not a failed catalog update. It means Atlios checked the issue
and decided there is no safe change to apply right now.

Common skip reasons:

* The issue is no longer in the `Open` state.
* Required issue evidence is missing or stale.
* The product or variant changed since the scan.
* The fixer needs AI and AI is not available.
* Atlios cannot infer a safe value.
* A Shopify metafield type cannot be resolved.
* A proposed AI value is empty, unchanged, or still duplicates another value.
* A deterministic patch would make no effective change.

<Note>
  Skipped fixes stay visible in issue activity so your team can see why no
  change was applied.
</Note>

## Bulk fix behavior

Bulk actions only start issues that can be handled safely as a group.

Atlios excludes selected issues when:

* The issue is already verifying, resolved, or suppressed.
* The issue requires manual input.
* The issue requires review before apply.
* No fixer is available for that issue type.
* Atlios already knows the fixer would make no effective change.

AI bulk fixes run in the background. Deterministic bulk fixes are prepared
immediately, then applied as one grouped fix job.

## Verification after apply

Product and variant fixes usually move from `Verifying` to `Resolved` after the
Shopify update succeeds. A later scan can reopen the issue if the same problem
is detected again.

Cross-catalog fixes, such as duplicate identifiers or duplicate product copy,
stay `Verifying` until the next full scan checks the catalog-wide condition.

## Issue types without automated fixes

These issue types are inspect-only:

* Negative inventory.
* Vendor not in your glossary.
* Product type not in your glossary.
* Tag not in your glossary.
* Option name not in your glossary.
* Option value not in your glossary.
* Unclassified product for metafield assignment rules.

Use the issue context to update Shopify, update your glossary, or adjust your
rules. Atlios re-checks the affected products automatically after the change.