Hope that this was not answered before, but couldn't find the same scenario: We are currently trying to expose prices via the POQ API qualification response. So far I've identified two ways to do so. First one would be the most straightforward, which is using ProductOfferingRef pointing to our Product Catalogue resource where the standard prices reside.But, sometimes the prices are "dynamic" or, more specifically, based on a customer specific contract or agreement. For this case, we are fetching prices from other APIs that provide the pricing information for those specific cases where a customer has a special price negotiated. To me, it seems that ProductOfferingRef is not the adequate place to put the price... I've checked also the ProductRefOrValue, but to be honest I still struggle to understand the differences between that resource and ProductOfferingRef. This one I see it has Pricing resource linked to it tho...What would be your suggestions or how would you overcome the situation? Is it okay to just extend the API specification or should another API take the role for this scenario?Thanks a lot in advance for your help!
Okay, maybe it is because I'm still quite "new" to the Telco/TMForum world haha, but could you give me an example/elaborate a bit more on what would be the difference between a Product and a Product Offering?
Again, thanks a lot for your help!