# Issue lifecycle
Source: https://docs.atlios.io/concepts/issue-lifecycle

What issue statuses mean and how issues move from open to resolved.

Issue status tells you where an issue is in the review and resolution process.

## Statuses

<AccordionGroup>
  <Accordion title="Open">
    Atlios is seeing the issue and it still needs review or action. This is the
    starting state for any issue a scan or Google Merchant Center surfaces.
  </Accordion>

  <Accordion title="Verifying">
    A fix, image workflow, or manual action has started, and Atlios is waiting
    for confirmation. Product and variant issues usually resolve after the
    Shopify update succeeds. Cross-catalog issues, and issues that Google needs
    to re-review, stay verifying until the next scan or sync confirms the
    condition is gone.
  </Accordion>

  <Accordion title="Resolved">
    Atlios no longer sees the issue, or an approved fix landed successfully.
  </Accordion>

  <Accordion title="Suppressed">
    Your team marked the issue as an intentional exception. Suppressed issues
    are kept for history, but they are not treated as active work.
  </Accordion>
</AccordionGroup>

## How issues move

Most issues follow this path:

<Steps>
  <Step title="Open">Atlios finds the issue during a scan or sync.</Step>

  <Step title="Action starts">
    You apply a supported fix, start a workflow, edit the product, or suppress
    the issue.
  </Step>

  <Step title="Verifying">
    Atlios waits for the fix, workflow, or next scan to confirm the issue is
    gone.
  </Step>

  <Step title="Resolved">
    A scan or action confirms the issue no longer needs active attention.
  </Step>
</Steps>

## Verification stages

Open an issue and the activity section shows how far the change has travelled:

* **Action started** and **Verifying**: the fix or workflow ran, and Atlios is
  waiting for confirmation.
* **Fixed**, **Cleared in Shopify**, or **Google accepted it again**: how the
  issue closed. Atlios only says it fixed something when the fix came from
  Atlios. A clear on Google's side or in Shopify is labelled as such, with the
  date Atlios observed it.
* **Live page**: whether your storefront is showing the value. This row is the
  current state with the date of the last check, not a milestone, so it can move
  backwards if a later check cannot confirm the value.

<Note>
  Live page checks cover the meta title and meta description only, so the row
  appears on those issues and not on others. You can always see a product's live
  page status on its **Search performance** section. Google re-checks updated
  items on its own schedule.
</Note>

## One issue, one or more sources

The same problem can be flagged by more than one source. If your Shopify scan
and Google Merchant Center both flag the same field on the same product, Atlios
treats it as **one** issue with both source badges, not two separate rows. It
counts once everywhere, and resolving it clears both signals.

## Reopened issues

An issue can reappear if a later scan finds the same problem again. This can
happen when catalog data changes, a product is edited, or a previous fix no
longer applies.

<Tip>
  Use the issue activity section to understand when an issue was first seen,
  fixed, suppressed, reopened, or moved into verifying.
</Tip>


# Issues
Source: https://docs.atlios.io/concepts/issues

What issues are and how teams use them in Atlios.

An issue is a problem Atlios found in your catalog, in Google Merchant Center,
or on a live product page. 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

Start at the [issue inbox](/product/issue-inbox), the store's front door for
quality work. It sits in the sidebar as Fix, carries a count of the open work,
and lets you filter, group, open, and act on issues. Your store home reads your
latest scan and links into the inbox already filtered to the highest-impact work.
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.


# How your catalog stays current
Source: https://docs.atlios.io/concepts/scan-freshness

The two ways Atlios keeps your issues up to date: scheduled scans and live product changes.

Atlios keeps your issues current automatically, so what you see usually reflects
your live catalog without you having to do anything.

## Scheduled scans

Atlios rescans your connected stores automatically, so issues stay fresh even on
days nothing changes in your catalog. These run on their own and appear in your
[Activity](/guides/review-job-history) like any other scan.

There are two scheduled passes on every plan:

* **A weekly full scan** re-checks every product, runs catalog-wide checks, and
  refreshes your overall quality scores.
* **A daily diff scan** catches products that changed since the last pass, so new
  issues surface within about a day instead of waiting for the weekly scan.

Scans are controlled backend work. They start on schedule rather than from a
manual action.

## Live product changes

When a product changes in Shopify, such as an edit to its title, price, or
images, Atlios notices the change and re-checks that product shortly after. This
keeps the issue list in step with everyday edits as they happen, in between the
scheduled scans.

## Why an issue might look out of date

Because the catalog and your issues update on slightly different schedules, you
may occasionally see an issue for a product you already fixed. The next live
re-check or scheduled scan clears issues that no longer apply. For more on how
issues open and close, see [Issue lifecycle](/concepts/issue-lifecycle).


# Scans
Source: https://docs.atlios.io/concepts/scans

How Atlios checks a Shopify catalog and turns results into reviewable work.

A scan is an Atlios review of your Shopify catalog. It checks product data,
variant data, image coverage, and duplicate identifiers, then records the
results for your team to review. Your live product pages are checked
separately, after Atlios applies a meta title or meta description fix.

Scans are point-in-time snapshots. They show what Atlios found when the scan
ran, not a live stream of every product change.

## When scans run

Atlios runs scans for you, so you do not have to start them:

* A first scan runs automatically when you connect a store.
* Scheduled scans run on a cadence that depends on your plan.
* Individual products are re-checked automatically when they change in Shopify.

See [How your catalog stays current](/concepts/scan-freshness) for the full
cadence, and [Collection launch readiness](/workflows/collection-launch-readiness)
for reviewing a product set before a launch.

## What a scan produces

A scan produces issues. Each issue groups a catalog problem into something a
person can review, prioritize, suppress, or fix. For how findings become
reviewable work, see [Scans and issues](/product/scans-and-issues).

## Keeping results current

You do not re-scan by hand. Atlios re-checks a product automatically after it
changes in Shopify, and the scheduled scans refresh the full catalog on a
cadence, so the issue list keeps pace with edits and applied fixes.


# Severity
Source: https://docs.atlios.io/concepts/severity

How Atlios helps teams prioritize catalog issues.

Severity helps teams decide what to review first. It is a prioritization signal
attached to each [issue](/concepts/issues), not a judgment that every store must
resolve every issue in the same way.

Higher-severity issues usually have a stronger chance of affecting operations,
storefront quality, or customer trust. Lower-severity issues may still matter,
but they are less urgent.

## Severity levels

Atlios uses four severity levels:

* **Critical.** Catalog problems that should be reviewed first, such as
  conditions that block product readiness or signal data corruption.
* **High.** Important issues that affect operations or customer-facing
  product content.
* **Medium.** Issues worth addressing in batches as part of a regular
  review.
* **Low.** Informational findings or minor inconsistencies.

## How to use severity

Use severity to plan review order:

* Start with the highest-severity issues in a new scan.
* Fix issues that block product readiness or storefront confidence.
* Review lower-severity issues in batches.
* [Suppress](/concepts/suppressions) intentional exceptions so future scans stay focused.

## Severity and business context

Your team's context still matters. A missing barcode may be urgent for one
operation and less important for another. Atlios gives you the signal; your
team decides the right catalog action.

## Severity can change

As Atlios adds checks and learns more about catalog workflows, severity
definitions may become more precise. Treat severity as a practical review aid,
not as a permanent taxonomy.


# Suppressions
Source: https://docs.atlios.io/concepts/suppressions

How to handle intentional exceptions in catalog quality reviews.

A suppression tells Atlios that an issue is an intentional exception and should
not keep distracting the team in future reviews.

Suppressions are useful when a rule is generally helpful, but a specific store,
product, or catalog situation should be allowed.

## When to suppress

Suppress an issue when:

* The catalog state is intentional.
* The rule does not apply to that product or store.
* The team has reviewed the issue and decided no action is needed.
* Repeated scans would otherwise surface the same valid exception.

## What suppression does

Suppression keeps the issue out of active review while preserving the history.
Use a clear reason so teammates understand why the exception exists.

Some suppression options apply to a specific product or variant. For tag
patterns, Atlios may also offer an option to ignore the same pattern across the
store.

## When not to suppress

<Warning>
  Do not suppress issues just to clear the list. If the product data is wrong,
  fix it in Atlios or Shopify; Atlios re-checks the product automatically after
  the change.
</Warning>

## Suppression keeps scans useful

Good suppressions make future scans easier to review. They remove known
exceptions so the issue list stays focused on work that still needs attention.


# Create products in bulk
Source: https://docs.atlios.io/guides/bulk-create-products

Use a spreadsheet and images to create many products in one batch.

When you need to add many products at once, use the bulk creator. You upload a
spreadsheet and a folder of images, review each product, then create them all
together.

<Warning>
  Bulk creation writes new products to Shopify. Review every product in the
  review step before you create the batch.
</Warning>

<Note>
  There is no menu entry for the bulk creator yet. Reach it by opening
  `/stores/<your store id>/products/bulk` directly, taking the store id from the
  address bar of any page in that store.
</Note>

## Bulk create flow

<Steps>
  <Step title="Download the template">
    Download the spreadsheet template. It is already set up with your store's
    vendors, product types, and a column for each inventory location.
  </Step>

  <Step title="Fill in your products">
    Add a row for each product and variant. Include details such as title,
    description, vendor, type, tags, options and values, price, SKU, inventory,
    and the image filename for each product.
  </Step>

  <Step title="Upload the file and images">
    Upload the completed spreadsheet together with a folder of the images you
    referenced.
  </Step>

  <Step title="Fix any warnings">
    Atlios checks the file and lists any warnings, such as a duplicate SKU.
    Resolve them before you continue.
  </Step>

  <Step title="Review each product">
    Each product appears as a card you can expand and edit. Check the details,
    options, variants, and inventory.
  </Step>

  <Step title="Match images">
    Drag any unmatched images onto the right product to set its images.
  </Step>

  <Step title="Create the products">
    Create the batch. Atlios shows the progress and reports success or an error
    for each product.
  </Step>
</Steps>

## The spreadsheet

The template includes a column for each thing Atlios needs, including product
handle, title, description, vendor, product type, tags, image filename, option
names and values, price, compare-at price, cost, SKU, barcode, weight, and one
inventory column per active location.

<Tip>
  Keep image filenames in the spreadsheet exactly the same as the files you
  upload so Atlios can match them automatically.
</Tip>

## Generate a description

While reviewing a product, you can ask Atlios to **generate a description** from
the product's title and images. This is optional and runs only when you choose
it. Review the generated text before you create the product.

<Note>
  Generating a description uses credits. See [Billing and
  credits](/product/billing-and-credits).
</Note>


# Product images
Source: https://docs.atlios.io/guides/bulk-image-upload

Add product images in bulk, match them to products, and start processing.

Use Product images when you have many images to add or update.

## Start a bulk upload

<Steps>
  <Step title="Open Products">Open the store, then go to **Products**.</Step>

  <Step title="Open Product images">
    Open the **More** menu and choose **Bulk image upload**.
  </Step>

  <Step title="Choose where images come from">
    Pick the source that matches your files.
  </Step>
</Steps>

## Add images

<Tabs>
  <Tab title="Device">
    Upload files from your computer. You can browse for files or drop images
    onto the page.
  </Tab>

  <Tab title="Cloud storage">
    Import image files from supported cloud storage.
  </Tab>

  <Tab title="URLs">Paste direct image URLs, one link per line.</Tab>

  <Tab title="Spreadsheet">
    Import a spreadsheet when you already have image URLs mapped to product
    handles or IDs.
  </Tab>
</Tabs>

## Match images to products

Atlios needs to know which product each image belongs to.

<Tabs>
  <Tab title="Smart match">
    Atlios reads filenames and tries to match images to products using clues
    such as SKU, product handle, or product name.

    Use this when filenames already include product hints.
  </Tab>

  <Tab title="CSV mapping">
    Upload a CSV that maps each filename to a product handle or product ID.

    Use this when your team already has a mapping sheet.
  </Tab>

  <Tab title="Manual match">
    Assign images to products yourself.

    Use this for small batches or when filenames do not contain useful product
    clues.
  </Tab>
</Tabs>

<Warning>
  Review matches before processing. A good image on the wrong product can
  confuse customers after publishing.
</Warning>

## Confirm and process

<Steps>
  <Step title="Review matches">
    Check matched, unmatched, and skipped images. Fix any wrong matches before
    continuing.
  </Step>

  <Step title="Choose templates">
    Use the job default template, or set a different template for specific
    images when they need a different treatment.
  </Step>

  <Step title="Start processing">
    Start the job. Atlios processes images and updates the page as each item
    finishes.
  </Step>

  <Step title="Return later if needed">
    You can leave the page and reopen the job from **Activity**.
  </Step>
</Steps>

## Next step

After processing starts, review the outputs before publishing. See
[Review and publish images](/guides/review-and-publish-images).


# Connect Google Merchant Center
Source: https://docs.atlios.io/guides/connect-google-merchant-center

Link a Google Merchant Center account to a store so disapprovals appear in Atlios.

Connect Google Merchant Center to bring product disapprovals and account
warnings into the same issue inbox as your Shopify scans.

## Before you start

<Info>
  You need to be an **admin on the Google Merchant Center account** you want to
  connect. If you are not an admin, Google blocks the connection.
</Info>

<Info>
  Only a workspace **owner** can connect or disconnect a Merchant Center
  account. See [user roles](/reference/user-roles).
</Info>

Find your **Merchant Center ID** before you start. It is the account number at
[merchants.google.com](https://merchants.google.com), shown in the account
switcher in the top right.

## Connect the account

<Steps>
  <Step title="Open the store integrations page">
    Open the store in Atlios and go to **Integrations**.
  </Step>

  <Step title="Start the connection">
    On the Google Merchant Center card, choose **Connect**.
  </Step>

  <Step title="Enter your Merchant Center ID">
    Enter the digits of your Merchant Center ID and continue.
  </Step>

  <Step title="Approve in Google">
    Sign in to Google and approve access so Atlios can read your product and
    account status.
  </Step>

  <Step title="Return to Atlios">
    Atlios returns you to the integrations page and confirms the connection.
  </Step>
</Steps>

## After you connect

Atlios needs a few minutes to finish setting up with Google. The card shows this
while it works, then starts the first sync on its own. You do not need to click
anything.

After the first sync, GMC issues appear in the
[issue inbox](/product/issue-inbox) and any account warnings show as a banner.
From the card you can **Sync now**, **View issues**, or **Disconnect**.

## Reconnect after access expires

If Google access is revoked or expires, the card shows **Access expired**. Choose
**Reconnect** and approve access again. Still-valid issues reappear on the next
sync.

## Disconnect

Disconnecting removes the Merchant Center connection and quiets open GMC issues
so they leave the inbox. Workspace owners are notified by email. Reconnecting
later re-surfaces any issues Google still reports.

<Tip>
  If the connection fails or shows an error, check the [troubleshooting
  reference](/reference/troubleshooting#google-merchant-center-will-not-connect).
</Tip>


# Connect Shopify
Source: https://docs.atlios.io/guides/connect-shopify

Install Atlios and connect a Shopify store.

Connect a Shopify store before running scans or fixes.

## Before you start

<Info>
  Make sure you have permission to install apps for the target Shopify store. If
  your team manages multiple stores, confirm which store should be connected
  before approving the installation.
</Info>

## Install Atlios

<Steps>
  <Step title="Open the installation link">
    Open the Atlios installation link for your workspace.
  </Step>

  <Step title="Choose the store">
    Choose the Shopify store you want to connect.
  </Step>

  <Step title="Review permissions">Review the requested permissions.</Step>
  <Step title="Approve in Shopify">Approve the installation in Shopify.</Step>

  <Step title="Confirm in Atlios">
    Return to Atlios and confirm the store appears in your workspace.
  </Step>
</Steps>

## After connection

Atlios syncs store metadata so scans and workflows can use current product and
variant context.

<Tip>
  If the store does not appear after installation, check the [troubleshooting
  reference](/reference/troubleshooting) or reconnect the store.
</Tip>


# Edit a product
Source: https://docs.atlios.io/guides/edit-a-product

Open a product in Atlios to update its details and save the changes to Shopify.

Open any product from the products list to view and edit it. Changes save back
to Shopify, so review them before you save.

<Steps>
  <Step title="Open the product">
    Find the product in the [products list](/product/products) and click its
    title.
  </Step>

  <Step title="Edit the details">
    Update any of the fields described below. An **Unsaved changes** indicator
    appears while you have edits in progress.
  </Step>

  <Step title="Review warnings">
    If the product is missing important details, Atlios shows a warning. Read it
    and decide whether to fix the detail first.
  </Step>

  <Step title="Save">
    Click **Save**. Your changes are written back to Shopify.
  </Step>
</Steps>

<Tip>
  Missing details? Use **Look up details** in the product details card to pull
  the title, vendor, type, and description from an external database by barcode,
  ISBN, or model. See [Look up product
  details](/guides/look-up-product-details).
</Tip>

## What you can edit

<AccordionGroup>
  <Accordion title="Basics">
    Title, description, status (Active or Draft), vendor, and product type.
  </Accordion>

  <Accordion title="Media">
    Upload images, edit and crop them, set alt text per image, reorder them, and
    choose the featured image.
  </Accordion>

  <Accordion title="Options and variants">
    Edit option names and values, such as Size or Color, and the variants they
    create.
  </Accordion>

  <Accordion title="Pricing and inventory">
    Set price, compare-at price, cost, SKU, and barcode per variant, and set
    inventory per location.
  </Accordion>

  <Accordion title="Organization">Add tags and assign collections.</Accordion>

  <Accordion title="SEO">
    Edit the meta description used by search engines.
  </Accordion>

  <Accordion title="Metafields">
    Edit the metafields your store tracks. Manage which metafields appear here
    from [Catalog standards](/product/glossary).
  </Accordion>
</AccordionGroup>

## Saving and warnings

The **Save** button stays disabled until you make a change. If a product is
missing a title, description, or price, Atlios warns you before saving. This is
a reminder, not a block: you can confirm the save when you are ready.

<Tip>
  After editing products that had open issues, Atlios re-checks them
  automatically once the changes save to Shopify. See [How your catalog stays
  current](/concepts/scan-freshness).
</Tip>


# Fix product issues
Source: https://docs.atlios.io/guides/fix-product-issues

Review and apply supported fixes for catalog issues.

Atlios can help prepare fixes for supported catalog issues.

<Warning>
  Always review the proposed change before applying it. Fixes affect live
  catalog content and should match your store's merchandising standards.
</Warning>

## Fix workflow

<Steps>
  <Step title="Open an issue">Open an issue from the issue list.</Step>

  <Step title="Read the context">
    Read the affected product or variant context.
  </Step>

  <Step title="Choose a supported fix">
    Choose the supported fix action if one is available.
  </Step>

  <Step title="Review the proposed change">Review the proposed change.</Step>

  <Step title="Apply the fix">
    Apply the fix when it matches your merchandising standards.
  </Step>

  <Step title="Let Atlios verify">
    Atlios re-checks the product automatically after the fix applies and
    verifies whether the issue is resolved.
  </Step>
</Steps>

## Fix action types

Atlios shows only the actions available for the issue you opened.

<AccordionGroup>
  <Accordion title="Apply fix">
    Atlios can start the fix directly. Use this when the suggested outcome is
    clear. You still see a preview before Shopify is updated.
  </Accordion>

  <Accordion title="Review before applying">
    Atlios can prepare a suggested change, but you should review it before it
    updates catalog content.
  </Accordion>

  <Accordion title="Enter value">
    Atlios needs a value from you before it can apply the change.
  </Accordion>

  <Accordion title="Open product">
    The issue needs manual review or editing in the product editor.
  </Accordion>

  <Accordion title="Open image workflow">
    The issue needs image workflow review before new images are published back
    to Shopify.
  </Accordion>
</AccordionGroup>

For a complete reference, see [Supported fixes](/reference/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.

<Steps>
  <Step title="Open the image issue">
    Open the issue and read which images are affected.
  </Step>

  <Step title="Choose Apply template">
    Atlios creates an image job using the store's default image template.
  </Step>

  <Step title="Review the processed images">
    Approve, reject, or regenerate image outputs before publishing.
  </Step>

  <Step title="Publish approved images">
    Publish only the images that pass review.
  </Step>

  <Step title="Let Atlios verify">
    Once the images publish, Atlios re-checks the product automatically to
    verify whether the issue is resolved.
  </Step>
</Steps>

<Note>
  The image job processes and publishes images. Atlios verifies the issue with
  an automatic re-check after the catalog has changed.
</Note>

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

<Note>
  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.
</Note>

Inspect-only issues include negative inventory, several approved-value
mismatches, and unclassified metafield assignment rules. See
[Supported checks](/reference/supported-checks) for each issue type.


# Look up product details
Source: https://docs.atlios.io/guides/look-up-product-details

Pull product details from an external database by barcode, ISBN, or model.

When a product is missing details, you can look it up in an external database
and pull the values straight into the product editor. Nothing saves to Shopify
until you click **Save**, so you stay in control.

<Steps>
  <Step title="Open the product">
    Open the product in the [editor](/guides/edit-a-product) and find the
    product details card.
  </Step>

  <Step title="Click Look up details">
    Click **Look up details** in the card header. Atlios opens a search box,
    already filled with the product's barcode or SKU when it can.
  </Step>

  <Step title="Search">
    Search by **barcode, ISBN, or model number**. A chip shows which type Atlios
    detected. If there are several matches, pick the right one.
  </Step>

  <Step title="Choose what to use">
    Each found field shows the external value next to your current value. Click
    **Use this** on a field, or **Use all** to take everything that differs.
    Fields that already match are marked **In use**.
  </Step>

  <Step title="Save">
    Review the changes and click **Save** to write them back to Shopify.
  </Step>
</Steps>

## What it can fill

A lookup can bring in the **title**, **vendor (brand)**, **product type**, and
**description**. If the source has an image, use **Use this image** to stage it
into the [Media](/guides/edit-a-product) section; it applies when you save.

Dimensions and weight, when found, are shown under **Also found** for reference.
They are not applied to the product.

## What you can search by

<AccordionGroup>
  <Accordion title="ISBN (books)">
    Book lookups work out of the box using Google Books and Open Library. No
    setup needed.
  </Accordion>

  <Accordion title="Barcode or model number">
    General retail lookups by barcode (GTIN) or model number (MPN) use the
    Barcode Lookup provider, which needs an API key. If no key is configured,
    Atlios tells you, and book lookups by ISBN still work.
  </Accordion>
</AccordionGroup>

<Warning>
  External data can be wrong or out of date. Review every field before you save.
  Atlios never changes the product on its own; the lookup only suggests values.
</Warning>


# Manage image templates
Source: https://docs.atlios.io/guides/manage-image-templates

Set the standard your product images are held to, and choose which products each one covers.

A template is the standard your product images are held to. It sets the
scenario, output size, format, quality, background and lighting. Products whose
images fall outside the template that applies to them show up in Fix, where you
can reframe them to it.

## Open image templates

<Steps>
  <Step title="Open Catalog standards">
    Open the store, then go to **Catalog standards**.
  </Step>

  <Step title="Open Images">Choose **Images** from the list of standards.</Step>

  <Step title="Review templates">
    Check the current templates and which one is marked as the store default.
  </Step>
</Steps>

The list opens on the templates that apply to products: your store default, plus
any template you have given rules about which products it covers. Switch to
**Only when you pick it** to see templates that run only when you choose them
for a job.

## Choose a scenario

Choose the scenario that matches the image result you want.

<Tabs>
  <Tab title="Studio">
    Best for clean product shots on one solid color.

    Set a backdrop color, shadow style, light direction, output size, format,
    and quality.
  </Tab>

  <Tab title="Background">
    Best for cutting out a product.

    Choose transparent output for design workflows or a solid color for
    marketplace requirements. Transparent output uses PNG.
  </Tab>

  <Tab title="Editorial">
    Best for campaign, seasonal, or lifestyle images.

    Describe the scene you want, then choose shadow and lighting settings.
  </Tab>

  <Tab title="Flat-lay">
    Best for garments photographed from above.

    Choose a surface prompt, such as linen or wood, or use a solid color
    backdrop.
  </Tab>

  <Tab title="On-model">
    Best for showing garments on a model.

    Choose framing, pose, and setting. Atlios uses product context when it can
    to fit the result to the item.
  </Tab>
</Tabs>

## Create a template

<Steps>
  <Step title="Select New template">
    Choose **New template** in the image templates list.
  </Step>

  <Step title="Pick a scenario">
    Select the type of image treatment you want.
  </Step>

  <Step title="Name the template">
    Use a name your team will understand, such as `White background 2048` or
    `Flat-lay linen`.
  </Step>

  <Step title="Set output">Choose width, height, format, and quality.</Step>
  <Step title="Save">Save the template so it appears in image jobs.</Step>
</Steps>

## Use templates in jobs

* The store default template is used when no other template is selected.
* You can set a template for the whole job before processing.
* You can override the template for selected images.
* If you change the template for an already processed image, reprocess that
  image before approving it.

<Tip>
  Keep template names plain and specific. Names like `Studio white square` or
  `Transparent PNG` are easier for first-time users than internal campaign
  names.
</Tip>


# Manage metafields
Source: https://docs.atlios.io/guides/manage-metafields

Choose which metafields Atlios tracks, set their scope, and stop tracking ones you do not need.

Atlios tracks the metafields you choose and checks them during scans. Tracked
metafields are also the ones you can edit on the product page. Manage them from
the **Metafields** group in [Catalog standards](/product/glossary).

## Scope

Each tracked metafield has a **scope**:

* **Product:** the metafield applies to the whole product.
* **Variant:** the metafield applies to an individual variant.

Scope decides where the metafield appears and how it is checked, so set it to
match how the metafield is used on your products.

## Add metafields

Use **Add** to start tracking more metafields. You can pick from several
sources:

<AccordionGroup>
  <Accordion title="Google MC">
    Google Merchant Center attributes, such as Brand or Product category. These
    can be locked to Google's allowed values.
  </Accordion>

  <Accordion title="Shopify">
    Metafield definitions that already exist in your Shopify store.
  </Accordion>

  <Accordion title="On products">
    Metafields Atlios saw on your products during the last scan but is not yet
    tracking.
  </Accordion>

  <Accordion title="Manual">
    Enter a metafield's namespace and key by hand.
  </Accordion>
</AccordionGroup>

Select the metafields you want from any source, then add them. They start
appearing on product pages and in scans.

## Filter and search

The metafields table can get long. Search by name or code, and filter by source
so you can find a specific metafield quickly. Each row shows its name, source,
and scope.

## Stop tracking

To stop checking a metafield, remove it from tracking. Select one or more
metafields and use **Stop tracking**. This does not delete anything in Shopify,
it only tells Atlios to stop tracking and checking those metafields.

<Tip>
  For Google Merchant Center attributes, you can lock a metafield to Google's
  allowed values so a scan flags anything outside the official list.
</Tip>


# Manage connected stores
Source: https://docs.atlios.io/guides/manage-stores

Connect, sync, reconnect, and disconnect Shopify stores.

Manage the Shopify stores in your organization from **Settings > Stores**. From
here you connect new stores, check their status, and reconnect or disconnect
them.

## Connect a store

Use **Connect store** to install Atlios on a Shopify store. You are sent to
Shopify to approve access, then returned to Atlios. For the full first-time
setup, see [Connect Shopify](/guides/connect-shopify).

## Sync store data

Before Atlios can scan a store, it reads the store's structure, such as its
metafields and metaobjects. This sync runs when you connect a store, and you can
run it again to pick up changes you made in Shopify. The stores list shows each
store's sync status.

## Reconnect a store

If a store's connection expires or its permissions change, reconnect it to
restore access. Reconnecting sends you back to Shopify to approve access again.

## Disconnect a store

<Warning>
  Disconnecting a store removes it from Atlios along with its scans and issues.
  This cannot be undone. Reconnect later if you want to track the store again.
</Warning>

Disconnect a store when you no longer want Atlios to track it. This frees up a
store slot against your plan's store limit.

<Note>
  Connecting and disconnecting stores is available to owners and admins. See
  [User roles](/reference/user-roles).
</Note>


# Review and publish images
Source: https://docs.atlios.io/guides/review-and-publish-images

Approve, reject, regenerate, download, and publish processed image outputs.

Review every processed image before publishing it to Shopify. This is the final
step of the broader [image workflows](/product/image-workflows). For a focused
pre-publish checklist, see [Image review before publish](/workflows/image-review-before-publish).

## Open a job for review

Open the job from the image workflow or from **Activity** in the sidebar. Jobs
that are still processing show live progress. Finished items appear as they
complete.

## Review each output

<Steps>
  <Step title="Compare the output">
    Open the image preview and check the processed result against the original.
  </Step>

  <Step title="Check product identity">
    Confirm the product still has the right color, pattern, logo, shape,
    material, and details.
  </Step>

  <Step title="Check image quality">
    Review crop, edges, background, shadows, lighting, and any generated scene.
  </Step>

  <Step title="Check product match">
    Confirm the image is attached to the right product.
  </Step>

  <Step title="Check SEO details">
    Review generated alt text and filenames when they are present.
  </Step>
</Steps>

## Decide what to do

<Tabs>
  <Tab title="Approve">
    Approve images that are ready to publish. You can approve one image or
    approve selected images in bulk.
  </Tab>

  <Tab title="Reject">
    Reject images that should not be published. Rejected images stay in the job
    history but are not published.
  </Tab>

  <Tab title="Regenerate">
    Regenerate an image when the product is right but the output needs another
    pass.

    Use this for weak backgrounds, bad edges, wrong shadows, failed metadata,
    or template changes that need reprocessing.
  </Tab>

  <Tab title="Set featured">
    When several new images go to the same product, choose the image that should
    become the featured image.
  </Tab>
</Tabs>

## Download a review zip

Use **Download zip** when you want to review files outside Atlios or share them
with a teammate before publishing.

## Publish approved images

<Steps>
  <Step title="Approve the images you want">
    Only approved images are included in the publish step.
  </Step>

  <Step title="Leave rejected images out">
    Rejected images are not sent to Shopify.
  </Step>

  <Step title="Publish">
    Start publishing. Atlios writes approved image changes to Shopify.
  </Step>

  <Step title="Check completed items">
    Confirm the job shows completed or review any failed publish items.
  </Step>

  <Step title="Let Atlios verify">
    After publishing, Atlios re-checks the affected products automatically to
    verify image-related checks, including when the job came from an image
    issue.
  </Step>
</Steps>

<Warning>
  Publishing changes Shopify product media. Review approved images carefully
  before starting the publish step.
</Warning>

## Status meanings

<AccordionGroup>
  <Accordion title="Pending">The image still needs review.</Accordion>

  <Accordion title="Approved">
    The image is ready for the publish step.
  </Accordion>

  <Accordion title="Rejected">The image will not be published.</Accordion>
  <Accordion title="Published">The image was written to Shopify.</Accordion>

  <Accordion title="Failed">
    The image or job could not finish. Retry or regenerate when the action is
    available.
  </Accordion>
</AccordionGroup>


# Review activity
Source: https://docs.atlios.io/guides/review-job-history

Track fix and image jobs for a store, inspect results, and undo applied fixes.

The **Activity** page lists the fix and image jobs that have run for a store, so
you can check what happened, follow jobs that are still running, and undo
applied fixes.

## The job list

Each row is a job, with its type (**Fix** or **Image**), what it did, when it
was created, its status, and its progress. Running jobs show a progress bar,
finished jobs show how many items succeeded and failed, and jobs that need your
input show **Needs review**.

You can filter the list by type, status, and time range (the default is the last
30 days), and search by store, rule, or job. Image jobs that are still running
can be canceled from the list.

## Job detail

Click a job to open its detail. The detail view shows how the job ran, including
the method used, the field it changed, the results (such as how many items were
applied, failed, or skipped), how long it took, who started it, and when.

Below that is the list of items the job touched, one per product or variant. You
can search the items and filter by **All**, **Failed**, **Skipped**, or
**Applied**. Expand an item to see:

* The error message, if it failed or was skipped.
* A before and after comparison of the change.
* A short note explaining the change.

## Undo a fix

If a fix was applied and can be reversed, an **Undo** button appears on the item.
You can undo a single item, or use **Undo all** to revert every applied item in
the job at once.

<Warning>
  Undo reverses the change in Shopify. Review the before and after comparison
  before you undo so you know exactly what will change back.
</Warning>

<Tip>
  After undoing fixes, Atlios re-checks the affected products automatically as
  the change lands in Shopify. See [How your catalog stays
  current](/concepts/scan-freshness).
</Tip>


# Use bulk issue actions
Source: https://docs.atlios.io/guides/use-bulk-issue-actions

Apply fixes or suppressions to multiple issues without losing review control.

Bulk actions help you handle groups of similar issues from the issue inbox.

Use them when the selected issues have the same intended outcome and do not
need separate review.

## Before you start

* Filter the inbox to the issue type or severity you want to handle.
* Review a few examples first so you understand what the rule is flagging.
* Avoid bulk action when the fix depends on product-specific merchandising
  judgment.

## Apply fixes in bulk

<Steps>
  <Step title="Filter the inbox">
    Narrow the list by rule, severity, status, or search.
  </Step>

  <Step title="Select issues">
    Select the issues you want to handle together.
  </Step>

  <Step title="Apply the available action">
    Start the bulk fix when Atlios shows one.
  </Step>

  <Step title="Check the result message">
    Atlios reports what started and which issues need individual review.
  </Step>

  <Step title="Let Atlios confirm">
    Once the changes apply in Shopify, Atlios re-checks the affected products
    automatically and resolved issues drop off the list.
  </Step>
</Steps>

## Why selected issues may be excluded

Atlios starts only the issues that can be handled safely in the selected bulk
action.

Issues can be excluded when:

* They are already verifying, resolved, or suppressed.
* They require manual input, such as SKU, barcode, or price.
* They require review before applying.
* No fixer is available for the issue type.
* Atlios already knows the fix would make no effective change.

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

## Suppress in bulk

Suppress issues in bulk only when the same exception applies to every selected
issue.

<Warning>
  Do not suppress issues just to clear the inbox. Suppression should mean the
  catalog state is intentional.
</Warning>

## When to review issues one by one

Review individually when:

* The issue affects product copy, image choice, tags, or merchandising meaning.
* Atlios asks you to review a proposed change first.
* Atlios asks you to enter a value.
* The issue needs a manual edit in Shopify.
* You are not sure the same action is right for every selected issue.


# Introduction
Source: https://docs.atlios.io/index

Customer help for connecting Shopify stores, monitoring catalog quality, and fixing product issues.

Atlios helps Shopify teams keep product catalogs accurate, complete, and ready
for storefront review. Connect a store, let Atlios scan your catalog, inspect the
issues it finds, and use guided fixes where the product workflow supports them.

<Columns>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Connect a store and review your first scan in a few minutes.
  </Card>

  <Card title="Catalog quality" icon="gauge" href="/product/catalog-quality">
    See what Atlios covers across catalog, image, and storefront workflows.
  </Card>

  <Card title="Catalog agent" icon="bot" href="/product/catalog-agent">
    Chat with the agent to plan and prepare catalog cleanups.
  </Card>

  <Card title="Concepts" icon="lightbulb" href="/concepts/scans">
    Learn how scans, issues, severity, and suppressions fit together.
  </Card>

  <Card title="Guides" icon="book-open" href="/guides/connect-shopify">
    Step-by-step setup, scanning, and fix walkthroughs.
  </Card>

  <Card title="Workflows" icon="list-checks" href="/workflows/weekly-catalog-review">
    Repeatable routines for weekly reviews and launch readiness.
  </Card>

  <Card title="Reference" icon="file-text" href="/reference/supported-checks">
    Supported checks and troubleshooting answers.
  </Card>
</Columns>

## Who Atlios is for

Atlios is built for catalog operations teams who need a clear way to find
missing product data, weak image coverage, live product pages that are
unreachable or blocked from search, and metadata issues before they affect
customers.


# Billing and credits
Source: https://docs.atlios.io/product/billing-and-credits

Understand plans, credits, your free trial, and how usage is counted.

Atlios uses a plan for your overall limits and features, plus credits for the
work that runs AI, such as fixes and image generation. You manage all of this
from **Settings > Billing**.

<Info>
  Plan changes, the billing portal, and buying credits are available to the
  organization owner. Other members see these options as owner only.
</Info>

## Plans

Your plan sets how many products you can track, how many credits you get each
month, and which features are available. The billing page shows the available
plans side by side so you can compare them.

Every paid plan includes one store. You can connect more, and each extra store
is added to your monthly bill as a per-store add-on. The price per extra store
is shown on the billing page before you connect one.

From the billing page you can:

* **Start a free trial** when you are on the free plan.
* **Upgrade** to a higher plan or **downgrade** to a lower one.
* **Manage billing** to open the secure billing portal, where you can update
  your card and view invoices.
* **Reactivate** a subscription that was canceled or past due.

Your current plan shows a **Current plan** badge, and the page shows when your
subscription renews or, if you have canceled, when it ends.

## Free trial

New paid plans start with a free trial. During the trial:

* The sidebar shows how many days are left.
* The billing page shows a banner with the days remaining and confirms your card
  is not charged until the trial ends.

You can cancel any time before the trial ends. When the trial ends, your
subscription begins on the plan you chose.

<Note>
  A trial grants a smaller starter pool of credits than the plan's full monthly
  pool. Your first full monthly grant arrives when the trial ends and the
  subscription begins. The billing page always shows the number you actually
  have.
</Note>

## Credits

Credits pay for the work that uses AI. You spend credits when you apply AI
fixes, generate images, and approve changes the catalog agent prepares:

* **1 fix = 1 credit**
* **Image generation: 6 to 10 credits per image, by output size**
* **1 credit per change the agent stages for your approval**
* **Product video: 40 to 70 credits per clip, by clip length**

Product video is a premium feature. A short clip costs much more to make than an
image, so it uses a larger number of credits. The cost depends on the clip
length, is always shown before you start, and is only charged if the video is
created.

| Clip length | Credits to create | Credits to refine |
| ----------- | ----------------- | ----------------- |
| 4 seconds   | 40 credits        | 55 credits        |
| 6 seconds   | 55 credits        | 85 credits        |
| 8 seconds   | 70 credits        | 110 credits       |

Refining costs more than creating, because a refine makes a new video from the
old one and is billed for both the video it reads and the video it writes. The
exact cost is shown before you start, and nothing is charged if it fails. Your
previous video is kept, so undoing a refine is free.

Larger images cost more credits because they cost more to generate. The size is
set by the output dimensions on the image template, and the template editor
shows the exact cost before you save:

| Output size (longest side) | Credits per image |
| -------------------------- | ----------------- |
| Up to 1024 px              | 6 credits         |
| 1025 to 2048 px            | 8 credits         |
| Larger than 2048 px        | 10 credits        |

Each paid plan includes a pool of credits that refreshes each billing period.
During a trial the pool is a smaller one-time starter grant. The
billing page shows a large **remaining** number, how many credits you have used
of the included amount, and when the pool resets. A progress bar turns amber and
then red as you get close to using all of your included credits.

Inline credit indicators also appear near AI actions and on store views, so you
can see your balance before you start work that uses credits.

<Note>
  New organizations on the free plan get a one-time grant of welcome credits
  after their first scan finishes, so you can try applying fixes and generating
  images before choosing a paid plan. The grant is 25 credits, or 50 during the
  open beta. Welcome credits do not expire at the end of a period.

  The grant is one per person: it needs a verified email address, it is claimed
  once per person across all the organizations you create, and it stops once you
  have a paid subscription.
</Note>

### What is included, not charged

Finding problems never costs credits. Scans, checks, and audits that only
detect and flag issues are included in your plan. You are charged only when you
apply a fix or generate an image.

This includes the image subject-position audit, which looks at where the product
sits in each catalog image and flags shots whose subject is off from your
template's set position. The check itself is included: a subject-position read
costs Atlios roughly $0.0004 per image and is absorbed in your plan, so a
one-time sweep of a 5,000-image catalog is about $2 to Atlios and \$0 to you.
Credits apply only when you apply the "Apply template" fix to reposition a
flagged image, at the usual image-generation rate above.

## Buy more credits

If you need more credits than your plan includes, use **Buy credits** to
purchase a one-time pack. Choose a preset amount or enter your own, from $10 up
to $10,000. Credits cost \$0.04 each and never expire.

<Note>
  Credits are prepaid. AI work never bills you after the fact: a busy month
  cannot produce a surprise credit invoice, because you cannot spend credits you
  have not bought. Your recurring bill is your plan price plus any extra-store
  add-ons.
</Note>

## When you run out

If you run out of credits, Atlios tells you what to do based on your plan:

* On the free plan, you are prompted to choose a paid plan to unlock a monthly
  credit pool.
* On a paid plan, you buy a credit pack to keep going.

Work already running stops cleanly at a zero balance. Anything it had already
produced is kept for you to review, and nothing is charged past your balance.

Some features are only on paid plans. When you reach a feature that your plan
does not include, Atlios explains which plan unlocks it and links you to
billing.

## Usage this period

The billing page shows your usage against your plan limits:

* **Stores:** connected stores, and how many your base plan price covers. On a
  paid plan you can go past that number; the extra stores are billed as add-ons.
* **Products:** tracked products compared to your plan's limit.
* **Scans today:** scans run today compared to the daily limit per store.

A **Recent activity** section lists your latest credit activity, such as fixes,
image generation, your monthly credit grant, and any credit purchases.


# Catalog agent
Source: https://docs.atlios.io/product/catalog-agent

Chat with the Atlios catalog agent to plan and prepare catalog cleanups.

The catalog agent is an assistant you chat with to clean up a store's catalog.
Tell it what you want in plain language, and it plans the work and prepares the
changes for you to approve.

## What it does

The agent plans the work for you, but it never changes your store on its own.
It works out the steps, prepares the changes, and puts them on a review screen.
Nothing reaches Shopify until you approve it.

It works on Shopify catalog cleanup: existing issues, safe product edits, tags,
vendors, product types, metafields, descriptions, image alt text, and selected
image-generation workflows. If you ask for something else, it lets you know it
cannot help with that.

Catalog scans are controlled backend jobs that run on schedule. The agent can
read their findings, but it cannot start a scan manually.

## What you can ask for

The agent can prepare these changes:

<AccordionGroup>
  <Accordion title="Move tags into a metafield">
    Turn a set of related tags into a proper metafield, for example
    `Gender_Male` into a `custom.gender` metafield, and drop the old tags.
  </Accordion>

  <Accordion title="Remove unwanted tags">
    Clean up junk, test, or leftover tags across the catalog.
  </Accordion>

  <Accordion title="Fix inconsistent values">
    Merge different spellings of a vendor or product type into one consistent
    value, for example `nike` and `NIKE` into `Nike`.
  </Accordion>

  <Accordion title="Rewrite descriptions">
    Rewrite product descriptions in your brand voice. Uses credits per product.
  </Accordion>

  <Accordion title="Rewrite image alt text">
    Generate fresh alt text for product images, for accessibility and SEO. Uses
    credits.
  </Accordion>

  <Accordion title="Fill in missing metafields">
    Fill the metafields your store tracks, or fix values a scan flagged as
    wrong.
  </Accordion>

  <Accordion title="Create a metafield definition">
    Set up a new metafield definition. This always asks for explicit
    confirmation first.
  </Accordion>

  <Accordion title="Triage catalog issues">
    List current problems, return export-ready data, assign an issue to a team
    member, prepare available fixes for review, or suppress an exact confirmed
    issue scope with a reason.
  </Accordion>

  <Accordion title="Prepare safe product edits">
    Change status to draft or archived, vendor, product type, tags, or supported
    product fields and metafields. Every edit is staged for review first.
  </Accordion>

  <Accordion title="Start reviewed image work">
    Inspect image templates and jobs, process template-mismatch issues, generate
    new product-image angles from existing catalog media, or regenerate one job
    item. Generation uses credits and needs explicit confirmation. The agent
    cannot upload, approve, delete, or publish image work.
  </Accordion>
</AccordionGroup>

Most actions are reversible. Generated content, like rewritten descriptions and
alt text, is not, so review it before you approve.

## Where to find it

You can reach the agent two ways:

* **[Store home](/product/dashboards)** is the agent, full screen. Opening a
  store puts you straight into a conversation about it.
* The **agent panel** follows you as you work on other pages.

Both share the same conversation, so you can pick up where you left off. The
panel hides itself on store home, so you never have two agents at once.

## Review and approval

Every catalog edit the agent prepares waits for your approval on the review
screen. Open it, check what will change and on which products, then approve or
discard. If **Apply from chat** is enabled for the store, the agent can show an
**Apply now** button for the exact prepared edit. You still confirm each action.

Issue suppression takes effect only after you confirm its exact scope and
reason. Image generation starts only after you confirm its scope and credit use;
generated output still requires human review before publishing.

<Note>
  Rewrites and alt text use AI credits. If you run out, or your plan does not
  include an action, the agent points you to upgrade. See [Billing and
  credits](/product/billing-and-credits).
</Note>


# Catalog quality
Source: https://docs.atlios.io/product/catalog-quality

What Atlios means by catalog quality and how it evaluates stores.

Catalog quality is the readiness of your product data, images, and storefront
presentation. Atlios looks for gaps that make products harder to sell, harder
to manage, or harder for customers to evaluate, including missing identifiers,
incomplete product copy, weak image coverage, and live product pages that
cannot be reached, are blocked from indexing, or are not showing a saved meta
value.

## What Atlios covers

* Store connection and metadata sync.
* Catalog scans for product, variant, and cross-entity checks.
* Issue tracking with severity, suppression, and scan history.
* Guided fixes for supported product and variant findings.
* Image workflows for upload, matching, processing, review, and publishing.
* Storefront verification: confirming a fixed meta title or meta description
  on the rendered product page, and reporting live-page findings.

## Quality signals

* Product content is present and usable.
* Variants have the identifiers and prices needed for operations.
* Images exist, are attached to products, and support customer evaluation.
* Live product pages are reachable, indexable, and showing the meta values you
  saved.
* Duplicate identifiers and cross-product conflicts are visible.

## Operational goal

The goal is not to make every catalog perfectly uniform. The goal is to make
catalog problems visible, actionable, and easy to verify after a team fixes
them.


# Dashboards
Source: https://docs.atlios.io/product/dashboards

See catalog quality across every store and dig into a single store.

Atlios has two dashboards: the **Portfolio** view across all of your stores, and
a **store home** page for each individual store. Both summarize catalog quality
so you know where to spend your time.

Counts are never doubled up: an issue flagged by both your scan and Google
Merchant Center is counted once. See [Issues](/concepts/issues) for how that
works.

## Portfolio

The Portfolio dashboard is a high-level view across every connected store. Use
the time window control to look at the last 7, 30, or 90 days, or all time.

It shows:

* **Value delivered:** estimated value protected over the window, estimated
  value at risk right now, hours saved, how many issues Atlios fixed, how many
  were resolved elsewhere, your portfolio quality score out of 100, and open
  issues. Each figure has an information hint that explains how it is worked
  out, and an arrow for how it changed over the window.
* **Trends:** an **Atlios fix activity** chart and a **Portfolio quality**
  chart.
* **Stores needing attention:** the stores to look at first.
* **By store:** a card per store with its quality score, products, hours saved,
  and issues resolved.
* **Portfolio details:** an **Issues by category** breakdown, and **Biggest
  time savers**, the issue types that saved you the most time.

Click a store card to open that store's home.

## Store home

Open a store to land on its home page. Store home **is** the
[catalog agent](/product/catalog-agent), full screen. There is no separate
dashboard to read first: you land in a conversation about this store.

A fresh visit starts a new chat. The greeting carries the store's opening
readout, so you can see where the store stands before you type anything.

### Overview cards

Under the greeting are four cards, one per area of the app:

* **Fix:** the one issue-fixing move that matters most right now.
* **Products:** the state of your catalog.
* **Create:** what there is to make next.
* **Grow:** how shoppers are finding your products.

Each card reads your latest saved snapshot, so it costs no credits and never
waits on the AI. Each card has two things you can click, and nothing else:

* The **pill** fills the message box with a prompt about that card, without
  sending it. You can edit it first, then press Enter.
* The **corner link** opens that area's own page.

A card shows a lock in the corner if that area is not switched on for your
store yet. If one card cannot load, the other three still work, and the broken
one offers a retry.

### Setup nudge

Above the cards, a short strip appears while there is still setup left to do,
such as connecting a channel. It hides itself once there is nothing to prompt
you about.

<Tip>
  Start your day on store home and read the four cards. Use the pill when you
  want the agent to do the work, and the corner link when you would rather
  drive the page yourself.
</Tip>


# Catalog standards
Source: https://docs.atlios.io/product/glossary

Curate the approved vocabulary Atlios uses to check your catalog.

**Catalog standards** are your store's approved vocabulary: the lists of product
types, vendors, tags, option values, and metafields that you consider correct.
When a scan runs, Atlios checks your products against these lists and flags
anything that falls outside them.

Keeping your catalog standards tidy is how you control which differences in your
catalog count as issues and which do not.

## The page

The page opens on whatever needs a decision. If Atlios found something it cannot
settle on its own, that question sits at the top with the values in front of you
and the products that use them. Decisions Atlios has drafted for you sit under
it, and you can apply them all at once.

Under the decision area are your six standards:

* **Vendors**, **Product types**, **Options**, and **Tags:** lists you curate.
* **Metafields:** the custom fields Atlios tracks and checks on your products.
* **Images:** the size, format and background each product's images are held to,
  set by image templates.

A list with something waiting shows how many decisions it holds. Images holds no
decisions, so it shows none. When a list has values in it, it is **Enforced**,
and products outside it are flagged on the next scan.

When nothing needs a decision the page says so.

<Note>
  The header says when Atlios last read your catalog. If that read did not
  finish, the header says how far it got, so an empty page is never mistaken for
  a complete one.
</Note>

## Decide values

Every value Atlios finds and cannot match to your lists becomes a decision. For
each one you can:

* **Approve** it to add it to your approved list.
* **Ignore** it so Atlios stops asking about it.
* **Skip** it to come back to it later.

Where several spellings look like the same thing, Atlios asks which one to keep
and settles the rest in the same step. Approving or ignoring a value changes only
your lists. It never changes your products.

Every decision saves as you make it. There is no save button.

## Vocabulary lists

Each list has a **Show** filter with three slices:

* **In use:** your approved values.
* **To review:** values waiting for a decision.
* **Ignored:** values the scan skips. You can restore any of them.

## Tags

Tags carry two extra kinds of rule, both on the Tags page:

* **Families:** tags that mean the same kind of thing, like `gender_male` and
  `gender_female`. Mark a family exclusive to flag products using more than one.
* **Conditional tags:** suggest a tag only when a related one is present.

Each rule saves on its own as you edit it.

## Metafields

Metafields are the custom fields on your products. Atlios tracks the ones you
choose and checks them during scans. Each tracked metafield has a **scope** of
either **Product** or **Variant**, which controls where it applies.

A metafield that points at another object, such as a metaobject entry, shows
the name of what it points at, never the underlying Shopify id.

See [Manage metafields](/guides/manage-metafields) for how to add, scope, and
stop tracking metafields.

## Metaobjects

Shopify's metaobject types are a read-only directory, under **Integrations**. It
shows each type in your store, its description, and its fields. You create and
change metaobject types in Shopify, under Settings, Custom data.


# Google Merchant Center
Source: https://docs.atlios.io/product/google-merchant-center

Pull Google Merchant Center disapprovals and account warnings into the same issue inbox as your Shopify scans.

The Google Merchant Center (GMC) integration pulls product disapprovals and
account warnings from Google into Atlios. They appear in the same issue inbox as
your Shopify scan findings, so one place covers both catalog quality and ad
eligibility.

Disapprovals cost ad eligibility and Free Listings reach. Surfacing them next to
your catalog work means a team can clear them in the same review cycle.

## What it does

You connect one Merchant Center account to a store. Atlios then checks Google
regularly and brings back three things:

* **Product status summary:** how many products are approved, pending, and
  disapproved, shown on the Google Merchant Center card.
* **Account warnings:** suspensions and warnings that affect the whole account.
* **Product disapprovals:** the specific products Google rejected, with the
  reason for each.

Atlios never changes anything in Google. For a few issue types, it can update
the matching field in Shopify so Google re-reviews the product. See
[supported checks](/reference/supported-checks) for which GMC issues you can fix
this way.

## How GMC issues appear

GMC issues use the same inbox as Shopify scans. You can tell them apart by the
rule name (every GMC rule is prefixed `GMC:`) and by filtering the **Rule**
control.

* **Product issues** group under their Shopify product, alongside any Shopify
  scan issues for the same product.
* **Account issues** show as a banner on the store home and at the top of the
  issue inbox. A suspension shows in red; other warnings show in amber. The only
  action is **Open in GMC**.
* **Unlinked products** is a separate group for GMC issues Atlios could not match
  to a Shopify product. These only offer **Open in GMC**.

Open a GMC issue to see what Google reported: the issue code, the affected
attribute, affected countries, reporting contexts, and Google's status. A **Learn
more** link opens Google's own help page for that issue.

## Fixing GMC issues

A few GMC issues have a guided fix in Atlios: missing GTIN, missing MPN, missing
brand, and description too short. For everything else, use **Open in GMC** and
resolve the issue in Google.

<Note>
  When you fix a GMC issue, Atlios updates the matching field in Shopify and the
  issue moves to a **Verifying** state. It stays there until the next sync
  confirms Google cleared the disapproval. It does not clear right away, because
  Google needs to re-review the product first.
</Note>

Once Google stops reporting an issue, Atlios resolves it for you on the next
sync.

## How often it syncs

Atlios checks Google every 4 hours for each connected store. To pull the latest
status sooner, choose **Sync now** on the Google Merchant Center card. After a
manual sync, wait a few seconds before you can run another.

The card shows when the last sync ran, and flags the connection as stale if it
has been more than 24 hours.

## Reporting contexts

Google reports product status per reporting context: Shopping Ads, Free
Listings, Local Inventory Ads, and Free Local Listings. The status summary on the
card uses Shopping Ads when available, then falls back to Free Listings.

## Get started

<Card title="Connect Google Merchant Center" icon="plug" href="/guides/connect-google-merchant-center">
  Link a Merchant Center account to a store.
</Card>


# Image workflows
Source: https://docs.atlios.io/product/image-workflows

How Atlios helps teams upload, process, review, and publish product images.

Use image workflows when you need to add product images, clean up existing
images, apply a consistent template, or review generated outputs before they go
to Shopify.

Image work has two paths:

* **Product images:** Add many images, match them to products, process them,
  review the results, and publish approved images to Shopify.
* **Issue-linked image workflow:** Start from an image issue, such as wrong size
  or format, then review and publish the processed images.

<Columns>
  <Card title="Product images" icon="upload" href="/guides/bulk-image-upload">
    Add images from your device, cloud storage, URLs, or a spreadsheet.
  </Card>

  <Card title="Image templates" icon="layout-template" href="/guides/manage-image-templates">
    Set the standard your product images are held to.
  </Card>

  <Card title="Review and publish" icon="check" href="/guides/review-and-publish-images">
    Approve, reject, regenerate, and publish image outputs.
  </Card>
</Columns>

## What happens in an image job

An image job is the work area for a batch of images. A job can upload files,
match them to products, process them through a template, prepare alt text and
filenames, and publish approved results.

<Steps>
  <Step title="Add images">
    Upload files, import from cloud storage, paste direct image URLs, or use a
    spreadsheet that maps image URLs to products.
  </Step>

  <Step title="Match products">
    Use smart matching, a CSV mapping, or manual matching so each image points
    at the right product.
  </Step>

  <Step title="Choose a template">
    Pick the saved template that controls the output size, format, background,
    lighting, and image scenario.
  </Step>

  <Step title="Process images">
    Atlios generates optimized image outputs. You can leave the page and return
    from Activity.
  </Step>

  <Step title="Review outputs">
    Approve strong outputs, reject wrong outputs, regenerate items that need
    another pass, and choose a featured image when needed.
  </Step>

  <Step title="Publish to Shopify">
    Publish approved images when they are ready for customer-facing product
    pages.
  </Step>
</Steps>

## Image template scenarios

Templates let you save common image treatments for reuse.

<Tabs>
  <Tab title="Studio">
    Use for clean catalog shots on a solid backdrop. Choose a background color,
    shadow style, light direction, output size, and format.
  </Tab>

  <Tab title="Background">
    Use when you need the product cut out on a transparent or solid-color
    background. Transparent outputs use PNG.
  </Tab>

  <Tab title="Editorial">
    Use when you want the product placed in a described scene, such as a
    seasonal setting or lifestyle backdrop.
  </Tab>

  <Tab title="Flat-lay">
    Use for garments shown from above on a surface or clean color backdrop.
  </Tab>

  <Tab title="On-model">
    Use for garments shown on a generated model. Choose framing, pose, and
    setting.
  </Tab>
</Tabs>

## Generate a scene from the video page

When you set up a product video, the source photo tile has a **Generate a
scene** button. Describe the setting you want, and Atlios makes one photo of
that product in that scene and offers it as the video's source photo. You stay
on the page.

The photo costs one image generation, shown on the button before you commit,
and is charged separately from the video.

The result is an ordinary image in your media:

* It is saved and reusable, so you can pick it as the source for later videos.
* It is not published to Shopify. Publishing it is still the explicit publish
  step in review and publish.
* A solid background color on the video style repaints the video's first frame,
  which replaces the scene. Leave the background on **Keep photo** to keep it.

Only one image job can run per store at a time. A scene request made while
other image work is running is not queued: Atlios says so and keeps the scene
you typed, so you can generate again once the other work finishes.

## Human review stays required

<Note>
  Atlios does not publish processed images until you approve them. Always check
  product identity, color accuracy, crop, background, edges, shadows, alt text,
  and featured image choice before publishing.
</Note>

## Issue-linked image work

Some catalog issues send you to the image workflow. For example, the **Wrong
image size or format** issue can start an image job that applies your default
template to flagged images.

The image job handles processing and publishing. The issue stays open until
Atlios verifies the catalog again.


# Issue inbox
Source: https://docs.atlios.io/product/issue-inbox

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

The issue inbox is where you review the catalog issues Atlios found in the
latest scans. It sits in the sidebar as Fix, with a count of the open work, 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
suppressed as an intentional exception.

## What you see

The inbox shows active issues by default. Each row includes the affected
product, the issue summary, rule, status, severity, and when Atlios last
detected it.

Issues from [Google Merchant Center](/product/google-merchant-center) appear here
too, prefixed `GMC:`. Account-level GMC warnings show as a banner above the list.

The summary at the top highlights:

* Active issues.
* Critical issues.
* High-severity issues.
* Issues resolved in the last 7 days.

You can also open scan settings, export issues, and open the suppression list
from the inbox controls.

## Find the right issues

Use the inbox controls to narrow the list:

* **Search** by product title, rule name, or issue message.
* **Status** to show open, verifying, resolved, or suppressed issues.
* **Sort** to order by severity or last seen date.
* **Severity** to focus on critical and high-severity work first.
* **Rule** to review one type of issue at a time.
* **Source** to focus on issues from your scan or from Google Merchant Center.
  An issue flagged by both shows a badge for each and appears once.
* **Group by** to organize the list by problem area, priority, check, product,
  entity type, attribute, or Google's reason. **Problem area** is the nine-way
  breakdown of what kind of problem it is.

**Group by Google's reason** 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 your scan is
grouped under Google's reason, 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.
</Tip>

## 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.
* A **Google-confirmed** indicator when Google Merchant Center is one of the
  sources, so you know the problem also affects your Google listings.
* The most useful details for that check.
* Any available fix action.
* Suppression options.
* Recent activity, such as fixes, suppressions, 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

<Steps>
  <Step title="Start with the highest impact issues">
    Use severity and rule filters to focus the inbox.
  </Step>

  <Step title="Open the issue">
    Read the issue message, affected product, and details.
  </Step>

  <Step title="Choose an action">
    Apply a supported fix, review a proposed fix, enter a required value, open
    the product for manual editing, or suppress a valid exception.
  </Step>

  <Step title="Let Atlios confirm">
    After fixes or Shopify edits, Atlios re-checks the affected products
    automatically and resolves issues that no longer apply.
  </Step>
</Steps>

## Available actions

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

<AccordionGroup>
  <Accordion title="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>

  <Accordion title="Enter a value">
    Use this when Atlios needs a value from you, such as SKU, barcode, or price.
  </Accordion>

  <Accordion title="Open an image workflow">
    Use this for image template mismatch issues that need generated image review
    before publishing.
  </Accordion>

  <Accordion title="Generate more images">
    Use this on a product flagged for too few images to generate extra angles
    for review before publishing.
  </Accordion>

  <Accordion title="Suppress an exception">
    Use suppression when the catalog state is intentional and should not keep
    appearing as active work.
  </Accordion>

  <Accordion title="Open product">
    Use this when the issue is inspect-only or needs a manual Shopify edit.
  </Accordion>
</AccordionGroup>

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

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

For a focused walkthrough, see [Use bulk issue actions](/guides/use-bulk-issue-actions).


# Products
Source: https://docs.atlios.io/product/products

Browse, edit, and create Shopify products from inside Atlios.

The **Products** area is where you work directly with the products in a
connected store. You can browse your catalog, open a product to edit it, create
new products, and create or update many products at once.

Changes you make here are saved back to Shopify, so review them the same way you
would review an edit in your Shopify admin.

<Columns>
  <Card title="Edit a product" icon="pencil" href="/guides/edit-a-product">
    Update titles, descriptions, media, variants, and metafields.
  </Card>

  <Card title="Create products in bulk" icon="table" href="/guides/bulk-create-products">
    Use a spreadsheet and images to create many products at once.
  </Card>
</Columns>

## Browse your catalog

The products list shows every product in the store with its image, title,
vendor, type, status, inventory, price, and any open issues.

You can:

* **Search** by product title.
* **Filter** by status, vendor, type, collection, tag, or whether a product has
  open issues.
* **Sort** by title, inventory, created date, or updated date.
* **Select** individual products, every product on the page, or every product
  that matches your current filters.

Status is shown as **Active**, **Draft**, or **Archived**. When a product has
open catalog issues, a severity badge appears so you can spot the products that
need attention first.

<Tip>
  Use the **Has open issues** filter to jump straight to the products a scan
  flagged, then open each one to review or fix it.
</Tip>

## Open and edit a product

Open any product to view and edit its details. You can change the title,
description, status, vendor, type, tags, and collections, manage media and alt
text, edit options and variants, set pricing and inventory per location, update
the SEO description, and edit tracked metafields.

The editor keeps an **Unsaved changes** indicator while you work, and the
**Save** button stays disabled until you make a change. If a product is missing
important details such as a title, description, or price, Atlios warns you
before you save, but you can still confirm the save.

If a product is missing details, **Look up details** in the editor pulls the
title, vendor, type, and description from an external database by barcode, ISBN,
or model. See [Look up product details](/guides/look-up-product-details).

For the full walkthrough, see [Edit a product](/guides/edit-a-product).

## Create a product

Create a new product using the same editor. New products start as **Draft** so
you can finish the details before they appear on your storefront. You can upload
images and apply an image template while you build the product, then publish it
when it is ready.

## Create or update many products

When you need to add a large batch of products, use the bulk creator. You
download a spreadsheet template that already includes your store's vendors,
product types, and inventory locations, fill it in, and upload it together with
a folder of images.

Atlios checks the file, lets you review each product before anything is created,
and can match your images to the right products. You can also ask Atlios to
generate a product description for a product from its title and images.

See [Create products in bulk](/guides/bulk-create-products) for the full flow.

## Product settings

Product settings control how Atlios treats products across the whole store:

* **Products:** rules that apply to every product, such as automatic tags and
  default field values.
* **AI:** your brand voice and instructions for how Atlios writes product copy,
  tags, and alt text.

<Note>
  Deleting products is permanent and is limited to 50 products at a time. Always
  confirm the selection before you delete.
</Note>


# Scans and issues
Source: https://docs.atlios.io/product/scans-and-issues

How scans produce actionable issues in Atlios.

A scan checks a store's catalog and storefront signals, then turns findings into
issues that teams can review and resolve.

Issues are the primary review surface in Atlios. They help teams focus on the
catalog work that needs attention, including missing data, invalid values,
duplicate identifiers, weak image metadata, and live-page findings such as a
product page that cannot be reached or is blocked from indexing.

Storefront verification also confirms a fix on the rendered page after a meta
title or meta description fix applies. Those two fields are the whole
rendered-page confirmation scope. Other fix types are confirmed against Shopify,
not against the page.

## Scan coverage

A scan checks product data, variant data, cross-product conflicts, and product
images. It does not fetch your live product pages: those are read separately,
after Atlios applies a meta title or meta description fix. Coverage can expand
over time as new quality rules are added.

## Issue review

Each issue should answer three questions:

* What is wrong or worth reviewing?
* Which product, variant, or storefront page is affected?
* What action should the team take next?

## Issue sources

Most issues come from catalog scans. If you connect [Google Merchant
Center](/product/google-merchant-center), Google's product disapprovals and
account warnings appear in the same inbox, prefixed `GMC:`. Filter by rule to
focus on one source.

When the scan and Google flag the same field on the same product, Atlios merges
them into one issue that carries both source badges. It counts once, and
resolving it clears both signals.

## Suppression

Some issues are valid exceptions for a specific store or product. Suppression
lets teams intentionally quiet those issues without losing scan history.


# Quickstart
Source: https://docs.atlios.io/quickstart

Connect a Shopify store and review your first catalog quality scan.

Use this flow when you are setting up Atlios for the first time.

<Info>
  You need permission to install apps for the target Shopify store before you
  start.
</Info>

<Steps>
  <Step title="Connect your store">
    Install Atlios for the Shopify store you want to monitor. During
    installation, Shopify asks you to approve the permissions Atlios needs to
    read catalog data and run quality workflows.

    After installation, Atlios keeps store metadata in sync so scans and fixes
    have the current product, variant, inventory, and storefront context.
  </Step>

  <Step title="Atlios runs the first scan">
    Once the store is connected, Atlios runs the first scan automatically. It
    checks product and variant data, image coverage, and metadata that can
    affect catalog quality.

    Scan results are grouped into issues so teams can focus on what needs
    review instead of reading raw validation output.
  </Step>

  <Step title="Review issues">
    Open the issue list to inspect severity, affected products, and recommended
    next steps. Some findings are informational; others indicate missing or
    invalid catalog data that should be fixed before products are published or
    promoted.
  </Step>

  <Step title="Apply supported fixes">
    For supported issue types, Atlios can prepare guided fixes.

    <Warning>
      Review each suggestion before applying it. Fixes affect live catalog
      content and should still match your store's merchandising standards.
    </Warning>
  </Step>

  <Step title="Let Atlios confirm">
    After fixing issues, Atlios re-checks the affected products automatically as
    the changes land in Shopify, and resolved issues drop off the list. See [How
    your catalog stays current](/concepts/scan-freshness).
  </Step>
</Steps>


# FAQ
Source: https://docs.atlios.io/reference/faq

Common questions about installing, scanning, and managing catalog data with Atlios.

Answers to the questions catalog teams ask most often.

<Note>
  If your question is not covered here, check the [troubleshooting
  reference](/reference/troubleshooting) or reach out to support.
</Note>

## Setup and connection

<AccordionGroup>
  <Accordion title="How is Atlios different from Shopify's built-in product validation?">
    Shopify validates basic fields at save time. Atlios runs broader catalog
    quality checks across products, variants, images, and cross-product
    conflicts, then groups findings into reviewable issues with severity and
    history. After it applies a meta title or meta description fix, Atlios also
    reads that product's rendered page to confirm the value went live and to
    report live-page problems.
  </Accordion>

  <Accordion title="Can I connect more than one Shopify store?">
    Yes. Each store is connected separately and shows up as its own workspace in
    Atlios. Scans, issues, and suppressions are tracked per store.
  </Accordion>

  <Accordion title="What Shopify permissions does Atlios need?">
    Atlios requests read access to products, inventory, locations, online store
    navigation, and metaobjects. These scopes cover product, variant, and image
    metadata used by scans, plus your store's web address and each product's
    page URL, which Atlios needs to fetch the live page. Shopify shows the exact
    scopes on the install screen before you approve.
  </Accordion>

  <Accordion title="Do I need a paid Shopify plan?">
    Atlios works with the standard Shopify plans that allow third-party app
    installation. Check the install prerequisites in your Shopify admin if the
    install step is blocked.
  </Accordion>

  <Accordion title="Can I connect Google Merchant Center?">
    Yes. Each store can connect one Merchant Center account. Atlios pulls
    product disapprovals and account warnings into the same issue inbox as your
    Shopify scans. See [Connect Google Merchant
    Center](/guides/connect-google-merchant-center).
  </Accordion>
</AccordionGroup>

## Scans and issues

<AccordionGroup>
  <Accordion title="How long does a scan take?">
    Scan time depends on catalog size and the checks enabled. Small catalogs
    typically finish in minutes; larger catalogs can take longer. The scan runs
    in the background; you do not need to keep the tab open.
  </Accordion>

  <Accordion title="Will Atlios change my catalog without permission?">
    No. Atlios only writes changes when you apply a guided fix and confirm the
    proposed change. Read-only checks never modify product data.
  </Accordion>

  <Accordion title="Can I schedule scans?">
    Yes. Atlios runs scheduled scans automatically on a cadence that depends on
    your plan, and re-checks individual products as soon as they change in
    Shopify, so you do not need to start scans yourself. See [scan
    freshness](/concepts/scan-freshness) for the full cadence.
  </Accordion>

  <Accordion title="What is the difference between fixing and suppressing?">
    Fixing changes the underlying product or variant data. Suppression marks an
    issue as an intentional exception so it stops appearing in future review
    cycles. See [suppressions](/concepts/suppressions) for details.
  </Accordion>

  <Accordion title="Why is my Google Merchant Center issue stuck on Verifying?">
    A fixed GMC issue stays in **Verifying** until the next sync confirms Google
    cleared the disapproval. Atlios syncs every 4 hours, or you can use **Sync
    now** on the Google Merchant Center card to check sooner.
  </Accordion>
</AccordionGroup>

## Data and accounts

<AccordionGroup>
  <Accordion title="Where is my catalog data stored?">
    Atlios stores metadata required to run scans and track issue history.
    Catalog data remains in Shopify; Atlios reads from Shopify on each scan.
  </Accordion>

  <Accordion title="What happens if I uninstall Atlios from Shopify?">
    Uninstalling revokes Atlios's access to the store. Scan history and issue
    records can be retained or deleted based on your workspace settings. Contact
    support if you need data removed immediately.
  </Accordion>

  <Accordion title="Can I invite teammates?">
    Yes. Owners can invite teammates and assign roles. Admins can run catalog
    work, but only owners can manage members, billing, and store connections.
    See [user roles](/reference/user-roles) for the full breakdown.
  </Accordion>
</AccordionGroup>


# Settings
Source: https://docs.atlios.io/reference/settings

Manage your organization, members, connected stores, billing, and per-store settings.

Atlios has two kinds of settings. **Account settings** cover the whole
workspace and live under **Settings**. **Store settings** cover one store and
live inside that store.

## Account settings

Opening **Settings** takes you to **Organization**. The other sections are
beside it.

### Organization

Set your organization's name and its short web address. This is also where the
**Danger zone** lives, which permanently deletes the organization and
everything in it. Owner only.

### Members

Invite teammates, set their role, remove people, and choose which stores each
person can reach. See [User roles](/reference/user-roles) for what each role
allows. Owner only.

### Stores

Connect new Shopify stores, see the status of the stores you have connected, and
reconnect or disconnect a store. See
[Manage connected stores](/guides/manage-stores). Owner only.

### Billing

Manage your plan, trial, credits, and payment details. See
[Billing and credits](/product/billing-and-credits). Everyone can see the page;
only the owner can change the plan or buy credits.

<Info>
  Organization, Members, and Stores are owner only. If you are not the owner,
  opening one shows an "Owner access required" message instead of the page.
  Billing is the exception: it opens for everyone, and the buttons that spend
  money are owner only.
</Info>

## Store settings

These settings belong to one store, so each store has its own.

### Automation

**Products > Settings > Automation**. Decide what Atlios does on its own:

* **Keep new products clean:** apply the safe, non-AI fixes to a product as
  soon as it is published.
* **Restyle new images automatically:** run your matching image template on new
  images, either preparing them for review or publishing them without review.
* **Product rules:** the per-field rules Atlios holds your products to.

### AI generation

**Products > Settings > AI generation**. Shape what the AI writes:

* **Lio:** whether the catalog agent may apply prepared changes from chat.
* **Brand voice:** the voice all generated copy follows.
* **Descriptions** and **Titles:** the quality bar generated copy must clear.

### Scan settings

**Fix > Settings**. Choose which checks run against this store, what severity
each one carries, which product states are scanned, and whether the image
subject-position audit runs on the featured image only or on all images.


# Supported checks
Source: https://docs.atlios.io/reference/supported-checks

Current catalog checks surfaced by Atlios, with what triggers each issue and what fix path is available.

Atlios runs checks against connected Shopify stores and creates an issue when a
product, variant, image, or cross-catalog pattern needs review.

Each check has a default severity. Store settings can change which checks run
and how severe they appear.

<Note>
  This page describes the current supported checks and fix paths. The app shows
  the exact action available for the issue you open.
</Note>

## How to read this page

* **Triggers when** explains why Atlios creates the issue.
* **Default severity** is the built-in priority before store-specific changes.
* **Fix path** explains what Atlios can help with.
* **No auto-fix when** explains when the issue needs manual review or a scan
  after a manual change.

For fix behavior, review rules, skips, and bulk exclusions, see
[Supported fixes](/reference/supported-fixes).

<Tabs>
  <Tab title="Images">
    <AccordionGroup>
      <Accordion title="Too few images">
        **Triggers when:** A product has fewer images than the configured
        minimum. The default minimum is 3 images.

        **Default severity:** Medium, raised to High when the product has no
        images at all.

        **Fix path:** Manual input. Open Shopify and upload enough images.

        **No auto-fix when:** Atlios cannot source or choose missing product
        images for you. Draft or archived products may be treated as not
        actionable.
      </Accordion>

      <Accordion title="Missing featured image">
        **Triggers when:** A product has no featured image.

        **Default severity:** High.

        **Fix path:** Direct apply. Atlios can set the first accessible product
        image as the featured image.

        **No auto-fix when:** The product has no accessible images.
      </Accordion>

      <Accordion title="Weak alt text">
        **Triggers when:** Image alt text is missing, too short, too long,
        generic, repeated across images, stuffed with repeated terms, or scored
        below the configured AI threshold.

        **Default severity:** Medium.

        **Fix path:** Review optional. Atlios can generate improved alt text for
        flagged images.

        **No auto-fix when:** AI is unavailable, issue evidence does not include
        image details, or AI returns no usable changed alt text.
      </Accordion>

      <Accordion title="Generic filename">
        **Triggers when:** Image filenames look generic, random, hash-like, too
        short, or do not follow a descriptive lowercase hyphenated format.

        **Default severity:** Low.

        **Fix path:** Direct apply. Atlios can prepare SEO-friendly filenames
        based on the product title.

        **No auto-fix when:** The issue evidence does not include image filename
        details, or the live Shopify filenames are already acceptable.
      </Accordion>

      <Accordion title="Wrong image size or format">
        **Triggers when:** Product images do not match the store's default
        image template dimensions or output format. Atlios skips detection for
        an untouched seed default template.

        **Default severity:** Low.

        **Fix path:** Manual input. Atlios builds a template-application
        job for the flagged images.

        **No auto-fix when:** The image needs workflow review before publishing
        back to Shopify. This issue is handled outside the normal fix engine.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Content">
    <AccordionGroup>
      <Accordion title="Weak product description">
        **Triggers when:** A description is missing, too short, has too few
        words, overlaps too heavily with the product title, contains known weak
        placeholder terms, or repeats terms too often.

        **Default severity:** Medium.

        **Fix path:** Review optional. Atlios can generate a product
        description draft. When the SEO setting is enabled, it can also prepare
        a paired SEO description.

        **No auto-fix when:** AI is unavailable or generation fails.
      </Accordion>

      <Accordion title="Weak product title">
        **Triggers when:** A title is missing, too short, too long, generic, or
        repeats terms in a way that makes the title less useful.

        **Default severity:** Medium.

        **Fix path:** Review optional. Atlios can generate a clearer product
        title suggestion.

        **No auto-fix when:** AI is unavailable, returns no usable title, or the
        suggestion matches the current title.
      </Accordion>

      <Accordion title="Duplicate product title">
        **Triggers when:** More than one product shares the same normalized
        title. Draft products are ignored by default.

        **Default severity:** High.

        **Fix path:** Review optional. Atlios can generate a distinct title for
        the affected product.

        **No auto-fix when:** AI is unavailable, duplicate-title context is
        missing, or the suggestion is unchanged or still duplicated.
      </Accordion>

      <Accordion title="Duplicate product description">
        **Triggers when:** More than one product shares the same normalized
        plain-text description. Very short descriptions are ignored by default.
        Draft products are ignored by default.

        **Default severity:** Medium.

        **Fix path:** Review optional. Atlios can generate a rewritten
        description to differentiate the product.

        **No auto-fix when:** AI is unavailable, returns no usable description,
        or the suggestion matches the current description.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Tags">
    <AccordionGroup>
      <Accordion title="Missing tags">
        **Triggers when:** A product has no tags.

        **Default severity:** Medium.

        **Fix path:** Review optional. Atlios can generate tag suggestions using
        product context, existing store tags, collection tag mappings, and
        similar products when available.

        **No auto-fix when:** AI is unavailable or generation fails.
      </Accordion>

      <Accordion title="Unusual product tags">
        **Triggers when:** Product tags look unusual compared with store tag
        patterns and similar products. Signals can include rare tags,
        misspellings similar to common tags, missing common peer tags, or low
        overlap with peer product tag patterns.

        **Default severity:** Medium.

        **Fix path:** Review required. Atlios can prepare a conservative tag
        patch showing tags to add and remove.

        **No auto-fix when:** The patch would make no effective change or the
        pattern is intentional. Suppress the issue or ignore the pattern when it
        is a valid exception.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Variants">
    <AccordionGroup>
      <Accordion title="Missing SKU">
        **Triggers when:** A variant has no SKU.

        **Default severity:** High.

        **Fix path:** Manual input. Enter the SKU before applying.

        **No auto-fix when:** Atlios should not invent SKU values. The action is
        unavailable if variant identity is missing.
      </Accordion>

      <Accordion title="Missing barcode">
        **Triggers when:** A variant has no barcode.

        **Default severity:** Medium.

        **Fix path:** Review required. Atlios proposes the variant's SKU as
        its barcode for you to review before applying.

        **No auto-fix when:** Atlios should not invent GTIN, UPC, EAN, or ISBN
        values. The action is unavailable if variant identity is missing.
      </Accordion>

      <Accordion title="Zero price">
        **Triggers when:** A variant price is missing or parses as zero.

        **Default severity:** Critical.

        **Fix path:** Manual input. Enter the correct price before applying.

        **No auto-fix when:** Atlios should not choose product prices for you.
        The action is unavailable if variant identity is missing.
      </Accordion>

      <Accordion title="Invalid compare-at price">
        **Triggers when:** Compare-at price is set and is lower than the selling
        price.

        **Default severity:** High.

        **Fix path:** Direct apply. Atlios can remove the compare-at price. The
        review UI can also offer a swap option when the prices appear reversed.

        **No auto-fix when:** Price evidence is missing from the issue.
      </Accordion>

      <Accordion title="Negative inventory">
        **Triggers when:** A variant inventory quantity is below zero.

        **Default severity:** High.

        **Fix path:** Inspect only.

        **No auto-fix when:** Inventory must be reconciled in Shopify or your
        inventory system.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Uniqueness">
    <AccordionGroup>
      <Accordion title="Duplicate SKU">
        **Triggers when:** The same SKU is used by more than one variant.

        **Default severity:** Critical.

        **Fix path:** Manual input. Enter a distinct SKU for the affected
        variant.

        **No auto-fix when:** Atlios should not invent identifier values, the
        variant identity is missing, or the variant no longer has a duplicate
        SKU.
      </Accordion>

      <Accordion title="Duplicate barcode">
        **Triggers when:** The same barcode is used by more than one variant.

        **Default severity:** High.

        **Fix path:** Manual input. Enter a distinct barcode for the affected
        variant.

        **No auto-fix when:** Atlios should not invent barcode values, the
        variant identity is missing, or the variant no longer has a duplicate
        barcode.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Catalog standards">
    <AccordionGroup>
      <Accordion title="Vendor isn't an approved value">
        **Triggers when:** The product vendor is not on the store's approved
        vendor list.

        **Default severity:** Medium.

        **Fix path:** Inspect only. Update the vendor or update your catalog
        standards if the value should be allowed.
      </Accordion>

      <Accordion title="Product type isn't an approved value">
        **Triggers when:** The product type is not on the store's approved
        product type list.

        **Default severity:** Medium.

        **Fix path:** Inspect only. Update the product type or update your
        catalog standards if the value should be allowed.
      </Accordion>

      <Accordion title="Tag isn't an approved value">
        **Triggers when:** A product tag is not on the store's approved tag
        list. Atlios creates one issue for each tag that isn't approved.

        **Default severity:** Medium.

        **Fix path:** Inspect only. Update the tag, update your catalog
        standards, or suppress the exception.
      </Accordion>

      <Accordion title="Option name isn't an approved value">
        **Triggers when:** A variant option name is not on the approved
        option-name list.

        **Default severity:** Medium.

        **Fix path:** Inspect only. Update the option structure or your catalog
        standards.
      </Accordion>

      <Accordion title="Option value isn't an approved value">
        **Triggers when:** A variant option value is not allowed for its option
        name.

        **Default severity:** Medium.

        **Fix path:** Inspect only. Update the option value or your catalog
        standards.
      </Accordion>

      <Accordion title="Metafield value isn't an approved value">
        **Triggers when:** A product metafield value is outside the Google
        Merchant Center enum or merchant allowlist for that metafield. Malformed
        list values can also be flagged.

        **Default severity:** Medium.

        **Fix path:** Review optional. Atlios can normalize by trimming
        whitespace, matching case, or applying a known synonym.

        **No auto-fix when:** The value is a malformed list, there is no
        allowlist, no confident match exists, or the Shopify metafield type
        cannot be resolved.
      </Accordion>

      <Accordion title="Variant metafield value isn't an approved value">
        **Triggers when:** A variant metafield value is outside the Google
        Merchant Center enum or merchant allowlist for that metafield.

        **Default severity:** Medium.

        **Fix path:** Review optional. Atlios can normalize by trimming
        whitespace, matching case, or applying a known synonym.

        **No auto-fix when:** The value is a malformed list, there is no
        allowlist, no confident match exists, or the Shopify metafield type
        cannot be resolved.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Metafields">
    <AccordionGroup>
      <Accordion title="Missing metafield">
        **Triggers when:** An in-scope product metafield is missing or blank.

        **Default severity:** Medium.

        **Fix path:** Review optional. Atlios can apply a default when the
        Google Merchant Center enum or your catalog standards has exactly one
        allowed value.

        **No auto-fix when:** No single unambiguous default exists, or the
        Shopify metafield type cannot be resolved.
      </Accordion>

      <Accordion title="Missing variant metafield">
        **Triggers when:** An in-scope variant metafield is missing, blank, or an
        empty list.

        **Default severity:** Medium.

        **Fix path:** Review optional. Atlios can apply a default when the
        Google Merchant Center enum or your catalog standards has exactly one
        allowed value.

        **No auto-fix when:** No single unambiguous default exists, or the
        Shopify metafield type cannot be resolved.
      </Accordion>

      <Accordion title="Invalid metafield format">
        **Triggers when:** A product metafield value does not match the expected
        Google Merchant Center format.

        **Default severity:** Medium.

        **Fix path:** Direct apply. Atlios trims surrounding whitespace
        and apply the value only when the trimmed value passes validation.

        **No auto-fix when:** The problem needs more than whitespace trimming,
        the field is not a known Google format field, the value has no
        surrounding whitespace, or the trimmed value still fails validation.
      </Accordion>

      <Accordion title="Invalid variant metafield format">
        **Triggers when:** A variant metafield value does not match the expected
        Google Merchant Center format.

        **Default severity:** Medium.

        **Fix path:** Direct apply. Atlios trims surrounding whitespace
        and apply the value only when the trimmed value passes validation.

        **No auto-fix when:** The problem needs more than whitespace trimming,
        the field is not a known Google format field, the value has no
        surrounding whitespace, or the trimmed value still fails validation.
      </Accordion>

      <Accordion title="Metafield value doesn't match its rule">
        **Triggers when:** A product matches an assignment rule, but the
        metafield is missing or does not equal the expected value.

        **Default severity:** Medium.

        **Fix path:** Review optional. Atlios can set the metafield to the value
        expected by the matching assignment rule.

        **No auto-fix when:** Issue evidence is incomplete or the Shopify
        metafield type cannot be resolved.
      </Accordion>

      <Accordion title="Variant metafield value doesn't match its rule">
        **Triggers when:** A variant matches an assignment rule, but the
        metafield is missing or does not equal the expected value.

        **Default severity:** Medium.

        **Fix path:** Review optional. Atlios can set the metafield to the value
        expected by the matching assignment rule.

        **No auto-fix when:** Issue evidence is incomplete or the Shopify
        metafield type cannot be resolved.
      </Accordion>

      <Accordion title="Unclassified product">
        **Triggers when:** Assignment rules exist for a metafield, but no rule
        matches the product.

        **Default severity:** Low.

        **Fix path:** Inspect only. Update the assignment rule conditions, add a
        default rule, or update the product classification data.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Google Merchant Center">
    These issues come from the [Google Merchant Center
    integration](/product/google-merchant-center), not from a catalog scan.
    Google reports them and Atlios shows them in the same inbox. Most use **Open
    in GMC**, where you resolve the issue in Google; a few have a guided fix that
    updates the matching Shopify field. After any fix, the issue stays in
    **Verifying** until the next sync confirms Google cleared it.

    <Note>
      Atlios may show a higher severity than the default below when Google marks
      the issue as critical. Any GMC issue type not listed here still appears,
      with Google's original wording.
    </Note>

    <AccordionGroup>
      <Accordion title="Missing GTIN">
        **Triggers when:** Google reports a product variant with no GTIN.

        **Default severity:** High.

        **Fix path:** Manual input. Enter the GTIN to save it as the Shopify variant barcode.
      </Accordion>

      <Accordion title="Missing MPN">
        **Triggers when:** Google reports a product variant with no MPN.

        **Default severity:** Medium.

        **Fix path:** Review required. The product is looked up by its
        barcode and a manufacturer part number is suggested. You review or edit
        the value, then it lands in the Shopify variant SKU.
      </Accordion>

      <Accordion title="Missing brand">
        **Triggers when:** Google reports a product with no brand.

        **Default severity:** High.

        **Fix path:** Review required. The product is looked up by its
        barcode or ISBN and a brand is suggested. You review or edit the value,
        then it lands in the Shopify product vendor field.
      </Accordion>

      <Accordion title="Description too short">
        **Triggers when:** Google flags a product description as too short.

        **Default severity:** Medium.

        **Fix path:** Review required. Atlios can generate a longer description
        for review before it writes to Shopify.
      </Accordion>

      <Accordion title="Title too long">
        **Triggers when:** Google flags a product title as too long.

        **Default severity:** Medium.

        **Fix path:** Review required. Atlios rewrites the title to fit
        Google's limit. The storefront title changes too, so you review it
        before it is applied.
      </Accordion>

      <Accordion title="Image link missing">
        **Triggers when:** Google cannot find an image link for the product.

        **Default severity:** Critical.

        **Fix path:** Review required. Atlios proposes the product's first
        image as its featured image, so Google has an image link. If the product
        has no images yet, upload one first.
      </Accordion>

      <Accordion title="Condition missing">
        **Triggers when:** Google reports a product with no condition value.

        **Default severity:** Medium.

        **Fix path:** Open in GMC.
      </Accordion>

      <Accordion title="Availability mismatch">
        **Triggers when:** The availability Google has does not match the
        product's actual availability.

        **Default severity:** High.

        **Fix path:** Open in GMC.
      </Accordion>

      <Accordion title="Price mismatch">
        **Triggers when:** The price Google has does not match the price on the
        landing page.

        **Default severity:** High.

        **Fix path:** Open in GMC.
      </Accordion>

      <Accordion title="Policy violation">
        **Triggers when:** Google flags the product for a policy violation.

        **Default severity:** Critical.

        **Fix path:** Open in GMC.
      </Accordion>

      <Accordion title="Landing page error">
        **Triggers when:** Google cannot crawl or reach the product landing page.

        **Default severity:** High.

        **Fix path:** Manual input. Choose which sales channels the product
        publishes to. The change lands in Shopify so Google can check the
        landing page again.
      </Accordion>

      <Accordion title="Local inventory issues">
        **Triggers when:** Google reports missing local inventory data, a missing
        in-store price, or a zero or negative in-store price for local listings.

        **Default severity:** High, except a zero or negative in-store price,
        which is Medium.

        **Fix path:** Open in GMC.
      </Accordion>

      <Accordion title="Product ID already used">
        **Triggers when:** The product ID conflicts with another item already in
        the account.

        **Default severity:** High.

        **Fix path:** Open in GMC.
      </Accordion>

      <Accordion title="Account suspended">
        **Triggers when:** Google suspends the Merchant Center account. Shown as
        an account-level banner, not a product row.

        **Default severity:** Critical.

        **Fix path:** Open in GMC.
      </Accordion>

      <Accordion title="Account warning">
        **Triggers when:** Google issues an account-level warning. Shown as an
        account-level banner, not a product row.

        **Default severity:** High.

        **Fix path:** Open in GMC.
      </Accordion>
    </AccordionGroup>
  </Tab>
</Tabs>


# Supported fixes
Source: https://docs.atlios.io/reference/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. 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.

<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, 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.
  </Accordion>

  <Accordion title="Manual input">
    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.
  </Accordion>

  <Accordion title="Inspect only">
    Some issues do not have a fixer by design. Review the context, update the
    product, variant, Shopify inventory, catalog standards, 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.
* 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 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 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.


# Troubleshooting
Source: https://docs.atlios.io/reference/troubleshooting

Common setup and workflow issues.

Use these checks when Atlios does not behave as expected. For broader questions,
see the [FAQ](/reference/faq).

## Store does not appear after installation

<Note>
  Confirm that installation completed in Shopify and that you returned to the
  Atlios workspace after approving permissions. If the store still does not
  appear, reconnect the store.
</Note>

## Scan results look stale

<Tip>
  Atlios re-checks products automatically after they change in Shopify and
  rescans on a schedule. Atlios tracks scan history, so make sure you are
  reviewing the latest completed scan.
</Tip>

## A fix is not available

Not every issue type has an automated or guided fix. Some catalog problems
need manual review in Shopify before Atlios can verify the result.

Check [Supported checks](/reference/supported-checks) to see whether the issue
type has a direct fix, reviewable suggestion, manual input, image workflow, or
inspect-only path.

## A fix was skipped

Atlios skips a fix when it cannot make a safe change. The product may have
changed since the scan, the issue evidence may be stale, AI may be unavailable,
or the suggested change may be empty or unchanged.

After manual edits, Atlios re-checks the product automatically. If the issue
still appears, open the issue activity to read the skip reason.

## Bulk action skipped some selected issues

Bulk actions exclude issues that need individual decisions. Manual-input,
review-required, already verifying, resolved, suppressed, and inspect-only
issues may be skipped from a bulk fix.

Filter by one rule first when you want the most predictable bulk result.

## Image job is still processing

Image jobs can take time, especially for larger batches. You can leave the page
and return from **Activity** in the sidebar. Finished items appear for review as
they complete.

## Image matched to the wrong product

Go back to the match step before processing, or use manual matching to assign
the image to the correct product. If the job already processed, reject the
wrong output and start a corrected job.

## Image output looks wrong

Reject outputs that should not be published. Use regenerate when the template
is right but the result needs another pass. If the template is wrong, choose a
different template and reprocess the image before approving it.

## Transparent image did not export as expected

Transparent background removal outputs must use PNG. If you need JPEG or WebP,
use a solid background color instead of transparency.

## Published image issue still appears

Run a new catalog scan after publishing images. Image issues, such as wrong
size or format, are verified by scan results after Shopify has the updated
media.

## Suppressed issue came back

Removing a suppression allows Atlios to detect the issue again. If the
underlying catalog state still matches the rule, the issue can return on the
next scan.

## Storefront checks fail

<Warning>
  Storefront verification fetches the rendered product page, where it confirms a
  fixed meta title or meta description and reports live-page findings. Confirm
  that the product is published, accessible, and using the expected storefront
  template.
</Warning>

## Google Merchant Center will not connect

Connecting to Google Merchant Center needs an account admin. If you see an admin
or permission error, confirm you are an admin on the Merchant Center account, not
just a Shopify or Atlios admin.

Other common causes:

* The Merchant Center ID is wrong. Copy the digits from the account switcher at
  [merchants.google.com](https://merchants.google.com).
* The account is already connected to this store. Disconnect first, then
  reconnect.
* Only a workspace owner can connect a Merchant Center account.

## Google Merchant Center issues are not appearing

The first sync starts a few minutes after you connect, while Atlios finishes
setting up with Google. After that, Atlios syncs every 4 hours. Use **Sync now**
on the Google Merchant Center card to pull the latest status sooner.

If the card shows **Access expired**, Google revoked the connection. Choose
**Reconnect** and approve access again.

## A Google Merchant Center issue is stuck on Verifying

A fixed GMC issue stays in **Verifying** until the next sync confirms Google
cleared the disapproval. Google can take time to re-review a product. Use **Sync
now** to check sooner, or wait for the next scheduled sync.

## Google Merchant Center products show as unlinked

**Unlinked products** are GMC issues Atlios could not match to a Shopify product,
usually because the product ID in Google does not map to a current Shopify
product. Resolve these from **Open in GMC**.


# User roles
Source: https://docs.atlios.io/reference/user-roles

What each Atlios role can do in a workspace.

Atlios has three workspace roles: `Owner`, `Admin`, and `Member`.

A role applies to the whole workspace: it sets *what* a person can do. Access
to a particular store is granted separately, per person, so it also decides
*where* they can do it. Owners see every store in the workspace. Admins and
members see only the stores they have been given access to.

Only an owner can invite people, remove them, change a role, or grant store
access. All of that lives in [Settings](/reference/settings).

## Role summary

| Role     | Best for                   | What they can do                                                                                         |
| -------- | -------------------------- | -------------------------------------------------------------------------------------------------------- |
| `Owner`  | Team lead or account owner | Full access to every store, including members, billing, and store connections                            |
| `Admin`  | Day-to-day operators       | Run workflows, review work, update settings, and push changes to Shopify                                 |
| `Member` | Reviewers and contributors | Review catalog work, start jobs, and update issues without changing store settings or pushing to Shopify |

## What each role can do

### Owner

Owners can do everything in Atlios, including:

* Invite and remove people.
* Change member roles.
* Grant or remove a person's access to a store.
* Connect or disconnect Shopify stores.
* Connect or disconnect Google Merchant Center.
* Manage billing.
* Everything an admin can do, in every store.

### Admin

Admins can handle day-to-day catalog operations, including:

* Review scan results.
* Create fix jobs and image jobs.
* Review, approve, cancel, and publish workflow items.
* Edit catalog standards, templates, scan rules, and store settings.
* Create or remove suppressions.
* Push product, image, and fix changes to Shopify.

Admins cannot manage workspace membership, billing, store access, or store
connections. An admin works only in the stores an owner has given them access
to.

### Member

Members can help with review and prep work, including:

* View products, issues, scans, and activity.
* Create fix jobs and image jobs.
* Update issue status.
* Delete image jobs they created.
* Work only in the stores an owner has given them access to.

Members cannot:

* Push catalog changes to Shopify.
* Publish images or apply fixes.
* Edit workspace settings, templates, catalog standards, or scan rules.
* Manage members, billing, store access, or store connections.

## Common questions

### Who should be an owner?

Give `Owner` to the small group responsible for account access, billing, and
team management.

### Who should be an admin?

Give `Admin` to people who run catalog operations and need to make live changes
in Shopify from Atlios.

### Who should be a member?

Give `Member` to people who need visibility and review access but should not be
able to change settings or publish updates to Shopify.


# Collection launch readiness
Source: https://docs.atlios.io/workflows/collection-launch-readiness

Use Atlios before publishing or promoting a product collection.

Use this workflow before launching a new collection, refreshing an existing
collection, or promoting a group of products.

The goal is to catch missing data, weak image coverage, and variant issues
before customers see the collection.

<Steps>
  <Step title="Confirm the product set">
    Identify the products that belong to the launch. Make sure the products
    are in the expected Shopify store and have the correct basic merchandising
    context.
  </Step>

  <Step title="Work from the latest scan">
    Review readiness against the latest scan results. Atlios re-checks each
    product automatically as you finish editing it in Shopify, so recent
    changes show up shortly after, in between the scheduled scans.
  </Step>

  <Step title="Review required product content">
    Look for missing descriptions, missing featured images, weak image
    coverage, and missing tags. These issues can make products harder to
    evaluate or harder to manage.
  </Step>

  <Step title="Review variant readiness">
    Check for missing SKUs, missing barcodes, zero prices, and invalid
    compare-at prices. Variant issues can affect operations, reporting, and
    checkout confidence.
  </Step>

  <Step title="Review live-page findings, if any">
    Live-page findings only exist for products where Atlios has already applied
    a meta title or meta description fix, so a brand new collection may have
    none. Where they exist, Atlios reports what would stop a shopper or a
    search engine from using the page: the page cannot be found, the page is
    blocked from indexing, the canonical tag points at another page, or your
    theme overrides a saved meta value. It also flags a page with no product
    structured data, which limits how your listing can appear in search. It
    also confirms a fixed meta title or meta description on the page. It does
    not check descriptions, featured images, alt text, or image count on the
    page.
  </Step>

  <Step title="Fix, suppress, or defer">
    For each issue, choose one outcome:

    * Fix it in Atlios or Shopify.
    * Suppress it if it is an intentional exception.
    * Defer it only if it does not block the launch.
  </Step>

  <Step title="Confirm before launch">
    After changes are complete, Atlios re-checks the affected products
    automatically. Use the refreshed issue list as the launch readiness
    checkpoint.
  </Step>
</Steps>


# Image review before publish
Source: https://docs.atlios.io/workflows/image-review-before-publish

Review product images before using them on customer-facing pages.

Use this workflow when product images have been uploaded, matched, generated,
processed, or prepared for publication.

The goal is to confirm that each image is attached to the right product,
supports customer evaluation, and is ready for the storefront.

<Steps>
  <Step title="Confirm image-product matching">
    Review whether each image is matched to the correct product.

    <Warning>
      Incorrect matching can create customer confusion even when the image
      quality is high.
    </Warning>
  </Step>

  <Step title="Check image coverage">
    Look for products with too few images or no featured image. Image coverage
    should support the way customers evaluate the product.
  </Step>

  <Step title="Review processed outputs">
    For processed images, check the result before publishing. Pay attention to
    background removal, crops, product edges, shadows, color accuracy, and
    whether the final image still represents the product honestly.
  </Step>

  <Step title="Approve, reject, or regenerate">
    Approve images that are ready, reject images that should not go to Shopify,
    and regenerate images that need another pass.
  </Step>

  <Step title="Choose the featured image">
    If several new images are going to the same product, choose the one that
    should become the featured image.
  </Step>

  <Step title="Review metadata">
    Check alt text and filenames where available. Strong image metadata
    supports storefront quality and makes image issues easier to manage later.
  </Step>

  <Step title="Publish approved changes">
    Publish only the image changes that pass review. If an output needs more
    work, leave it out of the publish step and return to the image workflow.
  </Step>

  <Step title="Let Atlios confirm">
    After publishing, Atlios re-checks the affected products automatically to
    confirm image-related issues have been resolved. Image fields are confirmed
    against Shopify, not against the rendered page: storefront verification
    covers the meta title and meta description only.
  </Step>
</Steps>

For the full review flow, see
[Review and publish images](/guides/review-and-publish-images).


# Weekly catalog review
Source: https://docs.atlios.io/workflows/weekly-catalog-review

A repeatable workflow for keeping catalog quality visible.

Use a weekly catalog review to keep catalog quality from becoming a last-minute
launch problem.

The goal is to review the latest scan, resolve high-priority issues, suppress
valid exceptions, and leave the issue list focused for the next review cycle.

<Steps>
  <Step title="Start from the latest scan">
    Atlios scans on a schedule, so the team reviews the most recent automatic
    scan rather than starting one by hand.

    <Note>
      If a scan is still running, wait for it to finish before making decisions
      from the issue list.
    </Note>
  </Step>

  <Step title="Review high-severity issues first">
    Open the issue list and start with the highest-severity issues. Prioritize
    anything that affects product readiness, variant data, whether your live
    product pages are reachable and showing the meta values you saved, or
    customer-facing product content.
  </Step>

  <Step title="Fix what Atlios supports">
    Use guided fixes where available. Review proposed changes before applying
    them, especially when the fix affects product copy, images, tags, or
    merchandising details.
  </Step>

  <Step title="Send manual work to Shopify">
    Some issues need manual updates in Shopify. Make those changes in the
    store, then return to Atlios for verification.
  </Step>

  <Step title="Suppress valid exceptions">
    If an issue is intentional for a product or store, suppress it. Good
    suppressions keep the next weekly review focused on new or unresolved
    work.
  </Step>

  <Step title="Let Atlios confirm">
    After the review work is complete, Atlios re-checks changed products
    automatically, and the next scheduled scan becomes the baseline for the
    following review.
  </Step>
</Steps>