I am planning to implement some proper ordering system, were you can mark parts for ordering, create order data objects, with information about what was ordered when (with metadata like delivery status, order number and so on), and the possibility to automatically add the ordered parts to your stock in the end. However that might take some time to implement and develop.

As a workaround you could maybe use tags, and add tags like "need to be ordered", "in delivery", etc. to your parts.

To the build information: If you want to know how many parts are missing to build a certain amount of a project, just type in your wished build quantity and try to build it. The build page will then show you exactly what amounts are missing.

I am planning to implement some proper ordering system, were you can mark parts for ordering, create order data objects, with information about what was ordered when (with metadata like delivery status, order number and so on), and the possibility to automatically add the ordered parts to your stock in the end. However that might take some time to implement and develop.

As a workaround you could maybe use tags, and add tags like "need to be ordered", "in delivery", etc. to your parts.

To the build information: If you want to know how many parts are missing to build a certain amount of a project, just type in your wished build quantity and try to build it. The build page will then show you exactly what amounts are missing.

I want also first thank you for the good work and fantastic documentation.
Is there a prospective date for the implementation of the ordering system ?

Is there a prospective date for the implementation of the ordering system ?

Not really. Currently I am working on some system to change settings/configure Part-DB from the WebUI instead of requiring env variables for everything.

Maybe I will look into the ordering system after that.