Skip to main content
Atlios offers a fix action only when it can prepare a safe next step for the issue type. Every issue type sits in exactly one of four fix modes. Some fixes update Shopify after you approve them, others ask you for a value first, and some issue types have no fixer at all.
Review proposed catalog changes before applying them. Fixes can update live product, variant, image, and metafield data in Shopify.

​
Fix modes

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.
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.
Atlios can build a patch, but you must review it before applying. This is used when the change may affect merchandising intent, when the value came from outside your store, or when a Google-only fix would also change your storefront.Product tag anomaly patches, missing barcode, and most Google Merchant Center fixes use this mode.
Atlios needs a value or a choice from you before it can apply the change. Use this for identifiers and prices that Atlios should not invent.Missing SKU, missing GTIN, duplicate SKU, duplicate barcode, zero price, and sales-channel issues use this mode.Image issues are manual input too, but they route to the image workflow rather than writing a field. Atlios builds an image job so you can review the generated images before they are published back to Shopify. Image template mismatch, oversized images, and subject-position issues all work this way.
Some issues do not have a fixer by design. Review the context, update the product, variant, Shopify inventory, catalog standards, or rule settings. Atlios re-checks the product on its own.

​
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.
  • Product SEO title.
  • Product status.
  • Product category, and the collections a product belongs to.
  • Collection description and collection SEO fields.
  • Image workflow output for image template, size, and position 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 Atlios last checked it.
  • 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.
Skipped fixes stay visible in issue activity so your team can see why no change was applied.

​
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. The issue can reopen if Atlios detects the same problem again later. Cross-catalog fixes, such as duplicate identifiers or duplicate product copy, stay Verifying until Atlios next checks the whole catalog, within a week.

​
Issue types without automated fixes

These issue types are inspect-only:
  • Negative inventory.
  • Vendor isn’t an approved value.
  • Product type isn’t an approved value.
  • Tag isn’t an approved value.
  • Option name isn’t an approved value.
  • Option value isn’t an approved value.
  • Unclassified product for metafield assignment rules.
Use the issue context to update Shopify, update your catalog standards, or adjust your rules. Atlios re-checks the affected products automatically after the change.