Is disabling unused modules and plugins enough?
What remains after switching off a PrestaShop or Shopware extension, and how to retire it without putting order data or integrations at risk.
AI-generated image- 1Quick answer
- 2Key takeaways
- 3What is the difference between disabling, uninstalling and removing?
- 4Can a disabled PrestaShop module still pose a risk?
- 5What should I consider with Shopware plugins and apps?
- 6How do I proceed without damaging orders or integrations?
- 7What happens to old ERP credentials and scheduled jobs?
- 8What if the vendor no longer provides updates?
- 9How does sjmedia help make the decision?
- 10Sources & further reading
- 11Cite this article
- 12Authors & technical review
Quick answer
Disabling an extension does not prove it is fully removed or secure. In PrestaShop and Shopware, remaining files, data and dependencies need separate review. Unused extensions should be removed through a controlled process after checks and backups; temporarily disabling them can be useful for troubleshooting.
An old shipping module, an abandoned payment-provider trial or a previous export tool: over time, a store collects extensions whose original purpose is no longer obvious. They appear as inactive in the administration. That status does not settle the question of their security.
At sjmedia, we separate two decisions: is the function still needed, and which components can actually be removed? This guide covers that distinction for PrestaShop and self-hosted Shopware 6. For a broader inventory, see our guide to reviewing store security.
Key takeaways
- It can be useful when diagnosing a fault.
- An inactive label is not evidence of security.
- In self-hosted Shopware 6, deactivation and uninstallation are separate operations too.
- Consider this hypothetical example: a merchant replaces an earlier export integration with an Odoo connector.
What is the difference between disabling, uninstalling and removing?
Disabling stops an extension's intended use. It can be useful when diagnosing a fault. It does not demonstrate that all files, stored data or external connections have disappeared.
Uninstalling runs the extension's designated uninstall process. Removing also addresses the software files left behind. The data retained depends on the system, version, extension and selected options. Technical support should therefore establish what the specific operation will change before proceeding.
Can a disabled PrestaShop module still pose a risk?
An inactive label is not evidence of security. PrestaShop's Module Manager distinguishes disabling, uninstalling and deleting. Disabling preserves configuration for later use; it does not automatically remove the module files.
Our assessment therefore considers the code actually present and the functions that remain reachable. If an extension contains its own directly accessible scripts, their access controls need separate evaluation. Not every disabled module is vulnerable. Equally, an inactive status does not establish that no attack surface remains. The implementation and any relevant vendor security advisory are what matter.
Being able to examine the module inventory directly is a practical benefit of a maintained PrestaShop store. It allows useful functions to remain while obsolete components are deliberately retired. That benefit comes from responsible maintenance, not from the platform choice alone.
- Define requirements
- Compare platforms
- Test workflows
- Plan the next step
What should I consider with Shopware plugins and apps?
In self-hosted Shopware 6, deactivation and uninstallation are separate operations too. Depending on the extension, uninstalling may require a decision about retaining its data. The Shopware extension-management documentation describes these steps. An option to delete all extension data should not be accepted casually.
References from existing orders deserve particular attention. Shopware specifically warns developers against simply removing a previously used payment method when orders reference it. Its plugin lifecycle documentation explains the technical reasoning.
We also distinguish locally installed plugins from apps connected to external services. Removing an entry from the store does not establish what still runs at the provider. For an old ERP integration, we therefore review the external access and the agreed handling of data as well. The exact steps depend on the integration; generic deletion commands are not a suitable substitute.
How do I proceed without damaging orders or integrations?
- Establish the purpose: Record the technical name, vendor, version and previous use. An unremarkable export extension may still support an essential business process.
- Check dependencies: Identify payment methods, shipping rules, templates, order data and ERP processes that rely on the extension. Ask the vendor or technical support when a dependency is unclear.
- Preserve required data: Back up configuration and relevant data in a traceable way. Provide a recovery option and establish which data the uninstall process would change.
- Test in isolation: Trial the removal in a restricted test copy. Outgoing emails, real payments and production ERP calls must be blocked or replaced with test connections.
- Verify affected workflows: Check historical orders, exports and relevant background processes as well as the cart and checkout. Only then apply the agreed procedure to the production store.
- Review the result: Have technical support assess remaining files, scheduled jobs and external permissions. Document what was removed, deliberately retained or remains under maintenance.
What happens to old ERP credentials and scheduled jobs?
Consider this hypothetical example: a merchant replaces an earlier export integration with an Odoo connector. The old extension is disabled, but its credentials remain valid at the connected service. The transition is not yet complete from an access-management perspective. This is an illustration, not a documented customer case study.
We would establish which process uses each credential, whether other applications depend on it and how unnecessary access can be withdrawn in a controlled way. Existing keys should not be revoked on a guess. The same applies to scheduled import and export jobs. Retiring old credentials belongs in a documented handover, rather than an uncontrolled FTP clean-up.
What if the vendor no longer provides updates?
First, we establish whether the function is needed and whether a specific security advisory applies. If the function remains necessary, a maintained replacement or targeted development may be appropriate. A component no longer needed should be retired from the running system after its dependencies have been reviewed. Unclear support status is not proof of an attack, but it is an unresolved maintenance issue.
For a confirmed vulnerability, urgency depends on whether the installation is affected and how the flaw can be exploited. A vendor-documented immediate mitigation may be necessary temporarily; the next routine maintenance date is not automatically sufficient. If there are signs of an existing compromise, incident investigation is needed instead of ordinary uninstallation.
How does sjmedia help make the decision?
We start with the extension inventory and the business processes actually in use. Each extension should receive a reasoned decision: retain and maintain, replace or remove through a controlled process. For PrestaShop, this can be coordinated with our module and store support. For Shopware, we agree the review and implementation scope around the plugins and apps installed.
Our maintenance and security page explains the ongoing services. A key distinction between the PrestaShop Security and Protect packages is that Protect includes ongoing system and module maintenance. Extensive removal of legacy components or replacement development is not automatically commissioned by selecting a package. Scope, dependencies and effort must be established first.
If a version upgrade follows, refer to our separate guides for PrestaShop updates and Shopware 6 updates. This article focuses on reducing the extension inventory in a traceable way while preserving necessary store functions and data.
Sources & further reading
Cite this article
Jochen Schmid (sjmedia GmbH, Kuppenheim): Is disabling unused modules and plugins enough?. 22 Nov 2026. https://www.sjmedia-consulting.de/en/wissen/shopsysteme/ungenutzte-module-plugins-deaktivieren
Author & technical review
Related to this topic.
Questions about this topic? Let’s talk about it.
I’ll listen to your situation and discuss which next steps suit your store.



