Zero downtime. Zero manual intervention. A data pipeline engineered for an ERP that could not change — but had to work.
Skin Health & You is a certified ecommerce retailer associated with Galderma's Cetaphil portfolio in India, managing high-volume skincare sales through digital commerce channels. Following the migration to Shopify, the brand faced a structural challenge that no off-the-shelf integration could solve: their existing ERP was architecturally configured for legacy marketplace data formats and could not accommodate Shopify's schema — within any available timeline.
The constraint was real and non-negotiable. Re-engineering the ERP was off the table. Manual data preparation was unsustainable at scale. The solution required a purpose-built enterprise middleware layer that could translate, enrich, and transmit order data automatically — sitting between Shopify and the ERP, absorbing the complexity so neither system had to change.
Three people were operating in a broken data pipeline. The middleware was built to make all three forget the pipeline exists.
ERP systems configured for legacy marketplace formats were structurally incompatible with Shopify order schemas, forcing teams to bridge the gap manually every day while the ERP remained locked on an unchangeable timeline.
⚙️ ERP architecture incompatible with Shopify schemaOperations managers spent hours each day manually reformatting order data — price breakdowns, coupon splits, and cashback fields — because none of it emerged from Shopify in the structure the ERP required.
⏱️ Hours daily on manual order data transformationBusiness heads overseeing a fresh platform migration faced the risk of fulfilment breakdown if order data failed to reach the ERP accurately — making operational continuity a non-negotiable requirement from day one.
🔒 Post-migration operational continuity is non-negotiableThe structural gap between Shopify's order schema and the ERP's expected data format was not a minor compatibility issue — it was an architectural incompatibility. The ERP had been configured specifically for legacy marketplace data structures. Shopify orders contained different field hierarchies, missing financial breakdowns that the ERP accounting workflows depended on, and structural formats the ERP simply couldn't parse without transformation.
The complexity extended beyond field mapping. Shopify's default API responses didn't provide the financial bifurcation the ERP required — MRP, selling price, coupon discounts, and cashback utilization needed to be computed and injected into the order payload before transmission. And two-way synchronization was needed: the ERP also had to push fulfilment, cancellation, return, and delivery status updates back into Shopify to keep the commerce layer accurate.
“An ERP that cannot change. A Shopify store that generates orders in a different language. And a business that cannot stop while the translation is being built.”
The middleware was engineered to be invisible — Priya's ERP receives perfect data, Akash stops preparing anything manually, and Neelam's business never pauses.
Designed and deployed a serverless middleware architecture on AWS using Lambda functions integrated with Shopify webhooks — processing every order event in real time without infrastructure management overhead.
ResilienceBuilt transformation pipelines that convert Shopify order payloads into ERP-compatible JSON structures automatically — Akash's daily reformatting work is replaced entirely by a system that runs without anyone watching.
SustainabilityImplemented logic to compute and inject financial breakdowns — MRP, selling price, coupon discounts, and cashback utilization — that Shopify's API doesn't expose natively but Priya's ERP accounting workflows depend on.
ResilienceEnabled bidirectional synchronisation: the ERP pushes fulfilment events, cancellations, returns, and delivery status updates back into Shopify — keeping both systems accurate without manual reconciliation.
SustainabilityEliminated dependency on ERP-side structural changes by handling all transformation externally — the solution respects the constraint that the ERP cannot change within available timelines.
ResilienceBuilt real-time order transmission workflows ensuring orders enter the ERP pipeline immediately after placement — Neelam's fulfilment operations run without waiting on a manual validation step.
ResiliencePriya's ERP receives correctly formatted, financially complete order data for every Shopify transaction — the schema incompatibility that caused daily friction no longer exists from the ERP's perspective.
Akash's team stopped preparing order data the morning the middleware went live. The hours previously spent on manual transformation are available for work that actually requires human judgement.
Neelam's post-migration operations ran without disruption. The middleware provided the bridge between two incompatible systems without requiring either to change — or the business to stop.
The AWS serverless architecture scales with order volume automatically — as Skin Health & You grows, the middleware grows with it, without infrastructure changes or proportional cost increases.
Enterprise middleware engineering for commerce-to-ERP order flows — handling schema transformation, financial bifurcation, and two-way sync so your operations run without manual intervention.