**TL;DR.** Oslo Running Co., a Norwegian premium running gear brand, lost 92% of their Google rich-result eligibility when Google enforced 2026 Product schema requirements. Migrating from Shopify to Ordiko restored eligibility on 100% of PDPs within days. Five weeks later organic CTR was up 28% and monthly organic sessions up 43%.

## Background

Oslo Running Co. was founded in 2018 by Magnus Eriksen and Hilde Sørensen to outfit Norwegian distance runners for Nordic conditions — base layers, technical jackets, trail shoes, hydration packs. The brand grew to NOK 28M annual revenue by 2024 with strong DTC sales in Norway and a growing customer base in Sweden, Denmark, and Finland.

Their stack from 2018 to 2026:

- Shopify (standard plan, then Shopify plan as they grew).
- Shop Pay for checkout.
- Klaviyo for email.
- A third-party schema app for Product structured data.

A single Shopify storefront served Norwegian and Swedish customers via subdomain (sv.) and currency-switching app — not true multi-store but functional.

## The challenge

January 2026 brought the moment Magnus had been watching for: Google began enforcing the `hasMerchantReturnPolicy` requirement for Product rich-result eligibility. The third-party schema app on Shopify hadn't shipped the 2026 fields. Within 14 days:

- 92% of PDPs lost rich snippet eligibility.
- Star ratings, prices, and availability disappeared from SERP listings.
- CTR on top-converting keywords dropped from 2.1% to 1.5%.
- Sessions dropped 18% month-over-month before bottoming out.

Magnus opened a ticket with the schema-app vendor. Their roadmap had `hasMerchantReturnPolicy` scheduled for "Q3 2026." That meant ~6 months of degraded rich results.

In parallel, the team had been planning a true multi-store expansion — independent Swedish and Danish storefronts with localized merchandising. Shopify Plus pricing (~€2,000–€2,500/mo for two stores) made the math hard.

## Evaluation

The team evaluated:

1. **Switch schema apps on Shopify**. The next-best app had `hasMerchantReturnPolicy` but was clunky; estimated 3 weeks of work + ongoing maintenance.
2. **Shopify Plus**. Solved multi-store but at 10x current cost.
3. **Custom theme on Shopify with hand-written 2026 schema**. Estimated 4–6 weeks of dev work + ongoing maintenance per Shopify update.
4. **Migrate to Ordiko**. Native 2026 schema on every PDP, native multi-store, €49/mo Growth plan.

Magnus chose Ordiko. The migration started 11 days after the rich-result outage began.

## The migration

The migration was lean — Oslo Running Co. had clean Shopify data and a small engineering team.

**Week 1**: Shopify CSV export, asset download, Ordiko account setup, two-store provisioning (Norway + Sweden), catalog import.

**Week 2**: Theme work. The team used Ordiko's React Server Components default theme as a base and customized it to match the brand. Native multi-store let them point `oslo-running-co.example.com` and `oslo-running-co.example.com/sv/` at distinct stores with independent catalogs.

**Week 3**: SEO configuration. Store-level return policy (30 days free return by mail for NO/SE/DK, return shipping at customer cost for other EU). Shipping policies for 5 zones. AI crawler allow rules. Hreflang for NO + SV with proper per-entity gating.

**Week 4**: Parallel running, payment-gateway testing (Klarna, Vipps for Norway), final QA, DNS cutover.

## Results

**Rich-result recovery** (Google Search Console → Enhancements → Products):

- Day 0 (cutover): 100% of PDPs emit valid 2026 schema.
- Day 14: 65% of PDPs re-eligible per GSC.
- Day 35: 100% re-eligible.
- Day 42: GSC and Rich Results Test both confirm full coverage.

**SERP CTR** (Google Search Console):

| Period                              | Impressions    | Clicks       | CTR    |
| ----------------------------------- | -------------- | ------------ | ------ |
| 28 days before schema enforcement   | 920,000        | 19,300       | 2.10%  |
| 28 days during outage (pre-migration) | 880,000        | 13,200       | 1.50%  |
| 28 days post-migration (week 5–8)    | 940,000        | 22,560       | 2.40%  |

CTR not only recovered but exceeded pre-enforcement levels — 2026 schema includes individual `review[]` entries that pre-enforcement Shopify hadn't emitted.

**Performance** (CrUX p75, mobile):

| Metric | Before (Shopify) | After (Ordiko) | Delta |
| ------ | ---------------- | -------------- | ----- |
| LCP    | 2.1s             | 1.3s           | -38%  |
| INP    | 320ms            | 110ms          | -66%  |
| CLS    | 0.07             | 0.03           | -57%  |
| TTFB   | 320ms            | 90ms           | -72%  |

The INP improvement was the biggest single performance gain — Shopify's theme had several third-party app scripts that hydrated on first interaction and tanked INP. Ordiko's RSC-based theme shipped 70% less client JS.

**Organic growth** (90 days post-migration):

- Monthly organic sessions: 22,000 → 31,500 (+43%).
- Conversion rate (organic landing): 2.4% → 3.1% (better CWV + better CTR feed each other).
- Revenue from organic channel: +52% over the same window.

## What we learned

Magnus's three takeaways:

1. **Schema vendors are a single point of failure.** Owning your Product schema (or being on a platform that owns it natively) is more resilient than depending on an app that may or may not ship the next Google requirement on time.

2. **Multi-store native is worth the migration.** Running NO + SE on a single Shopify install with a currency-switching app worked for years but was always a workaround. A genuine multi-store dashboard simplified operations meaningfully.

3. **INP fixes more than rankings.** Mobile INP going from 320ms to 110ms didn't just help CWV — it visibly sped up the entire mobile shopping experience. Mobile conversion rose 6% beyond what we'd predicted from CTR alone.

## Quote

> "When Google started enforcing hasMerchantReturnPolicy in early 2026, we lost rich snippets on 92% of our products overnight. Our Shopify schema app didn't ship the 2026 fields. We evaluated upgrading to Shopify Plus (priced out at €2k+/mo for the multi-store we wanted anyway) versus migrating. Ordiko emitted complete 2026 Product schema on every PDP from day one — return policy, shipping details, individual reviews, the lot. CTR recovered within five weeks. We now run our Norway and Sweden storefronts on one Ordiko account."
>
> — **Magnus Eriksen**, Head of Digital, Oslo Running Co.

---

*Oslo Running Co. runs on Ordiko Growth at oslo-running-co.example.com (Norway and Sweden storefronts).*