Display price per unit on variants

What is the need / problem?

In Europe when you sell a product with unit weight or volume, legislation requires you to display the price per kg or per liter. https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:31998L0006&from=EN
Currently hubs and producers who have a shop on the OFN add this in the description field, but:
1- it is not clear enough for the buyer.
2- if the hub is a reseller (buy and sell a product with a markup) the price per kg / liter of the product changes with the new price including the markup. The workaround used today doesn’t enable to adapt the price per kg if the distributor add a markup.
3- to complexify a bit the situation, some hubs are reseller (buy and resell with a markup) and some others sell distribution services so they don’t add a markup but they invoice, on top of the original price of the product from the producer (so same price per kg) a service fee. In this case the price per kg shouldn’t change.

Who does it impact?

All shops manager in France, but also all buyers that are used to compare price per kg.

What is the current impact of the problem?

The info is a bit hidden + some hubs can’t meet their legal obligation with the current OFN platform

What is the benefit of focusing on this?

More ability for the end buyer to compare prices, and better legal compliance.

Potential solutions that will solve the problem ?

1- Adding this as a new field? That would calculate automatically given certain setups, especially given the nature of the hub (hub buy and sell > price per kg = price including markup divided by nb of unit / hub sell only services > price per kg = original price per kg of producer). This is not possible with the current fee logic but might become possible when we have some “pricing table” later on.

Selection of a feature candidate

[value x ease matric if needed]

T-shirt size of our selected feature candidate

Metrics to measure if need is satisfied after feature is implemented

Feature owners

Epic/projet where you can follow implementation

Connected wishlist and discovery discussions*

[list precedent discussions]

This would be a field in the variant, maybe we can change the title of the post to variant?

Also, this is closely related to the already very messy list of fields we have around units and its descriptions in the variants model…

Correct! I changed the title. Also I made this post a wiki.

@Kirsten this morning Biruté has mentioned to me that you have a similar legal compliance. I found this text but I’m not sure it applies to OFN. Do you have more info? https://www.accc.gov.au/business/industry-codes/unit-pricing-code