Sale Order Sequence by Operating Unit
This module use to define sequence of Sale Orders by Operating Unit.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Assign a dedicated sale order numbering sequence to each operating unit, so new sale orders are numbered per operating unit instead of using one shared sequence.
This module lets you give every operating unit its own sale order number series. On the operating unit form you get a new field, Sale Order Sequence, where you pick the numbering sequence to use for that unit.
When a sale order is created without a number, Odoo looks at the operating unit on the order (or the default operating unit if none was chosen) and, if that unit has a sequence, uses it to generate the order reference. If the unit has no sequence, the normal Odoo numbering is kept.
When the module is installed, a sequence is automatically created for each existing operating unit, named after the unit and using a prefix built from the unit code followed by "-SO", with five-digit padding. These sequences are linked to the matching operating unit.
It touches the operating unit configuration screen and the sale order creation process, and relies on the operating unit feature already provided by the sale operating unit module.
Depends on
Models and fields (2)
- sale.order · extends an existing model
- operating.unit · extends an existing modelsale_sequence_id (Sale Order Sequence)
Text generated by AI (DeepSeek) from reading the Odoo 16.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/operating-unit.
terminal Installation and usage
OCA documentation · Odoo 16.0Configuration
Source · Odoo 16.0You can change the default sequence by the one of your choice going to Settings > Technical > Sequences & Identifiers > Sequences, and editing the record Sale Order of ....
You will only have access to that section if your section has Technical features permission check marked.
No verified information in OCA: Installation, Usage.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.