Blog Digital Product Infrastructure That Cannot Stop. A Leading Beauty Brand Migration to ShopifyInfrastructure That Cannot Stop. A Leading Beauty Brand Migration to Shopify
How Boldare became the trusted engineering partner for the most critical layer of one of the world’s fastest-growing beauty brands
The Client needed to migrate its entire Direct-to-Consumer ecosystem from Salesforce Commerce Cloud to Shopify. Zero downtime. No degradation in customer experience. Without overwhelming a 20-person internal team.
Boldare came in as the backend partner, built a central API hub serving 6+ stores across 3 regions and 20+ integrations, and then ran a fully transparent migration of the loyalty system. The result: a platform that handles peaks of 500 req/s, and a partnership now in its third year.
Table of contents
The Client
A fast-moving brand that needed a partner, not a supplier
The Client is a publicly listed beauty company known for professional-quality cosmetics at accessible prices – fully vegan and cruelty-free. Its portfolio spans four distinct brands sold direct-to-consumer across the US, UK, and EU.
E-commerce is the client’s strategic channel and primary competitive battlefield. The internal digital team numbers around 20 people. That’s lean for the scale of the operation – which is why, when the company decided to migrate its platform across every layer of the stack – frontend, API, data, and mobile – it needed a partner that wouldn’t require constant hand-holding.
The Challenge
Replacing the engine mid-flight
Salesforce Commerce Cloud was expensive, difficult to maintain, and blocking product iteration. Shopify had become the headless commerce standard in the beauty and DTC segment – market pressure was clear. The challenge touched every layer of the stack: from mobile apps to loyalty APIs to the data pipeline feeding Snowflake.
Boldare owned the backend layer – the central API hub that holds everything together.
The core technical challenge: running two loyalty systems simultaneously – LoyaltyCore (legacy) and PromoEngine/RewardHub (new) – across three regions, with fundamentally different API contracts. The end customer could not feel any difference during the switchover.
Why Boldare
Trust built at the frontend stage opened the door to core infrastructure
The engagement started with a frontend project – The Client needed experienced engineers quickly for work on the Salesforce PWA Kit. The quality of that first engagement – autonomous execution, cross-timezone communication, the ability to navigate incomplete context without escalation – built the trust that opened access to the backend API layer: the central hub serving 6+ stores across three regions, managing 20+ integrations and the loyalty data migration.
The technical fit was there too: deep familiarity with headless commerce, Shopify Hydrogen, and complex e-commerce integrations. But the path to the most critical layer of the Client’s stack ran directly through the work already delivered on the frontend.
What We Built
**
An abstraction layer as the architectural decision that changed everything**
The most important technical decision: introducing an abstraction layer in the loyalty API – hiding LoyaltyCore and PromoEngine/RewardHub behind a single consistent API contract. The migration became transparent to end customers. Alongside this, we adopted Clean Architecture, enabling external systems to be swapped out without touching business logic.
Central API hub
One system serving 6+ Shopify stores across US/UK/EU/AU/CA, managing 20+ integrations under a single contract.
Loyalty migration layer
LoyaltyCore and PromoEngine/RewardHub run in parallel behind a unified API – the end customer sees no difference during the switchover.
50+ Hangfire jobs
Full automation of data exports, synchronizations, and the pipeline to Snowflake feeding analytics and CDP.
Resilience by design
Polly retry policies with independent configuration per integration – each of the 20+ external services has its own failure tolerance threshold.
Stack
.NET 9.0 · ASP.NET Core Web API · Clean Architecture · Redis Stack · Hangfire 1.8 · AWS Elastic Beanstalk · Bitbucket Pipelines · Auth0 · Shopify Hydrogen · Builder.io · Snowflake · Polly
How We Worked
Close, but without micromanagement
The project required tight coordination across three time zones and several parallel workstreams. We built a rhythm that gives the Client full visibility without pulling them into every technical decision – engineers on both sides talk directly, and strategic matters reach the right people at the right time. The Time & Material model allows the scope to scale when the project needs it – without renegotiating the contract every time priorities shift.
The Release
June 3, 2026
For the final migration to production, the team set up a virtual War Room on Zoom – everyone involved connected simultaneously. Part of the part of the Client team was together physically; the rest joined remotely from the US, Poland, India, Brazil, the Philippines, and the UK. For anything that needed resolving, the group split into breakout rooms and worked through issues directly. No Slack queues, no ticket overhead – just the fastest path to a decision. Everything went smoothly.
Before & After
| Before | After |
|---|---|
| Monolithic SFCC, difficult to maintain and iterate | New features ship in days, not sprints – no platform bottleneck |
| No central API layer – each region managed separately | One contract serves 6+ stores across 3 regions – no regional divergence |
| Two loyalty systems with no unified interface | Transparent loyalty migration with no change for end customers |
| Small digital team overwhelmed by the migration project | Internal team focused on product, not on managing integrations |
| Instability during traffic peaks | 500 req/s during launches – system holds without degradation |
| — | Data exports, CDP sync, and Snowflake pipeline run fully autonomously |
| — | Platform scope expanded three times – mobile and new regions added without rearchitecting |
Timeline
Summary
The Client sells to millions of customers across three continents. Behind every transaction sits years of accumulated data – purchase history, earned rewards, redeemed points – tied to real people who chose this brand over every other option on the shelf. Being part of infrastructure that serves that many people – and getting the migration right for every single one of them – is exactly the kind of work we’re here to do. Three years in, we’re proud of what we’ve built together with the Client team.
Share this article:
