Sale Exception
This module allows you attach several customizable exceptions to your sale order in a way that you can filter orders by exceptions type and fix them.
This is especially useful in an scenario for mass sales order import because it’s likely some orders have errors when you import them (like product not found in Odoo, wrong line format etc.)
Table of contents
Configuration
If you are going to use Customer sale warning and Product warning, for setting corresponding information, you need to:
Go to Settings > User & Companies > Users.
Edit your user.
Check “A warning can be set on a product or a customer (Sale)” group.
Install sale_management addon.
Usage
Not Enough Virtual Stock: #. Go to Sales > Products > Products. #. Create new storable product without stock available. #. Go to Sales > Orders > Quotations #. Create new quotation. #. Add product without stock available. #. An exception will be displayed.
No ZIP code on destination: #. Go to Contacts. #. Edit or create new contact. #. Set empty zip code. #. Go to Sales > Orders > Quotations #. Create new quotation. #. Set delivery address with no zip code. #. An exception will be displayed.
Product warning: #. Go to Sales > Products > Products. #. Edit or create new product. #. Go to Sales tab. #. Set your desired warning option under the Warning when Selling this Product group. #. Set some warning message. #. Go to Sales > Orders > Quotations #. Create new quotation. #. Add product with warning message. #. An exception will be displayed.
Partner warning: #. Go to Contacts. #. Edit or create new contact. #. Go to Internal notes tab. #. Set warning option according to Warning on the Sales Order group. #. Set some warning message. #. Go to Sales > Orders > Quotations #. Create new quotation. #. Set partner with warning message. #. An exception will be displayed.
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
Raphaël Valyi <raphael.valyi@akretion.com>
Renato Lima <renato.lima@akretion.com>
Sébastien BEAU <sebastien.beau@akretion.com>
Guewen Baconnier <guewen.baconnier@camptocamp.com>
Yannick Vaucher <yannick.vaucher@camptocamp.com>
Simone Orsi <simahawk@gmail.com>
SodexisTeam <dev@sodexis.com>
Mourad EL HADJ MIMOUNE <mourad.elhadj.mimoune@akretion.com>
Raphaël Reverdy <raphael.reverdy@akretion.com>
Florian da Costa <florian.dacosta@akretion.com>
Iván Todorovich <ivan.todorovich@druidoo.io>
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.
This module is part of the OCA/sale-workflow 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-sale-exception 16.0.2.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 | Reset |
|---|---|---|---|---|
| odoo_addon_sale_exception-16.0.2.0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_sale_exception-16.0.2.0.0.4-py3-none-any.whl
| Download URL | odoo_addon_sale_exception-16.0.2.0.0.4-py3-none-any.whl |
|---|---|
| Size | 155.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6d3ca5b51ce123e1943fdf204b1bb2067ccc035f34cdc837deeb8bfd3b52d5c6
|
|
BLAKE2b-256 checksum How to use checksums |
d55a3f19531b1d0e9b1d46e8cddf40c9a815a137ba1f3c9b06d14b5702ff5574
|
| 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-sale-exception 16.0.2.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.
