Details about this thread
  • Replies 7 replies
  • Subscribers 307 subscribers
  • Views 1014 views
  • Users 0 members are here
Related content from around SugarClub

How to use Opportunity AND RLI with more flexibility ?

Frédéric Rinaldi

Hello,

I want to share a problem that some of us are facing and want to know how you deal with it.

Opportunity with RLI are great, because you can better express complex sales processes, including multiples Revenue Line (that should live their own live).

BUT, sometimes you only want to use the Opportunity WITHOUT RLI

  • for instance at the first step, maybe you don't know what products / lines you want to add
  • for instance for basic opportunity, you want to use it the way Sugar works without the RLI

For all those reason, I would like to understand how you manage opportunity and RLI, for advanced but also basic deals ?

Many thanks,

Fred

PS : additionnal question : do you also sometimes want to split the product catalog that is used for Opportunity (more macro) and the one used for Quotes (more micro) ?

Parents
  • Frédéric Rinaldi said:
    PS : additionnal question : do you also sometimes want to split the product catalog that is used for Opportunity (more macro) and the one used for Quotes (more micro) ?

    We do have multiple catalogs because the Opportunity is not defined in detail. We know the customer wants a given product but not specifically which edition. When we get to the quote we may quote different editions so that they can choose.

    For example: Imagine we were selling Sugar. The Opportunity will have "Sugar" but the Quote will have "Sugar Enterprise On-Site"

    Note that we added our own Opportunity Products (related to Opportunities) and Opportunity Product Catalog (for that module to pick products) back in Sugar Professional v.6.x and I am still looking at how those can be mapped and moved to RLI now that we have those in Enterprise.

    We also have code in Quotes that looks up pricing in our ERP, adds a service line if applicable as a QLI, but then prints as a single line "product with service" during the quote printing process. We do this so we can report service and product revenue separately from the QLI but sell as a unit where service is not optional . A nightmare when you start adding % or $ discounts, promotional codes (more custom code with product based lookups from ERP), and the consequent rounding errors and penny differences in totals...

    FrancescaS

Reply
  • Frédéric Rinaldi said:
    PS : additionnal question : do you also sometimes want to split the product catalog that is used for Opportunity (more macro) and the one used for Quotes (more micro) ?

    We do have multiple catalogs because the Opportunity is not defined in detail. We know the customer wants a given product but not specifically which edition. When we get to the quote we may quote different editions so that they can choose.

    For example: Imagine we were selling Sugar. The Opportunity will have "Sugar" but the Quote will have "Sugar Enterprise On-Site"

    Note that we added our own Opportunity Products (related to Opportunities) and Opportunity Product Catalog (for that module to pick products) back in Sugar Professional v.6.x and I am still looking at how those can be mapped and moved to RLI now that we have those in Enterprise.

    We also have code in Quotes that looks up pricing in our ERP, adds a service line if applicable as a QLI, but then prints as a single line "product with service" during the quote printing process. We do this so we can report service and product revenue separately from the QLI but sell as a unit where service is not optional . A nightmare when you start adding % or $ discounts, promotional codes (more custom code with product based lookups from ERP), and the consequent rounding errors and penny differences in totals...

    FrancescaS

Children
  • in reply to Francesca Shiekh

    I confess I didin't realize your latest question  .

    We guide our customers on managing the portfolio in such way it is easy/fast to search based on criterias like Product Type, Parent Product Category, Child Produt Category etc. This way it make it possible to reach a generic item x a quite specific one, for example.

    Thanks to the project enum-api it is easy to fetch runtime filtered data from a custom api. This way you can setup different se of views for Opportunity or Quote, depending on the context/requirements

    André Lopes
    Lampada Global
    Skype: andre.lampada