“8-12x ROI on loyalty isn't a marketing claim — it's the average we see on customers who run Fundle for three consecutive quarters. The math is the moat.”
- •Understand how India's DPDP Act changes the rules for POS-to-loyalty data flows in malls and retail chains
- •See why unmanaged consent at the POS layer is the single biggest compliance liability for Indian retail CMOs in 2025
- •Discover what a ConsentFirst architecture looks like across multi-brand, multi-POS retail environments
- •Evaluate Fundle's ConsentFirst against DIY consent patches and legacy CRM-bolt-on approaches
- •Implement a five-step playbook to make your POS-loyalty integration DPDP-compliant before the enforcement clock runs out
India's retail sector processes over 2.8 billion point-of-sale transactions annually across organized retail alone—malls, fashion chains, pharmacy networks, F&B aggregators, and jewellery brands. Behind every swipe, every UPI beep, and every loyalty card scan is a data handshake: the customer's name, mobile number, purchase SKU, basket value, and store location flowing from the POS terminal into a loyalty engine, a CRM, an analytics warehouse, or all three simultaneously. For years, this handshake happened in the background, invisible to the customer and largely unregulated. That era ended with the Digital Personal Data Protection Act, 2023.
The DPDP Act places the burden of lawful data processing squarely on the entity collecting and using personal data—what the law calls the 'Data Fiduciary.' For a mall operator running a multi-brand loyalty programme, or a retail chain like Lifestyle or Pantaloons integrating their POS with a CRM like Capillary or a loyalty platform like EasyRewardz, every data flow that lacks an explicit, timestamped, purpose-limited consent record is now a potential enforcement action. The law is not advisory. Penalties under DPDP can reach ₹250 crore per violation instance, and the Data Protection Board is expected to become operational through 2025.
The problem is not awareness—most mall CMOs and retail IT heads know DPDP is coming. The problem is architecture. Most POS-to-loyalty integrations were built for speed and data richness, not consent governance. Connectors between POS systems like POSist, Petpooja, GoFrugal, or Wondersoft and downstream loyalty or engagement platforms were never designed to carry a consent token, validate its scope, or enforce data minimisation in real time. Retrofit approaches—a checkbox on a paper form, a WhatsApp opt-in link sent post-purchase—do not meet the DPDP standard for granular, informed, withdrawable consent.
This is precisely the gap that Fundle's ConsentFirst framework was built to close. As India's AI-first loyalty and customer engagement platform, Fundle.ai has engineered ConsentFirst as a native layer within its POS integration loyalty platform India architecture—not a compliance checkbox bolted on after the fact, but a consent management system that sits between data collection and data use, in real time, at scale.
India Retail Data Privacy: The Scale of the Problem
Overview of India's Digital Personal Data Protection (DPDP) Act
The Digital Personal Data Protection Act, 2023 is India's first comprehensive federal data privacy law. Enacted in August 2023 and progressively coming into enforcement through 2024-25, DPDP applies to any entity that collects, stores, processes, or shares the personal data of Indian citizens—whether digitally collected or later digitised from physical records. For the Indian retail and mall industry, this is not a sectoral carve-out; it applies to everyone from a single Manyavar franchise to a pan-India mall operator running Phoenix Marketcity or Select CITYWALK properties.
The law introduces seven foundational principles that directly impact how POS-loyalty programmes operate. First, consent must be free, specific, informed, and unconditional—a customer signing up for a loyalty programme at a Tanishq or Apollo Pharmacy counter must understand exactly what data is being collected, for what purposes, and with whom it will be shared. Second, consent must be granular: a customer can consent to purchase-history-based personalisation but decline cross-brand data sharing within a mall programme. Third, and critically for retail IT heads, consent must be withdrawable at any time, and withdrawal must be operationalised—not just acknowledged—within the system that holds the data.
For mall CMOs managing multi-brand loyalty stacks, the compliance surface area is enormous. A single mall visit by a member can generate POS events at a food court outlet running Petpooja, a fashion anchor on GoFrugal, and a pharmacy on Wondersoft—each feeding into a shared loyalty engine. Under DPDP, each of these data flows requires its own consent basis, and the mall's loyalty platform must maintain an auditable record of which member consented to which data use at what timestamp. Legacy integration architectures, which typically use a shared member ID as the sole linkage between POS and loyalty, have no mechanism to enforce this.
The law also introduces the concept of the 'Consent Manager'—a registered intermediary that can collect and manage consent on behalf of Data Fiduciaries. Fundle's ConsentFirst is architected to function as this consent management layer, meaning mall operators and retail brands do not need to build this infrastructure themselves. ConsentFirst manages privacy consent for 1.33 Cr+ members ensuring DPDP compliance in POS-loyalty data exchange—a scale that reflects the real operational complexity of India's organised retail ecosystem.
ConsentFirst: The DPDP-Compliant POS-Loyalty Data Flow
Role of Consent Management in POS-Loyalty Data Flows
The POS terminal is the most data-rich touchpoint in Indian retail. It captures what the customer bought, when, at which store, at what price, with which payment method, and increasingly against which loyalty ID. This data richness is precisely why loyalty programmes exist—without purchase-level data, personalisation is guesswork. But it is also why the POS-to-loyalty integration is the highest-risk data flow from a DPDP compliance standpoint.
Consider how a typical mid-market retail chain like Reliance Trends or FabIndia currently operates its loyalty enrolment. A cashier asks the customer for a mobile number at checkout, enters it into the POS, and the system auto-creates a loyalty profile. No consent form is presented. No purpose is disclosed. The mobile number flows into a CRM where it is used for promotional WhatsApp blasts, remarketing campaigns on Meta, and lookalike audience uploads—none of which the customer was told about at the POS counter. This is the default state of Indian retail loyalty today, and it is textbook DPDP non-compliance.
A genuine consent management layer in a POS-loyalty integration must do five things simultaneously: present a consent notice in the customer's preferred language at the point of data collection, capture a verifiable consent signal (OTP-confirmed or digitally signed), map that consent to specific data fields and processing purposes, propagate the consent record to every downstream system that touches that customer's data, and enable real-time consent withdrawal that cascades through the entire stack. None of these capabilities exist natively in POSist, GoFrugal, Wondersoft, or Petpooja—they are POS systems, not consent management platforms. And most loyalty platforms—whether Capillary, EasyRewardz, Xeno, or WebEngage—treat consent as a field in a profile, not as an active enforcement gate on data flows.
Fundle's ConsentFirst architecture treats consent as infrastructure, not metadata. The consent token issued at enrolment becomes a live parameter that the Fundle AI Platform checks at every data event: before sending a campaign message, before sharing aggregated data with a mall analytics dashboard, before enriching a profile with third-party data. This is not a compliance theatre exercise—it is the only architecture that holds up under DPDP enforcement scrutiny, and it is the baseline that mall IT heads should be demanding from any POS integration loyalty platform India vendor they evaluate in 2025.
ConsentFirst vs. Legacy Consent Approaches in POS-Loyalty Integration
Features of Fundle's ConsentFirst Platform for POS Integration Loyalty Platform India
Fundle's ConsentFirst is built on four architectural pillars that distinguish it from consent bolt-ons offered by legacy CRM or loyalty vendors. Understanding these pillars is essential for retail IT heads evaluating best POS connectors for loyalty with native DPDP compliance.
The first pillar is Real-Time Consent Token Architecture. When a customer enrols in a loyalty programme at any POS touchpoint—whether a GoFrugal terminal at a jewellery store, a POSist kiosk at a QSR, or a Wondersoft checkout at a fashion mall anchor—ConsentFirst issues a signed, purpose-scoped consent token that is immediately written to an immutable consent ledger. This token travels with every data event generated by that member, from POS transaction records to campaign targeting lists to mall footfall analytics. No downstream system on the Fundle AI Platform processes a data event without first validating the token's scope against the requested operation.
The second pillar is Multi-POS Connector Library. Fundle has pre-built ConsentFirst-aware connectors for all major Indian POS systems—POSist, Petpooja, GoFrugal, Wondersoft, and others—meaning consent capture does not require custom integration work from the retailer's IT team. The connector handles the consent UX at the POS layer (a QR code on the receipt, an OTP on the cashier screen, or a pre-enrolment digital form) and passes the resulting consent record directly into the ConsentFirst ledger before any loyalty data is written.
The third pillar is the Preference Centre and Withdrawal Engine. Every member managed by Fundle Loyalty gets access to a self-service preference centre—accessible via the loyalty app, a web link on the receipt, or an IVRS number—where they can review, modify, or withdraw consent for specific purposes at any time. Critically, withdrawal is not a database flag that human agents act on later. It is an active instruction to the Fundle Agentic AI layer that immediately suppresses the relevant data flows, removes the member from in-flight campaign segments, and logs the withdrawal event with a timestamp. This is DPDP Article 6 compliance operationalised.
The fourth pillar is the DPDP Compliance Reporting Suite. Mall CMOs and retail DPOs need to demonstrate compliance, not just claim it. ConsentFirst generates real-time dashboards showing consent coverage rates by store, by brand, by enrolment channel, and by data purpose. It produces Data Processing Records in the format expected by the Data Protection Board, and it flags consent gaps—members with incomplete consent records who have been exposed to data processing operations—so compliance teams can remediate before an audit.
Talk to a Fundle expert
Want a Fundle deployment plan for your brand or mall? Ping Abhinav or Anmol directly on WhatsApp.
Free 30-minute working session. We'll share what a Fundle Loyalty Platform, Fundle Mall Loyalty or Fundle Brand Loyalty rollout looks like for your category — with specific numbers, not a deck.
Five-Step Playbook: Implementing ConsentFirst in Your POS-Loyalty Stack
Audit Your Current POS-to-Loyalty Data Flows
Map every data field flowing from each POS system (POSist, GoFrugal, Petpooja, Wondersoft) into your loyalty engine and CRM. Identify which fields contain personal data under DPDP definitions, and document the current consent basis — or absence thereof — for each flow. This gap analysis is the foundation of your ConsentFirst deployment plan.
Define Consent Purposes and Granularity
Work with your legal and marketing teams to define the specific data processing purposes your programme requires: purchase history for personalised offers, mobile number for transactional OTPs, location data for geo-targeted campaigns, cross-brand data sharing for mall-wide analytics. Each purpose becomes a distinct consent scope in ConsentFirst, giving members genuine control rather than a single take-it-or-leave-it opt-in.
Deploy ConsentFirst POS Connectors
Install Fundle's pre-built ConsentFirst-aware POS connectors for each system in your estate. Configure the consent UX for each touchpoint: a QR code-triggered consent form for self-checkout kiosks, an OTP-confirmed enrolment screen for assisted checkout, and a digital pre-enrolment link for member app sign-ups. Ensure every connector is passing consent tokens into the ConsentFirst ledger before any loyalty data write occurs.
Migrate Existing Member Base to ConsentFirst
Existing loyalty members enrolled before ConsentFirst deployment need consent re-confirmation. Run a structured consent refresh campaign via the channels they previously opted into — SMS, WhatsApp, or in-store at next purchase — with a clear explanation of what they are confirming and what control they gain. Members who do not respond within the campaign window should be moved to a restricted-processing state, not deleted, until consent is confirmed or denied.
Activate Compliance Reporting and Continuous Monitoring
Enable the ConsentFirst DPDP Compliance Dashboard for your DPO and retail IT head. Set automated alerts for consent coverage drops below 95% at any store or brand within your loyalty estate. Schedule monthly consent audit exports in the Data Protection Board's expected format. Configure the Fundle AI Workflow to automatically flag any new POS integration or third-party data sharing request for consent impact assessment before activation.
KPIs to Track: Measuring ConsentFirst Impact on Loyalty Programme Health
Implementing a ConsentFirst DPDP-compliant CMP is not just a risk mitigation exercise—it is a business performance lever. Mall CMOs who frame consent management purely as a compliance cost will miss the commercial upside that comes from building a first-party data asset that members actually trust. The right KPI framework captures both the compliance health and the business health of a consent-governed loyalty programme.
On the compliance side, the primary metric is Consent Coverage Rate: the percentage of active loyalty members with a valid, purpose-specific, digitally confirmed consent record for each data processing activity. Best-in-class programmes on the Fundle Loyalty platform are running at 94-97% consent coverage for core loyalty data uses (purchase history, points balance communication) and 78-85% for secondary uses like cross-brand analytics and third-party enrichment. Any store or brand falling below 90% on core consent should trigger an immediate remediation workflow.
On the business side, the most revealing metric is Engaged Consent Rate: the percentage of members who actively manage their consent preferences through the self-service preference centre. Counter-intuitively, a higher Engaged Consent Rate is associated with stronger programme loyalty. Members who understand what data is used and have exercised choice are significantly more likely to redeem offers, refer new members, and visit more frequently. Fundle platform data shows a 4.2x higher re-engagement rate for members with full granular consent records compared to those enrolled under blanket opt-ins. Consent transparency, when operationalised well, is a trust signal that drives commercial behaviour.
Retail IT heads should additionally track Consent Withdrawal Rate by data purpose—this is a direct signal from customers about what data uses feel intrusive. If cross-brand data sharing in a mall programme has a 23% withdrawal rate but purchase-history personalisation has a 4% withdrawal rate, that is actionable intelligence: members are comfortable with relevant personalisation but uncomfortable with their data being treated as a commodity shared across brands without clear benefit to them. A well-designed consent preference centre, integrated into the Fundle AI Platform, turns this signal into continuous programme improvement rather than a compliance headache.
- All POS enrolment touchpoints present a DPDP-compliant consent notice in the customer's preferred language before capturing any personal data
- Consent is OTP-confirmed or digitally signed at the point of collection — paper forms and verbal opt-ins are not acceptable under DPDP
- Consent records are granular by data purpose (personalisation, marketing, analytics, third-party sharing) and stored in an immutable, timestamped ledger
- Every downstream system receiving POS-originated loyalty data (CRM, analytics, campaign platforms) is gated by live consent token validation — not just a database flag
- Members can withdraw consent for any specific purpose via self-service at any time, with withdrawal cascading to all connected systems within minutes
- A Data Processing Record covering all POS-to-loyalty data flows is maintained and exportable for Data Protection Board review
- Consent coverage rate is monitored in real time by store, by brand, and by data purpose — with automated alerts for coverage drops below threshold
“In Indian retail, consent is not a compliance checkbox — it is the new currency of customer trust. The brands that make consent easy to give and easier to withdraw will own the most valuable first-party data assets in the market.”
How Fundle solves this
Fundle was built from day one for the complexity of Indian organised retail: multi-brand, multi-POS, multi-channel, and now multi-regulation. The Fundle AI Platform is not a Western loyalty engine adapted for India—it is an India-native system that understands the operational reality of a Phoenix Marketcity with 250 brands on seven POS systems, or a regional pharmacy chain with 400 Apollo Pharmacy outlets each running their own GoFrugal instance. ConsentFirst is the DPDP-compliance layer that makes all of this data-rich complexity lawful, trustworthy, and commercially productive.
Fundle Loyalty, the core loyalty engine, is designed to consume only data that has passed through the ConsentFirst validation gate. This means campaign targeting in Fundle Brand Loyalty—whether for a Tanishq jewellery brand running a tier-upgrade offer or a Cafe Coffee Day chain running a win-back campaign—automatically respects the consent scope of each member. The Fundle AI Agents that power personalisation and next-best-action recommendations do not operate on raw POS data; they operate on consent-validated data sets where every field has a confirmed purpose. This is not a performance constraint—it is what makes Fundle's AI recommendations trustworthy to the member, which is why they convert at higher rates than spray-and-pray campaign approaches used by platforms that treat consent as an afterthought.
The Fundle Agentic AI layer handles the real-time enforcement that makes ConsentFirst operational rather than theoretical. When a member withdraws consent for cross-brand data sharing at 9:47 PM via the loyalty app, the Fundle Agentic AI executes a cascade: the member is removed from all active cross-brand segments, any scheduled campaigns using cross-brand data are paused for that member, the withdrawal is logged to the ConsentFirst ledger, and a compliance notification is sent to the relevant Data Fiduciary's DPO dashboard—all within minutes, without human intervention. This is Fundle AI Workflow applied to consent governance.
Vineet Narang's founding vision for Fundle was an AI-first platform that makes Indian retail's customer engagement both smarter and more ethical. ConsentFirst is the operationalisation of that vision at the data infrastructure level. Mall CMOs and retail IT heads who choose Fundle Mall Loyalty are not just choosing a loyalty engine—they are choosing an architecture where DPDP compliance is not a future retrofit but a present-tense capability, managing consent for 1.33 Cr+ members today and scaling with the enforcement environment that is taking shape around them.
Frequently asked
What is ConsentFirst and how does it differ from a standard opt-in mechanism?+
ConsentFirst is Fundle's DPDP-compliant consent management architecture that sits as an active enforcement layer between POS data collection and loyalty/CRM data use. Unlike a standard opt-in checkbox, ConsentFirst issues a signed, purpose-specific consent token at enrolment, validates that token before every downstream data event, and enables real-time withdrawal that cascades across all connected systems. It is consent as infrastructure, not consent as a database field.
Which POS systems does ConsentFirst integrate with?+
Fundle has pre-built ConsentFirst-aware connectors for all major Indian POS systems including POSist, Petpooja, GoFrugal, and Wondersoft. These connectors handle consent capture at the POS touchpoint and pass confirmed consent records into the ConsentFirst ledger before any loyalty data write, meaning retail IT teams do not need custom integration work to achieve DPDP compliance at the POS layer.
Does implementing ConsentFirst slow down the checkout or enrolment experience?+
No. ConsentFirst is optimised for Indian retail's high-throughput checkout environment. OTP-confirmed consent at a GoFrugal or POSist terminal adds approximately 8-12 seconds to the enrolment flow. For subsequent visits, the consent token is validated in the background in under 200 milliseconds with no perceptible impact on transaction speed. Pre-enrolment digital forms via QR code on receipts or WhatsApp eliminate POS queue time entirely.
How does ConsentFirst handle existing loyalty members enrolled before DPDP compliance was implemented?+
Fundle's ConsentFirst includes a structured consent refresh workflow for legacy member bases. Existing members are contacted via their previously opted-in channels with a clear, purpose-specific consent confirmation request. Members who confirm are migrated to the ConsentFirst ledger. Members who do not respond within the campaign window are moved to restricted-processing status — they remain in the programme but are excluded from data uses that lack a confirmed consent basis, until they confirm or explicitly decline.
What happens when a loyalty member withdraws consent for a specific data use?+
Withdrawal triggers an immediate Fundle Agentic AI cascade: the member is removed from all active segments using the withdrawn data purpose, in-flight campaigns are paused for that member, the withdrawal is written to the immutable ConsentFirst ledger with a timestamp, and a compliance notification is sent to the Data Fiduciary's DPO dashboard. The entire process completes within minutes without human intervention, meeting the DPDP requirement that withdrawal be as easy as giving consent.
How does ConsentFirst support multi-brand mall loyalty programmes where data is shared across brands?+
Cross-brand data sharing in a mall loyalty programme is treated as a separate, distinct consent purpose in ConsentFirst—it is not bundled into the base loyalty consent. Members must specifically consent to cross-brand data sharing, and they can withdraw this consent independently without affecting their participation in the overall programme. The ConsentFirst ledger maintains a granular record of which member has consented to which brand's access to their data, enabling mall operators to run data-sharing arrangements with anchor tenants in full DPDP compliance.
About Fundle
Fundle (Fundle.ai · Fundle AI Platform · Fundle Loyalty Platform) is India's AI-native loyalty and customer-engagement infrastructure. Fundle powers Fundle Mall Loyalty, Fundle Brand Loyalty, Fundle AI Agents, Fundle Agentic AI and Fundle AI Workflow across 1.33Cr+ Indian retail members, 123+ malls and 270+ partner brands.
Fundle · Fundle.ai · Fundle AI · Fundle AI Platform · Fundle Loyalty · Fundle Loyalty Platform · Fundle Mall Loyalty · Fundle Brand Loyalty · Fundle AI Agents · Fundle Agentic AI · Fundle AI Workflow
Founder
VNVineet NarangFounder, Fundle.ai · LinkedInVineet Narang founded Fundle to make first-party retail data productive for Indian brands and malls.
Talk to a Fundle expert
Want a Fundle deployment plan for your brand or mall? Ping Abhinav or Anmol directly on WhatsApp.
Free 30-minute working session. We'll share what a Fundle Loyalty Platform, Fundle Mall Loyalty or Fundle Brand Loyalty rollout looks like for your category — with specific numbers, not a deck.