Field Service - Stock Picking
This module lets you send materials out to a Field Service location and receive materials back from it directly from the Field Service Order, using standard stock transfers (pickings).
On the Field Service Order you can:
list the outgoing and the incoming products;
choose the operation type (stock.picking.type) used for the outgoing and for the incoming transfer;
create the outgoing and/or incoming transfer in a single click; a transfer is only created when there are products that are not part of a transfer yet.
The outgoing and incoming operation types can be pre-set on the Field Service Order Template. When a template is selected on an order, its operation types are applied and take precedence over the warehouse defaults.
The created transfers are left in draft and are processed by the user through the standard transfer flow (mark as todo, check availability, validate).
Outgoing and incoming transfers are reachable from the Field Service Order through the Deliveries and Returns smart buttons provided by fieldservice_stock.
Table of contents
Configuration
To pre-set the operation types used by Field Service Orders:
Go to Field Service > Configuration > Templates and open (or create) a template.
Set the Outgoing Operation Type and/or the Incoming Operation Type.
When this template is selected on a Field Service Order, the operation types are copied onto the order, taking precedence over the warehouse defaults.
Usage
Open a Field Service Order and go to the Inventory tab.
Set the Outgoing Operation Type and/or the Incoming Operation Type (they default to the warehouse delivery and receipt operation types, or to the ones pre-set on the order template, see Configuration).
List the products to send under Outgoing Products and the products to receive under Incoming Products.
Click Create Transfers. The system creates an outgoing transfer for the outgoing products and an incoming transfer for the incoming products, when there is something to transfer.
Process each transfer with the standard flow (validate it from its own form view).
Use the Deliveries and Returns smart buttons to navigate to the related transfers.
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
Lorenzo Battistini <https://github.com/eLBati>
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 maintainer:
This module is part of the OCA/field-service project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo-addon-fieldservice-stock-picking 16.0.1.0.0.4
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 | Actions Reset |
|---|---|---|---|---|
| odoo_addon_fieldservice_stock_picking-16.0.1.0.0.4-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_fieldservice_stock_picking-16.0.1.0.0.4-py3-none-any.whl |
Release files / odoo_addon_fieldservice_stock_picking-16.0.1.0.0.4-py3-none-any.whl
| Download URL | odoo_addon_fieldservice_stock_picking-16.0.1.0.0.4-py3-none-any.whl |
|---|---|
| Size | 35.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e062d619126e429205bee40455c365e98c477447fdb9637c00015cb6bdc7d250
|
|
BLAKE2b-256 checksum How to use checksums |
4f071d44b62dae960ff0256fda63ea733efd088f22e517959f00ce34cb0663ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-fieldservice-stock-picking 16.0.1.0.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.