Field Service - Sale Stock From POS
This module adds compatibility between field_service_sale_stock and pos_order_to_sale_order, allowing the creation of FSM orders directly from the POS. It also includes logic to handle refunds.
Table of contents
Usage
Instructions for Creating FSM Orders from Point of Sale
1. Create or Edit a Product
Configure the product to create an FSM order per sale and add it to the Point of Sale (POS).
2. Configure Stock Update Behavior
In the POS settings, you can choose how stock updates:
Real-time: FSM orders and pickings will be linked immediately.
On session close: FSM orders and pickings will be linked only when the POS session is closed.
3. Configure the user who will recive notifications on fsm order creation
In the POS settings, under Sale Order Creation you can set the person who will recive notifications to review the orders and assign them.
4. Open a New Point of Sale Session
5. Add the Configured Product to the Order
6. Select a Customer
7. Click on “Create Order”
8. Behavior Based on the Selected Option
Create Draft Sale Order
A draft Sale Order will be created.
To process it, go to Quotations/Orders, select the order, and confirm it.
Real-time stock: An FSM order will be created and linked immediately to the pickings.
Non-real-time stock: You will need to close the POS session to link the FSM order to the pickings.
Create Confirmed Sale Order
A confirmed Sale Order will be created directly.
This flow works the same whether stock updates are real-time or not.
An FSM order will be created and linked to the Sale Order automatically.
Create Delivered/Invoiced Sale Order
These options will automatically complete both the FSM order and the associated pickings.
The difference between them is that Invoiced will also generate an invoice.
Refunds
Refunds can be processed directly from the POS. The behavior varies depending on whether it is a full or partial refund:
Full Refunds
If the FSM order is not yet completed, it will be canceled.
Partial Refunds
The picking will be updated by removing the refunded products.
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
APSL:
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-from-pos 17.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_sale_stock_from_pos-17.0.1.0.0.4-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_fieldservice_sale_stock_from_pos-17.0.1.0.0.4-py3-none-any.whl |
Release files / odoo_addon_fieldservice_sale_stock_from_pos-17.0.1.0.0.4-py3-none-any.whl
| Download URL | odoo_addon_fieldservice_sale_stock_from_pos-17.0.1.0.0.4-py3-none-any.whl |
|---|---|
| Size | 46.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
671b0e0545858a677b40d6bd464de17bf92e275a24f6e5fd1b68ea54554c2f36
|
|
BLAKE2b-256 checksum How to use checksums |
7e19e16bcd1a5172b43a0420be349a90e76494a7ff417c4de33ae4a61885e3e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for odoo-addon-fieldservice-sale-stock-from-pos 17.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.
