A missing WooCommerce Reports menu can be an intentional change on a new 11.3 store, not a lost database or broken sales import. First distinguish the legacy Reports screen from Analytics. Then test whether an authorized user can open the existing report directly.
As of October 28, 2026, 11.3 is in beta. Use a fresh staging installation and an upgraded staging copy for comparison. Do not rewrite a live store's installation-history option merely to make a menu appear.
Check which screen the user expects
Ask for the report name and the old navigation path. An extension's legacy tab is different from an Analytics dashboard or an external finance report. A screenshot of an older tutorial may show navigation that a new store no longer uses.
The legacy-menu implementation preserves the report page and its access capability while changing visibility on new installations. Existing-store history and extensions adding actual legacy reports affect the outcome. Missing navigation alone is not evidence that orders were deleted.
Record the installed version and the store's initial-install value with a read-only command:
wp option get woocommerce_initial_installed_version
If the option is absent, record that result rather than creating a guessed value. A staging site copied from production is not a fresh-install fixture just because its domain is new.
Test access without broadening permissions
Using the same authorized account, open the site's own wp-admin/admin.php?page=wc-reports route. Do not send this test to an unfamiliar domain. If the report loads, the first problem is discoverability. If access is denied, investigate the user's intended capability separately.
Avoid granting administrator access as a diagnostic shortcut. A reports-only user, shop manager and administrator can have different menus. Compare an approved account with the affected account and retain the response or error each receives.
Menu discovery, permission checks and report data are separate layers of the diagnosis.
Build the fresh-versus-upgraded matrix
| Fixture |
Extension state |
What to record |
| Fresh beta store |
No report extension |
Menu visibility and direct route |
| Upgraded store copy |
Same configuration |
Whether existing navigation remains |
| Fresh beta store |
Real legacy report extension |
Tab registration and discoverability |
| Fresh beta store |
Analytics-only integration |
Avoid assuming every report hook restores the menu |
A link to an extension tab should be tested after its plugin is active. A page that opens but has no expected tab points toward registration, not the visibility setting alone. Check the extension's supported WooCommerce versions before editing custom code.
For extension developers
Register report callbacks early and consistently, rather than only when the report screen is already active. This avoids a circular dependency where the menu decision cannot see the report until someone has opened it.
The documented override filter is woocommerce_show_legacy_reports_menu. Treat a forced-visible override as a deliberate compatibility choice, not proof the underlying report integration is correct. Keep the page capability intact and test with the actual intended user role.
The current release advisory and implementation description differ on the precise late-hook timing. Avoid building an integration around that timing detail. Verify the installed beta code and register before menu construction; record the exact build in any bug report.
Know when not to touch the data
If authorized direct access works and totals are correct, do not rerun imports, rebuild order tables or clear scheduled work. Those operations cannot repair a navigation label. If totals are wrong after opening the report, switch to sales and refunds reconciliation.
Update staff documentation and saved links only after confirming the intended destination. For a custom extension whose reports load directly but remain undiscoverable, request a focused admin integration fix with the fixture matrix and affected role.
Sources checked October 28, 2026. Synthetic fixtures and diagrams illustrate the proposed checks; they are not claims of customer testing.