Case Study: One of the World’s Biggest Sanity CMS Builds

Managing content across a multi-region, multi-language eCommerce platform requires structure. It’s the only way to scale. See how we created a reliable system to manage our client’s global content without slowing down regional teams or creating new dependencies.

About

OM System is a digital imaging and audio brand operated by OM Digital Solutions Corporation. Their global Adobe Commerce platform powers eCommerce for a wide range of high-end cameras, lenses, and accessories. With 70 store views and customers in over 20 languages, content consistency and control were becoming more complicated to manage.

Project goals

• Integrate a headless CMS to manage content delivery across 20 languages
• Replace scattered content logic with structured, reusable blocks
• Support a parallel frontend migration to the Hyvä theme
• Enable API-driven dynamic rendering inside Magento (Adobe Commerce)
• Improve content publishing workflows
• Set up an editor-friendly CMS studio for regional teams.

Approach

OM System’s platform is anything but simple. With three Adobe Commerce installations, 35 live store views, and another 35 in staging, plus content in 20 languages, their content architecture needed a clear structure. 

We chose Sanity CMS because of its headless, API-first approach, built to handle exactly this kind of multilingual, multi-site complexity. Unlike traditional CMS platforms, Sanity gave us the flexibility to define and scale content independently from the frontend.

The first step was defining and structuring all content blocks. We began by working closely with the client to map all design-approved content blocks before implementation across regions, categories, and page types. Some of them were simple, like banners or callouts, while others involved more complex logic and variations based on language, device, or campaign. In total, we built over 55 modular blocks, replacing at least four different methods the OM System’s content team previously used to create tiles in Magento Page Builder.

Dynamic rendering logic

On the backend, we developed custom logic in Magento (Adobe Commerce) to dynamically fetch and render Sanity content, block by block, across all 70 store views. A single structured content source could now power every site variant, whether for the UK, Japan, or the US, while respecting region-specific language and layout differences. This setup also supports flexible scheduling and localization, with editors able to control which content appears where and when, without touching the codebase or involving developers.

Sanity Studio

We configured the Sanity Studio interface to mirror real editorial workflows. This has reduced content publishing time from hours to minutes, while improving consistency across markets. Instead of a cluttered CMS with unnecessary fields and scattered logic, editors now have a clear, clean interface. They can:

• Update content across 20 languages in one session
• Reuse structured blocks across campaigns and countries
• Preview changes in context
• Push updates live without waiting on dev cycles

Collaboration and documentation

This project ran in parallel with a Hyvä frontend migration, while other teams worked on support, SEO, and analytics, with regular internal syncs.

For SEO, we added custom fields in Sanity for meta titles, descriptions, hreflang, canonical tags, and OG tags. These are fully manageable by editors and backed by automatic fallback logic to Mirasvit SEO rules when no custom value is set. 

After go-live, we held several workshops and supported OM System’s internal teams with how-to documentation and user guides, giving them confidence in the system from day one.

Also read:
Cervera’s Successful Digital Turnaround with Sanity CMS

Results

With 70 store views connected to a single CMS instance, this project stands among the largest Sanity implementations built to date. The system now supports 20 languages, 55+ reusable content blocks, and fully API-driven content rendering across Magento storefronts. Editorial workflows are significantly faster through an intuitive Sanity Studio setup. 

Key outcomes

• 70 store views managed under one CMS (35 production + 35 staging)
• 20 languages supported
• 55+ reusable content blocks implemented
• Content updates that previously took hours now take minutes
• Previously fragmented Magento content creation logic unified under a single CMS
• Delivered in 5 months from design sign-off to go-live.

Need to come up with an efficient way to manage and scale your content? Get in touch with us today to plan your CMS transformation.

Share on: