- 0:00–0:06
Store A • Name every layer • Headless splits the storefront • Three layers need owners • Detached storefront • Commerce backend • Integrations layer • Operations layer
The Store A badge stays fixed in its lane. The article's layer-owners figure: "Detached storefront" starts on top of the stack and lifts away, and one double-headed cyan connector draws across the new gap to "Commerce backend". A cyan outline then visits the blank owner tag beside "Commerce backend", "Integrations layer" and "Operations layer" in turn; every tag stays blank.
- 0:06–0:12
Store A • A storefront toolkit keeps the platform • You own storefront code • The platform runs checkout
A stack whose backend the platform runs: an office-building emblem on its backend block and a shop canopy for the storefront on top, drawn at the same size and place as the team-run stack in the next scene. The canopy lights in the team colour (cyan) while the backend stays in the platform colour (royal blue). "You own storefront code" points to the canopy and "The platform runs checkout" to the backend; a blank order card drops from the storefront into the platform's backend.
- 0:12–0:18
Store A • An open backend moves the work • Change the commerce logic • Run it for years
A stack whose backend the team runs: a server rack with a wrench on its backend block, at the same size and place as the platform-run stack before it. The backend lights in the team colour, then four small module tiles dock beside it one by one, two for integrations (plug) and two for operations (gear). "Change the commerce logic" and "Run it for years" appear in the team colour. Neither stack is marked as the better choice.
- 0:18–0:24
Store A • Test local payments • Approvals, declines, refunds • Sandbox, then production
A cyan route leaves the outer end of the Store A badge, runs down the side and on through a dashed sandbox frame into a solid production frame. Three blank test cards travel it one after another, pause in the sandbox and wait in production. No card is marked approved or declined.
- 0:24–0:30
Store A • Decide who issues invoices • Ask your tax adviser • Storefront choice does not settle it • Store backend • ERP • Accounting software
The article's invoice-issuer figure: one blank invoice sheet with three dashed cyan routes to "Store backend", "ERP" and "Accounting software". A cyan pulse travels down each route in turn and returns to the sheet. Every route stays dashed and no system is chosen, while "Ask your tax adviser" and "Storefront choice does not settle it" stay on screen.
An illustrative Gulf store names an owner for every layer, weighs a platform-run against a team-run backend, tests local payments and asks who issues tax invoices; neither option is declared the winner.
Read the article: Shopify Hydrogen vs Medusa: Storefront Toolkit or Commerce Backend?