I'm exploring the new features of 10.1 (I know I'm not early :) ), especially the brand new "purchases" module.
My first thought was "wow Sugar is now going towards a full-blown ERP and now manages vendor purchases".
Looking into the docs, I realise we're talking about customer purchases, in other words, orders.
This generated new questions for me:
- Why call this "purchases" when this term is mostly used for vendor purchases? "Orders" comes to mind more readily. In French it's even more disturbing as "Achats" is clearly the name of the team that handles vendors/procurement. I understand that from a customer's perspective they are indeed purchasing, but this tool is used by sales people who, well, sell :)
- For the moment I fail to see the added value of purchases vs RLIs. AFAIK records are not linked to the mother opportunity and do not have a status (ordered, delivery in progress, delivered, retired...). Is this interesting only for periodic orders, such as a monthly automatic renewal? Another use case I'm not seeing?
- The automatic creation of purchases is great but my hunch is that most customers will not use them, so the "generate purchase" should be no by default. Easy enough to change, but it is going to cost minutes in most projects (or useless data storage and processing time).
These are my thoughts, laid here for open discussion :)