-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warehouse exclusion in supply calculations #18740
Comments
It's the generalized case of #22354 and should be kept open/merged. |
No progress during the last 2 years ... For us this is one of the most important missing basic features. |
@altairis-tof et @altairis-noe any idea ? |
That could be very interesting. In rental situations, we have the possibility to dedicate special warehouses to « on site » (in the temporary client possession). With the advanced warehouses statuses, we manage to avoid those stock to be shippable (flagging the warehouses as « internal movements only »), but it would be very useful to have a feature that would exclude them from usable stock. After all, that is why we call Dolibarr a software for Enterprise Resource Planning. In my opinion, we should add a field in the object and the database that would exclude designated warehouses from available stocks. I am all for it, if someone wish to commission us 😇 |
#30199 ? |
#26384
Le jeu. 4 juil. 2024, 17:28, Christophe Battarel ***@***.***>
a écrit :
… #30199 <#30199> ?
—
Reply to this email directly, view it on GitHub
<#18740 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZC3QQC2R2N364Z3JMSAQ3ZKVS3DAVCNFSM6AAAAABKLRHGEKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGIZTENJWGA>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
Feature Request
Warehouse exclusion in supply calculations
Use case
Certain use cases should make it possible to exclude the selected warehouses from the supply calculations.
Suggested implementation
The text was updated successfully, but these errors were encountered: