Walk through GD Hub, KWG Group's distribution and storage centre in Poland, and you understand the business instantly: shelving at scale, showrooms, loading docks, product verticals from building materials to new energy — a genuine European trading centre connecting manufacturers to retail across Europe, the Middle East, and Asia.
Then, until recently, you'd visit their website: a WordPress template on a staging subdomain. A rotating hero, one paragraph, a logo strip, a contact form. No catalogue. No way for the team to change a phone number without a developer. Language support via a browser-translate plugin — machine-mangled copy in the two markets that matter most, Poland and China.
A warehouse business with a brochure for a front door. The mandate was simple to say and specific to build: give KWG a digital GD Hub — shelves, showroom, loading dock, and signage in the languages their buyers actually read — that their own team runs.
The Build: Shelves, Showroom, Loading Dock, Signage
The showroom — a full corporate site. Forty-four routed pages on a single KWG-branded design system: five dedicated service pages (supply chain, storage, logistics, distribution, consultation), eleven product-vertical pages, locations, partners, sustainability, careers, news, shipment tracking, and the legal set — replacing roughly eight template pages that couldn't hold the group's story.
The shelves — a real catalogue. Category browsing, category detail, and product detail pages backed by a properly modeled data layer: products, categories, variants, specifications, and multi-image galleries as separate related tables. When the catalogue is modeled instead of bolted on, then it grows without re-platforming — the schema was built for the full SKU set before the first SKU loaded.
The loading dock — a self-service admin portal. A role-gated back office where KWG's team manages all six content types — products, categories, news, careers, contact messages, and site settings — with image upload, sanitised rich-text editing, and a maintenance-mode switch as the safety net. Content changes moved from developer ticket to same-day self-service, which was the entire point: the scope explicitly ended at handover of an editable platform, never a static deliverable.
The signage — authored trilingual content. English, Polish, and Simplified Chinese as authored languages, not plugin output: 461 public strings and 94 admin strings per language, plus per-record translation tables in the database so catalogue content is translated as data rather than machine-guessed at render time. The admin portal shows a translation-status indicator per record — when a Polish description is missing, then the team sees the gap and fills it, instead of shipping a half-localised page to the market that matters.
The locks. The security spine, as always: 41 row-level security policies across 13 tables, admin identity in a dedicated table verified by security-definer functions (never on the user record), an activity log, privileged operations through edge functions only, DOMPurify-sanitised rich text, and Zod validation on every input. A back office the client operates daily has to be built like the client will operate it daily.
The Results
- From ~8 template pages to 44 routed pages, five service pages and eleven product verticals that simply didn't exist before
- From zero SKUs online to a database-driven catalogue with variants, specifications, and galleries
- From developer-ticket content to same-day self-service across six content types, with role-separated admin access and a maintenance-mode safety net
- From plugin auto-translate to three authored languages — including the Polish and Chinese markets KWG actually sells into — with per-record coverage visibility
- All of it verified from the delivered codebase: 37 migrations, 24 database functions, 90 components, 73 produced brand and product assets
"[Quote pending KWG Group sign-off — suggested angle: publishing products and news themselves, in three languages, the same day.]" — [Name, Title], KWG Group
Why It Worked: The Right Step Was Handing Over the Keys
The Rocket Now principle, in warehouse terms: a single step in the right direction is worth exponentially more than many steps in the wrong one. The wrong steps were another template, another agency retainer, another translate plugin — a prettier brochure. The one right step was building the platform as something KWG operates: catalogue modeled for growth, translation as first-class data with visible gaps, admin access that can't be escalated, and a handover that ends with the client publishing unaided. When the client owns the day-to-day, then the platform compounds with the business instead of decaying behind it.
Mid-market industrial or wholesale business stuck on a template? This pattern — corporate site, real catalogue, role-gated portal, authored languages — is built to repeat. → RocketNow.com
Editor's note — before publishing:
- Confirm client approval to publish and the canonical URL/domain to cite (kwg.rockematic.com vs. a kingwood.net successor); replace the placeholder quote
- Business metrics (traffic, enquiries, hours saved) are [TBD — client] in the source docs — the piece deliberately claims only codebase-verified figures
- Commercial terms intentionally omitted per the deal-registration doc
- The upsell pipeline (checkout, ERP/WMS sync, live carrier tracking, partner portal, WCAG audit) is documented as out-of-scope — useful for the follow-up conversation, not for this piece