Avoid FMCG Marketing Pitfalls: Managing Parallel Campaigns to Protect Cost Baselines

Identity Middle Platform (IMP)

IMP provides a standardized API/SDK layer for brands to manage digital identifiers that support anti‑counterfeiting, channel control, scan‑based marketing, and production collaboration.

Problem: Overlapping FMCG Campaigns

Fast‑moving consumer goods (FMCG) often run multiple promotions on the same product. A liquor bottle may be part of a national New‑Year red‑packet campaign, a regional distributor rebate, and a store‑level incentive simultaneously. Without clear code‑management rules, the same code can be redeemed by more than one system, leading to duplicate payouts and consumer complaints.

Concrete example : During a national scan‑to‑receive‑red‑packet campaign, an East‑China regional system also reserved the same bottle code for its own prize. Both systems issued a red‑packet, causing hidden financial loss and brand‑reputation damage.

Three Core Actions

Validation (check availability) – Query a code’s authenticity and current state without changing it.

Reservation (temporary hold) – Lock a code for a specific activity with a time‑to‑live (TTL), e.g., 24 hours. If the consumer does not complete the claim within the TTL, the reservation expires and the code becomes available to other campaigns.

Consumption (final transaction) – Issue the prize and mark the code as permanently used. Only consumption triggers expense recognition.

Key distinction: reservation does not equal consumption; treating a reservation as a cost creates “double‑spending”.

Four‑Step “One Code, One Activity” Logic

Batch Assignment – Allocate separate code batches to each campaign (e.g., batch A for the national promotion, batch B for the regional activity) to avoid source‑level collisions.

Code Identity Segmentation – Split codes into “inner” (marketing) and “outer” (anti‑counterfeit) layers. The outer layer is used only for authenticity checks; the inner layer participates in prize‑winning flows.

Reservation Rules – Apply a first‑come‑first‑served policy with a TTL (commonly 24 hours). The first system that successfully writes a reservation wins the prize; subsequent systems receive a “code already reserved” response.

Consumption as the Only Cost Trigger – Record expense only when a prize is actually delivered (consumption). Financial reconciliation should count only consumed codes.

Typical Scenarios and Mitigation Guides

Scenario 1 – National + regional overlap : Set a 24‑hour reservation TTL for the regional activity. If the regional claim is not completed, the reservation expires and the code can be used by the national campaign.

Scenario 2 – Multiple marketing systems scan simultaneously : All systems can read the code state, but only the first to write a reservation can award the prize (“read‑first, write‑wins”).

Scenario 3 – Emergency campaign shutdown : Freeze the associated code batch. Unconsumed codes become instantly unavailable, while consumed codes remain for audit.

Three Iron Rules for FMCG Code Management

One Code, One Activity : A code belongs to only one campaign at any time.

Reservation ≠ Consumption : Reservation is a temporary hold; only consumption counts as a cost.

End‑of‑Campaign Recovery : Use TTL‑based reservation expiry plus batch freezing to release or lock unused codes, preventing waste and cost leakage.

Conclusion

By enforcing validation, reservation, and consumption as distinct steps and by applying batch assignment, identity segmentation, and TTL‑based reservation, FMCG brands can eliminate “one code, multiple rewards” situations, ensure accurate expense accounting, and protect brand reputation.