Skip to content

Search is only available in production builds. Try building and previewing the site to test it out locally.

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.

The package version must match your Adobe Commerce release. Use the version from this table in composer require adobe-commerce/storefront-compatibility:VERSION.

Adobe CommercePackage versionReference
2.4.9 (recommended)4.9.3GraphQL and REST changes
2.4.84.8.28GraphQL and REST changes
2.4.74.7.15GraphQL and REST changes
  1. Change to your Commerce project directory.

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

    Terminal window
    magento-cloud environment:checkout <environment-id>
  3. Add the package using the version from Choose your B2C package.

    Terminal window
    composer require adobe-commerce/storefront-compatibility:4.9.3

    Use 4.8.28 for Adobe Commerce 2.4.8.

    Use 4.7.15 for Adobe Commerce 2.4.7.

  4. Update package dependencies.

    Terminal window
    composer update adobe-commerce/storefront-compatibility
  5. Commit and push so the cloud environment picks up composer.json and composer.lock.

    Terminal window
    git add composer.json composer.lock
    git 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.

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 CommercePackage version
2.4.9 (recommended)1.0.25
2.4.81.0.25

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

  1. Change to your Commerce project directory.

  2. Check out the environment branch you want to update, if you have not already done so for the B2C package.

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

    Terminal window
    composer require adobe-commerce/storefront-compatibility-b2b:1.0.25
  4. Update package dependencies.

    Terminal window
    composer update adobe-commerce/storefront-compatibility-b2b
  5. Commit and push so the cloud environment picks up composer.json and composer.lock.

    Terminal window
    git add composer.json composer.lock
    git commit -m "Add B2B compatibility package"
    git push origin <branch-name>

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:

    Terminal window
    composer update adobe-commerce/storefront-compatibility
  2. If you use B2B drop-ins, update the SCP-B2B package:

    Terminal window
    composer update adobe-commerce/storefront-compatibility-b2b
  3. Upgrade Commerce and clear the cache:

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

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.