DEV.co
Open-Source Ecommerce · w3bdesign

nextjs-woocommerce

A Next.js ecommerce frontend for WooCommerce-powered stores, built with React, TypeScript, and Algolia search. Requires WordPress backend with specific plugins and extensive configuration to function.

Source: GitHub — github.com/w3bdesign/nextjs-woocommerce
608
GitHub stars
151
Forks
TypeScript
Primary language
AGPL-3.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositoryw3bdesign/nextjs-woocommerce
Ownerw3bdesign
Primary languageTypeScript
LicenseAGPL-3.0 — OSI-approved
Stars608
Forks151
Open issues14
Latest release1.2.5 (2026-05-06)
Last updated2026-07-08
Sourcehttps://github.com/w3bdesign/nextjs-woocommerce

What nextjs-woocommerce is

Next.js 16.1.6 + React 19 headless storefront consuming WooCommerce via GraphQL (wp-graphql), with Zustand state management, Apollo Client, Algolia search integration, Tailwind CSS styling, and Playwright test coverage.

Quickstart

Get the nextjs-woocommerce source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/w3bdesign/nextjs-woocommerce.gitcd nextjs-woocommerce# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Decoupled WooCommerce Storefront

Organizations wanting to separate WordPress backend from React frontend while preserving WooCommerce product/cart logic and GraphQL queries.

High-Performance Search-Driven Ecommerce

Sites requiring fast faceted product search and filtering; Algolia integration provides low-latency search with minimal backend load.

Custom Checkout & Cart Workflows

Teams needing full control over checkout UX, cart state, and payment method handling independent of WordPress admin UI.

Implementation considerations

  • WordPress + WooCommerce + wp-graphql + wp-graphql-woocommerce + wp-algolia-woo-indexer must all be installed, activated, and compatible (versions tested: WP 6.9, WooCommerce 9.9.5, WPGraphQL 2.3.3).
  • Algolia account and indexing setup required for search; without wp-algolia-woo-indexer, search feature is non-functional.
  • Environment variables (.env) must be set for GraphQL endpoint, Algolia credentials, and other integrations; no documented validation or fallback behavior.
  • Cash On Delivery is currently the only payment method; Stripe/PayPal/other gateways require custom development.
  • Persistent cart state uses localStorage; no documented server-side cart recovery or session persistence strategy.

When to avoid it — and what to weigh

  • AGPL-3.0 Commercial Restrictions — AGPL-3.0 requires sharing source code if deployed as a web service. Proprietary or closed-source modifications require legal review before deployment.
  • Single-Vendor Plugin Ecosystem — Relies on w3bdesign's wp-algolia-woo-indexer plugin (not in official WP repo); no fallback indexing strategy documented if that plugin becomes unmaintained.
  • Minimal Backend Customization — Tied to WooCommerce + wp-graphql schema; significant backend logic changes require modifying WordPress plugins outside this codebase.
  • Small/Under-resourced Teams — Requires simultaneous management of Next.js, React, WordPress, WooCommerce, three GraphQL plugins, Algolia account, and environment configuration—high operational surface area.

License & commercial use

AGPL-3.0 (GNU Affero General Public License v3.0). This is a copyleft license requiring derivative works and SaaS deployments to share source code under the same license.

AGPL-3.0 is NOT a standard permissive license. Any web service deployment (even internal) that modifies or depends on this code must make modifications available under AGPL-3.0. Commercial use is possible but requires either: (1) compliance with full source disclosure, (2) proprietary license agreement with copyright holder, or (3) independent reimplementation. Requires legal review before production deployment.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityNeeds review
Deployment complexityHigh
DEV.co fitGood
Assessment confidenceHigh
Security considerations

Repository runs OWASP security CI and Codacy quality checks. No known vulnerability disclosure or security audit information provided. Considerations: (1) AGPL source disclosure requirement is a compliance control, not a security feature; (2) sensitive data (GraphQL endpoint, Algolia keys, WooCommerce credentials) stored in .env—standard practices apply; (3) no documented input sanitization strategy for product/cart data flowing from WordPress; (4) Cash On Delivery payment method is low-risk but extensibility to real payment gateways untested; (5) localStorage cart state is client-side only—no server-side validation of cart items at checkout.

Alternatives to consider

Shopify Hydrogen + React

Official Shopify headless framework with built-in Algolia support, better payment integrations, and permissive license (MIT). Steeper Shopify platform dependency.

Medusa.js + Next.js

Open-source commerce engine (MIT license) with GraphQL API, decoupled frontend, and modern payment/plugin ecosystem. No WooCommerce dependency; requires separate backend setup.

WooCommerce Admin + REST API (no headless)

Use WooCommerce with Storefront or custom theme instead of decoupled frontend. Simpler deployment, single-system maintenance, no AGPL compliance risk. Trades customization for simplicity.

Software development agency

Build on nextjs-woocommerce with DEV.co software developers

nextjs-woocommerce is a solid reference architecture for decoupled WooCommerce storefronts—but AGPL-3.0 license requires legal review, multi-system setup is complex, and single-author maintenance poses risk. Devco can guide license compliance, architecture hardening, and plugin dependency management.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

nextjs-woocommerce FAQ

Can I use this commercially without open-sourcing my changes?
Not without legal review or a proprietary license agreement. AGPL-3.0 requires you to share modified source if deployed as a web service. Standard permissive licenses (MIT, Apache 2.0) do not have this requirement.
What happens if wp-algolia-woo-indexer is no longer maintained?
Search feature becomes non-functional. No fallback indexing strategy is documented. You would need to fork the plugin or implement custom indexing—significant effort.
How do I add Stripe or PayPal payments?
Not documented in README. Requires: (1) configuring WooCommerce payment gateway, (2) updating WordPress GraphQL schema to expose payment method fields, (3) modifying Next.js checkout component. Likely requires custom development.
Is the cart state synced across tabs or devices?
localStorage sync is described, but server-side session persistence is not documented. Cart may be lost on logout or across devices without additional backend implementation.

Software developers & web developers for hire

DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If nextjs-woocommerce is part of your open-source ecommerce roadmap, our team can implement, customize, migrate, and maintain it.

Build a Custom Headless eCommerce Store

nextjs-woocommerce is a solid reference architecture for decoupled WooCommerce storefronts—but AGPL-3.0 license requires legal review, multi-system setup is complex, and single-author maintenance poses risk. Devco can guide license compliance, architecture hardening, and plugin dependency management.