
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 App Builder for Commerce developers: actions, events, webhooks, API Mesh and the admin UI SDK.

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.

Commerce GraphQL and a REST API behind one endpoint, joined without N+1 calls, plus the cache model: one response, one Cache-Control, strictest source wins.

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.

aio app logs shows the logs of your latest activation, or of up to 50 with --limit.

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.

aio app logs is fine on your laptop. For shared Stage and Production workspaces, set up New Relic log forwarding, check that it worked and know the limits.

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.

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.

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.

What aio app init actually creates, which three files decide how your app behaves, what never goes into git, and how a Commerce admin extension changes the layout.