Complete the initial installation of the Store Fulfillment for Adobe Commerce by Walmart Commerce Technologies extension in a non-production environment with queue manager running and caching configured to allow exception handling. Ensure that your development environment includes development tools to ensure best practices for operating and maintaining your Adobe Commerce instance.
Review the requirements for the Store Fulfillment solution and gather required information before you install or upgrade the Store Fulfillment extension for Adobe Commerce.
If you have installed a pre-release or beta version of the Store Fulfillment for Adobe Commerce extension, use the following command to remove it before installing the current version.
rm -rf composer.lock vendor/walmart && composer require walmart/magento-bopis-metapackage:1.0.0
Access to the Store Fulfillment by Walmart Commerce Technologies software archive (.zip file)—During the onboarding and enablement process, work with your Account Manager to get access to the installation file for the Store Fulfillment extension.
Adobe Commerce account information-Installing the Store Fulfillment solution requires a Commerce account. You need an account ID and credentials with Owner or Admin access to the Adobe Commerce project.
For Adobe Commerce on cloud infrastructure projects, software installers must have administrator access to the Cloud project. See Manage user access.
Experience using Composer and the Commerce CLI—See General CLI Installation for information about using these tools to install and manage extensions on the Adobe Commerce platform.
Experience installing third-party extensions on Adobe Commerce—For reference, see the Adobe Commerce documentation.
Follow the instructions provided by your account representatives to download the archive file that contains the Composer packages for installing the Store Fulfillment Services extension.
Extract the archive file that contains the integration bundle to install the Store Fulfillment Services extension.
Create a target directory for the extracted files.
From the command line, go to the web server doc root directory.
Extract the archive file to the new directory.
Verify that the files were extracted successfully by reviewing the file listing.
../var/www/html/artifacts]$ ls -a . .. bopis-sdk.zip module-magento-bopis-alternate-pickup-contact-admin-ui.zip module-magento-bopis-alternate-pickup-contact-api.zip
Use Composer to configure the source directory for the installation and install the Store Fulfillment Services extension.
Configure the source repository for the Composer installation.
composer config repositories.artifacts artifact artifacts/
Add the Store Fulfillment Services extension to
composer require walmart/magento-bopis-metapackage:1.0.0
For better performance on Adobe Commerce on-premises instances, you can update the autoload configuration:
composer dump-autoload --optimize
Complete the installation by using the
bin/magento setup:upgrade to update the database schema and data with the changes to support the Store Fulfillment solution.
For Adobe Commerce on cloud infrastructure projects, you do not have to register the extension. Instead, commit the code changes from the previous step, and push them to your environment branch. The commands to update the database schema and data are run automatically during the cloud build and deployment process.
Register the extension with Adobe Commerce by using the
setup:upgrade Magento CLI command.
If prompted, recompile your Commerce project.
Clean the cache.
Disable maintenance mode.
From the Adobe Commerce server, verify that the modules for the Store Fulfillment Services extension are installed and enabled.
Log in to the server.
For installations on Adobe Commerce on cloud infrastructure, use SSH to log in to the remote environment.
Verify that the Store Fulfillment Services modules are enabled.
bin/magento module:status --enabled | grep Walmart
The output should include the following modules:
Walmart_BopisBase Walmart_BopisAlternatePickupContact Walmart_BopisAlternatePickupContactFrontend Walmart_BopisApiConnector Walmart_BopisAlternatePickupContactAdminUi Walmart_BopisCheckoutPickInStoreApi Walmart_BopisInventorySourceAdminUi Walmart_BopisCheckoutPickInStore Walmart_BopisInventoryCatalogApi Walmart_BopisPreferredLocationApi Walmart_BopisHomeDeliveryApi Walmart_BopisHomeDelivery Walmart_BopisPreferredLocation Walmart_BopisInventoryCatalog Walmart_BopisPreferredLocationFrontend Walmart_BopisCheckoutPickInStoreAdminUi Walmart_BopisInventorySourceApi Walmart_BopisInventorySourceFaasSync Walmart_BopisInventorySourceReservation Walmart_BopisLocationCheckInApi Walmart_BopisLogging Walmart_BopisStoreAssociateApi Walmart_BopisLocationCheckInFrontend Walmart_BopisStoreAssociate Walmart_BopisOperationQueue Walmart_BopisOperationQueueAdminUi Walmart_BopisOperationQueueApi Walmart_BopisOrderFaasSync Walmart_BopisOrderUpdateApi Walmart_BopisLocationCheckIn Walmart_BopisInventoryCatalogAdminUi Walmart_BopisPreferredLocationAdminUi Walmart_BopisDeliverySelection Walmart_BopisCheckoutPickInStoreFrontend Walmart_BopisLocationCheckInAdminUi Walmart_BopisStoreAssociateAdminUi Walmart_BopisOrderUpdate Walmart_BopisStoreAssociateTfa Walmart_BopisStoreAssociateTfaApi
If needed, use the setup:static-content:deploy CLI command to deploy static view files to your production environment.
php bin/magento setup:static-content:deploy -f
-f option is required if you are using a blank theme.
For more information, see the Static content deploy best practices in Adobe Commerce article in the Adobe Commerce Help Center.