Headless WordPress and Next.js site for a UK aggregates supplier
A custom WordPress child theme exposes ACF fields, menus and a Supplies post type through the REST API; a Next.js App Router front end renders it on Vercel. Contact form submissions are proxied through a route handler, so the browser never talks to WordPress directly.
The client asked not to be named, so this case study has no screenshot, no address and no link to the site.
- ClientUK aggregates supplier
- RegionUnited Kingdom
- StackHeadless WordPress · Next.js · REST API
How the project was done.
- Client
- UK aggregates supplier
- Market
- United Kingdom
- Role
- Headless architecture · WordPress child theme · Next.js front end
- Stack
- Headless WordPressNext.jsREST APIACFTypeScriptVercel
A UK aggregates supplier wanted a fast, modern front end without retraining the team that already updates the site in WordPress. The answer was to keep WordPress as the editor and move everything visitors see to Next.js.
We built a WordPress child theme that exposes ACF fields, menus and a Supplies post type through the REST API, and a Next.js App Router front end, written in TypeScript and deployed on Vercel, that renders it.
What made it complex, and how we solved it.
- 01
The challenge
The team already knew the WordPress admin, and a new CMS would have meant retraining and moving every piece of content.
How we solved it
WordPress stayed as the back end: supplies, menus and page fields are edited exactly where they were before, and the front end reads them through the REST API.
- 02
The challenge
The supplies and the page content had to reach a separate Next.js app in a predictable shape.
How we solved it
A child theme that exposes ACF fields, menus and a dedicated Supplies post type through the REST API, typed on the Next.js side in TypeScript.
- 03
The challenge
A headless contact form usually means the browser posting straight to WordPress, which exposes the back end.
How we solved it
Submissions go through a Next.js route handler that passes them on, so the browser never calls WordPress directly.
How the project was completed.
The Next.js front end runs on Vercel, and the WordPress admin the client already knows is still where the content is edited.
What shipped
- 01WordPress child theme that exposes ACF fields, menus and a Supplies post type through the REST API
- 02Next.js App Router front end deployed on Vercel
- 03Contact form submissions proxied through a Next.js route handler, so the browser never calls WordPress
- 04Content editing stays in the WordPress admin the client already knows
No traffic, revenue or ranking figures are published here. We only publish numbers we can show you — a Lighthouse run, a Search Console export, an error rate — and for this project we do not hold them.
Send the brief — get a fixed price within two business days.
Send the brief and get a written scope with a fixed price within two business days. Client names can wait until the NDA is signed.




