Glow25 – Scaling WooCommerce to 5,000+ Orders per Day

Glow25 grew from a niche label to a DACH-wide beauty and supplement player within a few years. As revenue scaled, so did the complexity of the tech stack — and that is exactly the point where a shop tips into the next league: plugin monoliths running out of road, a database that no longer finishes its nightly maintenance, peaks that turn a marketing push into a traffic spike within minutes.

The brief as Head of Tech was correspondingly multi-dimensional — tech, team and business at the same time:

• Keep a WooCommerce shop doing 5,000+ orders per day stable — with a database that had grown to 350 GB and was blowing through its nightly maintenance windows
• Lead a 16-person tech team, develop it, and align it cross-functionally with Digital Product, Marketing, Finance and Acquisition — including recruiting in a tight market
• Answer the platform question: keep scaling WooCommerce or replatform to Shopify — for glow25.de, glow25.fr and glow25.nl, with every implication for checkout, payment, tax and country logic
• Integrate operational systems like Zendesk (customer service) and Reybex (ERP) cleanly — without breaking daily operations in support or logistics
• Enforce security and data-protection requirements (GDPR, PSD2, PCI) across a legacy architecture where not every decision had been made from the current seat
• Own budget, resource and risk planning — from hosting and licence costs through agency budgets to continuity plans for peak campaigns and Black-Friday weekends

All of it under one hard constraint: the shop had to keep selling in the meantime. Every change had to be live-safe, every rollout reversible, every peak covered.

The core of the work was a server switch from single-server to a multi-server setup: a dedicated database, a dedicated caching layer, and eight application nodes behind a load balancer. What used to be a shop on the edge during peak days became an infrastructure that handles 5,000+ orders per day without breaking a sweat — including Black-Friday weekends and marketing-push spikes that previously needed manual intervention.

In parallel, the database was reduced from 350 GB to 60 GB — through an automated archiving system that offloads legacy data in a structured way, plus an automated maintenance regime (index optimisation, cleanup jobs, backup and monitoring pipelines). What used to require hands-on night-shift attention now runs quietly in the background. Nightly maintenance windows hold again, backups are tested for recoverability, monitoring alerts before an incident reaches the shop.

Also in parallel ran the preparation for migrating WooCommerce to Shopify across three country shops (DE, FR, NL): data models, product and customer migration, checkout logic, payment and tax configuration, apps instead of a plugin monolith. Plus a clean platform comparison with hard criteria — total cost of ownership, operational load on the team, time-to-market for new countries. The groundwork that led to the actual replatforming later.

Technical strategy, team building and delivery ran from one seat: recruiting and developing the tech organisation, budget and resource planning, Zendesk and Reybex ERP integrations, QA processes, risk and continuity planning. Plus cross-functional alignment with Digital Product, Marketing, Finance and Acquisition — exactly the interfaces where e-commerce projects usually get stuck.

And when organisational pull was needed, the Product Owner role for the Digital Product team was temporarily taken on as well: backlog, prioritisation, stakeholder management — so tech didn't just deliver, but got a clean sense of what to deliver in the first place.