Storyblok content alongside your commerce backend

What Storyblok owns

Storyblok is the content layer of a headless commerce delivery. The editorial surfaces all live there:

• Marketing landing pages
• Blog posts
• Glossary entries
• Footer content
• Navigation copy
• Hero variants
• Translations

Editors get a visual editor with a structured component model that maps to the storefront component library.

The value of a dedicated headless CMS shows up most in three places: editor workflow (marketing composes pages without developer help), multi-market publishing (one story, many locales), and component reuse (the same block library across every page type). Storyblok covers all three.

What the commerce backend owns

Product data, pricing rules, inventory, and orders stay in Norce or Shopware. Frntkey reads from both systems and renders one storefront. Editors never edit commerce data in Storyblok and developers never edit catalog data in code.

The boundary is deliberate. Commerce data has strict consistency requirements. Price and inventory need to be right on every render, everywhere. Content data has strict editorial requirements. A marketing team needs to draft, review, translate, and publish without waiting on a code release. Splitting the two systems along that boundary is what makes both work at their best.

How translations work

Storyblok exposes field-level i18n on every blok. The Frntkey site reads the language-suffixed field per locale, so the EN page and the SV page are the same story rendered with different field values. Editors translate inline without managing parallel page trees.

For merchants running multi-market operations across the Nordics, this pattern removes the biggest pain of Nordic content management: the same product page copy no longer needs to be maintained in four separate CMS installations. One story, four field variants, four rendered pages. Storyblok's built-in AI translation makes the initial draft; the editorial team refines per market.

What Storyblok pairs with in a Frntkey stack

Storyblok is one part of the Frntkey stack. The full picture:

• Storyblok. This page. Editorial content, landing pages, translations, campaign blocks.
• Norce or Shopware. Commerce backend. Product, pricing, cart, checkout, orders.
• Junipeer. iPaaS for ERP and back-office. Fortnox, Business Central, Visma.
• Payment providers. Klarna, Walley, Vipps, Svea. Connected through the commerce backend's checkout.
• CRM and reviews. Voyado, Lipscore. Connected via GTM event hooks and API webhooks.
• Search. Hello Retail or Meilisearch. Connected through the storefront's search layer.

Storyblok sits at the top of the content flow. Each of the other integrations owns a specific slice of the data. Frntkey renders the result as one coherent storefront.