Industry challenge: premium content plus dozens of systems
A luxury watch brand sells not an SKU, but a story: movement caliber, case materials, a limited edition, and the service history of each piece. The storefront must present this content richly and without visual compromise, while behind the scenes it must connect CRM, boutique retail, tax and fraud prevention, search, and payment providers across dozens of countries. A classic monolithic CMS platform runs into two walls at once: a rigid storefront slowed down by the theme template, and integration complexity, where each new system requires core changes.
Saleor is an open-source (BSD-3-Clause) headless platform built around a GraphQL API. This is not about KT.Team, but an overview of what can generally be achieved with this tool in the watch and luxury segments. Below is a factual breakdown based on public sources.
What Saleor delivers for product content
The key argument for luxury is a flexible product model. In Saleor, a product is described through product types, attributes, and metadata: you can dynamically define attributes like "case diameter", "caliber", "power reserve", "bezel material", and "limited edition number" without changing code. This is built-in PIM, not an add-on (saleor.io).
Rich content is covered in two ways. Inside Saleor, structured attributes and rich-text descriptions are available; in parallel, a headless CMS is connected for editorial storytelling - official integrations exist with Storyblok, Contentful and Strapi (Contentful Marketplace, Strapi). The storefront can be anything: React, Next.js, Svelte - the frontend is not tied to the platform.
Multichannel support is built in: per-channel management of prices, currencies, warehouses, and assortment. For a brand with boutiques in dozens of countries, that means different price lists and availability by channel from a single data model.
How 20+ systems are handled: composition, not a fork
Saleor extensibility rests on four mechanisms: 160+ webhooks with filtering through subscription queries, Apps with dashboard iframe extensions (45+ UI mount points), metadata for arbitrary data and GraphQL subscriptions (saleor.io, github.com/saleor/saleor). External systems plug in alongside the core as services, while the core stays unchanged. This lowers upgrade costs and ensures transferability: the stack can be handed over to another team without rewriting.
Public example: Breitling
The most illustrative public case in the watch segment is Swiss Breitling, which moved to Saleor (a big bang migration from monolith to composable). Scale: 280+ boutiques in 120+ countries (Mirumee case study).
The integration set described in the public case clearly shows “20+ systems” at work:
- Contentful — headless CMS for content;
- Algolia — catalog search;
- Adyen — payments;
- Riskified — AI fraud prevention;
- Avalara — tax calculation and compliance;
- SendGrid — transactional email;
- Akamai — CDN;
- Vercel — storefront deployment and hosting (React/Next.js);
- its own back office: order management, PoS functions, and CRM.
Breitling's CTO puts it this way: “We built and customized more than 15 services for our needs, enabling online-to-offline and offline-to-online” (Mirumee). The internal order management tool was turned into a full application that connects the online storefront with boutiques: preorders, custom accessories, and complex delivery rules in a global checkout.
In public materials, Saleor places Breitling alongside LUSH (global retail and digital replatforming) and UNICEF as examples of high-load custom storefronts with advanced content modeling and internationalization (Saleor case studies).
What business outcome this delivers
Composable architecture turns "rich content + many integrations" from a problem into a manageable system:
- Feature delivery speed. Independent services and teams deploy in parallel - a new payment provider or market does not block a storefront release.
- Premium-grade managed content. Marketing handles storytelling in the CMS, merchandising handles attributes in the PIM, without involving developers for every change.
- Transferability and lower upgrade risk. The core is not forked; integrations are connected through webhooks/Apps, so updating Saleor does not break customizations.
- A unified O2O stack. One source of product and order data for the website and boutiques means seamless preorders, in-store reservations, and service history.
Business process as a service
Build the stack around a unified product model, not around the storefront. Define watch domain attributes in Saleor PIM (caliber, materials, edition limit), move editorial storytelling into a headless CMS, and connect each of the 20+ external systems (payments, taxes, fraud prevention, search, OMS/PoS, CDN, email) through webhooks and Apps without forking the core. Then adding a new market or provider becomes a service integration, not a migration project, and both content and integrations remain transferable across teams.