What "headless" means
Every online store has two parts: the front end (the pages customers see: product pages, cart, checkout) and the back end (products, prices, stock, orders, payments). In a traditional store, both come as one package from the same platform and theme.
In a headless store, the back end runs on its own and exposes everything through an API. The front end is built separately, often as a custom web app, and fetches what it needs. The same back end can then feed a website, a mobile app, a kiosk or a WhatsApp shop.
| Traditional (all-in-one) | Headless | |
|---|---|---|
| Setup | Theme + platform, quick | Custom front end + commerce API |
| Design freedom | Limited by the theme | Complete |
| Speed | Depends on theme and apps | Can be very fast if built well |
| Multiple channels | Mostly the website | Website, app, kiosk, social from one back end |
| Cost | Lower | Higher build and maintenance |
| Who can change it | Store owner via admin | Content via admin, layout via developers |
When headless is worth it
- You sell on several channels (website, mobile app, marketplaces, physical stores) and want one source of truth for products and stock.
- Speed is costing you sales and your theme can't get faster.
- Your brand experience is a selling point, e.g. custom product builders, rich content or unusual checkout flows.
- You've outgrown your platform's limits and keep fighting apps and plugins.
- You have, or can hire, developers to maintain the front end.
When it isn't
- You're just starting out or testing a product, so launch fast on a standard store first.
- You have fewer than a few hundred products and one sales channel.
- Nobody on your team can maintain custom code.
- Your main problem is marketing, not the technology.
Headless is a scaling decision, not a starting point. Most stores should earn their way to it.
A middle path
You don't have to go fully headless at once. Many stores keep their existing platform for orders and stock, and build just one high-value part headless: a fast landing page for campaigns, a mobile app using the same product API, or a custom product configurator.
Questions to ask before you commit
- Which specific problem will headless fix, and how will we measure it?
- Does our commerce platform have a good API (products, cart, checkout, customers)?
- How will payments, including local options like M-PESA, work in the new checkout?
- Who will update content, and do they need a headless CMS?
- What's the monthly cost to host and maintain it?
- How do we protect SEO during the switch: same URLs, redirects, structured data?
What it costs
A headless build costs more than a theme-based store because the front end is custom software. For comparison, at Biashara Softwares a standard e-commerce store starts from KSh 35,000, while custom web systems start from KSh 200,000. Most headless projects sit in the custom range, depending on features and channels.
Headless commerce is powerful for growing brands selling across several channels or limited by their platform. For most new and small stores, a fast, well-built standard store is the better investment, with headless as a later step. We build both: standard online stores with M-PESA and card checkout, and headless storefronts and apps for brands that have outgrown them.
See our website and e-commerce development service or custom software.
