<!– lead –>
Multi-store Magento 2 setups create a recurring operational friction point: confirming exactly which website, store group, or store view a request belongs to. Without a single authoritative surface, operators cross-reference the scope selector, Stores → All Stores, and Stores → Configuration to piece together context that should be obvious. The Store Overview module removes that friction entirely.
<!– wp:paragraph {"className":"brocode-impact-callout"} –>
The takeaway: one read-only admin widget that surfaces active website, store group, default store view, base URLs, currency, and root category — so operators always know which store they are looking at without switching scopes or opening multiple tabs.
<!– /wp:paragraph –>
The problem on multi-store setups
On installations with multiple websites, store groups, and store views, three failure modes repeat themselves:
- **Wrong-scope support tickets.** A ticket arrives referencing a symptom visible only on store view B, but the operator investigating it is scoped to store view A. Two hours later the mismatch surfaces.
- **Configuration changes applied to the wrong scope.** Stores → Configuration shows "Use Default" checkboxes that look identical across scopes. Without a clear ambient indicator of the active scope, a setting lands on the wrong website.
- **Onboarding friction.** New team members — ops, support, QA — routinely need a guided tour of which URL maps to which website, which store group owns which root category, and which locale corresponds to which store view. There is no built-in admin surface for this.
These failures are not caused by bad processes. They are caused by absent context. The admin panel optimises for editing, not for orientation.
What the module gives you
A lightweight, read-only dashboard widget that displays:
| Field | Value shown |
|—|—|
| Website | Code, name, and internal ID |
| Store group | Name and default store view |
| Default store view | Name, code, and locale |
| Base URL | Storefront and secure URLs for the active scope |
| Currency | Configured base currency and default display currency |
| Root category | Name and ID of the catalog root for this website |
No forms, no toggles, no editing surface — just the orientation data that prevents the failure modes above.
Admin menu placement
Following the [brocode admin menu discipline](/blog/magento-2-admin-menu-placement/), this module registers its admin entry under **System → Tools**, not under a vendor-named top-level node. Operators already look in System for store infrastructure tooling. The Store Overview meets them there.
<!– who_for –>
Who this is for
- **Operations and support teams** on multi-store setups who deal with scope confusion daily.
- **Developers onboarding** to a complex installation who need a reliable orientation surface before touching configuration.
- **QA engineers** verifying that the correct store view is active during test runs.
- Anyone who has ever applied a config change to the wrong website and only noticed it in production.
<!– who_skip –>
Who should skip this
- Single-store installations. On a default Magento 2 install with one website, one store group, and one store view, the scope selector already makes context unambiguous. The module adds no value there.
- Teams that have already solved orientation through a custom admin widget or a pinned Stores → All Stores bookmark.
Installation
composer require brocode/module-store-overview
bin/magento module:enable Brocode_StoreOverview
bin/magento setup:upgrade
bin/magento cache:flushNo database schema changes. No configuration required after installation. The widget appears immediately under the System menu.
Compatibility
| Magento version | PHP | Status |
|—|—|—|
| 2.4.6 | 8.1 / 8.2 / 8.3 | Stable |
| 2.4.5 | 8.1 / 8.2 | Stable |
| 2.4.4 | 8.1 | Stable |
<!– cta_bar –>
<div class="brocode-cta-bar"><a class="wp-block-button__link wp-element-button" href="https://github.com/brosenberger/module-store-overview">View on GitHub</a><a class="wp-block-button__link wp-element-button is-secondary" href="https://github.com/brosenberger/module-store-overview/archive/refs/heads/main.zip">Download ZIP</a></div>
FAQ
**Does this module affect store performance?**
No. The widget is rendered only on explicit admin requests to the System page. It performs a single read of the store configuration tree — no external calls, no scheduled tasks, no frontend impact.
**Can I control which scope the widget reflects?**
The widget reflects the scope currently selected in the admin scope switcher. If you switch from "All Store Views" to a specific website, the widget updates to show that website’s data.
**Does it work with custom website or store group names?**
Yes. The widget reads from the store configuration model directly, so any customisations to website name, store group name, or store view locale are reflected automatically.
**Is there a multi-site version?**
Not currently. The widget scopes to the currently logged-in admin’s active scope selection. A cross-instance overview would require a separate aggregation layer outside Magento.
Related
- [AMQP Monitor module](https://github.com/brosenberger/module-amqp-monitor) — another operator-first System → Tools entry that follows the same admin placement discipline.
- [Honor your inner monk: simpler adminhtml UIs](/blog/magento-2-admin-menu-placement/) — the rationale behind how this module registers its admin entries.