A Shopify store that doesn't look like Shopify

The brief

Root4 sells science-led skincare, and its customers rely heavily on information before purchasing. They read.

Ingredients, mechanisms, clinical detail, application guidance and which product suits which concern all play a role in the decision. That means the product page has to do far more than simply show a product, price and add-to-cart button.

On WordPress and WooCommerce, each product had been built as its own landing page. Fifteen to twenty sections of technical content, imagery, video and education were assembled individually. Bundle pages introduced another layer of complexity, with similarly detailed content requirements.

Why a standard migration approach wouldn't work

Shopify is built around reusable templates and sections, which is a much more manageable system than hand-building every page.

The challenge was that Root4's product pages could contain close to 20 custom sections, often in different combinations, with product-specific content throughout.

One option would have been to create a bespoke template for every product. That would have reproduced inside Shopify the same maintenance challenge the migration was meant to solve.

Instead, we needed the pages to feel bespoke while keeping the system underneath them reusable.

What we built

Product-specific content was moved into Shopify metafields and connected dynamically to reusable sections across a single product template.

Each product could retain its own clinical detail, ingredients, imagery, video and application guidance, while the structure underneath remained shared and manageable.

The fulfilment problem

The previous WooCommerce checkout included suburb and postcode validation so customers could correct their address before placing an order if something didn't match.

That exact experience didn't need to be recreated inside Shopify checkout.

Instead, Bob Go handles the validation behind the scenes by cross-referencing delivery details such as the suburb, address and postcode. This allowed the operational checks to remain in place without adding another validation step to the Shopify checkout experience.

Fastway could remain part of the courier setup, while the customer-facing checkout stayed clean and straightforward.

What happened next

The original migration brief was deliberately focused on preservation: move platforms, change as little as necessary and protect the content and customer experience Root4 had already built.

Since launch, that brief has naturally evolved.

We've gradually started introducing more Shopify commerce patterns into the store, including clearer layouts, conversion-focused design and an easier path through the product range, without stripping away the depth that made the original site work.

Moving to Shopify doesn't have to mean flattening a brand into a standard theme.

With the right content architecture, it can mean the opposite: the depth survives, while the system underneath becomes easier to manage, extend and improve.