Headless WooCommerce keeps WooCommerce for products, orders, stock and administration, while the customer experience, from product search to checkout, is built in a separate frontend such as Next.js. The business keeps a mature commerce platform its staff already know, but design, speed and the buying journey are no longer tied to a WordPress theme.
It suits growing stores where the experience, integrations or unusual pricing rules are a competitive factor. For a standard store that needs to launch quickly, it is usually too expensive. Below is how it works, where the risk sits and how to judge whether it pays off.
How the split works
In a conventional WooCommerce store, the WordPress theme generates every page: home, categories, product pages, cart and checkout. In a headless setup, WooCommerce handles data and business rules, and the frontend fetches products, prices and stock through an API such as the WooCommerce REST API, the Store API or GraphQL.
Cart and checkout are the most sensitive part. Either the whole checkout is built in the frontend and connected directly to a payment gateway, or the frontend handles browsing and cart and hands off to a checkout page run by WooCommerce or the payment provider. The first gives the most freedom but needs the most work and testing. The second is often a sensible first release.
Staff keep working in the WooCommerce dashboard: adding products, fulfilling orders, issuing refunds and setting discounts. Order emails and accounting integrations can keep running in the backend as before.
Where the benefits lie
- A buying journey designed around your products and customers, such as bundles, configurable products or subscriptions, instead of bending the business to fit a theme.
- Faster product and category pages, which matters for both conversion and search, especially on mobile.
- Clearer integrations with inventory, accounting, shipping and CRM, because they are built as part of the system rather than as a stack of plugins.
- Product data that serves more channels, such as an app, point of sale, a B2B portal or a reseller catalogue.
- Less dependence on which plugins exist and whether they are maintained, although WooCommerce itself still needs regular upkeep.
Integrations matter more than product count
The biggest uncertainty is rarely the frontend. It is the data and the connections. A thousand simple products with one price are less work than two hundred products with variants, volume discounts, business pricing and stock in several locations. Before a fixed scope is confirmed, you need to map which system owns which data and where it flows.
- Product data: where a product is created first, in WooCommerce, an inventory system or the accounting system, and which one wins when they disagree.
- Prices and discounts: list prices, promotions, customer groups, negotiated prices and how VAT is displayed.
- Stock: how often stock levels sync and what happens if an item sells out while a customer is in checkout.
- Payments and settlement: which gateways are used, how refunds work and how orders reach the accounting system.
- Shipping: delivery methods, rate rules, pickup points or parcel lockers, and how tracking numbers reach the customer.
Each of these can be a simple setting or an integration project in its own right. That is why a responsible partner will not give a fixed price for an online store before this has been reviewed.
When a ready-made platform is the better fit
If the goal is to launch a standard store quickly, without custom design or complex integrations, a self-service platform is almost always more economical. Ready-made platforms handle hosting, security, payment gateways and updates for a predictable monthly fee. Novamedia runs its own e-commerce platform, Cartico, for exactly these cases, and our sister company Vefsíða builds simpler online stores on a monthly subscription.
A conventional WooCommerce store with a well-built theme can also serve for a long time. If the problem is a slow site, you can often gain a lot by cutting plugins, improving hosting and optimising images before building a new frontend. Headless makes sense when those fixes are not enough and the experience or integrations are holding back growth.
What drives the cost
The main cost drivers in a headless store are checkout, the number of distinct page types, integrations and testing. Testing is often underestimated. Checkout has to be tested with different cards, discounts, shipping methods and error cases before real customers use it.
As an illustration, not a quote: if a headless store with a custom checkout and two or three integrations takes 200 to 350 hours, that is roughly ISK 3.6 to 6.3 million excluding VAT at our hourly rate of ISK 17,880. Stores with more systems, B2B pricing or several languages can go well beyond that. After launch come operations for both components and regular maintenance of WooCommerce, plugins and frontend.
A checklist for the decision
- Write down what the current store prevents, such as slow pages, a checkout that does not suit your products, or manual work on orders.
- List every system the store must talk to and who owns each one, both internally and at external providers.
- Summarise the catalogue structure: number of products, variants, special prices, and whether any products are configurable or sold as subscriptions.
- Decide whether the first release needs a custom checkout or can start with a checkout page run by WooCommerce or the payment provider.
- Check which plugins render features on the storefront today, since they will need to be rebuilt or connected in the frontend.
- Plan URLs and redirects so the search rankings of product and category pages survive the move.
- Define who monitors the store after launch and how a checkout failure outside business hours is handled.
Common questions
Can we keep WooCommerce and all our orders? Yes. In a headless setup WooCommerce remains the backend, so products, customers and order history stay where they are. What changes is what the customer sees.
Will our WooCommerce plugins keep working? Those that work in the backend, such as accounting connectors or order workflows, usually do. Those that display something on the storefront, such as product options, related-product suggestions or extra checkout fields, need to be rebuilt or connected in the frontend.
Can we go headless in steps? Yes. A common path is to move product and category pages to a new frontend while keeping the WooCommerce checkout, then move checkout once the first part has proven itself.
Next steps
Start by working through the checklist with the people who run the store day to day. The answers quickly show whether the problem lies in the experience, the integrations, or simply in plugins and hosting that can be fixed without a new frontend.
If the answer is unclear, Discovery and planning with Novamedia, a fixed ISK 214,560 excluding VAT for 12 hours, can map systems, risks and a realistic scope before you invest in a build. Design and build is delivered in visible phases from 80 hours, or ISK 1,430,400 excluding VAT. After launch, System operations at ISK 59,900 per month is designed for online stores and backends with a database. If a ready-made store turns out to be enough, we will say so.