Stock Request
This module was written to allow users to request products that are frequently stocked by the company, to be transferred to their chosen location.
Table of contents
Configuration
To configure this module:
Go to Stock Requests > Settings
Users should be assigned to the groups ‘Stock Request / User’ or ‘Stock Request / Manager’.
## Group Stock Request / User
Can see her/his own Stock Requests, and others that she/he’s been granted permission to follow.
Can create/update only her/his Stock Requests.
## Group Stock Request / Manager
Can fully manage all Stock Requests
Usage
## Creation
Go to ‘Stock Requests / Stock Requests’ and create a new Request.
Indicate a product, quantity and location.
Press ‘Confirm’.
Upon confirmation the request will be evaluated using the procurement rules for the selected location.
In case that transfers are created, the user will be able to access to them from the button ‘Transfers’ available in the Stock Request.
If needed to group together the Transfers from multiple Stock Requests, the user needs to set the same ‘Reference’ on them.
## Cancel
When the user cancels a Stock Request, the related pending stock moves will be also cancelled.
Known issues / Roadmap
There is no way to achieve Storck Request and Stock Request Orders. It should be developed taking into account that only Cancel and Done stock request can be archived.
It is also required to manage active field logically from Orders to SRs.
In case of multi step routes, the stock_request_id is not propagated in the downstream moves as this will then create a link / allocation to all moves in the chain. This however prevents linking other related documents (PO - stock_request_purchase, MO - stock_request_mrp) when they are generated at the end of the procurement chain. TODO: investigate propagating the value in the context instead and use this additionally to the one passed in the procurement values when generating the MO (stock_request_mrp) / PO (stock_request_purchase).
Bug Tracker
Bugs are tracked on GitHub 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.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Jordi Ballester (EFICENT) <jordi.ballester@forgeflow.com>.
Enric Tobella <etobella@creublanca.es>
Atte Isopuro <atte.isopuro@avoin.systems>
Lois Rilo <lois.rilo@forgeflow.com>
Raul Martin <raul.martin@braintec-group.com>
Serpent Consulting Services Pvt. Ltd. <support@serpentcs.com>
-
Maxime Chambreuil <mchambreuil@opensourceintegrators.com>
Steve Campbell <scampbell@opensourceintegrators.com>
Héctor Villarreal <hector.villarreal@forgeflow.com>
Kitti U. <kittiu@ecosoft.co.th>
Bernat Puig <bernat.puig@forgeflow.com>
Oriol Miranda <oriol.miranda@forgeflow.com>
Maintainers
This module is maintained by the OCA.
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.
Current maintainers:
This module is part of the OCA/stock-logistics-request project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Release files for odoo-addon-stock-request 19.0.1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo_addon_stock_request-19.0.1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_stock_request-19.0.1.0.2-py3-none-any.whl
| Download URL | odoo_addon_stock_request-19.0.1.0.2-py3-none-any.whl |
|---|---|
| Size | 214.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d8342789fcc740bcc12875baa8c9ebb85c925a88aae18514c2232b6e12e87996
|
|
BLAKE2b-256 checksum How to use checksums |
a0f36ae4dd7524501309bc197f90ed039af58ed99cbf0ea90a44e8b696ceab10
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
