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

Jacques Le Roux commented on OFBIZ-1495:
----------------------------------------

Yes you are right Chris. We need before to clarify what we want to see where. 
There is also still a case where you see only the product base price ($ 50 for 
a PC001) : Last Products boxe in eCommerce. I forgot that one and we have to do 
something there to keep consistency.

We should 1st define what we need where, and then see how to do it. The more 
informations we give the better.

A) I propose to show the Product Aggregated Price everywhere, ie
- eCommerce
    . Products list (where you choose to add a product)
    . Products details (where you choose to add/modify items)
    . Shopping cart view (where you check your choices during shopping)
    . Déjà vu list (aka Last Products boxe). 
    . Final Checkout Review  (where you check your choices before payment)
    . Order Confirmation  (where you check your payment)
For that point to be achieved we need only to show the Product Aggregated Price 
in déjà vu list in place of the product base price currently shown (this should 
have been done in your patch I commited recently, so we are both to blame ;o)

- Order Manager
    . Nothing to change (it behaves like eCommerce except that there is no Déjà 
vu list)

- POS
    . Item configuration window (where you choose to add an item)
    . Journal (where you check choices)
    . Receipt (where you check payment)
For that point to be achieved we need to show the Product Aggregated Price in 
Item configuration window. Maybe we can stay as is.

Below I will not repeat views where a price is already shown (ie no add/changes 
needed).

B) I propose to show the product base price in
- eCommerce
    . Products list
    . Products details
    . Shopping cart view
For that point to be achieved we need to show the product base price in three 
views

- POS
    . Item configuration window
    . Journal
    . Receipt
For that point to be achieved we need to show the product base price in three 
views. Maybe we can let Item configuration window as is.

C) I propose to show items prices in
- eCommerce
    . Products list 
    . Shopping cart view
For that point to be achieved we need to show default items prices in both views
 
- POS
    . Item configuration window
For that point to be achieved we need to show items prices in Item 
configuration window. Maybe we can stay as is.    
 
Something to note : there is one drawback in my proposition but this is already 
existing. 
    . Order view (eCommerce, Order Manager, etc.) is comparable to POS Journal 
but in Order view you don't have the details of the aggregated item.
    . Invoice is comparable to POS Receipt but in Invoice you don't have the 
details of the aggregated item.
        * There is currently a bug in trunk when rendering an invoice PDF, I 
have opened a new Jira issue for this OFBIZ-1549

> Aggregate items base price is displayed yet unattainable
> --------------------------------------------------------
>
>                 Key: OFBIZ-1495
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1495
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: order
>    Affects Versions: SVN trunk
>            Reporter: Chris Lombardi
>            Assignee: Bilgin Ibryam
>            Priority: Minor
>         Attachments: ofbiz-1495.patch, totalPrice.patch
>
>
> I did some research, and I couldn't find a way to get a valid base price that 
> made intuitive sense. So then I went to the e-commerce store to see how it 
> was implemented there.
> Configurable PC
> PC001 Your Price: $50.00
> Hey, 50$ for a PC, I want one! So I click on the item.
> Configurable PC
> PC001
> Product Aggregated Price: $385.00
> What?
> So, whatever is being called for the price of a "PC001" should probably 
> report the price of the default configuration, not the price of the 
> "unconfigured" product that you can't buy.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to