Build and deploy
After defining your app configuration, build and deploy your application so it is ready for association and installation with Adobe Commerce through App Management.
Generated files
The initialization process creates files organized by extension point:
commerce/extensibility/1 for App Management.
src/commerce-extensibility-1/.generated/app.commerce.manifest.jsonsrc/commerce-extensibility-1/.generated/actions/app-management/src/commerce-extensibility-1/ext.config.yamlpre-app-build hookcommerce/configuration/1 for Business configuration (when a businessConfig is defined).
src/commerce-configuration-1/.generated/configuration-schema.jsonsrc/commerce-configuration-1/.generated/actions/app-management/src/commerce-configuration-1/ext.config.yamlpre-app-build hookcommerce/backend-ui/1 for Admin UI SDK registration (when adminUiSdk.registration is defined in app.commerce.config).
src/commerce-backend-ui-1/.generated/actions/registration/src/commerce-backend-ui-1/ext.config.yamlpre-app-build hookGenerated runtime actions
The libraries generate runtime actions organized by extension point. These are auto-generated directories and any manual changes can be lost during regeneration.
App Management actions from commerce/extensibility/1
app-configinstallationBusiness configuration actions from commerce/configuration/1
These actions handle configuration and scope operations (generated when a businessConfig is defined).
configscope-treeThe scope tree action supports syncing scopes from Adobe Commerce, setting custom scope hierarchies for external systems, and unsyncing Commerce scopes. Structural changes in Commerce (websites, stores, store views) are not reflected in App Management until an Admin runs Sync commerce scopes for each associated application that uses scopes; see Scope tree synchronization.
Admin UI SDK registration action from commerce/backend-ui/1
When adminUiSdk.registration is defined, a generated action serves the registration payload to Adobe Commerce.
registrationBuild and deploy
After you change app.commerce.config, build and deploy your application. The pre-app-build hook runs the generators for you, so the manifest, schema, and runtime actions under .generated stay in sync without a separate step.
aio app build --force-build
aio app deploy --force-deploy --no-build
data-variant=tip
data-slots=text
npx aio-commerce-lib-app generate … without a full App Builder build to refresh generated files quickly.After deployment, your application is ready to be associated with Adobe Commerce using App Management. See manage your app for association, installation, and other lifecycle steps.
Find an application in the Admin
Under Apps > App Management, each application appears as a card. The list can include every app associated with the Adobe Commerce instance for the selected Adobe IMS organization. Use the controls above the cards to narrow results:
Search text and both dropdowns apply together (logical AND). To display the full list again, set Status and Extensibility patterns back to their All … options, and clear the search field.
Acquire App
Acquire App opens a new browser tab (or a separate browser view) to Adobe Exchange, where you can discover Commerce-related marketplace listings and add applications to your Adobe IMS organization. After the app is acquired, approved, and deployed, it appears in App Management for association and installation.