Manual installation

This page is for Commerce PaaS 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 and after Adobe Commerce B2B is on the instance. Not sure this is your path? See Find your path.

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.0	GraphQL and REST changes
2.4.8	4.8.25	GraphQL changes

Install the B2C package

Commerce on Cloud (PaaS)

1. Change to your Commerce project directory.

2. Check out the environment branch you want to update.

   magento-cloud environment:checkout <environment-id>

   Replace <environment-id> with your environment ID from the Cloud console or CLI.

3. Add the package using the version from Choose your B2C package.

   composer require adobe-commerce/storefront-compatibility:4.9.0

   Use 4.8.25 for Adobe Commerce 2.4.8.

4. Update package dependencies.

   composer update "adobe-commerce/storefront-compatibility"

5. Commit and push so the cloud environment picks up composer.json and composer.lock.

   git add -A
   git commit -m "Add module"
   git push origin <branch-name>

   Replace <branch-name> with the branch that deploys to your target environment. When the push finishes, check the Deploy log in the Cloud console to confirm the deployment succeeded.

On premises

1. Add the package using the version from Choose your B2C package.

   composer require adobe-commerce/storefront-compatibility:4.9.0

   Use 4.8.25 for Adobe Commerce 2.4.8.

2. Apply the module to your Commerce instance.

   bin/magento setup:upgrade

Choose your B2B package

B2B drop-ins need SCP-B2B in addition to the B2C package. Adobe Commerce B2B must already be on your Commerce instance. SCP-B2B supports Adobe Commerce 2.4.8 and 2.4.9 only; it does not support 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	Reference
2.4.9 (recommended)	1.0.22	B2B Compatibility Package
2.4.8	1.0.22	B2B Compatibility Package

Install the B2B package

Install SCP-B2B only after the B2C Storefront Compatibility Package is on the instance.

Commerce on Cloud (PaaS)

1. Change to your Commerce project directory and check out the environment branch you want to update, if you have not already done so for the B2C package.

2. Add SCP-B2B using the version from Choose your B2B package.

   composer require adobe-commerce/storefront-compatibility-b2b:1.0.22

3. Update package dependencies.

   composer update "adobe-commerce/storefront-compatibility-b2b"

4. Commit and push so the cloud environment picks up composer.json and composer.lock.

   git add -A
   git commit -m "Add B2B compatibility package"
   git push origin <branch-name>

   Replace <branch-name> with the branch that deploys to your target environment.

On premises

1. Add SCP-B2B using the version from Choose your B2B package.

   composer require adobe-commerce/storefront-compatibility-b2b:1.0.22

2. Apply the module to your Commerce instance.

   bin/magento setup:upgrade

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.

1. Update the B2C package:

   composer update adobe-commerce/storefront-compatibility

2. If you use B2B drop-ins, update SCP-B2B:

   composer update adobe-commerce/storefront-compatibility-b2b

3. Upgrade Commerce and clear the cache:

   bin/magento setup:upgrade && bin/magento cache:clean

What’s next

After you install the packages, configure your storefront to connect to Commerce. Confirm any remaining items on the Commerce PaaS checklist before you go live.