Platforms such as Shopify and WooCommerce let a South African business open an online store quickly, with themes, payments and apps ready to use. For most stores that is exactly right. As a store grows, though, some hit limits: themes and plugins slow the site on mobile, the checkout cannot be shaped the way the business needs, or the same products have to be sold through a website, an app and physical stores at once. Headless commerce is one answer to those limits, but not the only one, and not a cheap one.
What is headless commerce?
In a standard store, the storefront and the e-commerce engine are one system: the theme that displays products is part of the platform that manages them. In headless commerce, the two are separated. The engine, which can still be Shopify, WooCommerce or another platform, manages products, stock, orders and payments, while a custom storefront, often built with a framework such as Next.js, displays them and talks to the engine through an API such as the Shopify Storefront API.
| Standard theme store | Headless store | |
|---|---|---|
| Storefront | A theme inside the platform | A custom front end connected by API |
| Speed on mobile | Depends on theme and apps; often slowed by plugins | Can be engineered for very fast loads |
| Design freedom | Within the theme’s limits | Complete control |
| Apps and plugins | Install from the app store | Many must be integrated by developers |
| Editing | Theme editor and page builders | A content management system set up for the storefront |
| Build cost | Lower | Higher, plus ongoing development |
| Best for | Most small and medium stores | Larger stores with demanding performance or channel needs |
What are the signs a store has outgrown its theme?
- Product and checkout pages fail Google’s Core Web Vitals on mobile, even after images and apps have been cleaned up.
- Dozens of plugins or apps are needed to make the store work, and each update risks breaking something.
- The business needs shopping experiences the theme cannot support, such as complex product configurators, trade pricing or bundles.
- The same catalogue has to serve a website, a mobile app, in-store systems or marketplaces from one place.
- Marketing campaigns need landing pages and content the theme makes slow or difficult to build.
If only the first sign applies, try optimisation first. Removing unused apps, compressing images and switching to a lighter theme often solves speed problems far more cheaply than going headless. Our guide to website speed covers the fixes.
What are the benefits of headless commerce?
- Speed: pages can be pre-built or rendered on the server and served close to customers, which matters on South African mobile networks.
- Control: the browsing and checkout experience can be designed around your customers rather than a theme’s defaults.
- One backend, many channels: the same products and stock can feed a website, app and other channels.
- Flexibility: the storefront can be redesigned without migrating the store, and the engine can be changed without rebuilding the storefront.
What are the trade-offs?
- Higher cost to build and to maintain, because the storefront is custom software.
- Developers are needed for changes a theme editor would handle.
- Some apps that plug straight into a theme, such as reviews or upsells, need integrating separately.
- Two systems to run and monitor instead of one.
What should a South African headless storefront include?
- Local payment options: card, instant EFT such as Ozow, PayFast, buy-now-pay-later such as Payflex, and bank app payments such as Capitec Pay.
- Courier and delivery integrations with clear costs and timelines before checkout.
- Server-side conversion tracking, such as Meta’s Conversions API, so marketing can see which campaigns produce sales.
- Stock and order sync with the e-commerce engine and accounting, so nothing is sold that is not in stock. See our guide to connecting business systems.
- Search engine essentials: server-rendered pages, product structured data and redirects from the old store’s URLs.
What does headless commerce cost?
At Lulonke, a headless e-commerce build typically costs R80,000 to R350,000 or more and takes 6 to 10 weeks, depending on catalogue size, integrations and custom features. It includes a Next.js storefront, South African payment gateways, inventory and courier integrations, server-side conversion tracking and cart recovery. It generally suits stores selling around R500,000 or more a month, where the gains in speed and conversion justify the investment. For most stores below that, a well-optimised theme store is the better value. Our website development price guide compares all the options.
Frequently asked questions
Is headless commerce better than Shopify?
Not better in general, and often not separate: many headless stores still use Shopify as the engine behind a custom storefront. Headless suits larger stores with demanding speed, design or multi-channel needs. For most stores, a standard Shopify or WooCommerce setup is better value.
Does headless commerce improve SEO?
It can, mainly through faster pages and full control over page structure and structured data. Done badly it can hurt SEO, for example if pages are rendered only in the browser or old URLs are not redirected. Server rendering and careful migration are essential.
How much does a headless store cost in South Africa?
At Lulonke, headless e-commerce builds typically cost R80,000 to R350,000 or more and take 6 to 10 weeks, plus ongoing development and hosting.
Can I keep Shopify or WooCommerce if I go headless?
Yes. Both can act as the engine for products, orders and payments while a custom storefront handles what customers see, which lets you keep your existing admin and data.
When should a store not go headless?
When it is small, has no developer support, relies on many plug-and-play apps, or has speed problems that optimising images and apps would fix. In those cases headless adds cost without matching benefit.
