[jira] [Comment Edited] (OFBIZ-12298) Wrong price calculation for productConfigProduct

["Mart Naum (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OFBIZ-12298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399634#comment-17399634 ] 

Mart Naum edited comment on OFBIZ-12298 at 8/16/21, 9:33 AM:
-------------------------------------------------------------

Alright, this once again follows a certain logic. And I clearly was not aware of the fact that the price purpose COMPONENT_PRICE is added to the PURCHASE price in aggregated products. If I understand that correctly the FAJITA_BEEF price is calculated by the PURCHASE-price of ENCHILADAS plus the COMPONENT_PRICE of FAJITA_BEEF. This is also what I now observe in the ecommerce UI.

This also means that the PURCHASE price of FAJITA_BEEF is redundant information and never taken into account. I propose to delete it to boost the understanding of those productConfigProducts for new users.

Nevertheless I think that we should stick to the PURCHASE-price of the parent product (i.e. ENCHILADAS with a price of 6 USD) if there is no COMPONENT_PRICE instead of doubling the PURCHASE-price in that constellation. It is really confusing if one declares a PURCHASE price and observes twice the price in the ecommerce UI, like it is currently the case with ENCHILADAS.


was (Author: martnaum):
Alright, this once again follows a certain logic. And I clearly was not aware of the fact that the price purpose COMPONENT_PRICE is added to the PURCHASE price in aggregated products. If I understand that correctly the FAJITA_BEEF price is calculated by the PURCHASE-price of ENCHILADAS plus the COMPONENT_PRICE of FAJITA_BEEF. This is also what I now observe in the ecommerce UI.

This also means that the PURCHASE price of FAJITA_BEEF is redundant information and never taken into account. I propose to delete it to boost the understanding of those productConfigProducts for new users.

Nevertheless I think that we should stick to the PURCHASE-price of the parent product (i.e. ENCHILADAS with a price of 6 USD) if there is no COMPONENT_PRICE instead of doubling the PURCHASE-price in that constellation. It is really confusing if one declares a PURCHASE price and observes twice the price in the ecommerce UI, like it is currently with ENCHILADAS.

> Wrong price calculation for productConfigProduct
> ------------------------------------------------
>
>                 Key: OFBIZ-12298
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-12298
>             Project: OFBiz
>          Issue Type: Bug
>          Components: product
>            Reporter: Mart Naum
>            Assignee: Priya Sharma
>            Priority: Major
>         Attachments: config-product.png
>
>
> The enchiladas are implemented in the backend using productConfigProduct. For the standard product, the cheese enchiladas, the productPrice is configured to be 6 USD. The productPrice for fajita beef enchiladas is 8 USD.
> However, the order in the webshop shows a price of 12 USD for a single order of cheese enchiladas. That's exactly double the price stored in productPrice. On the other hand the price calculation for the fajita beef enchiladas seems to be correct.
> I experimented a bit with productConfigProduct and saw that the price always doubles in the ecommerce UI as well as in the resulting order when the productConfigProduct is identical to the parent product of this product configuration. This is so also the case with the configurable PC. I assume there is a glitch within the price calculation for productConfigProducts.
>  
> Update: When I add enchiladas to a shoppingList, the shoppingList shows the correct price of 6USD.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)