Hi Guy,
The main function of the product catalogue is to enable a price to be calculated on opportunities / quotes / orders / and invoice line items which are rolled up to the values on the parent opportunity / quote / order / invoice.
To give you my burger analogy... a restaurant has a 'bar menu' and an 'a-la-carte' menu (2 price lists). Both menus have a hamburger (product) available. The bar menu charges £9 and the a-la-carte menu charges £18 (price list items).
Both menus have child portions (half a unit in the 'portion' unit group) at £4.50 and £9 respectively. So there are 4 price list items there:
- bar menu, burger, adult unit £9
- bar menu, burger, child unit £4.50
- a-la-carte, burger, adult unit £18
- a-la-carte, burger, child unit £9
Rob (Contact) is cheap and likes to dine from the bar menu so the bar staff make a note of this (default price list) to save them having to ask which menu Rob would like to see each time he visits.
Looking at your entity model, your proposed Country > Development > Property entites are sound. I would only bother with the product catalogue if you need to attach opportunities/quotes/orders/invoices to your Property or Development entity and need
a price to be automatically calculated.
If you have a need to email the development, then I would consider using the account entity as the 'Development' (add a 'Type' picklist to the account with a value of 'Development) and either add a Country picklist or Country parental entity. See this
thread for thoughts on picklist or entity when dealing with countries.
Hope that gives you some ideas,
Rob
CRM MBSS Consultant - GAP Consulting Ltd.
