Mask Makers LLC has a traditional sales channel that uses an existing CPQ implementation to process orders. Customers frequently reorder previous purchases quickly and split the order into several deliveries for different locations. Additionally, these customers are given special pricing through Price Books m CPQ based on annual spending and other parameters. The customer currently makes their purchase by sending an email or calling their appointed sales representative, and then waits to receive a quote.
Mask Makers LLC wants to move away from this very manual and time-consuming process. The company wants to provide its customers with a personalized experience that is simplified and streamlined with existing special pricing visible and the option to self- serve- Mask Makers LLC would also like to deliver this within a short timeframe, as business must continue to grow.
Which design approach should a Solution Architect recommend to meet these requirements within the timeframe while adhering to best practices.
A. Implement B2B Commerce and use the CPQ B2B Commerce Connector to integrate to CPQ. Set B2B Commerce as the Product and Pricing master.
B. Implement B2B Commerce and use the CPQB2B Commerce Connector to integrate to CPQ. Keep CPQ as the Product and Pricing master.
C. Implement B2B Commerce and use the CPQ B2B Commerce Connector to integrate to CPQ. Allow bidirectional updates to Products and Pricing.
D. Implement B2B Commerce and build a custom integration to CPQ. Keep CPQ as the Product and Pricing master.
B. Implement B2B Commerce and use the CPQB2B Commerce Connector to integrate to CPQ. Keep CPQ as the Product and Pricing master.
Explanation:
📦 B2B Commerce provides the self-service storefront customers need, allowing them to reorder, split deliveries, and view personalized pricing.
🔗 The CPQ B2B Commerce Connector enables integration so that CPQ remains the pricing and product master, ensuring consistency with the existing setup for special pricing, quote logic, and rules.
✅ B allows rapid implementation by reusing the current CPQ logic, while Commerce handles the front-end experience.
❌ A is incorrect—making Commerce the pricing master adds complexity and deviates from best practices.
❌ C and D introduce unnecessary complexity or custom integration not recommended for speed or maintainability.