Installing a Magento extension with Composer: keep the rollback in reach

composer require succeeds. That tells you the package could be resolved and downloaded. It does not tell you that its database changes ran, its storefront assets exist or its feature works with your checkout.

Install a Magento extension as a deployment: test on staging, record the dependency change and keep a restore path. The commands below are an illustrative sequence for a conventional production-mode installation, not a substitute for the vendor's instructions or your deployment tooling.

Check the fit before downloading

Confirm Magento edition and version, PHP requirements, dependencies, licence access and theme and checkout support. Back up the database and relevant files and establish how they can be restored together. Installation can introduce schema and data changes; restoring code alone may be insufficient.

Use a staging environment with representative catalogue and customer-group data. Prevent it from sending real customer messages or making unintended external transactions.

Authenticate without putting keys in the repository

Follow the vendor's repository instructions. Composer's private package authentication guide describes supported authentication methods. Keep auth.json out of version control and use your CI secret mechanism for automated deployments.

For CommerceGears packages, the current repository and key instructions are on Composer access. Package names and module names are different identifiers; copy each from the product documentation.

Resolve and test on staging

Replace the placeholders below with the vendor's real package and module names. Resolve dependencies in the development or staging workflow and commit the resulting composer.json and composer.lock. Production should install that tested lock file rather than independently selecting new versions.

composer require vendor/package-name
bin/magento module:status Vendor_Module
bin/magento module:enable Vendor_Module

Check module status before enabling it; if already enabled, the enable command is unnecessary. Review dependency changes, not just the new package. A broad, unrelated package update adds risk to a feature installation.

Complete the Magento deployment

Adobe's extension installation guidance documents the Magento setup steps. A conventional production-mode workflow includes:

bin/magento maintenance:enable
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f en_GB
bin/magento cache:clean
bin/magento maintenance:disable

Run as the filesystem owner with the correct PHP binary. Replace en_GB with the locales and theme scope your store needs. Cloud and established CI deployment workflows may handle these steps differently; follow their process. Hyvä modules may also require a Tailwind CSS rebuild.

If a step fails, investigate before reopening the store. Do not continue down a copied command list and disable maintenance merely because it is the final line.

Test the feature and its neighbours

Check configuration scope, permissions, cron or queue dependencies and the actual customer workflow. If you installed product attachments, open a public file and test a restricted one as a guest. If you installed social login, test an existing account, a new account and cancellation at the provider.

Then test a purchase. A catalogue feature can still affect product rendering, basket behaviour or performance.

Plan removal separately

composer remove removes package code; it is not proof that module data or installation side effects have been removed. Use the vendor's supported uninstall procedure and a tested backup. Decide what data must be retained before removing anything.

When staging passes, deploy the same committed dependencies through your normal production process and repeat the trading checks. Choose a module with installation and support requirements you can maintain, and send us your environment details if a prerequisite is unclear.