ABC Telecom uses Communications Cloud while its distributors use their own CRM system. ABC Telecom wants to share product catalog information, including technical descriptions of products from ABC Telecom's Communications Cloud. Distributors can then use this information to set up their own CRM product catalog.
What should a Consultant suggest as a starting point for this integration?
In Communications Cloud, the single source of truth for commercial and technical products is the Enterprise Product Catalog (EPC). For external systems---like distributors' CRMs---to consume product specifications, offerings, attributes, technical details, and bundled components, Salesforce provides EPC REST APIs.
These APIs expose:
Product Offerings
Product Specifications
Commercial & technical attributes
Prices (optional depending on configuration)
Relationships and hierarchies
They are designed explicitly for external catalog synchronization, making them the ideal starting point for distributors to pull up-to-date product definitions.
Why others are incorrect:
A (Product2 APIs): Product2 is not used for Communications Cloud catalog; EPC uses Vlocity EPC objects.
B (TMF620): Salesforce EPC is not natively TMF620 compliant. TMF620 requires a mediation layer; using EPC APIs directly is the recommended starting point.
D (getCartProducts): CPQ APIs require a cart context and do not expose full catalog specs.
Dierdre
9 days agoLoreen
14 days agoAlbert
19 days agoLenna
24 days ago