Headless commerce, also called headless e-commerce, is a platform architecture that decouples the front end of an e-commerce website with the back end. The front end, or the “head,” is typically a content management system (CMS) or digital customer experience delivery (DCED) platform that stores, manages and distributes content. The back end is the e-commerce platform that provides the purchasing logic, data and capabilities. This headless approach combines the customization of a CMS with the security of a software as a service (SaaS) e-commerce platform.
Headless commerce may be a good solution for businesses that focus heavily on content marketing or branding, businesses that use unconventional design templates and businesses that rely on B2B operations. E-commerce platform vendors that support a headless approach include BigCommerce, WooCommerce and SAP CX Commerce Cloud. CMS products that can be integrated with a headless approach include Wordpress, Adobe Experience Manager, Drupal and BloomReach.
Headless commerce has risen in popularity as a way to combat the growth of the internet of things (IoT). Since the content of an e-commerce platform is not connected to the back end, businesses can deliver a consistent, functional experience to devices like computers, smartphones, smartwatches, kiosk screens and AI assistant skills.
How headless commerce works
The headless commerce architecture works by passing requests between the presentation and application layers of a platform. This is done through web services of API calls that connect the front end with back end functionality.
For example, a user may click an “Add to Cart” button that is registered on the presentation layer, or the front end. An API call will then be sent to the application layer, or back end, of the platform that registers the product as active for future action, such as purchase.
Benefits of headless commerce
In many scenarios, a headless commerce approach can provide the following benefits:
- Increases flexibility with updating or developing new front end functionality.
- Makes it easier and quicker to perform optimization tests cases.
- Helps to create a consistent and personal user experience.
- Allows businesses to become omnichannel, or compatible with any devices and platforms.
- Lowers risk of error in back end code.
- Enables a faster release of new content or design changes.
However, a few drawbacks that should be considered include the potentially high cost of ownership and the requirement of maintaining two systems.
Headless e-commerce vs traditional e-commerce
Headless e-commerce is an evolution of traditional e-commerce. Traditional e-commerce relies on a front end and back end that function together. Due to this, developers experience more constraints with traditional e-commerce. The first is that any changes or updates require more time as all edits need to be made within the databases, code and user interfaces. The second is that more traditional e-commerce platforms tend to limit business in terms of customization as they come with predefined functionality. Lastly, since the front end and back end are coupled, there is a higher risk associated with making a change that could disrupt logic or operations.