Tailoring the MSCRM Product Catalogue

The MSCRM Product Catalogue is a multi-talented area of functionality – capable of tracking different Units of Sale for Products and from there related Units Groups and Discounts.

MSCRM Product Catalogue ERD

Product Catalogue ERD for Dynamics CRM

However this area of functionality often hits difficulties between either being too basic for Companies that have a product-based business model (such as manufacturing) and too needlessly complex for Companies offering a more simple bespoke Product Pricing business model.

For the first point, there are various software extensions and Quoting Tools available to extend the MSCRM Product Catalogue to support Product Features, optional extras and quoting rules for building a final customer price – this will be a topic for a different blog post maybe.

On the second point however often I encounter clients who like to simplify the process of building a Quote or Opportunity within MSCRM, and would like to remove some of the offered functionality of the Product Catalogue.

The following set of blog posts is a rolling series on various techniques to customise the relevant MSCRM entities to support this simplified use of the Product Catalogue. The posts aim to offer a step by step guide on how to build this simplified version of the Product Catalogue – this is not intended as a solution that will fit every business model but moreso as a how-to guide that contains several useful pieces of functionality that may be helpful in some MSCRM projects.

1. Defaulting the Opportunity Price List

2. Adding Opportunity Products

3. Overriding the Product Catalogue to allow for bespoke pricing

4. Showing the list of Products for an Opportunity or Quote

5. Hiding the Write-in Products Area

6. Mapping fields from Opportunity Product to Quote Product records

7. Managing Tax Codes in MSCRM

Customising MSCRM to include Tax Codes

Assigning Tax Codes via the MSCRM Child Pipeline

2 Responses to Tailoring the MSCRM Product Catalogue

  1. Pingback: Tailoring the MSCRM Product Catalogue | CRM Consultancy Blog

  2. ryancdorn says:

    I’m having trouble with unit groups… it seems like this should be a common scenario but I haven’t been able to find any information on it. My company sells bulk products that are frequently packaged in drums, totes, supersacks and other large containers.

    So we may have a 500lb drum SKU. When we talk to our customers all of the discussions are in price per lb, price per kg or price per gallon so I want sellers to view pricing guidance and enter prices in those terms. I see three options theat each have drawbacks, I’m hoping you can advise what the best practice to manage this scenario is.

    Option 1
    Set up 1 lb as the default unit then make a drum unit with a qunatity of 500. If I do that, how do I avoid a situation where a sales rep quotes a quantity of 300lbs when the quantity really must be a multiple of 500 because we can’t sell part of a drum?

    Option 2
    Set up a 500lb drum be the base unit then create a lb unit with a quantity of .002? I’m worried if I do the latter precision will become an issue because of rounding.

    Option 3
    Set up a 500lb drum as the base unit then add a net weight attribute and a specific gravity attribute to the product and use workflows to calculate a drum price based on the user submitted the price per lb, per kg and per gallon….


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s