Retention Automation Case Study

D2C Skincare Retention Automation India for Repeat Orders

A D2C skincare brand had strong first purchases but weak replenishment behavior after 45 days. We built retention journeys that used product cycle, skin concern, and order history instead of blanket coupon campaigns.

3 April 2026Mumbai, Maharashtra, IndiaE-commerce
D2C Skincare Retention Automation India for Repeat Orders

Client

D2C skincare brand

Team size

18-person team, 12,000+ monthly orders across Shopify and marketplaces

Industry

E-commerce

Build

Shopify orders -> product cycle tagging -> WhatsApp and email retention -> Razorpay subscription link -> Looker Studio reporting

Repeat orders stalled after the first purchase

The skincare brand acquired buyers through Meta ads, but customer data stopped at the first Shopify order. Replenishment windows were tracked in spreadsheets, WhatsApp broadcasts were generic, and buyers with different skin concerns received the same discount-led message. Paid acquisition kept filling the top of the funnel while profitable second and third orders were left to chance.

D2C skincare retention automation india tied to product usage

We connected Shopify, n8n, Mautic, WhatsApp Business API, and Razorpay so every order created a replenishment date based on product type and quantity. Customers were segmented by skin concern, last order, average order value, and subscription eligibility, then moved into WhatsApp and email journeys that encouraged reorders, bundles, and prepaid subscriptions. Looker Studio showed retention by SKU, campaign, and cohort.

Documented delivery scope

What this case study can evidence

This case study is based on the delivery scope documented on this page: shopify orders -> product cycle tagging -> whatsapp and email retention -> razorpay subscription link -> looker studio reporting for a d2c skincare brand in Mumbai, Maharashtra, India. It is an implementation record, not a promise that another business will see the same outcome.

Workflow evidence

The recorded build includes order data enrichment, replenishment date logic, segmented retention journey, subscription offer routing, cohort reporting. Each step is shown below so readers can see the stated handoffs rather than infer hidden work.

Tools and ownership

The listed tools support the defined workflow: Shopify for provides order, sku, customer, and checkout-source data for retention triggers; n8n for calculates replenishment dates and moves customer events between shopify, mautic, whatsapp, and sheets; Mautic for runs segmented email journeys when product usage windows are approaching; WhatsApp Business API for sends reorder reminders, skin concern education, and subscription links to opted-in buyers; Looker Studio for shows repeat-purchase cohorts by sku, channel, and customer segment. Final operating ownership remains with the client team.

How to read results

The results section reports only the stated retention process and message relevance and subscription readiness and cohort visibility. Context, offer quality, team response, and adoption affect any future implementation.

Evidence-led delivery record

Context, scope, handover, and measurement

The details below are limited to the documented record on this page. They clarify what was in scope for this d2c skincare brand in Mumbai, Maharashtra, India; they do not add unverified client facts, guarantees, or transferable outcome claims.

Starting constraint

The skincare brand acquired buyers through Meta ads, but customer data stopped at the first Shopify order. Replenishment windows were tracked in spreadsheets, WhatsApp broadcasts were generic, and buyers with different skin concerns received the same discount-led message. Paid acquisition kept filling the top of the funnel while profitable second and third orders were left to chance.

Agreed implementation scope

We connected Shopify, n8n, Mautic, WhatsApp Business API, and Razorpay so every order created a replenishment date based on product type and quantity. Customers were segmented by skin concern, last order, average order value, and subscription eligibility, then moved into WhatsApp and email journeys that encouraged reorders, bundles, and prepaid subscriptions. Looker Studio showed retention by SKU, campaign, and cohort.

Launch and handover boundaries

The recorded workflow identifies the delivery path from order data enrichment through cohort reporting. The listed tools and owners are the reference for testing, exception handling, and operational handover; this page does not claim work beyond that recorded scope.

How the change is assessed

The recorded measures are retention process, message relevance, subscription readiness, cohort visibility. They provide the stated review points for this implementation; results depend on the client context, adoption, and operating process.

Workflow Built

1

Order data enrichment

Shopify order events route into n8n with SKU, quantity, customer phone, UTM source, and skin concern tags captured from checkout notes and quizzes.

2

Replenishment date logic

n8n assigns a next-purchase date by product type, such as cleanser, serum, or sunscreen, and writes the date back to Google Sheets and Mautic.

3

Segmented retention journey

Mautic triggers email and WhatsApp messages based on skin concern, purchase recency, and product cycle so oily-skin serum buyers do not receive dry-skin bundle offers.

4

Subscription offer routing

Customers with two repeat purchases receive a Razorpay subscription link and a WhatsApp explanation of delivery frequency, cancellation rules, and bundle value.

5

Cohort reporting

Shopify, Mautic, and Razorpay data flows into Looker Studio to compare repeat orders, subscription starts, and campaign source by cohort.

Results

Retention process

Manual spreadsheet reminders were replaced by product-cycle journeys triggered from Shopify orders

Message relevance

Skin concern and SKU history controlled what each buyer received instead of one broadcast list

Subscription readiness

Repeat buyers were identified and offered Razorpay subscription plans at the right purchase moment

Cohort visibility

The team could see which products and ad sources created customers who reordered

FAQs

How does d2c skincare retention automation india work for Shopify stores?+

D2C skincare retention automation india starts with Shopify order data. n8n reads SKU, quantity, phone number, and customer tags, then triggers Mautic and WhatsApp Business API reminders when the product is likely to run out.

Can WhatsApp automation for D2C skincare reduce discount dependency?+

Yes. WhatsApp automation for a skincare brand can use product education, routine reminders, and replenishment timing before offering discounts. The buyer receives context based on their last product instead of a generic coupon blast.

Can Scallar build a Klaviyo alternative for Indian D2C brands?+

For many Indian D2C brands, Scallar can combine Mautic, n8n, Shopify, and WhatsApp Business API as a lower-control-risk retention stack. It supports email, WhatsApp, segmentation, and reporting without locking every workflow into one SaaS platform.

What data is needed for d2c skincare retention automation india?+

The useful data includes SKU, order date, phone number, product category, skin concern, UTM source, and payment behavior. Even if the data starts messy, Scallar can clean Shopify exports and build retention journeys in stages.

Want a Workflow Like This?

We can map your lead flow, identify manual delays, and build the automation layer that makes follow-up instant.

Book a Free Automation Audit
Chat on WhatsApp