Effectdev Technology LLC v2026.5
online [email protected] $ schedule_call ↗
~ / work / lumen-apparel
b4a2f17 · 2026-03-18 · service: e-commerce · ● shipped

Lumen Apparel replatformed to Shopify Plus in nine weeks.

A US-based medical-apparel retailer running on a decade-old Magento 1 stack that nobody wanted to touch. We rebuilt it on Shopify Plus, restructured the swatch architecture with metaobjects, and migrated 80k customer accounts the week Shopify deprecated the legacy login.
01
+47%
CVR vs. legacy site
02
1.4s
p75 LCP mobile
03
$1.8M
GMV first 90 days
04
9 wks
discovery to live
// §01

The brief.

The client came to us through their long-time creative partner. The site was Magento 1, end-of-life since 2020, patched into Frankenstein territory by three previous agencies. Every product had between 8 and 40 color and material variants, hand-coded into the theme as static swatches. Adding a new SKU took a developer half a day.

They needed three things: a platform that wouldn't die on them again, a swatch system that merchandisers could actually use, and a customer account migration that didn't break the loyalty data their repeat buyers depended on. Shopify's new customer account deprecation was the wrench in the timeline.

$ cat ./constraints.txt
· Swatch system must support 40-variant products without developer involvement
· Mobile p75 LCP of 3.8s → under 1.8s
· Migrate 80k customer accounts before legacy auth deprecation
· Zero loss of repeat-purchase history or loyalty balances
· Creative partner owns design; we own architecture, no overlap
// §02

The approach.

Four phases. Nine weeks. Two senior devs, one BA running client comms, design handled in parallel by the creative partner.
01

Audit

Two weeks of requirements gap analysis. We mapped every Magento extension, every theme override, every loyalty integration. Output: a 52-page functional tech spec and a swatch architecture decision document.
02

Architect

Shopify Plus with swatch logic built on metaobjects, not metafields. One metaobject per color family, referenced across product variants. Merchandisers add a new colorway in under two minutes.
03

Build

Six-week sprint. Two devs full-time, design handled in parallel, weekly client demos. Customer account migration scripted against the new Shopify account API, dry-run twice before go-live.
04

Cutover

Saturday 10pm ET. DNS swap, Shopify Plus checkout live, legacy Magento archived read-only. Account migration ran overnight. Live by Sunday noon. Zero loyalty data loss.
// §03

The stack.

L1/5
Storefront
Shopify Plus Dawn (forked) Liquid Tailwind utilities
L2/5
Backend
Shopify Admin API Customer Account API
L3/5
CMS
Shopify Metaobjects (swatches) Shopify Files
L4/5
Payments + Subs
Shopify Payments Shop Pay Klaviyo
L5/5
Ops
GitHub Actions CI Cloudflare DNS Sentry PagerDuty (first 60d)
// §04

The numbers.

Measured over the first 90 days post-launch vs. the trailing 90 days on the legacy Magento site, like-for-like organic + direct traffic.
CVR MOBILE
+52%
from 1.4% → 2.1%
CVR DESKTOP
+41%
from 2.2% → 3.1%
LCP P75 (MOBILE)
-63%
3.8s → 1.4s
TIME-TO-ADD-VARIANT
-94%
4h dev work → 2 min in Shopify
AOV
+8%
bundle PDP redesign
LOYALTY RETENTION
100%
80k accounts, zero loss

Effectdev shipped a swatch system our merch team actually uses. We added 60 new SKUs in the first month without a single developer ticket.

— HEAD OF MERCHANDISING, VIA AGENCY OF RECORD
// related/

More e-commerce commits.

Or see the full ship log →
E-COMMERCE
Solace Beverage
32%
read case study →
E-COMMERCE
Ironvane Supply
$180k
read case study →
E-COMMERCE
Meridian Industrial
+212%
read case study →

Got a Lumen-shaped problem?

Most replatforms like this are scoped in 5-10 days and shipped in 8-12 weeks. Let's see if yours fits.
$ schedule_call --re lumen-apparel