we call it "oranges problem" ;-)
Today there is only one unit of measure in the sales and purchase Documents. For some items it is relevant to distinguish between an Order Unit of Measure and a Price Unit of Measure.
For example for fruits. Mostly fruits are ordered in boxes (and also handled in the warehouse in this unit), but the price depends on the weight of the fruits (because two boxes of the same fruit don't have the exactly same weight and there are sometimes heavier and sometimes lighter). So there sould be a possibility to add an additional Price Unit of Measure to an item which is used in Sales and Purchase Documents. The Quantity in Price Unit of Measure sould be linked to the normal Unit of Measure, but changeable so that it is possible to insert the exactly weight of the item and the prices and discounts are searched for this unit and not for the order unit of measure.
This would be an excellent idea. The number of units being picked is good but when it comes to charging a customer based on the weight of the product, it is important to gain accuracy to enter the correct weight based on which the customer is charged. Similar functionality is required for products that can have a variable weight. For example, lets of ham. Each leg of ham can have a different weight and the customer is charged per leg of ham. While each unit it being sold, it would be great to enter the weight of the unit so the customer can be charged correctly for $/kg
I think this idea is related to the process of managing "catch weight items". It could be useful both in sales than in purchases.
This scenario is frequent in food industries.
Unfortunaly I have to expand my requirement a little bit. There are not only 2 different units, but even 3. Their is also a Need for an shipment Unit of Measure to handle the item in this Units in outgoing and incoming Warehouse documents.
For example your customer orders boxes, the Price refers to kilogramm, but you ship pallets.
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future.
Business Central Team