[FR] Build Order Allocation Improvements
Maintainers usually reply within 1 day
@SchrodingersGat is already working on this.
Since Mar 10, 2026.
Assessment
This issue has not been assessed yet.
Description
Problem
When allocating "tracked" items against a build order, there exists conditions where the users need to allocate the tracked input items before the output items are individually generated.
Currently this is not possible, as tracked items must be allocated against an individual build output. This means that a bulk set of input items cannot be allocated against the build order until the unique outputs are created.
This prevents the stock levels for the input parts from accurately reflecting that they are "reserved" (allocated) to the particular build order, even if they have been set aside for that order.
Example
For example, a particular order requires 80x input subcomponent part, which is produced in a batch intended to be consumed by the build. The individual build outputs are created one at a time over a long time period, and for the intervening period, the input parts appear as "available" - because they have not yet been allocated to the order.
This can lead to confusion around the actual stock availability of the input parts.
Solution
The proposed solution is to allow tracked items to be allocated against the build order in general. Before they can be consumed, they bust also be assigned to a particular build output.
A quantity of input items can be allocated to the build order itself, even before the outputs are generated. Once the outputs are generated, the input items can be individually assigned to the build outputs.
Additionally the existing workflow can remain in place - i.e. tracked items are allocated to the build order and assigned to a particular build output in a single step.
The "change" here is to allow input items to be allocated against the build order - which marks them as "unavailable" for use elsewhere while the build order is in production.
Nomenclature
This also provides an opportunity to clear up the terminology around the process:
- Stock items are allocated against a build order
- Tracked items are assigned to a particular build output
Similarity - Sales Orders / Shipments
This is a similar approach to how sales order / shipments are handled. The "sales order" is the "build order", and the "shipment" is the "build output".
Items are allocated to the sales order, and then assigned to the particular shipment. They can be allocated to the sales order without being assigned to a particular shipment - or even before a particular shipment even exists.
- Dominant language
- Python
- Stars
- 7.7k
- Forks
- 1.6k
- Avg merge
- 21h 45m
- Merged PRs (30d)
- 204
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from inventree/InvenTree
-
enhancement triage:not-checked
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
inventree/InvenTree#13318 · 1 reaction ·
Maintainers usually reply within 1 day
-
enhancement User Interface wontfix
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
inventree/InvenTree#13292 · 5 comments ·
Maintainers usually reply within 1 day
-
[FR] Add spinner arrows in Quantity when adding a BOM itemMay be free again @Alonso-Lopez-1 claimed this 50 days ago, and no pull request is open. Openenhancement help wanted starter User Interface
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
inventree/InvenTree#12677 · 6 comments ·
Maintainers usually reply within 1 day
-
enhancement triage:not-checked
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
inventree/InvenTree#13317 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug stock
Difficulty 3/5 1-2 days Newbie friendliness 40/100
inventree/InvenTree#13285 · 1 comment ·
Maintainers usually reply within 1 day
All issues in inventree/InvenTree
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ip-tools/patzilla#219 · 2 comments ·
Maintainers usually reply within 1 day
-
EPSSClient commits to its SQLite cache once per score: a 100-CVE bulk fetch makes 101 disk flushesOpenpriority:p3 technical-debt
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jimmy058910/jmo-security-repo#1673 ·
Maintainers usually reply within 1 day
-
enhancement ready
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
integration: frontier_silicon
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
home-assistant/core#193176 · 2 comments ·
Maintainers usually reply within 1 day
-
task create and task update take --body-file and --stdinPossibly taken @JuanBarriosS claimed this today. Opencli enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
pyrite-wiki/pyrite#1687 · 1 comment ·
Maintainers usually reply within 1 day