Problems with unit price

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Laimonas
    Senior Member
    • May 2021
    • 201

    Problems with unit price

    Hi there,

    I'm having trouble understanding if there's a bug or a specific reason for this issue. Let me outline the situations:

    1st situation:

    MinQ = 5, price = 225 EUR
    MinQ = 6, price = 260 EUR
    When I select "quantity = 6" in the Quote, I receive "unitPrice = 260" (all good).

    2nd situation:

    MinQ = 5, price = 225 EUR
    MinQ = 6, price = 130 EUR
    When I choose "quantity = 6" in the Quote, I get "unitPrice = 225" (not okay).

    It seems like I cannot have a higher MinQ and a lower price than the last price record has...

    I think that by buying more pieces you should get a lower price per unit. But I cannot do that in this case...

    Please find print screens attached.
    Attached Files
  • yuri
    Member
    • Mar 2014
    • 8528

    #2
    I'll look into.
    If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

    Comment

    • yuri
      Member
      • Mar 2014
      • 8528

      #3
      It's supposed to suggest the min price available for the quantity. I'll fix it, it worked, but for some reason stopped after some changes.

      Your 2nd case should work, the 1st case should not work, it should return the min price.
      If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

      Comment


      • Laimonas
        Laimonas commented
        Editing a comment
        In my opinion, both scenarios should work. In case I have higher production costs for a higher quantity - I will charge more for a higher quantity.
        I expect the system will show the price that is set per unit in the "Price" record without interpretation.
    • yuri
      Member
      • Mar 2014
      • 8528

      #4
      Fixed in v2.1.2.
      If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

      Comment

      Working...