Thanks for these Eriol. Feedback as per your questions:
From your specific instance/job function context, what worries you most about the unit price for shoppers?
This is a new concept for shoppers and producers alike here. (See my comments below on the back office.) Yes shoppers will get confused between item price and unit price. They wonāt know why its there. For me, as someone who never sees this when shopping online elsewhere now - Iād suggest that the rationale for it seems quite similar to why we do the āprice breakdownā in the pie chart. We also as shoppers here, never see price breakdown like this elsewhere. I understand unit price to be part of full transparency to the shopper - and I agree with that. I am wondering, if we might handle it like we handle price breakdown then? A separate icon to the pie (not sure what) that the shopper has the option to click on to reveal unit pricing. Or a more elaborate explanation in the pie breakdown? Basically - as a shopper who never sees this anywhere I shop now - Iām confused about what it means and why its here. I need a bit more coaching through it.
e.g. We think bulk, large quantity shoppers might get confused between the item price and unit price
From the point of view of producers using the back office, what will be the most difficult thing about unit prices in product listings.
I think this will be a very challenging learning curve in instances where we have no substantive history with or requirement for unit pricing. The entire concept is new - not just how we operationalize it.
The biggest confusing point for me as a user is the use of the term āitemā. If as a user I select my āunit sizeā as āitemā (when I create a product) - I then enter what I will call this item as the āunit nameā (ie: slice, or lemon, or workshopā¦) . But the unit price never uses the āunit nameā I give it. That is confusing. I donāt understand what this is comparing when it says it is a cost for 1 item. I probably have entered 100 items. Is it doing a cost comparision across all my items? So the term item in the comparsion doesnāt make sense to me. Second, Iām confused by the ā1ā. Isnāt the 1 redundant? it will always be cost per ā1ā of whatever we decide we are comparing (either āunit nameā or āunit sizeā). I THINK we are comparing whatever āunit nameā the user enters. So canāt we do whenever the āunit sizeā of āitemā is selected? So - in your 2 slices example - the unit price would read as the cost āfor each sliceā. the terms āfor eachā or āperā would always be there - and the term āitemā changes to match whatever the producer enters as āunit nameā. Iām saying this because the comparison is not across all items - the comparison is for that specific kind of item (item name) - per slice, per lemon, per bunch, per workshop, per pickup time ā¦We are not doing a cost comparsion across all āitemsā.
Sorry if this doesnāt make sense - but it is my first though as a user who has no familiarity with this. Its not clear what we are comparing, and why we are saying ā1ā when there doesnāt ever seem to be a comparision that is other than for 1.
Second - I just want to make sure - the unit price calculation on the producerās product list - and on the shopās inventory list - can be hidden from view (as per the ācolumnsā selector). In the videos - Iām assuming you just had these columns selected. So in both product list and inventory list, a user can hide it from view? Could we make it hidden from view by default? Could we make it the LAST column that shows when it is selected to show? This would lesson the confusion I think - a producer in an instance where we simply donāt use this concept at all - could just hide it. (just like they hide sku if they donāt use it)
Other back office things to consider: ādisplay asā field is not included in product imports now. Iām trying to think this through - will it now have to be included in the product importer? Iām just not clear on the implications for product import of the unit pricing. Also - will unit pricing appear anwhere in reports?
From the point of view of a back office user and a shopper, how clear do we think the directions are for unit price? Do the tool-tip texts explain clearly? does text near input fields help users to understand?
Iām not sure where to find the tool tip text - so donāt know what that says so Iām not sure if it explains this to the user or not. Will it be translatable so an instance can customize? Sorry if I missed this - but Iām not seeing any directions.
Again - Iām not blocking this. Iām just saying the concept is a foreign one to me - and these are my initial reflections on it as a user and a shopper.
) . I leave beautiful for the artists!
If you have any comments, now is a good time to raise them 
I must have forgotten some people 
I was trying to do 1 person per instance, but maybe we should come up with a list somewhere or create a group we can ping easily. Otherwise itās going to be difficult as we grow.
