Wix Headless Explained: When to Pair Wix with Next.js

Wix Headless lets you keep Wix as the backend (products, orders, bookings, members, CMS content and checkout) while you build the front end in any framework you like, such as Next.js or Astro. It is the right choice when your team wants full control of the front-end code, performance and design, but does not want to build and maintain commerce, booking or member systems from scratch. If your site just needs a custom feature or two, Velo inside a normal Wix site is simpler and cheaper.

Key takeaways

• Wix Headless exposes Wix's business services (Stores, eCommerce checkout, Bookings, Events, Members, CMS, Blog) through the Wix JavaScript SDK and REST APIs.
• Two paths: Wix-managed (Wix hosts and deploys your front end; Astro gets the full integration) and self-managed (any framework, including Next.js, hosted where you choose).
• Checkout, booking and ticket flows can stay on Wix-hosted pages, so you do not rebuild payment-critical screens.
• Wix Headless is free to start; you upgrade to a premium plan for payments, custom domains and analytics.
• Velo is for custom logic inside a Wix site. Headless is for a custom site that uses Wix as its backend. Pick based on how much of the front end you need to own.

What "headless" means on Wix

A standard Wix site is one system: the editor renders the pages, the CMS stores the content, Wix Stores handles products and checkout, and Velo lets you add code inside all of that.

In a headless setup, you split the two halves. Wix keeps the business data and the dashboards your team already uses. Your developers build the front end as a separate application and pull data from Wix through the Wix JavaScript SDK (@wix/sdk plus a package per domain such as @wix/stores or @wix/bookings) or the REST API. Wix's docs list eCommerce, bookings, events, memberships, CMS and blog among the "business solutions" available this way.

Two details make this practical rather than theoretical:

Wix-hosted pages. You can send visitors to Wix-hosted checkout, booking and ticketing pages and bring them back to your site afterwards. Payment handling, tax, coupons and order emails stay with Wix. You build the catalog and cart experience; Wix does the part that has to be right the first time.

One project, many front ends. A website, a mobile app and an internal tool can all read from the same Wix project, which is useful for brands that already run a React Native app or a kiosk.

Wix's own documentation states that Wix Headless projects come with Wix's compliance coverage (it names SOC 2 Type II, HIPAA and GDPR). That is Wix's claim about its platform; confirm the specifics for your industry with Wix before relying on it.

Wix-managed vs self-managed headless

This is the part most 2024-era articles get wrong, because Wix changed it. In 2026 there are two routes.

Wix recommends the managed Astro route. If you are starting fresh and your team does not have a strong framework preference, it is the lowest-maintenance option and worth considering.

But the question in this post's title is about Next.js, and here the honest answer is: Next.js on Wix Headless is a self-managed setup. Wix publishes official Next.js templates (a Next.js Commerce starter for Wix Stores and a minimal-examples repo), the SDK works the same way, and you deploy to Vercel or wherever you already deploy Next.js. You own hosting, SEO metadata, sitemaps, analytics and secrets. For a team that already runs Next.js in production, that is exactly what they want. For a team that does not, it is extra responsibility that Astro-managed hosting would take off their plate.

What the code looks like

Here is the shape of a self-managed Next.js integration with Wix Stores, based on Wix's eCommerce quick start. Install the SDK and the modules you need:

npm install @wix/sdk @wix/stores @wix/ecom @wix/redirects

Create a client with your OAuth app's client ID (from the Headless Settings page of your Wix project) and query products:

// lib/wix.js
import { createClient, OAuthStrategy } from '@wix/sdk';
import { products } from '@wix/stores';
import { currentCart } from '@wix/ecom';
import { redirects } from '@wix/redirects';

export const wixClient = createClient({
  modules: { products, currentCart, redirects },
  auth: OAuthStrategy({ clientId: process.env.NEXT_PUBLIC_WIX_CLIENT_ID }),
});

// Anywhere in your app
export async function getProducts() {
  const result = await wixClient.products.queryProducts({});
  return result.items;
}

Adding to the cart and handing off to Wix-hosted checkout is a few more calls: currentCart.addToCurrentCart(), then currentCart.createCheckoutFromCurrentCart() to get a checkout ID, then redirects.createRedirectSession() to get the URL of the Wix-hosted checkout page, with a postFlowUrl so the visitor returns to your site afterwards.

In a real Next.js build you would also handle visitor session tokens so carts persist across page loads (the quick start uses a cookie), register your domain in the OAuth app's allowed redirect list, and use Server Components or route handlers for anything that should not run in the browser. The Wix Velo tutorial for beginners is the right starting point if you have never touched Wix's APIs; the SDK patterns carry over.

Headless vs Velo: which one do you actually need?

This is the decision that matters, and we see people get it wrong in both directions.

Choose Velo (a normal Wix site with custom code) when:

