Recommendations
Your open issues ranked by estimated revenue impact, and exactly how the ranking is worked out.
On this page
Open Commerce Health → Recommendations for a short “fix this first” list. It doesn’t add new findings. It re-orders the issues you already have.
How the ranking works
Each issue gets an impact score: its severity score multiplied by how directly that kind of problem threatens revenue. The values are fixed in this version.
| Severity | Score |
|---|---|
| Critical | 100 |
| High | 75 |
| Medium | 50 |
| Low | 25 |
| Info | 10 |
| Kind of issue | Multiplier | Effort estimate |
|---|---|---|
| Payment Gateway, Stuck Payments, Cart and Checkout Page | 1.3 | Medium |
| Shipping (any issue about shipping) | 1.2 | Low |
| JavaScript Error | 1.1 | Medium |
| Everything else, including Core Web Vitals and the free plugin’s scan findings | 1.0 | Medium |
| Plugin Conflict | 0.9 | Low |
A score of 75 or more is High impact, and 40 or more is Medium impact. Anything lower is not listed here, so this screen stays focused. Low-severity issues stay on the Issues screen.
Examples. A Critical gateway issue scores 100 × 1.3 = 130 (High). A Medium JavaScript error scores 50 × 1.1 = 55 (Medium). A Low gateway issue scores 25 × 1.3 = 33, below 40, so it isn’t listed.
What you see
- Issues grouped as High or Medium impact, highest score first.
- An effort estimate for each. It is a fixed default per type of issue, not a calculation for that specific issue.
- A View in Issues link that opens the exact issue.
- Filter chips to show only High or only Medium impact.
Still need help?
Search the docs first — or open a ticket and our team will pick it up from the Support screen.