Confirmation about Pricing conditions for bundles

(1) Share

Report

Posted on by CU05111420-0

Hi everyone.

The organization I'm configuring Dynamics Sales for, has the following strategy:

Each product can be sold separately
Products can be associated with a bundle, which has its own price
Products can be removed from bundles in the context of an opportunity
Bundles should keep their price regardless of the items within. If I remove products from the bundle (in the context of an opportunity), the overall price of the bundle should be kept.

I think condition 3 and 4 go against each other, in regard to the OOTB behavior of the tool. In particular, condition 1 requires me to define a price for each product. However, if I set such products as required in the bundle I'm not allowed to remove them in the context of the opportunity. If instead I set them as optional, their single price is added to the bundle price.

I also fear that such "optional" price appears in the document I need to generate, while my requirement would be to show every price at 0 except for the bundle one.

Do you confirm I need to set all products as optional in the bundles and setup a custom price engine for the E2E Opportunity to Order chain of entities to skip adding up of optional products price?

Thanks

Categories:

Dynamics 365 Sales

All responses (2)

Answers (1)

Verified answer

Saif Ali Sabri 370 on at

Like (0)

Report
Confirmation about Pricing conditions for bundles

Your analysis is accurate. Out-of-the-box (OOTB) Dynamics 365 Sales currently handles optional products within bundles by adding their individual prices to the bundle’s total, which conflicts with your need to maintain a fixed bundle price regardless of included items.

To achieve your pricing and document requirements, you'll indeed need a custom solution. Setting products as "optional" within the bundle lets you remove them in opportunities, but their prices will aggregate with the bundle’s, affecting both the displayed price in the opportunity and any generated documents.

Defining each product’s price (condition 1) is straightforward, but including them as required products in bundles limits their removal in an opportunity, conflicting with condition 3. Conversely, marking products as optional allows their removal but introduces the issue of their prices being added to the bundle price, which conflicts with conditions 3 and 4.

For document generation, where only the bundle price should be visible, setting products as optional may result in displaying their individual prices, which you want to avoid.

To address this, implementing a custom price engine is indeed a suitable approach. Here’s how it could help:

Control the Opportunity Pricing Logic: The custom pricing engine can override the default behavior, allowing you to skip the sum of optional product prices in the bundle, so the bundle maintains its fixed price.

Document Customization: You could customize the document generation process to exclude optional product prices, ensuring that only the fixed bundle price appears.

Here’s a high-level approach:

Custom Pricing Engine: Implement a custom pricing engine that overrides the default behavior during the Opportunity to Order process. This engine would set the price of optional products to zero within the bundle context, ensuring only the bundle price is considered.

Custom Document Generation: Use a custom document generation solution to control how prices are displayed. The custom engine can prevent optional product prices from appearing or being added in any documents, displaying only the bundle price as required.

This setup would give you the flexibility to meet all four conditions in the Opportunity-to-Order process.
Suggested answer

Daivat 998 on at

Like (1)

Report

Confirmation about Pricing conditions for bundles

Hello CU05111420-0,

You've correctly identified a potential conflict between your business requirements and the standard behavior of Dynamics 365 Sales. The challenge lies in reconciling the need for flexible bundle composition with maintaining a fixed bundle price.

Here are a few potential strategies to address this:

1. Custom Price List and Product Configuration
Create a Custom Price List: Define a specific price list for bundles where the bundle price is the only relevant price.
Configure Products: Set up products as optional within bundles.
Custom Price Calculation Logic: Implement custom logic, either through a plugin or workflow, to calculate the total price of an opportunity based on the selected bundle and its fixed price, regardless of the individual product prices.

2. Use a Third-Party Solution or Customization
Consider a Third-Party Solution: Explore third-party solutions that offer more flexibility in pricing and configuration.
Custom Development: If necessary, custom development can be used to create a more tailored solution to meet your specific requirements.

Key Considerations
Data Validation: Implement validation rules to ensure that bundle prices are accurately calculated and maintained.
User Interface: Consider customizing the user interface to provide clear information about bundle pricing and product options.
Testing: Thoroughly test any customizations or integrations to avoid unexpected behavior.

While the standard Dynamics 365 Sales behavior may not directly align with your requirements, these strategies can help you achieve the desired outcome.

It's important to consult with a Dynamics 365 expert or partner to assess the feasibility and complexity of implementing these solutions. They can provide tailored guidance based on your specific business needs and technical capabilities.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more.
If you have further questions, please feel free to contact me.

Best Regards,
Daivat Vartak