Six sections. Every critical checkpoint.
Each section mirrors a domain from our forensic platform audit. The checklist distills each domain into the specific things you can verify without outside help.
Patch & Security Exposure
Whether your Magento version is current, which security patches are missing, and where known CVE vulnerabilities may be open.
Compromise Indicators
File-integrity checks, suspicious admin accounts, injected JavaScript, and telltale signs of prior or active breach.
Performance & Database
TTFB baselines, cache-layer verification, indexer configuration, slow-query patterns, and table bloat indicators.
Revenue-Path Integrity
Checkout-flow reliability, quote mutation risks, payment gateway health, and cart-to-order conversion blockers.
Upgrade & Change Risk
Dependency audit, extension compatibility, customization surface area, and the specific risks of your next version jump.
Cost & Vendor Verification
Hosting spend vs. actual resource usage, redundant service subscriptions, and contract terms that create lock-in.
Here is one checkpoint in full.
We're not asking you to trust a table of contents. Here's checkpoint #11 exactly as it appears in the checklist.
Indexer mode configuration
Check: Run bin/magento indexer:status. Every indexer should show "Update by Schedule," not "Update on Save."
Why it matters: "Update on Save" triggers reindexing on every catalog change: product save, price update, category assignment. On stores with more than a few hundred SKUs, this creates cascading lock contention during admin activity and can stall checkout when quote-dependent indexes are rebuilt mid-order.
What to do: Switch all indexers to "Update by Schedule" and verify the Magento cron is running the indexer_update_all_views job at an appropriate interval. Monitor for backlog growth using mview_state. A growing backlog means the cron interval is too wide for your catalog's change rate.
Enter your email and we'll send it over.
No call. No sequence you can't leave.
What this checklist will and won't do.
It will
- Give your team a structured way to evaluate platform health
- Surface the specific risks most teams don't check until something breaks
- Provide clear instructions for each checkpoint
- Work on any Magento 2 / Adobe Commerce installation
- Help you ask better questions of your current agency or hosting provider
It won't
- Replace a forensic audit. It covers what is verifiable without deep code analysis.
- Fix anything automatically. It identifies problems, not solutions.
- Cover every possible failure mode. A comprehensive audit examines hundreds of data points.
- Tell you what to prioritize. That depends on your traffic, revenue, and risk tolerance.
If your team is dealing with active platform issues, start with an audit.
The checklist can guide planning, but forensic analysis is the fastest path to root-cause clarity when revenue or stability is already being affected.
Request Platform Audit