README

Magento 2 Scope Override Inspector

KodeXpo_ScopeOverrideInspector makes Magento scope overrides visible in admin.

Built by KodeXpo.

Need custom Magento development, admin tooling, or help debugging complex Adobe Commerce backend behavior? Contact: dev@kodexpo.com

It shows when lower-scope values on store views or websites still take precedence over parent scope values, directly on:

product edit pages
category edit pages
Stores > Configuration section pages

It is designed for teams that work on All Store Views for products and categories, on Default Config in Stores > Configuration, and across multiple scopes, and need clear warnings when saved website or store view values still override what they see or save.

Why This Module Exists

Magento supports Default Config, website, and store view scope, but admin users often miss when lower-scope values still override the parent scope.

This module helps by:

showing override notices on product, category, and config pages
listing which scope is overriding
showing which values differ from the parent scope
linking directly to the overriding scope
adding store view helper actions to reset visible fields back to default

This is not just a Use Default Value fix. It is an admin visibility tool for scope inheritance and override debugging.

Built By KodeXpo

This module is part of KodeXpo's Magento and Adobe Commerce engineering work.

If your team needs:

custom Magento modules
admin workflow improvements
Adobe Commerce backend troubleshooting
complex scope / configuration debugging

contact dev@kodexpo.com

Features

Product override notices on All Store Views
Category override notices on All Store Views
Config section override notices on Default Config, website, and store view scope
Store View Overrides sidebar with grouped details on supported admin edit pages
Configurable notice layout mode: Sidebar (default) or Inline
Direct links to overriding scopes
Human-readable labels instead of raw config paths where possible
Store view helper actions:
- Check All Use Default
- Check All Use Default And Save
Post-save notices when lower-scope values still take precedence
Included translations:
- cs_CZ
- de_DE
- en_US
- es_ES
- fr_FR
- hu_HU
- it_IT
- nl_NL
- pl_PL
- pt_PT
- ro_RO

Scope Coverage

Products

On All Store Views, the module can show:

how many store views contain saved values
how many attributes are saved
how many attributes actually differ from All Store Views
which store view is overriding
which attributes differ

Example:

Store view overrides exist for this product in 1 store view (8 attributes total, 1 differs from default values).
Store View "Default Store View"
Status: Default Values = "Disabled", Store View = "Enabled". The store view override currently takes priority.

Store Configuration

The module checks configuration overrides inside the currently edited configuration section.

It does not rely only on core_config_data.

For configuration, the module combines:

saved rows from core_config_data
effective lower-scope values resolved through Magento config fallback
values coming from etc/config.xml on default, websites, or stores scope when they change the effective value

Behavior by scope:

on Default Config: shows lower-scope overrides from websites and stores
on website scope: shows values saved on that website and on child store views under that website
on store view scope: shows values saved directly on that store view

Screenshots

Configuration Notices

Default Config configuration notice:

Website scope configuration notice:

Store view configuration notice:

Category Notices

Category override notice:

Category store view helper actions:

Product Notices

Product override notice:

Product store view helper actions:

Display Modes

Inline notice layout on product edit page:

Notice layout setting in module configuration:

Store View Helper Actions

On product and category store view pages, the module can show two helper actions:

Check All Use Default
Check All Use Default And Save

Check All Use Default

checks all available Use Default Value checkboxes on the current page context
does not save automatically

Check All Use Default And Save

checks all available Use Default Value checkboxes on the current page context
asks for confirmation
triggers the normal save action

Installation

Composer

composer require kodexpo/module-scope-override-inspector
bin/magento module:enable KodeXpo_ScopeOverrideInspector
bin/magento setup:upgrade
bin/magento cache:clean

If needed:

bin/magento setup:di:compile
bin/magento setup:static-content:deploy en_US ro_RO -f

Manual

Copy the module to:

app/code/KodeXpo/ScopeOverrideInspector

Then run:

bin/magento module:enable KodeXpo_ScopeOverrideInspector
bin/magento setup:upgrade
bin/magento cache:clean

Configuration

The module can be enabled or disabled from:

Stores > Configuration > KodeXpo > Scope Override Inspector > General > Enable Scope Override Inspector

When disabled:

no notice blocks are rendered
no post-save notice markers are recorded
the module remains installed but passive

Notice layout mode:

Sidebar (default): renders scope overrides in a right sidebar panel
Inline: renders scope overrides as the original inline admin notice block

Compatibility

Designed for Magento Open Source / Adobe Commerce 2.4.5 to 2.4.9 style admin APIs.

Package requirements currently allow:

PHP 8.1
PHP 8.2
PHP 8.3
PHP 8.4

Limitations

Product and category reset actions affect available admin fields with a Use Default Value checkbox in the current page context.
Hidden or technical store view rows can still exist in the database even when all available fields already use default.
Configuration notices currently report lower-scope values but do not provide a bulk reset action similar to product/category pages.

Compared To Other Scope Fixes

Most Magento scope-related fixes focus on a single issue, usually Use Default Value behavior on product forms.

ScopeOverrideInspector is broader:

it covers products, categories, and system configuration
it highlights real lower-scope precedence issues
it helps admins navigate and reset overrides instead of only fixing one UI bug

Development

Run unit tests:

vendor/bin/phpunit -c Test/Unit/phpunit.xml.dist

Support

For custom Magento development, consulting, or implementation help related to this module, contact:

dev@kodexpo.com

License

This module is licensed under the Apache License, Version 2.0. See LICENSE.txt for details.

kodexpo / module-scope-override-inspector

Maintainers

Package info

Statistics

Security