I have posted a new post with some Use Case examples on how to leverage the Sugar Framework to add additional functionality. What are your thoughts? Do you have more use cases I can add to the list?
I have posted a new post with some Use Case examples on how to leverage the Sugar Framework to add additional functionality. What are your thoughts? Do you have more use cases I can add to the list?
hey Jeff Bickart
I think Sugar could do with some help for implementing CRM for customers that have a B2C customer base rather than just B2B, or even better to have ability to deal with both.
i.e. a business that has all B2C customers that place orders from a website, and also has to manage relationships with their suppliesr (B2B).
.
It is possible to configure as Sugar B2C; You can enable this property, require_accounts
I think that the issue is when one has both B2B and B2C
We resorted to "first, last" for account names for B2C (on an older system and took that with us in Sugar) and actual company/university name for B2B, but then we have to have Contacts that need to be able to link to both a B2C (for their personal software licenses) and B2B as representatives of their company/university so now we have M-M Contact-Account relationships and identifying (and merging) duplicates is even harder....
I think that the issue is when one has both B2B and B2C
We resorted to "first, last" for account names for B2C (on an older system and took that with us in Sugar) and actual company/university name for B2B, but then we have to have Contacts that need to be able to link to both a B2C (for their personal software licenses) and B2B as representatives of their company/university so now we have M-M Contact-Account relationships and identifying (and merging) duplicates is even harder....