Headless Commerce Specifications for aLuxury Fashion House

Context

From May to August 2025 I worked as Lead Business Analyst on a luxury fashion house's transformation toward a composable commerce architecture. The work was cross-functional over three months, with teams split between Paris, London and a partner IT services firm.

The challenge

Composable commerce is like moving from one big house to a village of small ones: each piece can evolve on its own, but someone has to draw the streets. Several teams were building parts of the same storefront, and the brand expects every page, every image and every interaction to feel like one house.

That only works when the work is described precisely enough that a developer in another city builds what the brand meant, not what the ticket happened to say.

What we did

• Led the functional discovery across teams and structured the Azure DevOps backlog into epics, features and stories.
• Audited the Storybook design system, so components were reused instead of rebuilt page by page.
• Wrote the specifications for the bot protection on customer-facing forms.
• Mapped how assets travel from the DAM to the frontend, so every image reaches the right component in the right format.

What it taught me

In a headless setup, the customer only sees the last step of a long chain. If the asset journey and the backlog are unclear upstream, the brand pays for it at the very last pixel. For the architecture trade-offs behind this kind of move, see MACH vs monolith.