DPDP-Compliant WhatsApp Opt-Ins for Ecommerce Checkout

This guide is educational, for operators who search WhatsApp opt-in Shopify India DPDP. It is not legal advice, not a DPDP certification, and not a Meta policy ruling. Laws, rules, and platform terms change. Ask qualified counsel for your company.

Two regimes sit on the same phone number:

1. Meta / WhatsApp — businesses need a valid opt-in to message people; quality tanks when you blast strangers.
2. DPDP Act, 2023 — you (the brand) are typically the Data Fiduciary for checkout data. Consent, when you rely on it, should be free, specific, informed, unconditional, and unambiguous, with withdrawal as easy as giving it (see Section 6 of the Act). Notices should be understandable.

WatsBerry is a processor for End User data you run through the app. Read Privacy Policy, Data Processing Agreement, WhatsApp & Meta Data Use Policy, and Security Policy. Join the waitlist for invite-only access — we still will not sign a “DPDP-compliant” sticker on your theme.

Shopify already captures a phone for shipping. That is not automatically:

• consent to WhatsApp marketing, or
• Shopify SMS marketing, or
• permission to sell the number to a grey bulk tool.

A DPDP-minded checkout separates purposes:

Control	Job	Pattern
Phone field	Deliver the order	Required for COD/shipping. Explain that you may send order, delivery, and support updates (including WhatsApp) to fulfil the purchase.
Unticked WhatsApp marketing box	Offers, launches, cart recovery sequences that are promotional	Named channel (“WhatsApp”), named purpose (“offers and abandoned-checkout reminders”), link to your privacy notice. Not pre-ticked. Not bundled as “agree to everything or you cannot buy.”
Email marketing (Shopify native)	Email list	Keep it; do not treat it as WhatsApp.
SMS marketing (Shopify native)	SMS list	Not a WhatsApp opt-in. WatsBerry’s Shopify import can optionally keep only SMS-subscribed customers — that is a conservative SMS filter, not DPDP WhatsApp proof.

If you want both service WhatsApp and marketing WhatsApp, ask for both, with copy a person can understand. Hindi or another Eighth Schedule language on request is a DPDP notice theme — offer it if your storefront already is bilingual.

Be precise about the product:

WatsBerry does not currently inject a native Shopify Checkout UI extension. Do not expect a WatsBerry app block inside the checkout iframe on every plan.

Practical collection points Indian D2C actually uses:

1. Checkout Extensibility / Shopify Plus — add your own unticked WhatsApp marketing checkbox and store the attribute/metafield your ops can export.
2. Thank-you / order status / new customer account — post-purchase opt-in when checkout is locked down.
3. Storefront — WatsBerry website conversion tools, spin-the-wheel, and subscribe box (privacy-policy URL on the widget). These sit on the theme, not inside checkout.
4. Keyword / QR — “WhatsApp us JOIN” on the pack or thank-you page; campaign flows can start on opt-in or keyword.
5. CSV — only with a trail (source, timestamp, wording). No scraped number lists.

Whatever you use, the record matters: who, when, which exact sentence they saw, which purpose, which page. That is what you produce later — not a screenshot of “we have Shopify.”

Match sends to purposes:

• Order / COD / shipment — order alerts and COD confirmation follow a purchase. Still use approved templates outside the care window; category is usually utility if Meta agrees (marketing vs utility).
• Offers and most cart nudges — marketing templates and a marketing opt-in. First-touch “you left items” is typically marketing in our cart playbook.
• Support — if they messaged you, the care window is for that thread, not a licence to add them to a festive blast.

Withdrawal as easy as consent: STOP / unsubscribe in campaigns, honoured on the WABA, plus a way to reach you. WatsBerry unsubscriber tools help; you still owe a process when someone emails the brand.

Processors. Meta, Shopify, payment gateways, and WatsBerry process data you instruct. Your DPA and terms require valid opt-in before you message. We do not settle that duty for you.

Template hygiene: templates without the headaches.

• Privacy notice linked from checkout / widget (your store policy and WatsBerry’s for the SaaS).
• Unticked WhatsApp marketing control, purpose in plain language.
• Service-update explanation for the phone number — not hidden in T&Cs only.
• SMS marketing ≠ WhatsApp; do not import the whole customer admin as a blast list.
• Opt-out path that ops actually honours.
• Official Cloud API, not WhatsApp Web (app vs API).
• Dual billing understood: Meta + plan.

Public signup is waitlist-gated. Join the beta waitlist if you want this stack on WatsBerry — then have counsel review your checkbox, not our headline.

Is this legal advice?

No. This page is educational for Indian ecommerce teams. The Digital Personal Data Protection Act, 2023 and Meta’s WhatsApp policies both apply; your counsel should review checkout copy, notices, and retention for your entity. WatsBerry does not certify that a checkbox makes you compliant.

If they gave a phone number to place the order, can I broadcast offers?

Treat delivery/order WhatsApp as a different purpose from promotions. DPDP consent is purpose-specific; Meta also wants a valid opt-in for business-initiated marketing. Use a separate, unticked WhatsApp marketing control.

Does WatsBerry add a WhatsApp checkbox inside Shopify Checkout?

Not in the current product. Collect consent with Shopify checkout customisation (where your plan allows), thank-you / account pages, or WatsBerry website widgets and subscribe boxes on the storefront, then sync numbers.

Who is responsible for End User consent?

You (the brand) are responsible for notices and lawful bases. WatsBerry acts as processor for End User data you send through the platform — see /privacy-policy, /data-processing-agreement, /whatsapp-data-policy, and /security-policy.