← Platform Cheat Sheets
Commerce engine (core)

commercetools

What it is

A cloud-native, API-first headless commerce engine and a MACH Alliance founder. Founded 2006 (Munich); raised a $140M Series C in 2021. Acquired Frontastic for a composable frontend.

Where it sits in the stack

The commerce-engine layer — catalogue, carts, checkout, orders, pricing, promotions via REST/GraphQL. Not a CMS or storefront by default; pairs with best-of-breed CMS, search, payments, OMS.

Why enterprises care

One of the earliest API-first movers and the reference composable engine; enterprise B2B/B2C scale; lets teams iterate without replatforming.

Business problem it solves

Frees enterprises from monolithic suites by decoupling backend from frontend — faster iteration, omnichannel, swap components without a rebuild.

Account-expansion opportunity

A commercetools build is Orium's most common land; it opens content (Contentstack/Amplience), search (Algolia), OMS (Fluent), payments (Stripe), and managed optimisation.

What Darren should say

"commercetools is usually the engine at the centre of a composable build — it's where Orium's commercetools Accelerator and the Harry Rosen and SiteOne work live."

What NOT to overclaim

Don't quote the ~$1.9B valuation as fact (secondary-sourced). Don't claim it includes a CMS or storefront natively.

Likely client objection

"Isn't building our own frontend risky?" — yes, headless shifts frontend ownership to you; the mitigation is accelerators and a managed-services relationship.

Interview-ready phrasing

"commercetools is the engine; the value to the client is being able to change everything around it without touching it."

Built for Darren O'Donoghue · Not affiliated with or endorsed by Orium · For private interview preparation only.