Manual installation
On Commerce on Cloud or on-premises with Adobe Commerce Optimizer, install the B2C Storefront Compatibility Package with Composer on your Commerce server. If you use B2B drop-ins, also install the Storefront Compatibility B2B Package (SCP-B2B) on the same instance after the B2C package. Not sure this is your path? See Find your path.
Choose your B2C package
Section titled “Choose your B2C package”The package version must match your Adobe Commerce release. Use the version from this table in composer require adobe-commerce/storefront-compatibility:VERSION.
| Adobe Commerce | Package version | Reference |
|---|---|---|
| 2.4.9 (recommended) | 4.9.3 | GraphQL and REST changes |
| 2.4.8 | 4.8.28 | GraphQL and REST changes |
| 2.4.7 | 4.7.15 | GraphQL and REST changes |
Install the B2C package
Section titled “Install the B2C package”-
Change to your Commerce project directory.
-
Check out the environment branch you want to update.
Terminal window magento-cloud environment:checkout <environment-id> -
Add the package using the version from Choose your B2C package.
Terminal window composer require adobe-commerce/storefront-compatibility:4.9.3Use
4.8.28for Adobe Commerce 2.4.8.Use
4.7.15for Adobe Commerce 2.4.7. -
Update package dependencies.
Terminal window composer update adobe-commerce/storefront-compatibility -
Commit and push so the cloud environment picks up
composer.jsonandcomposer.lock.Terminal window git add composer.json composer.lockgit commit -m "Add module"git push origin <branch-name>To confirm the deployment succeeded, check the Deploy log in the Cloud console when the push finishes.
-
Add the package using the version from Choose your B2C package.
Terminal window composer require adobe-commerce/storefront-compatibility:4.9.3Use
4.8.28for Adobe Commerce 2.4.8.Use
4.7.15for Adobe Commerce 2.4.7. -
Apply the module and clear the cache.
Terminal window bin/magento setup:upgrade && bin/magento cache:clean
Choose your B2B package
Section titled “Choose your B2B package”B2B drop-ins need SCP-B2B in addition to the B2C package. Adobe Commerce B2B must already be configured on your Commerce instance. SCP-B2B supports Adobe Commerce 2.4.8 and 2.4.9 only, not Adobe Commerce 2.4.7.
Use the version from this table in composer require adobe-commerce/storefront-compatibility-b2b:VERSION. For GraphQL changes in the package, see B2B Compatibility Package.
| Adobe Commerce | Package version |
|---|---|
| 2.4.9 (recommended) | 1.0.25 |
| 2.4.8 | 1.0.25 |
Install the B2B package
Section titled “Install the B2B package”Install SCP-B2B only after the B2C Storefront Compatibility Package is on the instance.
-
Change to your Commerce project directory.
-
Check out the environment branch you want to update, if you have not already done so for the B2C package.
-
Add SCP-B2B using the version from Choose your B2B package.
Terminal window composer require adobe-commerce/storefront-compatibility-b2b:1.0.25 -
Update package dependencies.
Terminal window composer update adobe-commerce/storefront-compatibility-b2b -
Commit and push so the cloud environment picks up
composer.jsonandcomposer.lock.Terminal window git add composer.json composer.lockgit commit -m "Add B2B compatibility package"git push origin <branch-name>
-
Add SCP-B2B using the version from Choose your B2B package.
Terminal window composer require adobe-commerce/storefront-compatibility-b2b:1.0.25 -
Apply the module and clear the cache.
Terminal window bin/magento setup:upgrade && bin/magento cache:clean
Update the packages
Section titled “Update the packages”Use these steps after your initial Composer install to move to a newer patch version. Open the changelog and filter for the Storefront Compatibility Package or Storefront Compatibility B2B Package before you update.
-
Update the B2C package:
Terminal window composer update adobe-commerce/storefront-compatibility -
If you use B2B drop-ins, update the SCP-B2B package:
Terminal window composer update adobe-commerce/storefront-compatibility-b2b -
Upgrade Commerce and clear the cache:
Terminal window bin/magento setup:upgrade && bin/magento cache:clean
What’s next
Section titled “What’s next”After you install the packages, configure your storefront to connect to Commerce. Confirm any remaining items on the Commerce on Cloud or on-premises checklist before going live.