.. image:: https://odoo-community.org/readme-banner-image
:target: https://odoo-community.org/get-involved?utm_source=readme
:alt: Odoo Community Association
==================================
Stock Available to Promise Release
==================================
..
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! This file is generated by oca-gen-addon-readme !!
!! changes will be overwritten. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! source digest: sha256:16334172016468cdfd5eb49615584c0b1167342f08aaa831dae444affb03b2b3
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
.. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png
:target: https://odoo-community.org/page/development-status
:alt: Beta
.. |badge2| image:: https://img.shields.io/badge/license-LGPL--3-blue.png
:target: http://www.gnu.org/licenses/lgpl-3.0-standalone.html
:alt: License: LGPL-3
.. |badge3| image:: https://img.shields.io/badge/github-OCA%2Fstock--logistics--reservation-lightgray.png?logo=github
:target: https://github.com/OCA/stock-logistics-reservation/tree/18.0/stock_available_to_promise_release
:alt: OCA/stock-logistics-reservation
.. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png
:target: https://translation.odoo-community.org/projects/stock-logistics-reservation-18-0/stock-logistics-reservation-18-0-stock_available_to_promise_release
:alt: Translate me on Weblate
.. |badge5| image:: https://img.shields.io/badge/runboat-Try%20me-875A7B.png
:target: https://runboat.odoo-community.org/builds?repo=OCA/stock-logistics-reservation&target_branch=18.0
:alt: Try me on Runboat
|badge1| |badge2| |badge3| |badge4| |badge5|
Currently the reservation is performed by adding reserved quantities on
quants, which is fine as long as the reservation is made right after the
order confirmation. This way, the first arrived, first served principle
is always applied. But if you release warehouse operations in a chosen
order (through deliver round for example), then you need to be sure the
reservations are made in respect to the first arrived first served
principle and not driven by the order you choose to release your
operations.
Allow each delivery move to mark a quantity as virtually reserved.
Simple rule would be first ordered, first served. More complex rules
could be implemented.
When the reservation of a picking move occurs, the quantity that is
reserved is then based on the quantity that was promised to the customer
(available to promise):
- The moves can be reserved in any order, the right quantity is always
reserved
- The removal strategy is computed only when the reservation occurs. If
you reserve order 2 before order 1 (because you have/want to deliver
order 2) you can apply correctly fifo/fefo.
- For instance order 1 must be delivered in 1 month, order 2 must be
delivered now.
- Virtually lock quantities to be able to serve order 1
- Reserve remaining quantity for order 2 and apply fefo
- Allow to limit the promised quantity in time. If a customer orders now
for a planned delivery in 2 months, then allow to not lock this
quantity as virtually reserved
- Allow to perform reservations jointly with your delivery rounds
planning. Reserve only the quants you planned to deliver.
When move qty is not completely satisfied on release, the remaining qty
is split and attached to a new picking that can be released later.
Important: if the "Stock reservation horizon" is set, the qty is
calculated on moves which have an expected date not beyond $today +
$horizon (in days).
Important: Moves without a warehouse set are not supported. If the
warehouse is not set on the move, the "Ordered Available to Promise"
Quantity will always be 0. It will also not be considered as consuming
existing stock. The warehouse gets set by the Stock rule, if the Rule is
not assigned to a warehouse, also the move will not end up with a
warehouse.
**Table of contents**
.. contents::
:local:
Configuration
=============
In Inventory > Configuration > Routes, activate the option "Release
based on Available to Promise" on the routes where you want to use the
feature.
To modify the horizon go to "Inventory > Settings" and change "Stock
reservation horizon".
Usage
=====
When an outgoing transfer would generate chained moves, it will not. The
chained moves need to be released manually. To do so, open "Inventory >
Operations > Stock Allocation", select the moves to release and use
"action > Release Stock Move". A move can be released only if the
available to promise quantity is greater than zero. This quantity is
computed as the product's virtual quantity minus the previous moves in
the list (previous being defined by the field "Priority Date").
This behaviour is activated by stock route by setting the option
"Release based on Available to Promise".
By default, when an outgoing transfer is released, a backorder is
created for the remaining quantities for products not available at
release time. This behaviour can also be changed by stock route by
setting the option "No backorder at release". In such a case, moves
created for unavailable products will remain in the original outgoing
picking and no backorder will be created.
One a picking is released, you can also ensure that new move will no
more be assigned to a released picking by setting the option "Prevent
new move after release". on the stock picking type.
At the end of the picking process (when the picking is validated) of an
outgoing transfer, if a backorder is created, the chained moves can be
automatically unreleased. This behaviour is activated by setting the
option "Unrelease on backorder" on the stock picking type.
Bug Tracker
===========
Bugs are tracked on `GitHub Issues <https://github.com/OCA/stock-logistics-reservation/issues>`_.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us to smash it by providing a detailed and welcomed
`feedback <https://github.com/OCA/stock-logistics-reservation/issues/new?body=module:%20stock_available_to_promise_release%0Aversion:%2018.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_.
Do not contact contributors directly about support or help with technical issues.
Credits
=======
Authors
-------
* Camptocamp
* BCIM
Contributors
------------
- Guewen Baconnier <guewen.baconnier@camptocamp.com>
- Simone Orsi <simone.orsi@camptocamp.com>
- Jacques-Etienne Baudoux <je@bcim.be>
- Dung Tran <dungtd@trobz.com>
- Laurent Mignon <laurent.mignon@acsone.eu>
- Michael Tietz (MT Software) <mtietz@mt-software.de>
Other credits
-------------
The development of this module has been financially supported by:
- Camptocamp
Maintainers
-----------
This module is maintained by the OCA.
.. image:: https://odoo-community.org/logo.png
:alt: Odoo Community Association
:target: https://odoo-community.org
OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.
This module is part of the `OCA/stock-logistics-reservation <https://github.com/OCA/stock-logistics-reservation/tree/18.0/stock_available_to_promise_release>`_ project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Raw data
{
"_id": null,
"home_page": "https://github.com/OCA/stock-logistics-reservation",
"name": "odoo-addon-stock-available-to-promise-release",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.10",
"maintainer_email": null,
"keywords": null,
"author": "Camptocamp, BCIM, Odoo Community Association (OCA)",
"author_email": "support@odoo-community.org",
"download_url": null,
"platform": null,
"description": ".. image:: https://odoo-community.org/readme-banner-image\n :target: https://odoo-community.org/get-involved?utm_source=readme\n :alt: Odoo Community Association\n\n==================================\nStock Available to Promise Release\n==================================\n\n.. \n !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\n !! This file is generated by oca-gen-addon-readme !!\n !! changes will be overwritten. !!\n !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\n !! source digest: sha256:16334172016468cdfd5eb49615584c0b1167342f08aaa831dae444affb03b2b3\n !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\n\n.. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png\n :target: https://odoo-community.org/page/development-status\n :alt: Beta\n.. |badge2| image:: https://img.shields.io/badge/license-LGPL--3-blue.png\n :target: http://www.gnu.org/licenses/lgpl-3.0-standalone.html\n :alt: License: LGPL-3\n.. |badge3| image:: https://img.shields.io/badge/github-OCA%2Fstock--logistics--reservation-lightgray.png?logo=github\n :target: https://github.com/OCA/stock-logistics-reservation/tree/18.0/stock_available_to_promise_release\n :alt: OCA/stock-logistics-reservation\n.. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png\n :target: https://translation.odoo-community.org/projects/stock-logistics-reservation-18-0/stock-logistics-reservation-18-0-stock_available_to_promise_release\n :alt: Translate me on Weblate\n.. |badge5| image:: https://img.shields.io/badge/runboat-Try%20me-875A7B.png\n :target: https://runboat.odoo-community.org/builds?repo=OCA/stock-logistics-reservation&target_branch=18.0\n :alt: Try me on Runboat\n\n|badge1| |badge2| |badge3| |badge4| |badge5|\n\nCurrently the reservation is performed by adding reserved quantities on\nquants, which is fine as long as the reservation is made right after the\norder confirmation. This way, the first arrived, first served principle\nis always applied. But if you release warehouse operations in a chosen\norder (through deliver round for example), then you need to be sure the\nreservations are made in respect to the first arrived first served\nprinciple and not driven by the order you choose to release your\noperations.\n\nAllow each delivery move to mark a quantity as virtually reserved.\nSimple rule would be first ordered, first served. More complex rules\ncould be implemented.\n\nWhen the reservation of a picking move occurs, the quantity that is\nreserved is then based on the quantity that was promised to the customer\n(available to promise):\n\n- The moves can be reserved in any order, the right quantity is always\n reserved\n- The removal strategy is computed only when the reservation occurs. If\n you reserve order 2 before order 1 (because you have/want to deliver\n order 2) you can apply correctly fifo/fefo.\n\n - For instance order 1 must be delivered in 1 month, order 2 must be\n delivered now.\n - Virtually lock quantities to be able to serve order 1\n - Reserve remaining quantity for order 2 and apply fefo\n\n- Allow to limit the promised quantity in time. If a customer orders now\n for a planned delivery in 2 months, then allow to not lock this\n quantity as virtually reserved\n- Allow to perform reservations jointly with your delivery rounds\n planning. Reserve only the quants you planned to deliver.\n\nWhen move qty is not completely satisfied on release, the remaining qty\nis split and attached to a new picking that can be released later.\n\nImportant: if the \"Stock reservation horizon\" is set, the qty is\ncalculated on moves which have an expected date not beyond $today +\n$horizon (in days).\n\nImportant: Moves without a warehouse set are not supported. If the\nwarehouse is not set on the move, the \"Ordered Available to Promise\"\nQuantity will always be 0. It will also not be considered as consuming\nexisting stock. The warehouse gets set by the Stock rule, if the Rule is\nnot assigned to a warehouse, also the move will not end up with a\nwarehouse.\n\n**Table of contents**\n\n.. contents::\n :local:\n\nConfiguration\n=============\n\nIn Inventory > Configuration > Routes, activate the option \"Release\nbased on Available to Promise\" on the routes where you want to use the\nfeature.\n\nTo modify the horizon go to \"Inventory > Settings\" and change \"Stock\nreservation horizon\".\n\nUsage\n=====\n\nWhen an outgoing transfer would generate chained moves, it will not. The\nchained moves need to be released manually. To do so, open \"Inventory >\nOperations > Stock Allocation\", select the moves to release and use\n\"action > Release Stock Move\". A move can be released only if the\navailable to promise quantity is greater than zero. This quantity is\ncomputed as the product's virtual quantity minus the previous moves in\nthe list (previous being defined by the field \"Priority Date\").\n\nThis behaviour is activated by stock route by setting the option\n\"Release based on Available to Promise\".\n\nBy default, when an outgoing transfer is released, a backorder is\ncreated for the remaining quantities for products not available at\nrelease time. This behaviour can also be changed by stock route by\nsetting the option \"No backorder at release\". In such a case, moves\ncreated for unavailable products will remain in the original outgoing\npicking and no backorder will be created.\n\nOne a picking is released, you can also ensure that new move will no\nmore be assigned to a released picking by setting the option \"Prevent\nnew move after release\". on the stock picking type.\n\nAt the end of the picking process (when the picking is validated) of an\noutgoing transfer, if a backorder is created, the chained moves can be\nautomatically unreleased. This behaviour is activated by setting the\noption \"Unrelease on backorder\" on the stock picking type.\n\nBug Tracker\n===========\n\nBugs are tracked on `GitHub Issues <https://github.com/OCA/stock-logistics-reservation/issues>`_.\nIn case of trouble, please check there if your issue has already been reported.\nIf you spotted it first, help us to smash it by providing a detailed and welcomed\n`feedback <https://github.com/OCA/stock-logistics-reservation/issues/new?body=module:%20stock_available_to_promise_release%0Aversion:%2018.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_.\n\nDo not contact contributors directly about support or help with technical issues.\n\nCredits\n=======\n\nAuthors\n-------\n\n* Camptocamp\n* BCIM\n\nContributors\n------------\n\n- Guewen Baconnier <guewen.baconnier@camptocamp.com>\n- Simone Orsi <simone.orsi@camptocamp.com>\n- Jacques-Etienne Baudoux <je@bcim.be>\n- Dung Tran <dungtd@trobz.com>\n- Laurent Mignon <laurent.mignon@acsone.eu>\n- Michael Tietz (MT Software) <mtietz@mt-software.de>\n\nOther credits\n-------------\n\nThe development of this module has been financially supported by:\n\n- Camptocamp\n\nMaintainers\n-----------\n\nThis module is maintained by the OCA.\n\n.. image:: https://odoo-community.org/logo.png\n :alt: Odoo Community Association\n :target: https://odoo-community.org\n\nOCA, or the Odoo Community Association, is a nonprofit organization whose\nmission is to support the collaborative development of Odoo features and\npromote its widespread use.\n\nThis module is part of the `OCA/stock-logistics-reservation <https://github.com/OCA/stock-logistics-reservation/tree/18.0/stock_available_to_promise_release>`_ project on GitHub.\n\nYou are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.\n",
"bugtrack_url": null,
"license": "LGPL-3",
"summary": "Release Operations based on available to promise",
"version": "18.0.1.1.1.4",
"project_urls": {
"Homepage": "https://github.com/OCA/stock-logistics-reservation"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "c555082a2b2cae0dc92f78a6113320ed181876eef086a6b2df2c8caac5b58312",
"md5": "7282e273096ad1b0adf8344182b0150b",
"sha256": "3920ef004e88ebc8d88c1540286f7b12324cb3c87a25b1874bfea759689b4c87"
},
"downloads": -1,
"filename": "odoo_addon_stock_available_to_promise_release-18.0.1.1.1.4-py3-none-any.whl",
"has_sig": false,
"md5_digest": "7282e273096ad1b0adf8344182b0150b",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.10",
"size": 105547,
"upload_time": "2025-07-23T03:47:53",
"upload_time_iso_8601": "2025-07-23T03:47:53.337119Z",
"url": "https://files.pythonhosted.org/packages/c5/55/082a2b2cae0dc92f78a6113320ed181876eef086a6b2df2c8caac5b58312/odoo_addon_stock_available_to_promise_release-18.0.1.1.1.4-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-07-23 03:47:53",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "OCA",
"github_project": "stock-logistics-reservation",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [
{
"name": "openupgradelib",
"specs": []
}
],
"lcname": "odoo-addon-stock-available-to-promise-release"
}
JSON
