Multi-attribute Pricing

pricing attributes can be used to determine variations of pricing for a specific product common pricing attributes include currency (e g usd, cad, rmb) unit of measure (e g user/year, user/month) region (e g uk, united states) partner level (e g silver, gold platinum) account type (e g enterprise, strategic) a list price can be defined by a combination of pricing attributes for example, the list price for an iphone 11 in the united states is 1000 usd, but is priced as 900 euro when sold in france in this example, the region (united states, france) and the currency (usd, euro) determined the list price nue’s multi attribute pricing feature allows you to define any number of combinations of attributes to define a price we will walk through how you can define these multi attributes we will first start with understanding the object model \# object model to support multi attribute pricing, nue creates a ‘shadow’ product with a record type of ‘multi attributes’ this allows one product to have more than one price book entry within a price book it is similar to how salesforce supports multi currency for one product let’s walk through the example below in the above nue configuration, there are two price book entries for the ‘bundle builder’ product in the standard price book uom of user / month, price = $3 uom of user / year, price = $30 this creates two corresponding product records (see below) one has a product record type of ‘product’ and the other ‘multi attributes’ the product code and sku are auto generated for the ‘multi attributes’ type, since they will only exist with their corresponding record of ‘product’ record type additionally, two corresponding price book entries are created for each list price the multi attributes products are not visible at operation time (e g quotes, orders, subscriptions, etc ) since they only exist to allow nue to create multiple price book entries for a single product in the nue app, you will see the logical list of products, price book entries, etc in essence, we are using salesforce as the database, and nue is the logical layer on top of it \# multi attribute pricing this section will walk through the steps in creating multi attributes for pricing there are two options in creating multi attribute pricing prices based on unit of measure prices based on attributes on the account, opportunity, quote, etc (any object related to the quote and order) \# price based on uom every product and bundle must have at least one list price this list price is based on a default unit of measure the first step in defining a price is to define the unit of measure this is done in nue → price builder → uoms define each uom that you are planning to use for pricing next, create a new product or bundle the list price is defined on the last step continue to add a ‘new list price’ for each uom \# price based on multi attributes \# # step 1 define pricing attributes to define multi attribute pricing in nue, login to the nue app and navigate to settings → pricing attributes nue allows you to define up to 10 different pricing attributes click on the edit icon next to the first pricing attribute, and you will get the following pop up a pricing attribute can be mapped to an object field the object types available to be selected include customer order quote opportunity any objects related to the quote or order object fields are limited to the following types picklist checkbox formula (checkbox) here is an example of a common attribute used in pricing the account type field on the account object can be used to determine pricing the different picklist values for the account type (customer direct, customer channel, channel partner / reseller, etc ) is used to define different list prices note if you want to create a pricing attribute that maps to a custom field on quote or order object, or a custom field on a custom object related to quote or order object, please add the custom field on both quote or order object, or the same custom object related to both quote or order nue handles pricing attributes on quote and order in the same way if you only define the custom attribute on quote or order, but not both, the custom attribute will not be available for binding to the pricing attributes \# step 2 create the price book when creating a price book, you can add one or more custom pricing attributes to a price book there are two attributes that are defaulted in the price book, currency and uom you cannot remove these pricing attributes in the nue ui as they are considered standard pricing attributes navigate to the nue app → price builder → price books and click on new price book click on the pricing attributes at the bottom of the screen, and select the newly added pricing attribute for account type remove a pricing attribute from the price book if you need to remove a pricing attribute from the price book, there are some rules to follow you cannot remove currency and uom pricing attributes from the nue ui these are standard pricing attributes a custom pricing attribute may only be removed from a price book if it is not referenced by any pricing book entry when you remove a price book attribute by clicking on ‘x’ on the pricing attribute that is currently being referenced by one or more price book entries, you will receive the following alert message when there are no price book entries related to the pricing attribute, you can remove the pricing attribute label, and click ‘save’ to save the changes \# step 3 define the multi attribute list prices now that you’ve created your price book, you can begin to create your products and define list prices based on those attributes create a new product or bundle in nue in the last step ‘prices’, select the price book that you defined in the previous step the multi attributes should be visible so that you can select the appropriate value for each list price in the example below, account type is a multi attribute that can be used to drive different list prices \# use custom fields of price book entry as pricing attributes optionally, users can use custom fields of price book entry object as pricing attributes for example, the company is selling a device with the following price book entries having 2 custom attributes storage and is early access customer the prices are defined as in the following table product currency storage early access customer price smart device usd 16gb yes $100 smart device usd 128gb no $500 smart device usd 16gb no $110 smart device usd 128gb no $550 each combination of storage and is early access customer drives a different price at quoting time, sales reps would like to browse the prices of all combinations of storage and is early access customer to address this scenario, users can simply create custom fields on the price book entry object, and enable them as pricing attributes to use custom fields from the price book entry object as pricing attributes, follow these steps create custom fields in the price book entry object in salesforce add these custom fields to the " fields exposed to nue " field set, as well as " product search columns " field set go to nue → settings → business objects and click 'sync custom fields from salesforce' button please note please make sure the integration user has view and edit access to the custom fields before syncing the custom fields over to nue, otherwise, you may run into issues when using the custom fields as pricing attributes in nue later navigate to nue → settings → pricing attributes in the "use custom fields as pricing attributes" section, check the checkboxes of both custom attributes, as shown in the image below after following these simple steps, the custom fields can be utilized as pricing attributes, just like any other pricing attributes however, please be aware of the differences when using the custom fields from the price book entry as pricing attributes compared to other pricing attributes these custom attributes do not need to be explicitly marked as pricing attributes in any price books—they are implicitly available as pricing attributes when users edit list prices in a price book, these custom attributes will appear after regular pricing attributes but before other custom attributes, all suffixed with "($)" to indicate that each combination of the pricing attributes requires a unique price book entry when creating quotes, users will see the price book entries for all possible combinations of custom attributes used as pricing attributes, with no context matching required