Every partner, a trustworthy reference code
Automatic, configurable, unique reference codes for contacts, customers, and vendors — assigned the moment a partner is created, visible everywhere, and never duplicated.
Odoo's native Reference field is a free-text box: nobody fills it in consistently, it is never enforced as unique, and it is easy to overlook after install. Staff end up hand-typing customer numbers, producing duplicates, gaps, and codes that mean nothing to accounting or sales downstream — especially painful when migrating from a legacy system where every customer already had a number.
Partner Sequence Codes assigns independent, fully configurable reference codes for contacts, customers, and vendors automatically on creation. One record can carry a customer code and a vendor code at once, every code is guaranteed unique, existing partners can be backfilled in one action, and the codes are visible in the form and list view from the moment you install.
Everything a partner numbering system needs
Every capability below is implemented in the module.
Automatic assignment on creation
Every new partner receives a unique contact code the instant it is created, with zero manual steps — and a customer or vendor code the moment it gains that rank.
Separate contact, customer & vendor codes
One partner record can hold a contact code, a customer code, and a vendor code simultaneously, each generated by its own independently configured sequence.
Fully configurable format with live preview
Control prefix, suffix, zero-padding width, starting number, increment step, and date tokens such as {year} — and see an example code update live as you edit.
Alphabetic or numeric sequencing
Choose plain numeric numbering, or an alphabetic mode that derives the code from the partner's first letter for name-based grouping — independently per sequence.
Guaranteed uniqueness
Codes can never collide within a company and scope, whether generated automatically or typed in by hand — a clear validation error blocks any conflicting entry.
Guided bulk backfill
One wizard numbers every existing partner that matches a scope, previewing how many records will be affected before you run it — ideal for migrating legacy data.
On-demand generation & correction
Set any sequence to manual mode and generate codes on demand, or regenerate a single wrong code through a controlled, uniqueness-safe action — no direct database edits.
Full assignment audit trail
Every assignment, backfill, and regeneration is logged with the user and timestamp, so admins can always see who got which code and when.
Multi-company & optional mandatory codes
Configure a distinct sequence per company, and optionally require a code before a partner of a given scope can be saved — both switched off by default.
How it works
Configure your sequences
Set the prefix, padding, and format for contact, customer, and vendor codes from one screen, checking the live preview as you go.
Create or import partners
New contacts, customers, and vendors get their codes automatically; imported records that already carry a legacy value keep it untouched.
Backfill existing records
Run the backfill wizard once to number your existing partner base, previewing the affected count before committing.
Search, track, and correct
Find any partner by code, review the full assignment history, and regenerate an individual code whenever a correction is needed.
See it in action
From contact list to configuration screen to audit log — every part of the workflow.
Contact codes appear as a searchable column in the standard Contacts list — visible out of the box, no view editing required.
The Reference Codes group shows contact, customer, and vendor codes side by side on one partner, with Generate and Regenerate buttons in the header.
Every sequence — contact, customer, vendor — is managed from a single configuration list, one row per scope and company.
Prefix, suffix, padding, and step are all configurable, with a live example code and the underlying counters shown for full transparency.
A dedicated Settings block lets an admin opt in to showing the code inside the partner's display name, choosing its position.
Every assignment, backfill, and regeneration is recorded with the partner, scope, code, and user, giving a complete audit trail.
Frequently asked
Does this replace Odoo's built-in Reference field?
No. The module adds three dedicated fields — contact, customer, and vendor code — and never touches the native Reference field, so it cannot collide with other apps that use it.
What happens to partners I already have when I install?
Nothing changes automatically — new codes apply to future records only. Run the Backfill wizard whenever you're ready to number your existing partners; it previews the affected count first and never overwrites an existing code unless you choose to.
Can a customer and a vendor share the same code?
Uniqueness is enforced within each scope: two partners can never share the same customer code, and separately can never share the same vendor code, within the same company. The same string may appear as a customer code on one record and a vendor code on another, or even both on the same record.
Does the code appear at the Point of Sale?
Not in this release. The code fields are plain indexed fields on the partner record, so a POS lookup bridge is a natural future add-on; today the focus is back-office numbering, search, and reporting.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Automatic, configurable reference codes for contacts, customers, and vendors — unique, visible, and backfillable across your whole partner base.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Contacts (contacts)
• Invoicing (account) • Discuss (mail) |
| Lines of code | 696 |
| Technical Name |
cerevantix_partner_sequence |
| License | OPL-1 |
| Website | https://cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module