Modules and the control centre Free

StoreMaster is one plugin made of independently switchable modules. That is not a packaging detail — it is the reason a toolkit this size can be fast.

A disabled module registers nothing

When a module is off, StoreMaster never creates it. It registers no hooks, enqueues no scripts, schedules no background jobs and runs no queries. On a storefront request with nothing enabled, StoreMaster reads one database option and stops.

This is checked rather than claimed: the test suite disables every module, boots the plugin, and then reads WordPress’s own hook registry to prove no StoreMaster callback is attached to any storefront hook. A health check does the same thing on your live site and reports it under Diagnostics.

What the control centre shows you

Each module card carries:

• State — Enabled, Disabled, Needs attention, or Not in this build.
• Outcome — what a merchant gets, in one sentence.
• Storefront footprint — what it adds to a page request.
• Dependencies — what must be on first, and what would break if you turned it off.

Before a change is applied you see a preview listing every affected behaviour. Nothing changes until you confirm.

Dependencies and conflicts

Some modules build on others. Advanced discounts extends the discounts module rather than replacing it, so the control centre will not let you enable it on its own — and if you disable discounts later, it tells you what stops working first.

Safe mode

If you ever need to know whether StoreMaster is involved in a storefront problem, turn on safe mode. Every StoreMaster module stops running on the storefront while your settings stay exactly as they were. Turn it off and everything comes back.

Safe mode is per-administrator by default. Making it site-wide is a separate, deliberate choice, and it is announced in the admin so nobody forgets it is on.