In agricultural commodity trading, quantities are typically tracked in kg while pricing is expressed per metric ton (1 000 kg). ERPNext currently has no native way to handle this cleanly.
The UOM conversion feature doesn’t solve it: it converts the quantity for stock purposes, but the transaction document still lives in a single UOM. So you either invoice in metric ton (breaking the kg convention) or invoice in kg with a per-kg rate (which is never how prices are communicated in this sector).
The core issue is that amount = qty × rate assumes quantity and pricing are in the same UOM. What’s needed is effectively amount = qty × rate × conversion_factor, where the pricing UOM and its conversion are defined separately from the stock/transaction UOM.
The only workable workaround we’ve found is a custom “Rate per MT” field with a client script dividing it by 1000 to populate the actual rate. Functional, but a hack, and often results in unexpected problems.
Is there an existing app or project that handles this? And if not, would there be interest in supporting a dedicated pricing UOM in ERPNext core? It seems like a pattern that would apply beyond just our sector: anywhere the traded unit and the priced unit differ.
