Skip to main content
Atlios can help prepare fixes for supported catalog issues.
Always review the proposed change before applying it. Fixes affect live catalog content and should match your store’s merchandising standards.

​
Fix workflow

1

Open an issue

Open an issue from the issue list.
2

Read the context

Read the affected product or variant context.
3

Choose a supported fix

Choose the supported fix action if one is available.
4

Review the proposed change

Review the proposed change.
5

Apply the fix

Apply the fix when it matches your merchandising standards.
6

Let Atlios verify

Atlios re-checks the product automatically after the fix applies and verifies whether the issue is resolved.

​
Fix action types

Atlios shows only the actions available for the issue you opened.
Atlios can start the fix directly. Use this when the suggested outcome is clear. You still see a preview before Shopify is updated.
Atlios can prepare a suggested change, but you should review it before it updates catalog content.
Atlios needs a value from you before it can apply the change.
The issue needs manual review or editing in the product editor.
The issue needs image workflow review before new images are published back to Shopify.
For a complete reference, see Supported fixes.

​
Image issue fixes

Some image issues use the image workflow instead of the normal fix preview. For example, Wrong image size or format can show an Apply template action.
1

Open the image issue

Open the issue and read which images are affected.
2

Choose Apply template

Atlios creates an image job using the store’s default image template.
3

Review the processed images

Approve, reject, or regenerate image outputs before publishing.
4

Publish approved images

Publish only the images that pass review.
5

Let Atlios verify

Once the images publish, Atlios re-checks the product automatically to verify whether the issue is resolved.
The image job processes and publishes images. Atlios verifies the issue with an automatic re-check after the catalog has changed.

​
Why a fix may be skipped

Atlios may show that a fix was skipped instead of failed. This means Atlios checked the current issue and decided there was no safe change to apply. Common reasons:
  • The product or variant changed since the scan.
  • Required issue evidence is missing.
  • AI is not available for an AI-generated fix.
  • A generated suggestion was empty, unchanged, or still duplicated.
  • A metafield needs a value Atlios cannot infer.
  • A tag patch or filename change would make no effective change.
After manual edits, Atlios re-checks the product automatically and closes issues that no longer apply.

​
When no fix is available

Some issues require manual review or changes in Shopify. Use the issue context to understand what needs to change, update the product or variant, then run a new scan.
Inspect-only issues include negative inventory, several glossary mismatches, and unclassified metafield assignment rules. See Supported checks for each issue type.