Technical delivery · Employer work, name withheld

Wellness brand commerce replatform

A decade of commerce history, moved without losing it.

Title card for the commerce replatform: fifteen phases, one replatform, led as Web Developer
Employer
A holistic wellness brand, name withheld
Role
Web Developer
Method
Shopify's own migration guide
Status
Built, not launched

A holistic wellness brand needed to leave WooCommerce for Shopify without losing ten years of orders or a storefront its customers already recognized. I led the replatform as their Web Developer: the migration and its reconciliation, the storefront rebuild, a payment review under a restricted ingredient flag, third party fulfillment and the tracking layer a paid media program is waiting on. I quoted three weeks plus a protected fourth against an outside agency estimate of one to two months, and ran it alongside my other work.

Work by Will Mosley as Web Developer at a holistic wellness brand, during his employment. The employer's name is withheld here; the work is shown as an individual contribution as an employee.

The preparation that came before any data moved

01

Back up first. Rehearse second.

The method came from Shopify's own migration guide rather than improvisation. A scope audit of products, customers, orders, plugins, DNS and email came before any decision. A protected backup was verified in a second location, a staging clone kept production out of the test path, and a representative rehearsal import had to pass before anything ran at scale.

The inherited data fault, found and corrected

02

The fault the tooling called success.

A block of failed legacy orders had imported as payment pending and was being counted as real sales, overstating lifetime revenue. Most of it traced back to a single historical spam wave. The importer reported success either way. Reconciling against the source records found it, the deletion set was derived and removed, and the remaining orders then matched the old store exactly, order for order over a fixed period rather than by trusting an analytics card.

How the rebuild was reviewed

03

Parity, checked side by side.

Homepage, mega menu with live search, mobile drawer, footer, newsletter capture, live cart and every collection were rebuilt, along with about thirty secondary pages with their legacy redirects preserved so no inbound link breaks. Review runs against the old site at desktop and at 390 pixels wide, and B grade is rejected. A launch audit was allowed to return a clear no, which produced a defect list instead of a declaration of done.

The payment review and the fulfillment onboarding

04

The part that is not the website.

A payment provider flagged a restricted ingredient class. The catalog was audited image by image, including every regulatory panel, to establish that the restriction was ingredient specific rather than category wide, and the review was carried to approval for the rest of the catalog while the affected products were held with their history intact for a later appeal. Fulfillment onboarding used a deliberately one way integration, with every barcode reconciled and non shipping items classified so they could not create phantom pick tasks.

The reusable migration runbook

05

What the next one inherits.

The work produced a fifteen phase runbook with hard gates and stop rules: tax treatment, shipping rules, policy copy, a controlled test order, business sign off, the final order delta, redirects and DNS, and a rehearsed cutover and rollback. The brand's paid media plan was read rather than nodded at, and the reading was raised: its first four months sit below any plausible breakeven for a physical product, and no repeat purchase assumption is modelled anywhere in it.

Next project

Pure Water communication piece

One message across two sides.

View the project

03 project stories

More in technical delivery

Related projects, each with its own scope and credit.

View collection →

Next step

Start a conversation. No pitch, just fit.

If this is the kind of leadership your team needs, I would like to hear about the role.

Start a conversation Read the résumé →