Open APIs

Hi Community, I'm back with one more question.

I've seen many CSPs rolling out offers like `Get 5GB extra data (A) for 3 months if you buy this "Amazing Max" plan (B)` during the Easter break (10/4/2025 to 17/4/2025). "Amazing Max" is a bundle that contains unlimited mins/texts (X), phone insurance (Y), unlimited MMS (Z). I was trying to see how to model this in the product catalog. 

A:

  ProductOfferingTerm: 3 months

  data allowance characteristic: 5GB

B:

  bundledProductOffering: [X, Y, Z]

  productOfferingRelationship:

    type: includes

    id: A

    validFor: (10/4/2025 to 17/4/2025)

Is this a good way? or should I include 'A' also in the bundledProductOffering? or is there any other way that's recommended?

------------------------------
Manu
------------------------------

Any recommendations about this approach or any alternate approaches?

------------------------------
Manu

Original Message:
Sent: Feb 27, 2025 20:16
From: MMH HH
Subject: Supporting limited time promotional offer with data bundles

Hi Community, I'm back with one more question.

I've seen many CSPs rolling out offers like `Get 5GB extra data (A) for 3 months if you buy this "Amazing Max" plan (B)` during the Easter break (10/4/2025 to 17/4/2025). "Amazing Max" is a bundle that contains unlimited mins/texts (X), phone insurance (Y), unlimited MMS (Z). I was trying to see how to model this in the product catalog. 

A:

  ProductOfferingTerm: 3 months

  data allowance characteristic: 5GB

B:

  bundledProductOffering: [X, Y, Z]

  productOfferingRelationship:

    type: includes

    id: A

    validFor: (10/4/2025 to 17/4/2025)

Is this a good way? or should I include 'A' also in the bundledProductOffering? or is there any other way that's recommended?

------------------------------
Manu
------------------------------

Hi,

For controlling the benefit duration, I would consider, in that order:

1. use product Terms as you suggested

2. Add new attribute via @schemaLocation: applicationDuration on the ProductOffering resource.

This attribute already exists under PriceAlteration and its behaviour (alter the normal price for a set duration) is exactly what you're doing here: you alter the normal data allowance for a set duration. I have used this approach for a long time.

    " applicationDuration": {
      "amount": 3,
      "units": "month"
    }

3. Use a policy to support your scenario.

for product modelling, I would consider, in that order:

1. Model the 5GB benefit as an atomic product offer (same prodSpec as the baseline data PO)
   1. bundle it or use a relationship or use a promotion to sell them together for the duration of the "Easter campaign".

I would NOT consider use a single data product with 2 characteristics:

1.  normal allowance and bonus allowance. One overrides the other

Any recommendations about this approach or any alternate approaches?

Hi Community, I'm back with one more question.

I've seen many CSPs rolling out offers like `Get 5GB extra data (A) for 3 months if you buy this "Amazing Max" plan (B)` during the Easter break (10/4/2025 to 17/4/2025). "Amazing Max" is a bundle that contains unlimited mins/texts (X), phone insurance (Y), unlimited MMS (Z). I was trying to see how to model this in the product catalog. 

A:

  ProductOfferingTerm: 3 months

  data allowance characteristic: 5GB

B:

  bundledProductOffering: [X, Y, Z]

  productOfferingRelationship:

    type: includes

    id: A

    validFor: (10/4/2025 to 17/4/2025)

Is this a good way? or should I include 'A' also in the bundledProductOffering? or is there any other way that's recommended?

------------------------------
Manu
------------------------------

Thank you for the response, Matthieu. You're an invaluable contributor in these forums.

Hi,

For controlling the benefit duration, I would consider, in that order:

1. use product Terms as you suggested

2. Add new attribute via @schemaLocation: applicationDuration on the ProductOffering resource.

This attribute already exists under PriceAlteration and its behaviour (alter the normal price for a set duration) is exactly what you're doing here: you alter the normal data allowance for a set duration. I have used this approach for a long time.

    " applicationDuration": {
      "amount": 3,
      "units": "month"
    }

3. Use a policy to support your scenario.

for product modelling, I would consider, in that order:

1. Model the 5GB benefit as an atomic product offer (same prodSpec as the baseline data PO)
   1. bundle it or use a relationship or use a promotion to sell them together for the duration of the "Easter campaign".

I would NOT consider use a single data product with 2 characteristics:

1.  normal allowance and bonus allowance. One overrides the other

Any recommendations about this approach or any alternate approaches?

Hi Community, I'm back with one more question.

I've seen many CSPs rolling out offers like `Get 5GB extra data (A) for 3 months if you buy this "Amazing Max" plan (B)` during the Easter break (10/4/2025 to 17/4/2025). "Amazing Max" is a bundle that contains unlimited mins/texts (X), phone insurance (Y), unlimited MMS (Z). I was trying to see how to model this in the product catalog. 

A:

  ProductOfferingTerm: 3 months

  data allowance characteristic: 5GB

B:

  bundledProductOffering: [X, Y, Z]

  productOfferingRelationship:

    type: includes

    id: A

    validFor: (10/4/2025 to 17/4/2025)

Is this a good way? or should I include 'A' also in the bundledProductOffering? or is there any other way that's recommended?

------------------------------
Manu
------------------------------