Skip to content

[17.0][ADD] sale_order_price_precision: set specific decimal precison for sales prices#4153

Open
dreispt wants to merge 1 commit intoOCA:17.0from
ursais:17-dr-sale_order_price_precison
Open

[17.0][ADD] sale_order_price_precision: set specific decimal precison for sales prices#4153
dreispt wants to merge 1 commit intoOCA:17.0from
ursais:17-dr-sale_order_price_precison

Conversation

@dreispt
Copy link
Member

@dreispt dreispt commented Feb 12, 2026

No description provided.

@dreispt dreispt changed the title [ADD] sale_order_price_precision: set specific decimal precison for sales prices [17.0][ADD] sale_order_price_precision: set specific decimal precison for sales prices Feb 12, 2026
@rousseldenis rousseldenis added this to the 17.0 milestone Feb 13, 2026
@rousseldenis
Copy link
Contributor

@dreispt Wouldn't this weird towards other flows (invoicing,... ) that have not this change ?

@dreispt
Copy link
Member Author

dreispt commented Feb 13, 2026

I think you're right, and this should also be set on the invoice side.
It should be enough to stop there, I can think of other sales related unit price fields.

The underlying pain/motivation is that purchases and costing needs 5 or 6 digits, but sales only needs two.

@dreispt dreispt force-pushed the 17-dr-sale_order_price_precison branch from ce9fa34 to 3121cf9 Compare February 16, 2026 18:20
@dreispt dreispt force-pushed the 17-dr-sale_order_price_precison branch from 3121cf9 to b29596f Compare February 16, 2026 18:23
@dreispt
Copy link
Member Author

dreispt commented Feb 16, 2026

@rousseldenis Added also on account.move.line
I don't think we're missing any other relevant unit price fields.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants