Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.atlios.io/llms.txt

Use this file to discover all available pages before exploring further.

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

Run a fresh scan

Start with a new scan so the team is reviewing current catalog data.
If a scan is already running, wait for it to finish before making decisions from the issue list.
2

Review high-severity issues first

Open the issue list and start with the highest-severity issues. Prioritize anything that affects product readiness, variant data, storefront confidence, or customer-facing product content.
3

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

Send manual work to Shopify

Some issues need manual updates in Shopify. Make those changes in the store, then return to Atlios for verification.
5

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

Re-scan and confirm

Run another scan after the review work is complete. Use the new results as the baseline for the next review.