Katrine Marso

Katrine Marso sells a natural, Canadian skincare line built around personalized care. The store already had a quiz that sorts customers into profiles, with quiz links and customer metafields in place. What it lacked was a landing page for each profile's bundle.

The brief covered a bundle page that could repeat across 22 profiles. Each page needed its own content and button link, managed without code. The team also wanted to send traffic to Profile #1 first and A/B test it on their side before deciding whether to build the other 21.

There was no page that showed one profile and its bundle. Quiz takers and email readers had nowhere focused to land, so the bundle offer had no clear home.

Twenty-two profiles meant 22 pages. Building each one by hand would be slow to make and harder to keep consistent when content changed.

The store already relied on working URLs, customer metafields and quiz links. The team asked directly whether publishing a new theme would change any of them. A broken quiz link would cut customers off from their results.

The team wanted proof before scaling. They did not want a second version or 21 more pages yet. They wanted Bundle 1 live so they could test it.

These pages are not in the main navigation. Without links in customer emails, based on what each person bought before, customers would never find them.

• 01 A staging theme copied from live We did the work on a duplicate of the live theme, named "Staging | Bundle Changes". Because it matched the current live version, everything the customer already saw stayed the same. The team could preview the new bundle page through a theme preview link before anything went live. The earlier live theme, "Staging | Quiz Updation | Old Live", stayed in the theme library as a fallback.
• 02 One bundle template for every profile We created a page template called "bundle". To add a profile page, the team creates a new page and assigns it the bundle template. The layout, sections and styling come with it. That keeps all 22 profile pages consistent, and a layout change made once applies to every page that uses the template.
• 03 Page metafields for content and links We set up metafields for the bundle pages so each one holds its own content. Each metafield for the bundle sections has settings for links and copy, so the team can customize a page without touching code. For the main button, the team uses the link from the document we shared earlier, so each profile points to the right offer.
• 04 Bundle 1 and Bundle 2 set up We built the first page at /pages/bundle-1 for Profile #1, with the brand's copy about combining nature and science in a vegan, eco-friendly Canadian line. We also updated the links for Bundle 2. When the team said they only needed one profile and one bundle on the page for now, we kept the scope to Bundle 1.
• 05 Publishing without breaking existing links Before going live, the team asked whether their URLs, customer metafields and quiz links would stay the same. We confirmed that publishing would not affect other links or pages, since the theme duplicated the live one. Then we made "Staging | Bundle Changes" the live theme, and /pages/bundle-1 went live for the team to send traffic to.
• 06 Handover for emails and the next 21 After launch, we explained the next steps. Add the bundle-1 link to emails or the site, and match links to customers' past purchases, since the pages are not reachable otherwise. When the A/B test supports it, the team can create the remaining 21 pages from the bundle template and fill in their metafields.