Deep dive · Nutraceuticals
One platform for 4 brands and 19 storefronts
How we moved the separate merchant storefronts of an international multi-brand nutraceuticals producer onto one commerce platform, across languages, markets and brands.
Client anonymized. Approved by the client.
- Main brands
- 4
- Partner storefronts
- 19
- Commerce platform
- 1
- Content platform
- 1
Key facts
The project at a glance
Client: international multi-brand nutraceuticals producer, headquartered in the United States. Dietary supplements, sold through its own brand storefronts and through partner storefronts.
Company size:
Markets and channels: multiple languages, markets and brands, sold through 4 main brand storefronts and 19 partner storefronts.
Platform and main systems: Medusa for commerce, Storyblok for content.
Project period and relationship: . The client retained us after launch and we still ship new features.
From architecture and custom backend development to design, content and project management, Sonklar delivered top-tier work in every area.
Starting point
Many storefronts, no shared core
What was broken: many separate merchant storefronts across languages, markets and brands, which all had to run on one platform.
Why it mattered: custom branded partner stores need to be created quickly on demand based on a shared product database.
Constraints: numerous marketing channels, fulfillment and other third-party systems to connect, complex legacy data to migrate, and an external software firm already working on shared integrations.
Approach
How we approached it
Discovery
We spent several weeks analyzing business goals, operational constraints and architectural requirements. The result was a detailed work plan and a realistic budget, before any build started.
Architecture decisions
Two decisions shaped the platform. We chose a composable architecture, so the platform scales flexibly and individual parts can be replaced later as the business grows. We also chose flexible hosting options, to cover a complex geographical reach.
Integrations
The platform connects to marketing channels, fulfillment systems and other third-party systems. We coordinated the shared integrations with the client’s external software firm.
What we built
The main capabilities
We led the planning, architecture and custom backend development. The external software firm handled its part of the shared integrations.
One core, many brands
A commerce core customized substantially for multiple markets and multiple brands.
Custom backend
Custom backend development on top of the core, planned and architected by us.
Admin and reporting tools
Highly custom admin and reporting tools that support daily operations.
Storefronts and content
Storefronts we designed, with content structured for the multi-storefront model.
Legacy data migration
The complex legacy data moved onto the new platform.
Connected systems
Marketing channels, fulfillment and other third-party systems wired in.
After launch
Running and evolving it
The go-live moved by a few months, because of external vendor dependencies and changes in project scope. After launch, the client retained us to refine the platform and roll out new features.
Since then, new partner shops and features have rolled out continuously. We extended the commerce backend with management and reporting functionality built for the very specific needs of the client’s business.
Capabilities
What the client can do now
Run every storefront from one place
Brands, partner storefronts, languages and markets share one platform instead of separate setups.
Operate with purpose-built tools
Custom admin and reporting tools support the daily work of the team.
Keep shipping new features
The platform keeps evolving after launch, with us as the retained engineering team.
Given their technical skill and reliable execution, we have retained Sonklar post-launch to continue refining the platform and rolling out new features.
Questions
Questions about this project
Facing a similar multi-brand setup?
Talk to a senior engineer about your situation. A senior engineer joins every first call.