Uninstall
Stop your Magento store's sync, delete the data in Fullmetrix and remove the module from the server without breaking anything.
Removing Fullmetrix from a Magento store happens in three places, Fullmetrix, the Magento admin and the server. First choose what you want to achieve, then follow the matching part.
Choose the right action
| Your goal | The action | What happens |
|---|---|---|
| Erase the store and its data from Fullmetrix | Disconnect in Fullmetrix | The connection and the imported orders are deleted from your organization |
| Cut the link on the store side | Disconnect in Magento | The module forgets the connection and sends nothing more. It stays installed. |
| Stop the module without removing it | Disable the module | The module's code no longer runs. The package stays on the server. |
| Remove the module from the server | Uninstall the Composer package | The module leaves the Magento project |
To remove everything, do all four, in the order of this page.
Delete the store in Fullmetrix
Export what you want to keep
The imported data will be erased. First export the numbers or lists you need, from the reports or the Exports page.
Disconnect the store
In the sidebar, click Settings, then the Integrations tab. On the Magento card, click Disconnect. The Disconnect this store? window warns that the connection and all imported order data will be deleted, with no way back. Click Disconnect to confirm.
Wait for the deletion to finish
The card shows Deleting, then disappears.
Disconnect the module in Magento
In the Magento admin, open Marketing, then Fullmetrix, and click Disconnect. Magento does not ask for confirmation. The message Boutique déconnectée de Fullmetrix. (store disconnected from Fullmetrix) appears and the page goes back to the connection form.
Your developer can do the same on the command line.
bin/magento fullmetrix:disconnectThe module then erases the code, the connection key, the chosen store view and the changes waiting to be sent. It stays installed and enabled, but sends nothing more.
A disconnected code cannot be reused
After disconnecting in Magento, the old code is rejected with the message Ce code est déjà associé à un autre site (this code is already associated with another site). To reconnect the store, delete it in Fullmetrix and add it again to get a fresh code. Your data is then imported again from the store.
Disable the module (for your developer)
Disabling the module stops all its code without removing it from the server. It is useful for a test or a temporary pause. Your developer follows the usual deployment process and runs these commands.
bin/magento module:disable Fullmetrix_Connector
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:flushsetup:di:compile is only needed if the store runs in production mode. To enable the module again later, they replace module:disable with module:enable and run the same commands. The connection is kept as long as there was no disconnect. While the module is disabled, Fullmetrix can no longer read the store and its card in Integrations shows sync errors. This is expected. After enabling it again, click Sync on that card.
Remove the module from the server (for your developer)
First disconnect the store in Magento, as described above. Then, from the Magento project folder, your developer runs these commands.
bin/magento module:disable Fullmetrix_Connector
composer remove fullmetrix/magento-connector
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:flushThey then deploy composer.json, composer.lock and the generated files with the store's usual process. If the module was installed from the zip file, they delete the app/code/Fullmetrix/Connector folder instead of running composer remove.
The module's queue table, fullmetrix_webhook_queue, and a few settings saved by Magento may remain in the database. They are inactive. Only delete them by hand after a backup, and only if you are sure you will not reinstall the module.
Reconnect the store later
Follow Installation again with a fresh code from Fullmetrix. The history import starts over from the beginning.