[FR] Build Order Allocation Improvements

Open
#11,480 2 comments 2 reactions 1 assignee View on GitHub

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

api build enhancement refactor User Interface
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

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from inventree/InvenTree

All issues in inventree/InvenTree

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.