Showing 1 Result(s)
Salesforce cpq discount schedule editor

Salesforce cpq discount schedule editor

About 25 mins.

Set Up Volume-Based Discount Schedules

As you saw in the last unit, Salesforce CPQ can aggregate quantities from multiple records across orders to determine the right discount tier to use for a discount schedule.

For example, a cross order schedule tells CPQ to aggregate every asset that exists on the account, but AW Computing wants only those assets purchased in the last days to count. With a little work it is possible to filter which asset records are included in the aggregated sum.

salesforce cpq discount schedule editor

The first step in filtering records is to distinguish which assets have been purchased in the last days. In this example, AW Computing has diligently maintained an asset field named Purchase Date over the years. Now every asset purchased in the last days will have the custom field named Purchased This Year automatically checked, while assets older than a year will be unchecked. Now that asset records are separated into two distinct groups, it is much easier to filter which are included in aggregate quantities.

Our next challenge is to put what we know into a format that CPQ can understand. The answer key takes the form of a custom field on the quote object. So far, so good. In the first step, you created a field that distinguishes new assets from old. In the second step, you made an answer key that identifies which assets should be included in aggregate sums.

The final step is to update the Bulk Keys discount schedule to use the answer key as a way of filtering asset records by their Purchased This Year value. Now only assets purchased in the last year count toward the discount tier quantity. You can see if only new assets are included in the discount schedule by adding RFID key cards to a quote for University of Arizona, a customer who has purchased key cards two times in the past.

Excellent, you now know that only key cards purchased within the last year count toward the discount schedule tier. For this example, we used Purchase Date to drive the formula field that distinguishes one group of assets from another, but you can use any information on the asset record, making the Discount Schedule Constraint Field quite a versatile tool. By default, Salesforce CPQ uses the Quantity field on the quote line to determine which discount tier to use.

Product design question examples

Imagine this scenario: AW Computing wants to give a discount on RFID Key Cards, but it wants to base the discount on how many door locks are sold, not how many key cards are sold.

In this case, the quantity of key cards is irrelevant. Discount schedules using the Quote Line Quantity field do not support cross order functionality to aggregate quantities from asset records. Learn more close. Sign Up. Home Learn. Time Estimate. Question, feedback or help.

Marimba sound download

Learning Objectives. Note Discount schedules using the Quote Line Quantity field do not support cross order functionality to aggregate quantities from asset records.As you saw in the last unit, Salesforce CPQ can aggregate quantities from multiple records across orders to determine the right discount tier to use for a discount schedule.

For example, a cross order schedule tells CPQ to aggregate every asset that exists on the account, but AW Computing wants only those assets purchased in the last days to count. With a little work it is possible to filter which asset records are included in the aggregated sum. The first step in filtering records is to distinguish which assets have been purchased in the last days.

In this example, AW Computing has diligently maintained an asset field named Purchase Date over the years. Now every asset purchased in the last days will have the custom field named Purchased This Year automatically checked, while assets older than a year will be unchecked. Now that asset records are separated into two distinct groups, it is much easier to filter which are included in aggregate quantities. Our next challenge is to put what we know into a format that CPQ can understand.

The answer key takes the form of a custom field on the quote object. So far, so good. In the first step, you created a field that distinguishes new assets from old. In the second step, you made an answer key that identifies which assets should be included in aggregate sums. The final step is to update the Bulk Keys discount schedule to use the answer key as a way of filtering asset records by their Purchased This Year value.

Now only assets purchased in the last year count toward the discount tier quantity. You can see if only new assets are included in the discount schedule by adding RFID key cards to a quote for University of Arizona, a customer who has purchased key cards two times in the past.

Excellent, you now know that only key cards purchased within the last year count toward the discount schedule tier.

For this example, we used Purchase Date to drive the formula field that distinguishes one group of assets from another, but you can use any information on the asset record, making the Discount Schedule Constraint Field quite a versatile tool. By default, Salesforce CPQ uses the Quantity field on the quote line to determine which discount tier to use.

Imagine this scenario: AW Computing wants to give a discount on RFID Key Cards, but it wants to base the discount on how many door locks are sold, not how many key cards are sold. In this case, the quantity of key cards is irrelevant. Discount schedules using the Quote Line Quantity field do not support cross order functionality to aggregate quantities from asset records.

Learn more close. Sign Up. Learning Objectives. Note Discount schedules using the Quote Line Quantity field do not support cross order functionality to aggregate quantities from asset records.Product Catalog. Price Book. Product Bundles. Guided Selling.

Salesforce CPQ Tutorial Part 1: Install Package & Configure Templates

Product Configurator. Quote Line Editor. Multidimensional Quoting. Proposal Document Generation. Order Management. Subscriptions and Assets. Evergreen Subscriptions. Contract Amendments. Automated Renewals. Contracted Pricing. Product and Pricing Rules. Discount Controls. Conditional Quote Terms.