• You need custom features, not a custom front end. Filtered directories, calculators, member dashboards, CRM syncs and API integrations are all Velo jobs. See Wix Velo development.
• Your team edits the site in the Wix editor and wants to keep doing that.
• Your budget is in the hundreds or low thousands, not tens of thousands.
• You are happy with Wix Studio's design and performance ceiling, which is high for most business sites.

Choose Wix Headless when:

• You need complete control of the front-end code: a design system, animations or interactions the editor cannot produce, or strict performance budgets you want to control directly.
• Your developers already work in Next.js, Astro or React and you want one codebase for web and app.
• You need the same business data in several front ends (site plus mobile app plus kiosk).
• You want Wix's commerce, bookings or membership engines without Wix's editor.

Do not choose Headless because someone told you Wix sites cannot rank or cannot be fast. Both are solvable inside Wix; our post on whether Wix is good for SEO covers that. Going headless to fix an SEO problem usually trades one set of issues for a bigger one, because you now own metadata, sitemaps, structured data and rendering yourself.

A rule of thumb from our projects: if more than about 70% of the site is standard pages that a marketing team edits, stay in Wix Studio and add Velo where needed. If the site is the product and the developers own every pixel, headless is the better architecture.

What a Wix Headless project costs

Three cost lines, and only one of them is Wix.

The Wix plan. Wix's docs state Wix Headless is free to start, and that you upgrade to a premium plan for payments, custom domains and in-depth analytics. There is no separate headless fee or per-API-call charge at the time of writing. Check Wix's current pricing page for the plan you need, because accepting payments requires a paid plan.

Hosting. For Wix-managed, included. For self-managed Next.js, whatever Vercel, Netlify or your cloud provider charges. Small sites often fit free or low tiers; high-traffic stores do not.

Development. This is the real cost. A headless build is custom web development: you are building every page, component and state of a site in code. Our Wix Headless builds start from $2,000, and a headless store with a real catalog, cart, member area and content pages typically lands well above that. Compare that with a Wix Studio store from $800 and the difference is clear: you are paying for control, and you should only pay for it if you will use it.

Things to plan for before you start

• SEO is your job on self-managed. Page titles, descriptions, canonical tags, Open Graph, sitemaps and structured data all live in your front end now. Next.js makes this manageable with its Metadata API, but someone has to do it.
• Members and login. Wix supports visitor and member authentication through OAuth, with a Wix-hosted login page or a custom one. Decide early, because it affects every page that shows personalized data.
• Admin operations. Anything that should run with elevated permissions (bulk updates, admin reports) uses API keys or client credentials on the server, never in the browser.
• Content editing workflow. Your marketing team will still edit products, posts and CMS items in the Wix dashboard. Make sure they understand that a layout change now goes through a developer.
• Migration from an existing Wix site. Wix documents adding a headless front end to an existing site and migrating from one. Your data, orders and members can stay where they are while the new front end is built alongside the old site.

How Wix Engine can help

We build on both sides of this line: Wix Studio and Velo sites for teams that want to stay in the editor, and Wix Headless development with Next.js for teams that want their own front end on top of Wix's commerce, booking and member systems. Book a free call and we will tell you which one your project needs, including when the answer is "stay in Wix Studio and save the budget." Our Next.js development team handles the front end; our Legend Partner Wix team handles the backend configuration.

Book a Free Call

FAQ

Is Wix Headless the same as Velo?

No. Velo is Wix's JavaScript platform for adding custom code inside a Wix site that the Wix editor renders. Wix Headless replaces the Wix front end entirely: you build the site in Next.js, Astro or another framework and use Wix only for business data and services through the SDK or REST API. Many projects need Velo; far fewer need headless.

Does Wix Headless support Next.js?

Yes, as a self-managed project: you build in Next.js, call Wix through the JavaScript SDK and host the app on Vercel, Netlify or your own infrastructure. Wix publishes official Next.js starter templates. Wix-managed hosting gives Astro the full integration; other frameworks run there only as static client builds or on the Cloudflare Workers runtime.

How much does Wix Headless cost?

Wix Headless is free to start, and you upgrade to a Wix premium plan when you need payments, a custom domain or analytics. The larger cost is development, because every page is custom code. Expect a headless build to cost several times a Wix Studio site with the same pages; Wix Engine headless builds start from $2,000.

Can I keep Wix checkout in a headless site?

Yes. Wix-hosted pages let you redirect visitors to Wix's checkout, booking and ticket purchase flows, then return them to your site with a post-flow URL. Payments, tax, coupons and order confirmation emails stay with Wix, so you do not rebuild or re-certify payment screens.

Is Wix Headless good for SEO?

It can be, but on a self-managed project you are responsible for everything Wix normally handles: metadata, sitemaps, canonical URLs, structured data and server rendering. Frameworks like Next.js and Astro give you the tools, but nothing is automatic. If SEO is your main reason for leaving the Wix editor, fix it inside Wix first.