Order Purchase Quantity Bug

[odsPSI]

Please verify that this bug has NOT been raised before.

• I checked and didn't find a similar issue

Describe the bug*

When purchasing an order through the Build Order, the order purchase quantity is not based on the required quantity displayed on the manufacturing order (Important note is that the available stock is filtered based on the source location). Hence, I get multiple 0 quantities because the part exists outside of the source location. The required table on the build order does have the correct values though.

Steps to Reproduce

Go to a build order (with a specific source location for your stock),
Select an item out of stock in that location but exists elsewhere,
Add that item to your purchase order.

Expected behaviour

Quantity table = 0

Deployment Method

None

Version Information

Version = 1.2.0 dev

Try to reproduce on the demo site

I tried to reproduce

Is the bug reproducible on the demo site?

Reproducible

Relevant log output

[odsPSI]

Example on the demo = Build Order: BO0028

[matmair]

Provide a full version information block (as provided by the big, orange button labeled "copy version information" in the "about inventree" dialog) for reproducibility

[odsPSI]

InvenTree-Version: 1.2.0 dev
Django Version: 5.2.9
Commit Hash: bed83bc
Commit Date: 2025-12-09
Commit Branch: null
Database: django.db.backends.postgresql
Debug-Mode: False
Deployed using Docker: True
Platform: Linux-5.15.0-100-generic-x86_64-with-glibc2.41
Installer: DOC
Active plugins: false

[SchrodingersGat]

the order purchase quantity is not based on the required quantity displayed on the manufacturing order

The current logic is that the overall part requirements are considered when pre-filling the purchase quantity.

It is difficult to account for all possible complexities or considerations, as you might imagine.

Perhaps if you can make a suggestion as to how the existing calculation for "suggested quantity" can be improved?

[odsPSI]

Hi, I understand that taking into account all complexities are difficult. I just thought that since this purchase order is being made inside a build order, the purchasing quantity should reflect the BOM inside that order. For example, the build order has the required quantity and available stock columns that have already been filtered by the source location.

Hence, I think a simple logic would be that if available stock < required quantity then purchase stock = required quantity - available stock.

That way, if there is stock in warehouse B, but my build is filtered only for warehouse A it will input the correct value inside the purchase order rather than the 0 (zero) presented in the image in the initial post.

Just to clarify, the zeros I was getting is because the system assumed I didn't need to make a purchase because the stock existed outside of my source location for that specific Build Order.

[SchrodingersGat]

This needs to be solved in the general case for the "order parts" dialog - as it is used in multiple places in the UI.

Perhaps, we can add the option to pass override values through to the dialog. In the case of the build order, it can be based on the "location" of the build order, and determine the required quantity based on this?