Customer story · Nomad Fire Co.

A BBQ webshop that runs everything in one place.

Nomad Fire Co. sells kamados, planchas and tabletop grills in the Netherlands, Germany and the rest of Europe. The store moved from WordPress with WooCommerce to Neuramerce. Here is how we did it, and how we make the shop a little better every week.
The Nomad Fire Co. homepage on nomadfire.shop, built on Neuramerce
Where we started

From a pile of plugins to one platform.

Nomad Fire ran on WordPress with WooCommerce and a translation plugin, with separate tools for email, chat and analytics. Every tool had its own admin, its own costs and its own idea of who the customer was.

In the move, products, blog articles and recipes came along to Neuramerce, in Dutch, English and German. Every old URL got a redirect to its new place, so no link from Google or another site ends up on an error page.

The shop has been live since late September. We will share revenue and search figures once there is enough data to prove something. What we do show: how each part is set up, and why.

First everything in one place. Then a little better every week.

The technology behind the storefront

What a visitor to nomadfire.shop gets in the browser runs on this stack. Server-rendered HTML, a little of our own JavaScript and no framework that has to load first.
No React, Vue or other framework bundle in the browser: the shop is plain HTML with its own scripts.
Why these choices

A fast BBQ webshop starts with what the browser has to load.

HTML from the server

Next.js 16 on Node.js 22 builds every page on the server and keeps it briefly in a cache. The browser gets ready-made HTML and can draw straight away, instead of starting up an app first.

Own templates and blocks

The shop runs on the Neuramerce template system: HTML templates with blocks that follow the Brand Kit. New pages are built from blocks, not from code.

Little JavaScript

Only small scripts of our own run in the browser, for cart, search, filters and menu. What a page doesn't need doesn't load.

3D only on request

Google model-viewer shows the kamado in 3D and AR, but only loads once the visitor taps 3D. Until then it costs the page almost nothing.

Images via Cloudflare R2

Product photos are stored in Cloudflare R2 and go through our own image service, which delivers WebP at the size the screen asks for.

Search in the database

Search runs on PostgreSQL with full-text search and synonyms. No separate search service, so no extra script and no extra subscription.
Why Next.js and Node.js

One language from database to browser.

Node.js runs JavaScript on the server. That means the shop, the dashboard, the integrations and the scripts in the browser all speak the same language: TypeScript. A product field has the same type everywhere, from the database to the product card, and a mistake shows up at build time instead of in front of a customer.

Next.js 16 handles routing, server rendering and caching. A page is built once and then kept for a short while, so the next visitor gets ready-made HTML. Node.js is designed for many simultaneous requests that wait on something, like the database or a payment provider, which is exactly what a web shop does all day.

The difference with WooCommerce is mostly in the structure. WordPress loads its core plus every active plugin on each request, and every plugin can add its own scripts and styles to every page. On Neuramerce the shop, search, translations, chat and analytics live in one codebase: what a page does not need, never ends up in it.

Fewer layers between the customer and the page.

The WooCommerce stack next to the Neuramerce stack

FeatureWooCommerce (old shop)Neuramerce (now)
Server languagePHPTypeScript on Node.js 22
FrameworkWordPress with the WooCommerce pluginNext.js 16 with its own template system
DatabaseMySQL or MariaDB, much data stored as meta rowsPostgreSQL with a fixed column per field
Extra featuresA plugin per feature, each with its own updatesShop, search, translation, chat and analytics built in
Scripts in the browserThe theme plus whatever each plugin adds, often with jQuerySmall in-house scripts, only where a page needs them
TranslationSeparate translation pluginBuilt in, with its own URL per language
SearchDefault WordPress search or an extra serviceFull-text search with synonyms in PostgreSQL
ImagesUploads folder on the web serverCloudflare R2 with WebP at screen size
HostingPHP hosting per shopRailway, containers that scale along
Also on Neuramerce

Grill Bill has its own shop.

Grill Bill, one of the brands Nomad Fire sells, has its own shop at grillbill.eu, where new features go live first. Read the Grill Bill case.

FAQ

Frequently asked questions about this BBQ webshop

Nomad Fire Co. is a BBQ webshop selling kamados, planchas and tabletop grills in the Netherlands, Germany and the rest of Europe, including Grill Bill and Tiger Fire. The shop runs on nomadfire.shop.
The old shop ran on WordPress with WooCommerce, a translation plugin and separate tools for email, chat and analytics. On Neuramerce, shop, customer service, analytics and translations live in one platform, with one view of the customer.
Server-rendered HTML from Next.js 16 on Node.js 22, our own templates and blocks, a little vanilla JavaScript, Google model-viewer for 3D and AR and rrweb for session recordings. No React or other framework loads in the browser.
The new shop has been live since late September 2026. We will share revenue and search figures once there is enough data to really prove a difference.
Yes. We first map all your existing URLs, migrate products, content and languages, and redirect every old link. Request a demo to see how that works for your shop.

Your webshop on one platform too?

In 20 minutes we show you what the move looks like for your shop, including products, content and redirects.