Usage Pricing and Quoting. Advanced Order Management. Advanced Approvals. Invoice Scheduler.About 30 mins. Why get a single roll of paper towels when you can get 40 at a nice discount? Businesses offer these quantity-based discounts to encourage larger deals, but it can be a challenge for sales reps to keep track of how much they should discount for given quantities.

Salesforce CPQ can automatically apply the right volume-based discount for each specific deal by using a tool called Discount Schedules. You can think of a discount schedule as a table of quantities and percentages. Notice that the discount schedule uses 60 for both the upper quantity of the first tier and the lower quantity of the second. This can seem odd, but it makes sure there are no gaps for fractional quantities to fall through.

Specht modules for weyl groups

If the upper quantity of the first tier was 59, then Customers typically buy enough cards for their employees and to have extras on hand. Now that we have our discount schedule and discount tiers created, we just have to tell Salesforce CPQ that we want to use the discount schedule whenever the RFID Key Card product is added to a quote.

Hovering over the icon pops open an overlay to show the Discount Schedule details. As a side note, you can also include information about the discount schedule right in the proposal so your customer knows what a deal they can get for buying more. One last thing about our new Bulk Keys Discount Schedule. While we only applied it to the RFID Key Card, the Discount Schedule record itself is not specific to any product, so we can use it again for another product.

A single Discount Schedule can be applied to any number of products, making them a versatile tool in quote pricing.

Now, every time key cards are added to a quote, the discount schedule is in effect. But what if AW Computing only wants the discount schedule to apply when key cards are sold in a specific bundle? Salesforce CPQ supports this scenario too—Product Option records in bundles have their own discount schedule lookups. The administrator just needs to remove the Bulk Keys Discount Schedule from the Product record and update the Option record for the bundle.

salesforce cpq discount schedule editor

There are even more objects that have Discount Schedule lookups, allowing administrators to apply volume-based pricing in very targeted ways.

Since discount schedules can be applied in so many different places, there are times when there can be a quote line that qualifies for two or more discount schedules. Only one schedule can be used for volume-based pricing of a quote line, so Salesforce CPQ chooses the one from the object with the highest priority. As you can see in the table above, Contracted Price has the highest priority, so CPQ uses that discount schedule.

Sometimes businesses use different price books to control pricing for certain types of customers. For example, they can have a price book specifically for academic institutions. By default, discount schedules apply to all quotes, regardless of which price book is used. However, it is possible to identify price books that should not use a given Discount Schedule.

From now on, quotes including that price book will stop using it. These two lookup fields are always used together and cause the discount schedule to apply only when the specified product is added to a quote that uses the specified price book.

Additionally, be aware that a discount schedule set up this way overrides the Discount Schedule lookup field on the Product record. That said, it still has the lowest priority when compared to other places discount schedules can be applied. For example, a discount schedule used for a contracted price still takes priority over a product and price book-specific schedule. Now you know how to create discount schedules and where to use them. Next, we look at how to adjust the way discount schedules count quantities when determining which discount tier to use.

Learn more close. Sign Up. Home Learn. Time Estimate. Question, feedback or help.About 10 mins.

salesforce cpq discount schedule editor

This seems straightforward, but what happens if the cards are split across two quote lines of 75 each? Will they still get a discount? What if 60 of those cards were included free of charge as part of a bundle? Now what? The answer to these questions depends on the settings of the discount schedule. Salesforce CPQ supports many ways to count or exclude quantities when determining the correct discount tier. One of the most important discount schedule settings is the Aggregation Scope field.

This tells CPQ how to handle multiple quote lines that share the same discount schedule. There are three possible choices for Aggregation Scope.

Optional items are meant to show customers what is possible, not what they actually get. Then, the sales rep sells the Security Console bundle with key cards, and also adds extra key cards as a separate line, as seen below. Even if the aggregation scope of the discount schedule is set to Quote, only the quantity of the bundled key cards is counted. Therefore the bundled quote line only qualifies for the — tier discount, ignoring the extra key cards.

If you want the stand-alone key cards to aggregate with the bundled key cards, you must add the Bulk Keys discount schedule to the product record of the RFID Key Card. Some bundled products are included free of charge due to the Bundled checkbox on the product option.

By default, the quantities of these free products are not included in discount schedule calculations. If you need them to count toward a discount, check the Include Bundled Quantities checkbox on the Discount Schedule record. They want customers to get the same volume discount on key fobs as they do key cards, so they reuse the Bulk Keys discount schedule on the Key Fob product record.

This seems to work well until a sales rep realizes that when both products are sold on the same quote, the quantities are considered independently. They ask their CPQ admin if the volume discount can be applied to the total amount of cards and fobs combined—this is called cross product aggregation. Just check the field named Cross Products on the Discount Schedule record.

Override Volume-Based Discounts

Then, this week, the customer comes back to buy 50 more key cards. By default, CPQ treats each quote independently.

Zksoftware adms download

