Reference

Video Library

Curated videos for the hard concepts and executive context. Use the “Watch first” set as a 2-day playlist. Each card has why to watch, what to listen for, 3 takeaways, and 2 interview phrases to borrow.

Verification note: this environment can't load YouTube directly, so these were corroborated by search but not live-played here. Click “Open on YouTube” on each card to confirm it still plays before relying on it.
Watch firstComposable commerce~1 min

Explained in 60 seconds: What is Composable Commerce?

commercetools

Why watch: The cleanest vendor-neutral-ish definition to anchor the term before you go deeper.

Listen for: How they frame 'best-of-breed components assembled to fit the business' vs a monolith.

3 takeaways
  • Composable = assemble best-of-breed building blocks rather than buy one suite.
  • The value is flexibility and speed-to-market, not technology for its own sake.
  • Contrast is always against the monolithic all-in-one platform.
Interview phrases to borrow
  • "Composable means you assemble best-of-breed capabilities instead of inheriting one vendor's whole roadmap."
  • "The point isn't the architecture — it's the speed and optionality it gives the business."
Open on YouTube ↗ (verify it still plays before relying on it)
Commerce architecture~5-8 min

Why commercetools Built a Layered Composable Commerce Architecture

commercetools (Dirk Hoerig)

Why watch: Founder-level rationale for layering composable systems — good for the 'why' behind architecture.

Listen for: How a layered approach manages complexity at enterprise scale.

3 takeaways
  • A layered approach organises composable components so enterprises aren't overwhelmed.
  • API-first / cloud-native origins trace to the 2010s mobile + cloud shift.
  • Layering is how you keep best-of-breed from becoming best-of-chaos.
Interview phrases to borrow
  • "Composable only pays off if you layer it — otherwise best-of-breed becomes best-of-chaos."
  • "The orchestration layer is what makes a set of components behave like one system."
Open on YouTube ↗ (verify it still plays before relying on it)
Watch firstMACH / DXP~8 min

What is MACH Architecture? Composable | DXP

Sitecore (Thomas Desmond)

Why watch: Connects MACH to composable DXP and PBCs in one explainer — two topics at once.

Listen for: Each MACH letter expanded, and how MACH underpins a composable DXP.

3 takeaways
  • MACH = Microservices, API-first, Cloud-native (SaaS), Headless.
  • MACH is the technical foundation; composable is the business strategy on top.
  • Components are pluggable, replaceable Packaged Business Capabilities (PBCs).
Interview phrases to borrow
  • "MACH is the architecture; composable is the operating strategy it enables."
  • "PBCs are the business-recognisable building blocks — Search, Cart, Promotions — not raw microservices."
Open on YouTube ↗ (verify it still plays before relying on it)
MACH Alliance~3-5 min

What's the MACH Alliance all about?

The MACH Alliance

Why watch: Authoritative source on what the Alliance is and certifies — industry context.

Listen for: Vendor-neutral, non-profit positioning and what certification signals.

3 takeaways
  • Founded 2020 by commercetools, Contentstack, EPAM, and Valtech.
  • Vendor-neutral non-profit advocating open, best-of-breed architecture.
  • Membership is certified against MACH standards — a credibility marker.
Interview phrases to borrow
  • "Orium's MACH Alliance membership is shorthand for a certified commitment to open architecture."
  • "The Alliance exists to push the market away from monolithic lock-in."
Open on YouTube ↗ (verify it still plays before relying on it)
Headless CMS / DXP~5 min

Contentstack Headless CMS — Product Overview

Contentstack

Why watch: The canonical 'what is a headless CMS / composable DXP' reference from a MACH founder.

Listen for: How content is decoupled from presentation and delivered to any channel via API.

3 takeaways
  • API-first content engine decouples content from the presentation layer.
  • One content source delivers to web, app, and increasingly AI agents.
  • Governance, asset management and visual editing make it enterprise-grade.
Interview phrases to borrow
  • "Headless CMS turns content into a service the whole experience layer can consume."
  • "Contentstack pairs naturally with commercetools — content engine plus commerce engine."
Open on YouTube ↗ (verify it still plays before relying on it)
Salesforce Commerce Cloud~6-10 min

Salesforce Commerce Cloud Overview Demo

Salesforce

Why watch: Official platform walkthrough — direct prep for SFCC-specific questions.

Listen for: Unified B2C/B2B, AI features, and speed-to-launch positioning.

3 takeaways
  • SFCC is a managed enterprise commerce platform spanning B2C and B2B.
  • AI-driven, mobile-first experiences across channels are the headline.
  • Composability comes via PWA Kit / Composable Storefront, not a rebuild.
Interview phrases to borrow
  • "SFCC clients modernise incrementally — decouple the storefront first, keep the engine."
  • "Incremental composability is a lower-risk path than a big-bang replatform."
Open on YouTube ↗ (verify it still plays before relying on it)
Watch firstAgentic commerce~10-20 min

How Salesforce and Forter Drive Trust in the Agentic Commerce Era

Salesforce / Forter

Why watch: Covers the 2025-26 agentic wave and the Agentic Commerce Protocol — the most current topic.

Listen for: Why trust/fraud and identity matter when agents transact autonomously.

3 takeaways
  • The Agentic Commerce Protocol (ACP) lets AI agents discover and transact.
  • Trust, fraud and delegated authentication are the hard problems.
  • Enterprises must expose structured, agent-readable endpoints.
Interview phrases to borrow
  • "Agentic commerce shifts discovery and checkout from human UIs to agent-mediated transactions."
  • "The agent-ready enterprise wins because it's easiest for agents to understand and trust."
Open on YouTube ↗ (verify it still plays before relying on it)
B2B commerce~3-5 min

Where B2B Commerce Meets Bold Innovation

commercetools

Why watch: Vendor framing of B2B-specific needs on a composable stack — relevant to Orium's SiteOne-style work.

Listen for: Business units, role-based permissions, customer-specific catalogues and pricing.

3 takeaways
  • B2B needs business units, approval roles, and account-specific pricing natively.
  • B2C-plus-plugins tends to fall short for serious B2B requirements.
  • Composable lets B2B scale complex buyer hierarchies without a monolith.
Interview phrases to borrow
  • "B2B isn't B2C with a login — it's contract pricing, approvals, and reordering as first-class features."
  • "PunchOut and account hierarchies are where B2B commerce earns its keep."
Open on YouTube ↗ (verify it still plays before relying on it)
Built for Darren O'Donoghue · Not affiliated with or endorsed by Orium · For private interview preparation only.