Sugar Babies, Part Three: A Storefront Facelift With No Replatform

The Setup

Sugar Babies is a baby boutique with a physical store in Washington and a national DTC catalog built on premium third-party brands: Nuna, UPPAbaby, Cybex, Maxi-Cosi, Stokke, Silver Cross. By the time the storefront work started, the Google Ads account had already been rebuilt once (part one) and scaled into a six-campaign Performance Max matrix (part two).

That created a specific problem. The paid program had outgrown the storefront. The catalog carried $1,000 strollers and heirloom-grade nursery furniture, and the site presenting them looked like what it was: a stock Shopify theme with default settings. Premium brands, default frame.

The Decision: Facelift, Not Rebuild

The standard answer to “the site looks dated” is a redesign project. A new theme or a headless build, a quarter of work, a five-figure invoice, and a migration that puts your checkout, your tracking, and your SEO equity all at risk in the same month.

I took the other route: keep the stock theme and upgrade it in place. Custom CSS and JavaScript injected through the theme layer, every change staged and reviewed on a theme copy before it touched the live store, the production site untouched until go-live day.

The reasoning is not aesthetic, it is operational. The Performance Max matrix runs on these landing pages. Server-side tracking runs through this checkout. A replatform would have reset signal the ad account had spent months building. A facelift upgrades the frame without touching the foundation.

The test I run before recommending either path is a short one. Is the theme incapable of the structure the catalog needs, or is it capable and badly used? A stock theme that cannot express shop-by-room architecture for a 150-SKU furniture catalog is a rebuild. A stock theme rendering generic product cards, an unreadable hero, and reviews locked inside an app dashboard is a configuration problem wearing a redesign costume. Sugar Babies was the second case on every count. The long version of that decision, with the four signals I check, is at facelift or full rebuild, and the $30,000 quote that made me write it up is in the blog post.

The staging discipline is the part people skip. Every change went onto an unpublished duplicate theme, reviewed there, then published in one move. That matters more on this store than most, because the checkout carries a server-side tracking spine feeding Google Ads and Meta. A theme edit made directly on the live store is an edit made underneath a live ad account with no rollback.

Where the Storefront Landed

The store at shopsugarbabies.com now opens on a brand-led hero, moves through the ten premium partner brands up front, and merchandises the six core categories the buying decisions happen in: travel systems, car seats, nursery furniture, high chairs, gliders, diaper bags.

Product cards carry variant swatches so a buyer can move through colorways without leaving the collection page. On a catalog where the same travel system sells in six fabrics, a colorway change that costs a page load costs conversions, and the swatch is the cheapest fix for it.

The 195-plus customer reviews that used to live only in an app dashboard now run as social proof on the storefront itself, next to the products they were written about. Those reviews were already bought and already written. They were sitting behind a login, doing nothing for the buyer deciding between a $1,000 stroller here and the same stroller at a national retailer. Surfacing existing proof is the highest-return work on most storefronts I audit, because the asset already exists and the only cost is the plumbing.

The catalog SEO layer shipped in parallel: collection copy, internal linking, and twelve thousand image alt texts, documented in part two.

None of it required a platform decision. All of it shipped while the store kept selling.

What I Am Not Claiming Here

There is no conversion-rate lift in the numbers at the top of this page, and that is deliberate. The storefront work landed in the same period as a six-campaign Performance Max matrix and a catalog SEO program. Attributing a storefront conversion delta to the storefront under those conditions would be a guess dressed as a measurement, and I would rather publish the scope than invent the outcome.

What is verifiable is the scope and the risk profile: no replatform, no theme rebuild, no migration window, no interruption to the ad program running on these landing pages. Those were the terms of the decision, and they held.

The measured tracking work on this store is written up separately and does carry numbers, because it could be isolated. Part four is the missing subscription that had the store recording two add-to-carts in ten days, and the same-day fix that brought ad-attributed add-to-carts to 509 a month.

Why This Is the Playbook

Most Shopify stores doing $1M to $20M do not need a replatform. They need the storefront brought up to the caliber of their catalog, without interrupting the machine that is already running. That is a different discipline than web design: it is knowing which upgrades move conversion, which ones risk the ad account, and how to ship on a live store without breaking it.

Same operator on the storefront as on the campaign matrix as on the tracking stack. That is the point. The person changing the product cards knows exactly which landing pages the ad spend depends on.

The call this project started from is answered at facelift or full rebuild, and the one founders ask next at redesigning without losing sales.

If your storefront is the thing lagging behind your catalog, the storefront work runs exactly like this.