
App Builder · Ep 11: what runs on your machine, and what needs a deploy
Every piece of the series, tested three ways: fully local, local code against a Stage workspace, and deployed. A grid of what worked, what failed, and why.
Adobe Commerce (Magento 2) in practice: modules, upgrades, security patches, static analysis, indexers, integrations and the fixes that keep a store running.

Every piece of the series, tested three ways: fully local, local code against a Stage workspace, and deployed. A grid of what worked, what failed, and why.

The capstone. Take an observer-based integration module, move it to events, an action and an admin page, and weigh what got better against what got harder.

Give your integration a home where merchants work: enable the Admin UI SDK, get Adobe's sample showing, then add a stuck-orders page from your App Builder app.

A Commerce webhook lets your action block or change an operation before it completes. Declare one, verify the signature, and fail open or closed on purpose.

Move the order-placed observer out of Commerce: connect the workspace, subscribe to only the fields you need, and write a handler that survives duplicates.

App Builder now has a document database for actions. When to use it instead of State, how to provision it, the auth that trips people up, and a sync log to query.

Ask Composer which installed packages refuse the target version before you bump Adobe Commerce.

Map each part of an Adobe Commerce module to its App Builder equivalent, then build a scheduled stuck-order alert with an alarm trigger, State for de-duplication and a lock against overlapping runs.

The fixes every Adobe Commerce store needed in autumn 2026, in one list, with links to the steps.

APSB26-146 and APSB26-153 landed weeks apart, and the October patches don't include the September hotfix. My runbook to check, apply and verify each one.

Three ways to start an App Builder project for Commerce, which one I'd pick for an integration, and the steps from clone to a deployed action on Stage.

Two PHP engine flaws allow unauthenticated remote code execution on almost any PHP app, Adobe Commerce included. Where the sources disagree, and the order I'd patch in.