How is this different from Adobe’s built-in audit tools?

Adobe ships several built-in audit tools that overlap with this checklist but don’t replace it. Quick comparison:

• Adobe Commerce Site-Wide Analysis Tool (SWAT) — ships in Adobe Commerce 2.4.6+, runs static analysis on your codebase. Catches code-quality issues, security smells, deprecation warnings. Strong on code, blind to ops + B2B + SEO config. Run it monthly — complements this checklist, doesn’t replace.
• Magento Marketplace Module Health — per-extension static analysis. Useful for vendor extensions, useless for custom in-house modules. One narrow slice.
• Adobe Experience Manager Best Practices Analyzer — primarily for AEM, partial overlap with Magento. Not really applicable.
• This checklist — covers the 50 cross-cutting checks an operator would run before signing off a Magento store as production-healthy. SWAT can’t answer “do you have 2FA enforced” or “is your daily backup test-restored quarterly” — those are operational state, not code state.

How they fit together:

1. Run this checklist quarterly. Get the cross-functional state-of-the-store snapshot.
2. Run SWAT monthly. Catch code-quality regressions between checklist runs.
3. Schedule a paid deep audit annually. Catches the things both miss (slow-query patterns, custom-module security depth, ERP drift, B2B data integrity).

Three layers, three time horizons, three different blind spots. None of them replaces another.