This module allow user to add optional sequences to some document model. On which sequence is used, is based on domain matching with document values (and original sequence will be bypassed).
For example, it is now possible to,
- Avoid using Odoo automatic sequence on invoice and vendor bill with old style sequence.
- Customer payment and vendor payment to run on different sequence.
- Assign different sales order sequence based on customer region.
This is a base module and does nothing by itself. Following are modules that will allow managing sequence options for each type of documents, I.e.,
- Purchase Order: purchase_sequence_option
- Invoice / Bill / Refund / Payment: account_sequence_option
- Others: create a new module with few lines of code
auto_awesome What this module does
AI-generated from the code · Odoo 18.0This base module lets administrators define alternative numbering sequences for documents, chosen automatically by matching rules on the document's own values. It does nothing on its own; other modules must enable it for each document type.
This is a technical foundation module: it adds the screens and rules needed to set up alternative document numbering, but it does not change any document by itself. Other modules (for example for purchase orders or invoices) must be installed to actually apply it.
Where it appears in Odoo: - A new menu "Manage Sequence Options" under the Settings area, with a list and form screen. - On the form you choose the model the options apply to, the company, and a toggle "Use sequence options". - Each option line has a description, a matching rule ("Apply On"), and the sequence to use, with its prefix, suffix and implementation shown for information.
Business rules and automatic behaviour: - When a document asks for its next number, Odoo first looks for an option whose matching rule fits that document; if one is found, that sequence is used instead of the normal one. - If no option matches, the original Odoo sequence is used as a fallback. - If more than one option matches the same document, an error is raised: "Multiple optional sequences found for this model!". - Options are filtered by company, and multi-company record rules restrict who sees which options.
Access: ordinary users can only read the configuration; only Settings administrators can create, change or delete it.
Depends on
Required by other modules
Menus it adds
Models and fields (3)
- ir.sequence · extends an existing model
- ir.sequence.option · new modelname, model (Apply On Model), company_id (Company), option_ids (Sequence Options), use_sequence_option (Use sequence options)
- ir.sequence.option.line · new modelname (Description), model, prefix (Prefix), suffix (Suffix), base_id, company_id, sequence_id (Sequence), filter_domain (Apply On), implementation (Implementation), use_sequence_option
Text generated by AI (DeepSeek) from reading the Odoo 18.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: 5 confirmed, 4 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/server-tools.
terminal Installation and usage
OCA documentation · Odoo 18.0Usage
Source · Odoo 18.0To use this module, you need to:
- Go to Settings \> Technical \> Sequences & Identifier \> Manage Sequence Options.
- Based on extended module installed, different document types will be listed, i.e., Purchase Order.
- Activite "Use sequence options" to use, if not, fall back to normal sequence.
- For each option, provide,
- Name: i.e., Customer Invoice for Cust A., Customer Payment, etc.
- Apply On: a filter domain to test whether a document match this option.
- Sequence: select underlining sequence to perform
Note:
- If no options matches the document, fall back to normal sequence.
- If there are multiple sequence options that match same document, error will be raised.
No verified information in OCA: Installation, Configuration.
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.