WooCommerce Case Study: grüum, From Zero to 80,000+ Orders a Month
WooCommerce case study: grüum is a UK skincare, haircare and shaving brand. Rowerr built its WooCommerce store in December 2015, before the brand launched in 2016, redesigned it in 2021 and added AI-ready workflows in January 2026. Monthly orders grew from zero to more than 80,000. In September 2026 we fixed custom order statuses that were being cut short in the database.
- CLIENT & MARKETS
- grüum · UK and Europe (GBP, EUR)
- PLATFORM
- WordPress · WooCommerce · Elementor · custom HTML pages
- PROJECT HISTORY
- Dec 2015 build · 2021 redesign · Jan 2026 · Sep 2026
- ROWERR'S ROLE
- Store build, redesign, subscriptions and bundles, AI workflows, ongoing development
Results at a glance
| Business task | Launch a new personal-care brand online and scale one-off orders, subscriptions and bundles. |
|---|---|
| Before | No store. Rowerr built it in December 2015, before the brand launched. |
| Constraints | Subscriptions, configurable bundles with stock, gift cards, GBP and EUR, very high order volume. |
| What we changed | Built the store, redesigned it in 2021, added AI-ready workflows in 2026, and fixed truncated custom order statuses. |
| How we checked | For the status fix: saved and reloaded test orders in a fresh request, queried by status, and checked no payments, stock or emails were triggered. |
| Measured result | Monthly orders grew from zero to more than 80,000. |
| Status | Solved. Still working together. Revenue figures are kept private at the client's request. |
Figures reported by the client and Rowerr's project records, November 2026.
Book a free consultation →Project Overview
grüum is a UK personal-care brand making skincare, haircare, bodycare and shaving products, formulated and made in-house in Stockport. It has 10 core ranges with more than 150 products, and sells to the UK and Europe in GBP and EUR.
Rowerr built the WooCommerce store in December 2015, before the brand launched in 2016. We redesigned it in 2021, made it AI-ready with new workflows in January 2026, and are still working with the team today.
Business Challenges
- Launching from zero: a new brand needed a store ready on day one.
- Subscriptions and bundles: recurring billing and build-your-own bundles that track stock.
- Scale: growing from a handful of orders to tens of thousands a month.
- Two currencies: UK and European customers.
- Status bug: long custom order statuses were cut short when saved, so orders vanished from status filters.
How Customers Buy & The Stack
| Route | How it works |
|---|---|
| Single products | Skincare, haircare, bodycare and shaving products in GBP or EUR. |
| Subscriptions | Regular deliveries billed automatically. |
| Bundles and gifts | Configurable bundles that respect stock, plus gift cards. |
| Need | Tool |
|---|---|
| Pages | Elementor and custom HTML pages |
| Store | WooCommerce |
| Product filters | WooCommerce AJAX filters |
| Recurring orders | WooCommerce Subscriptions |
| Bundles | WooCommerce product bundles |
| Gift cards | WooCommerce gift cards |
| Order updates | WooCommerce custom notifications |
Building the Store Before Launch
The goal: a store ready for launch day.
We built grüum’s WooCommerce store in December 2015 so the brand could launch online in 2016, with single products, subscriptions, bundles and gift cards.
Running subscriptions and bundles at scale?
We build and look after high-volume WooCommerce stores with subscriptions, bundles and custom order flows.
Discuss Your WooCommerce Project Explore WooCommerce ServicesGrowing From Zero to 80,000+ Orders a Month
| Stage | Orders a month |
|---|---|
| Launch | 0 → 20+ |
| Stage 2 | 20 → 700+ |
| Stage 3 | 700 → 5,000+ |
| Stage 4 | 5,000 → 30,000+ |
| Stage 5 | 30,000 → 50,000+ |
| Today | 80,000+ |
We redesigned the store in 2021 and added AI-ready workflows in January 2026 to keep up with this volume.
Fixing Custom Order Statuses That Were Cut Short
The problem: orders disappeared from status filters.
A long custom order status looked like it saved, but when the order was loaded again the status was cut short. Searches and order-list filters for the full status then missed those orders.
What caused it
WooCommerce stores order statuses in a field limited to 20 characters, including the “wc-” prefix, so a custom status key can be at most 17 characters. The store accepted a longer key and the database quietly cut it, while the save still reported success.
How we fixed it
- Listed every custom status key and its label, and switched to short internal keys (for example awaiting-pickup) while keeping the full label customers see.
- Listed every integration using the old keys: order filters, automations, ERP exports, email triggers and paid-status rules, with one old-to-new mapping.
- On staging, registered the new keys and tested a status change on a test order, reloading it in a fresh request.
- Found affected orders by ID, order notes and a read-only review of stored values, without guessing the status from the cut-off text.
- Set the correct short status on each verified order through WooCommerce, after testing stock, email and payment effects.
- Reconciled the repaired orders with fulfilment and integrations, and kept a dated repair log. We did not change WooCommerce core database columns.
How we verified it
- The short key survived saving, a fresh reload and a status query.
- Orders showed in the right status view and the normal order list.
- No payments reopened, no stock restored, no duplicate emails or ERP shipments.
- The status form now rejects keys longer than 17 characters with a clear message.
Status: solved.
Results
| Year | Milestone | Outcome |
|---|---|---|
| Dec 2015 | Store built by Rowerr | Ready for the 2016 brand launch |
| 2021 | Full redesign | Store rebuilt for a growing range |
| Jan 2026 | AI-ready workflows | Less manual work at high volume |
| Sep 2026 | Custom status fix | Short keys, orders repaired; solved |
| Today | 80,000+ orders a month | |
WooCommerce Custom Order Status FAQ
01Why is my WooCommerce custom order status not saving correctly?
WooCommerce limits order statuses to 20 characters including “wc-”, so a custom key can be at most 17 characters. Longer keys get cut short in the database.
02How do I rename a custom status without breaking integrations?
Keep the long label for customers, use a short internal key, and map the old key to the new one in every filter, automation and export first.
03Can I just make the database column bigger?
No. Changing WooCommerce core columns causes problems with updates. Use short keys instead.
04How do you repair orders with a cut-off status?
Identify each affected order by ID and notes, then set the correct status through WooCommerce after testing stock, email and payment effects.
05Can a WooCommerce store handle 80,000 orders a month?
Yes. grüum runs subscriptions, bundles and gift cards on WooCommerce at more than 80,000 orders a month.
Key Takeaway
A store that grows from zero to 80,000 orders a month needs the same partner to keep improving it. And small limits matter at scale: a custom status one character too long can hide thousands of orders from your team.
Running subscriptions and bundles at scale?
We build and look after high-volume WooCommerce stores with subscriptions, bundles and custom order flows.
Discuss Your WooCommerce Project Explore WooCommerce Services