Commerce
Zero-Maintenance Commerce Across 60 Markets
Sunstar consolidated two Adobe Commerce Cloud instances into a single Adobe Commerce SaaS platform — covering 60 websites and 66 storeviews across EU and US markets. Zero infrastructure overhead. Full catalog continuity. Seamless user experience.
The Challenge
Sunstar ran two separate Adobe Commerce PaaS instances for EU and US — with dual catalogs for Consumer and Professional audiences. Every update, every customization had to be managed twice. Infrastructure complexity was scaling faster than the business.
The Scenario
The Solution
One Platform, Zero Infrastructure Burden
Comwrap Reply migrated Sunstar's entire commerce backend from two Adobe Commerce Cloud (PaaS) instances to a single Adobe Commerce SaaS (ACCS) platform — without touching the existing AEM storefront.
The core challenge was not just moving data. It was re-engineering the integration layer between AEM and Commerce while keeping 60 live websites operational. Here's what we delivered:
New CIF Integration Framework Adobe CIF Core Components were built for PaaS. They could not talk to SaaS out of the box. Comwrap Reply designed and implemented a new integration framework that enables CIF Core Components to work with both SaaS and PaaS endpoints — a capability that did not exist before this project. This means Sunstar's AEM authoring teams continue working exactly as before, while the entire backend runs on SaaS.
Catalog Consolidation Two separate product catalogs — one per region — were merged into a single unified catalog on ACCS. Consumer and Professional catalogs remain separated by audience, but content and catalog management now happen from one place. Products, categories, attributes, attribute sets, and all SEO optimizations were migrated and validated.
Custom Logic via Adobe App Builder Features that previously lived as custom modules inside Adobe Commerce — including SEO-critical URL rewrites and category URL structures — were reimplemented as isolated Adobe App Builder modules. This keeps the SaaS instance clean, maintainable, and fully upgradeable without custom code dependencies.
The result: Sunstar operates a modern, fully managed commerce platform with zero infrastructure maintenance — and a storefront that didn't change for a single end user.
How we did it
Joint Migration with Adobe — Daily Cadence
This was not a lift-and-shift. Adobe Commerce SaaS does not allow custom codebase modifications — so every custom feature had to be reviewed, rearchitected, or retired. Comwrap Reply ran a structured migration in close collaboration with Adobe and Sunstar.
Phase 1: Feature Analysis Adobe and the Comwrap Reply team jointly reviewed every custom module in the existing ACC instances against business requirements. Each feature was classified: migrate, reimplement via App Builder, or deprecate. This ruthless prioritization kept scope under control and timelines realistic.
Phase 2: API Mapping & Catalog Consolidation The product delivery APIs between PaaS and SaaS differ significantly. Comwrap Reply mapped every API difference and created the correct request/response translations. Simultaneously, the team defined and executed the catalog consolidation — merging two regional catalogs into one while preserving audience-specific segmentation for Consumer and Professional users.
Phase 3: Frontend Adaptation All AEM CIF Core Components on the storefront were updated to work with the new SaaS Catalog Service endpoints. This required designing a compatibility layer that abstracts the differences between SaaS and PaaS — making the CIF components endpoint-agnostic.
Phase 4: Migration Execution & QA Adobe ran proprietary PaaS-to-SaaS migration scripts to move content, while building Adobe App Builder modules for SEO features like custom URL rewrites and full category URL structures. Daily syncs between Comwrap Reply, Sunstar, and Adobe ensured issues were caught and resolved in real time.
Go-Live Adobe processed the final migration and go-live testing together with the Comwrap Reply team — a joint delivery that reflects the depth of the partnership.
The Results
Sunstar now operates a single Adobe Commerce SaaS instance across 60 websites and 66 storeviews — down from two PaaS instances. Infrastructure maintenance costs drop to zero: Adobe manages the platform entirely. Custom logic is cleanly isolated in Adobe App Builder modules, eliminating upgrade friction and technical debt. Content and catalog management happen from a single point, cutting operational complexity for marketing and merchandising teams across EU and US markets. Most importantly, end users experienced no disruption — the storefront remained unchanged while the entire backend was replaced. The updated CIF integration framework now supports both SaaS and PaaS, giving Sunstar architectural flexibility for future evolution.
About the Client
Sunstar is a global life sciences company founded in Japan in 1932, headquartered in Etoy, Switzerland. The company operates across oral care, health & beauty, and industrial sectors, with annual group revenues of approximately $1.4 billion. The GUM® brand — Sunstar's flagship oral care line — is available in over 90 countries, serving both consumers and dental professionals. Sunstar's product portfolio includes toothbrushes, interdentals, dental rinses, and specialty oral health solutions.
Ready to Move Your Commerce to SaaS?
Let's discuss how Comwrap Reply can migrate your Adobe Commerce platform — with zero storefront disruption and zero future infrastructure overhead.