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