However, your discount schedule can be configured to count the amount of products sold in previous sales. All you have to do is check the Cross Orders field on the Discount Schedule record. Asset records are created automatically during the CPQ contracting process, so the information is there when needed. Note that Cross Orders only affects the price of the key cards on the current quote. Be aware that Cross Orders uses all assets records a customer has when aggregating the total quantity to use for the discount schedule.

This includes assets that were bought years ago! We look at how to handle this situation in the next unit. Learn more close. Sign Up. Home Learn.Environ 25 min. However, some businesses need to discount by a defined amount instead of a percentage. To use a fixed amount instead of a percentage for a discount schedule, set the Discount Unit field to Amount. If your org is configured to use multicurrency, discount schedules that use amount-based discounts require discount tiers for each currency.

In the screenshot above we can see how a sales rep can create a completely new, third tier for the Bulk Keys discount schedule. When sales reps save changes in the discount schedule editor, a clone of the original discount schedule is saved and used only for this one quote. The source discount schedule remains untouched. Cloned discount schedules have a lookup field to the original in case sales reps want to revert. They also have lookups to the quote and account records.

Lastly, they have a checkbox field named User Defined that is checked, making it easy to identify custom discount schedules. The field named Override Behavior, found on the Discount Schedule record, controls if sales reps can modify discount tiers. It has has three choices.

Configure Quantities for Discount Schedules

Sales reps should also be trained how to add discount tiers properly. If the lower bound of a tier is not equal to the upper bound of the next tier, an error message appears.

Instead of applying a single discount percent to all units, the cards are divided into three slabs:, and The first slab has no tier defined, so gets no discount. Slab discount schedules are perfect for when you need different price-per units for each tier. If we used the Range type, then no units are discounted because there is no tier for five units. This is just one example of many clever ways to leverage Slab discount schedules. Slab discount schedules do not work with cross products. If you add 30 key cards and 80 key fobs to a quote, you get units overall.

With Slab, only 10 units get discounted. But which units get the discount, key cards or key fobs? Discount schedules are helpful because you can precisely define quantities that deserve specific discount amounts.

This is a way of having a different discount percent for every possible quantity. Compound discounts are calculated using a mathematical function where we define one parameter. When the function is graphed we see something like this:. If we look at 1 unit, the multiplier is exactly 1. In other words, the unit is full price. If the quantity is 2, the multiplier is about 0. Move over to a quantity of 6 and the multiplier is about 0. Every quantity has its own multiplier which never reaches zero, even at huge quantities.

Salesforce CPQ plugs in the value from the Compound Discount field on the product, does the math, then automatically adjusts the regular price. Both compound discount and discount schedules affect regular price, but only the compound discount applies if both are used at the same time. Good job making it through the math-heavy portion of this module!

Now you know just how powerful volume-based discounts can be. In the next unit, things get easier as we see how sales reps can apply discounts manually. Learn more close.About 10 mins. Partners and distributors often get extra discounts when they sell products on your behalf, separate from the discounts meant for the customer.

These kinds of discounts are referred to as channel discounts. Salesforce CPQ accounts for channel discounts by keeping track of them in separate quote line fields: Partner Discount and Distributor Discount. Either way, both fields play a role in the price waterfall. It works the same way. This locks the field in the Quote Line Editor, and prevents the quote line from inheriting the partner discount from the quote.

Because of the way the price waterfall processes channel discounts, the overall amount of the partner discount gets smaller with every prior discount, and the amount of Distributor Discount is reduced even further than that. Some businesses want the amount of partner and distributor discounts to reflect a percent of the List Price, which is unaffected by volume and manual discounts. This results in larger discount amounts when deducted near the end of the Price Waterfall, as we see in the right of the diagram.

Using half of the List Price makes the Partner Price significantly smaller. Administrators can control which way channel discounts are handled. Also, in the future if you need to toggle between the two waterfalls, you can do so by replacing the 1 with a formula that considers outside conditions to return either 0 or 1. Partner discounts are usually handled very late in the price waterfall, making the discount apply after customer-focused discounts like Additional Disc.

But what if your business needs partner discount to occur earlier so partner pricing is adjusted before volume and manual discounts are recognized? Using another special field, administrators can make that happen too. The yellow circles are for the Partner Discount—the biggest difference here is whether the discount is applied before or after the special price is calculated. Surprisingly, when setting partner discounts first, cost plus markup pricing is ignored, and CPQ deducts the partner discount directly from the list price.

CPQ knows to deduct the distributor discount straight from the customer price to get net price, as if the partner price never existed. This is not supported, and will likely result in incorrect price calculations. This last price waterfall adjustment is indirectly related to channel discounts by moving customer price to after net price. In this table, we see the price waterfall before and after the change. Customer price always contains the result of manual discounts, so moving it to the end makes manual discounts apply after channel discounts, instead of before.

Since Customer price is no longer above partner price, CPQ changes the partner price calculation to use regular price. Moving customer price is done in a similar manner to the previous two adjustments.