Details about this thread
  • State Suggested Answer
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 292 subscribers
  • Views 2329 views
  • Users 0 members are here
Related content from around SugarClub

Product level tax rates

Tony Romano

Has anyone else looked into implementing different Tax rates at product level, to subsequently use these within Quoted line items module?

The Product Catalogue module currently only has a dropdown to identify if a product is either Taxable or Non-Taxable, no filed to select which tax rate.

By the way, as we cannot even create the relationship between Product catalogue and Tax module as it's not in Studio, does anyone know how to expose this module to make use of it in Studio?

Many thanks

Parents
  • 0

    Here in Brazil tax rates are quite a nightmare, several variables and specific conditions. That said, we implement for our local customers these approaches, according to complexity of business taxes:

    • 1:M relationship between Tax Rates and QLI so Sales Person can select the Tax which better fits the scenario (easier approach)
    • Custom Accounting modules, their relationships with Product Catalog and some custom fields in the Product Catalog as well so CRM can calculate the appropriate Tax Rates based on nature of select QLI and Customer Accounting configuration (the powerful approach)

    Some other customers like to send the Quotes to ERP and let it to calculate the Tax Rates as it has all the data to process it and then bring back to CRM the calculated/updated Quote with Taxes.

    André Lopes
    Lampada Global
    Skype: andre.lampada
  • 0 in reply to André Lopes
    André Lopes said:
    1:M relationship between Tax Rates and QLI so Sales Person can select the Tax which better fits the scenario (easier approach)

    Not sure if I'm understanding correctly, but that is already standard, i.e. when you select a product (QLI) in a Quote, you have the option to select a Tax rate that is held in the Tax rates module.


    Dmytro Chupylka said:
    Its possible to add a custom dropdown field to the Product Catalogue

    That would not be an acceptable solution, because

    a) dropdown values would ned to be maintained seperatley instead of only once using the Tax rates module

    b) you'd need to change the core functionality and calculations that already use the standard relate field for each QLI that looks up from the Tax rates module.


    I believe the 'ideal' solution for us would be be able to select from the Tax rate module within the Product catalogue record.

    In order to do this, it seems we need to expose the Tax rate module so it's viewable in Studio, and then create either a Relate field or a full relationship (1:M relationship between Tax Rates and Product Catalogue?)

Reply
  • 0 in reply to André Lopes
    André Lopes said:
    1:M relationship between Tax Rates and QLI so Sales Person can select the Tax which better fits the scenario (easier approach)

    Not sure if I'm understanding correctly, but that is already standard, i.e. when you select a product (QLI) in a Quote, you have the option to select a Tax rate that is held in the Tax rates module.


    Dmytro Chupylka said:
    Its possible to add a custom dropdown field to the Product Catalogue

    That would not be an acceptable solution, because

    a) dropdown values would ned to be maintained seperatley instead of only once using the Tax rates module

    b) you'd need to change the core functionality and calculations that already use the standard relate field for each QLI that looks up from the Tax rates module.


    I believe the 'ideal' solution for us would be be able to select from the Tax rate module within the Product catalogue record.

    In order to do this, it seems we need to expose the Tax rate module so it's viewable in Studio, and then create either a Relate field or a full relationship (1:M relationship between Tax Rates and Product Catalogue?)

Children