Open APIs

 View Only

TMF658 Loyalty vs TMF671 Promotion: Which API should be used when the outcome is a reward?

  • 1.  TMF658 Loyalty vs TMF671 Promotion: Which API should be used when the outcome is a reward?

    Posted 5 hours ago
    Edited by Ajay Saini 5 hours ago

    Hi everyone,

    I am trying to understand the use of TMF658 Loyalty Management vs TMF671 Promotion Management for a rewards use case.

    For example, we have the following scenarios:

    1. Customer performs their first payment → 50 coins

    2. Customer performs their first recharge → 50 coins

    3. etc

    In all cases, the outcome is a reward/coins being credited to the customer.

    My question is:

    Should these use cases be modeled using TMF658 Loyalty Management or TMF671 Promotion Management?

    I understand that TMF658 contains concepts such as:

    LoyaltyProgramProductSpec
       -
    LoyaltyRule
       ├── LoyaltyEventType
       ├── LoyaltyCondition
       └── LoyaltyAction
              ↓
          LoyaltyEarn
              ↓
          LoyaltyBalance

    While TMF671 contains concepts such as:

    Promotion
       ↓
    PromotionPattern
       ├── PromotionCriteria
       └── PromotionAction
              ↓
         Bonus Point / Reward

    So I am trying to understand the boundary between the two APIs. Should all reward-generating rules be modeled in TMF658 because the final outcome is a loyalty reward/coin balance?

    Conversely, when should a reward-generating use case be considered a Promotion rather than a Loyalty Rule?

    I would particularly appreciate guidance on the TM Forum intended semantic distinction between:

    • LoyaltyRule in TMF658

    • PromotionCriteria / PromotionPattern / PromotionAction in TMF671

    and how they should be used when both ultimately result in a customer receiving coins/rewards.

    Thanks in advance.



    ------------------------------
    Ajay
    ------------------------------