Adobe Commerce extensibility
Build apps that extend Adobe Commerce using the Adobe Developer App Builder framework.
Traditional Commerce extensions run inside the application, sharing resources and release cycles with core code. Out-of-process extensibility (OOPE) moves your custom code outside Commerce to Adobe's serverless infrastructure, where it communicates through APIs and events.
This separation means your apps deploy independently, scale on their own, and don't block Commerce upgrades. When issues arise, Commerce keeps running while you debug and redeploy.
Learn more about extensibility approaches
Your development journey
Building an out-of-process app follows the following phases:
| Phase | What you'll do |
|---|---|
Setup | Learn about OOPE apps and set up your development environment |
Plan | Define requirements, set up App Builder access, connect to Commerce |
Build | Develop using starter kits or core capabilities (Events, Webhooks, Admin UI SDK) |
Submit | Prepare documentation, meet security requirements, submit for review |
You can explore each phase in detail.
Start building
Connect Commerce to ERP, OMS, PIM, or CRM systems with pre-built data flows.
Build custom payment, shipping, or tax integrations.
React to Commerce activities asynchronously.
Intercept and modify Commerce behavior synchronously.
Add custom pages and configuration to the Commerce Admin.
Additional resources
- Learning path - Curated tutorials and videos for developers new to App Builder
- Extensibility examples - See how App Builder, API Mesh, and Events work together
- PHP to App Builder comparison - Map familiar PHP patterns to App Builder equivalents
- App submission guidelines - Requirements for publishing to Adobe Exchange