Field Service - Sale Stock Route
This module integrates the fieldservice_sale_stock and fieldservice_route modules, enabling automatic generation of FSM order day routes from sales orders.
Requirements for Confirming a Sales Order
If a sales order contains a product that generates an FSM order, the following conditions must be met before confirmation:
An FSM location must be set.
The FSM location must have an assigned route.
The FSM route must have a designated FSM person.
The FSM route must have assigned working days.
Automatic Scheduling of FSM Orders
If the commitment_date and commitment_date_end fields are not set on the sale order upon confirmation, they will be automatically assigned to the next available route day based on the FSM location’s schedule.
If these fields are set, the FSM order will be scheduled accordingly, with validation ensuring that the commitment_date falls on a valid route day. This validation can be overridden by enabling the “Force Schedule” option on the FSM route to allow scheduling on any day.
This module also introduces a “Postpone Delivery” button in the FSM order form view, allowing users to reschedule the order to the next available route day based on the FSM location’s schedule.
Table of contents
Usage
To use this module, you need to:
Navigate to Sales > Orders.
Create a new sales order.
Add a product that generates an FSM order (Field Service Tracking set to “Create one FSM order per sale order” on the product form).
Set the Customer and FSM Location.
Make sure the FSM Location has a route set and this route has a person assigned and route days set.
In the sale order, navigate to the ‘Other Info’ tab and set the ‘Delivery Date’ and ‘Delivery End Date’ fields. You can also leave them empty to have the system automatically assign the next available route day.
Confirm the sale order.
If the ‘Delivery Date’ and ‘Delivery End Date’ fields were empty, the system will automatically assign the next available route day based on the FSM location’s schedule. If they were set, the FSM order will be scheduled accordingly. In case the ‘Delivery Date’ falls on a day that is not part of the route, the system will show an error message.
If you navigate to the FSM order, you will see that the Schedule Details are based on the ‘Delivery Date’ and ‘Delivery End Date’ fields from the sale order.
Additionally, you will find a ‘Postpone Delivery’ button in the FSM order form view, allowing you to reschedule the order to the next available route day based on the FSM location’s schedule. You can also manually reschedule the order by changing the ‘Delivery Date’ and ‘Delivery End Date’ fields in the sale order.
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
Patryk Pyczko <ppyczko@apsl.net>
Bernat Obrador <bobrador@apsl.net>
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.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-fieldservice-sale-stock-route 18.0.1.0.0.5
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_sale_stock_route-18.0.1.0.0.5-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_fieldservice_sale_stock_route-18.0.1.0.0.5-py3-none-any.whl |
Release files / odoo_addon_fieldservice_sale_stock_route-18.0.1.0.0.5-py3-none-any.whl
| Download URL | odoo_addon_fieldservice_sale_stock_route-18.0.1.0.0.5-py3-none-any.whl |
|---|---|
| Size | 46.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d1774df844e3220d3a58bcc0c038e8edaf438db94e734f2475977d8040d0cf9c
|
|
BLAKE2b-256 checksum How to use checksums |
142dc5951e9b6fe8c4205fb43bd3ae9ef96083656cbd257e2bfc3a6432971961
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-fieldservice-sale-stock-route 18.0.1.0.0.5
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.
