Moltin

Overview

Moltin sold commerce as a set of APIs. Developers could add catalogs, carts, checkout, inventory, and orders to any interface without adopting a fixed storefront. Elastic Path acquired Moltin in January 2020, moved all employees into the combined company, and turned the product into Elastic Path Commerce Cloud. Terms were not disclosed.

Founding Story

Jamie Holdroyd and Adam Sturrock started Moltin in the United Kingdom. Their premise was that commerce software should supply building blocks while product teams controlled the customer interface. That appealed to developers building mobile apps and other experiences poorly served by store templates. Moltin later joined Y Combinator's Winter 2015 batch.

Timeline

• Winter 2015: Moltin joined Y Combinator.
• 2016: It announced $2 million in seed funding.
• 2018: Moltin announced an $8 million Series A and reported more than 17,000 developers.
• January 13, 2020: Elastic Path announced the acquisition.
• 2020: The acquired service became Elastic Path Commerce Cloud.

What They Built

Moltin separated the commerce engine from the storefront. Its API exposed product, inventory, cart, checkout, payment, and order capabilities that developers could assemble behind websites, apps, kiosks, and connected devices. Cloud hosting removed the need to run the commerce backend.

The product offered flexibility at the cost of more implementation work. A brand could create a distinctive experience, but still needed developers, integrations, content, search, and operational tooling around the API.

Market Position

Target Customers

Moltin first appealed to developers and digital agencies, then moved toward brands and retailers with custom commerce requirements.

Market Size

It participated in the broad e-commerce software market, specifically the emerging headless and composable segment. No reliable source disclosed Moltin's serviceable market or share.

Competition

Competitors included Shopify, Magento, BigCommerce, CommerceTools, Elastic Path, and custom commerce services. Moltin emphasized API simplicity and cloud delivery; incumbents offered larger ecosystems and more business-user tools.

Business Model

Moltin sold hosted commerce software through tiered plans and enterprise contracts. Usage likely affected price, while larger customers required solution work and support. Public sources do not disclose average contract value, gross margin, or revenue.

Traction

The company reported more than 17,000 developers before its Series A. Elastic Path described hundreds of commerce businesses using Moltin by the acquisition. These figures show ecosystem reach but do not distinguish free experimentation from paid production accounts.

Post-Mortem

Moltin did not shut down; it became the cloud product of a larger headless-commerce vendor. Elastic Path brought enterprise customers, business tooling, and sales reach. Moltin contributed a multitenant, API-first service and developer community. The overlap made the combination credible, while also showing why a developer-first commerce engine can need a larger commercial layer.

The buyer retained every employee and both major offices, evidence that this was a team-and-product acquisition rather than an asset wind-down. The undisclosed price prevents conclusions about venture returns.

Key Lessons

1. An API can be the product, but not the whole purchase. Business tooling, integrations, support, and implementation still decide enterprise adoption.
2. Developer registrations are an early signal, not revenue. Production customers and expansion matter more.
3. Architecture can create strategic value. Moltin supplied the cloud-native product Elastic Path wanted alongside its existing platform.
4. A clean acquisition does not reveal the economics. Employee retention and product continuity prove use, not investor outcome.

Sources

1. Elastic Path acquisition announcement
2. Moltin CEO letter and Series A
3. Connect Ventures portfolio
4. VentureBeat seed report
5. IDC assessment