If your customers are companies, you can install the B2B for Adobe Commerce module to extend your Adobe Commerce on cloud infrastructure Pro project to accommodate a business-to-business model. Although this topic provides information specific to installing and configuring the B2B module for Adobe Commerce on cloud infrastructure, you can find additional B2B information in the following guides:
Because B2B is a module for Adobe Commerce on cloud infrastructure, Adobe recommends that you deploy your Adobe Commerce application to an Integration or Staging environment before beginning.
Adobe recommends working in a development branch when adding the B2B module to your project. If you do not have a branch, see Create a branch for development. When installing the B2B module, the
Magento_B2b module name is automatically inserted in the
app/etc/config.php file. There is no need to edit the file directly.
To install the B2B module:
On your local workstation, change to your project directory.
Create or check out a development branch.
Add the B2B module to the
require section of the
composer require magento/extension-b2b --no-update
Update the project dependencies.
Add, commit, and push code changes.
git add -A
git commit -m "Install the B2B module."
git push origin <branch-name>
After the build and deploy finishes, use SSH to log in to the remote environment and verify that the B2B module installed.
bin/magento module:status Magento_B2b
An extension name uses the format:
Magento_B2b : Module is enabled
If you encounter deployment errors, see Recover from component failure.
When you install the B2B module using Composer, the deployment process automatically enables the module. If you already have the B2B module installed, you can enable or disable the module using the CLI
Enable the B2B module:
bin/magento module:enable Magento_B2b
The following modules have been enabled: - Magento_B2b Cache cleared successfully. Generated classes cleared successfully. Please run the 'setup:di:compile' command to generate classes. Info: Some modules might require static view files to be cleared. To do this, run 'module:enable' with the --clear-static-content option to clear them.
See Manage extensions.