Table of Contents
- What Is Headless Commerce?
- Is Shopify a headless CMS?
- Do your customers care?
- Is Headless Commerce Right for Your Business?
- How Does Headless Commerce Work?
- What is a headless API?
- Different ways to build your headless architecture
- Some Headless Myths
- Leading Headless Platforms
- So, Should You Go Headless?
- How Do You Get Started With Headless?
|Traditional commerce||Headless commerce|
|• Tethered frontend and backend platforms||• Separated frontend and backend platforms (still ‘talk’ to each other seamlessly)|
|• Slower page load times due to many API calls and technical constraints of the platform||• Flexible frontend development without the need to update backend functions|
|• Can be hard to make design changes (especially for highly unique experiences)||• Uses technology that greatly increases the speed or load times of the site|
|• Third-party integrations can be quick to deploy (think: click to install), but cause problems to the storefront due to poor architecture and code bloat||• Easy to totally customize your store (no more design constraints|
or a speed tradeoff)
|• Largely unresponsive to new channels||• Increased possibilities of integration with third parties|
|• Testing is faster and iterations can be made more quickly|
|• Adaptable to new channels and touchpoints|
|• Unified customer experience|