Forced Unification of Multiple FMCG Sub‑Brand Marketing Systems: Chaos or Incremental Identity Platform Solution

Identity Middle Platform (IMP) Overview

IMP is a digital identity infrastructure for brand owners that provides standardized API/SDK services for anti‑counterfeit, channel control, scan‑based marketing, and production collaboration.

Problem: Multiple Sub‑Brands, Isolated Marketing Systems

Large FMCG groups often let each sub‑brand run its own marketing system, creating “siloed” data, high operational costs, and compliance risks. Forcing a single new system can interrupt ongoing campaigns, cause sales drops, and provoke strong resistance from sub‑brand teams.

Why Identity Is the Key Entry Point

Every marketing activity originates from a code ("identity"). By unifying the "code issuance right" instead of replacing all downstream systems, a group can centralize data collection while leaving existing brand‑level workflows untouched.

Three Fatal Flaws of a One‑Size‑Fits‑All System Unification

Business continuity breaks, directly hurting sales.

Data assets and mature activity playbooks are lost, resetting user value to zero.

Organizational resistance turns the new system into a low‑adoption "showpiece".

Four Systemic Risks of a "Let‑It‑Be" Approach

Decisions lack data support; budget allocation becomes guesswork.

Repeated construction inflates total cost of ownership.

Cross‑brand collaboration is difficult, missing opportunities for traffic reuse.

Inconsistent data definitions raise compliance and audit risks.

Proposed Incremental Solution: "Collect Code Rights, Retain Systems"

The core logic is to centralize code generation in IMP while allowing each sub‑brand to continue using its own marketing system for activity configuration, redemption, and reporting. This avoids the three fatal flaws and reduces resistance.

Four‑Step Practical Guide

Standardize Coding Rules : Define code structure, length, usage categories, status, and approval processes so that all codes generated by IMP are recognized by any sub‑brand system.

Collect Issuance Rights Without Taking Over Systems : Sub‑brands request codes via a standardized API; IMP generates compliant codes and forwards them to packaging factories, while the sub‑brand handles downstream activity execution.

Build a Unified Data Dashboard : Scan data first passes through IMP, where it is cleaned, transformed, and aggregated. The unified view feeds ERP, CRM, and finance systems, enabling real‑time monitoring of scan volume, user distribution, redemption rates, and expense usage.

Consolidate Shared Capabilities : Gradually migrate common services—identity authentication, points management, prize pool, risk engine—into IMP, creating a shared‑service center that sub‑brands can call, reducing duplicate development.

Benefits of the Incremental Approach

Real‑time, group‑wide metrics provide accurate data support for budgeting and strategy.

Unified code procurement creates scale economies, sharply lowering overall TCO.

Standardized data enables cross‑brand campaigns and traffic reuse.

Consistent coding standards and audit trails reduce compliance risk.

Conclusion

For FMCG groups facing the dilemma of multiple sub‑brand marketing systems, a forced "one‑size‑fits‑all" overhaul or a laissez‑faire stance are both suboptimal. The "collect code rights, retain systems" incremental identity unification captures the core "code" data point with minimal intrusion, preserving sub‑brand continuity while delivering group‑level data governance, cost savings, and shared capabilities, paving the way from data unification to capability and business unification.