Skip to Content

Sales & Customers · Odoo 20, Odoo 19, Odoo 18

New Partner Codes & Name Standard

Customer and vendor codes that never repeat, and one spelling for every name

Partner Codes & Name Standard gives every customer and vendor a code from a template you set per company, such as DT-NB-00001, with one counter per pattern that never hands out the same number twice. Contact names are written in one standard form on save, with a spelling dictionary and Arabic letter forms, and a contact with the same name as another one is flagged or refused.

Key features

The problem

Without a code on each contact, customers and vendors are told apart by name only, and names are typed in many ways: AHMAD and Ahmed, Mustafa and Mostafa, all capitals or all lower case. The same company ends up in Odoo twice, and nobody notices until the statements disagree. Codes kept in a spreadsheet get reused or skipped, and nobody knows which branch a code belongs to.

Screenshots

Contact Coding settings with customer template {company}-{branch}-{seq}, vendor template and template parts
Code templates per company, with a live example of the next code and the name standard below.
Contact list filtered by Code DT- with Customer Code, Vendor Code and Customer Branch columns
Customer and vendor codes in the contact list, searchable from the search bar.
Contact Mohamed Saleh Trading with code DT-NB-00006, Reissue button and a same-name warning with Compare
The code is issued on save, the name is standardized, and a contact with the same name is flagged.
Standardize Names dialog listing five contacts with Now and Becomes, toggles and an Apply button
Existing names change only after a preview, where each change can be unticked or corrected.
Animated demo of the Contact Coding settings with the customer and vendor code templates highlighted Play demo
Animated demo of setting up the code templates.

What it does

Code templates per company

  • Set a customer template and a vendor template for each company, for example {company}-{branch}-{seq} and {company}-V-{seq}.
  • Build templates from a company code, the branch prefix, the customer class, the state code of the address, the year the contact was created and the running number, which is required.
  • See a live example of the next code in Settings.
  • The parts a template uses become required fields on the contact form.

Counters that never repeat

  • Each code pattern has its own counter, drawn under a database row lock.
  • A new counter starts after the highest code already issued in that pattern.
  • A contact manager can reissue a code. The contact gets the next number of its current branch, the old code stays in the chatter and is never given out again.

Codes you can find

  • Customer Code and Vendor Code columns in the contact list.
  • The code is searchable in every contact field.
  • Code existing contacts in one go with Assign Codes; new contacts get their code on save.

One standard form for names

  • New and edited names are written in the standard form on save: spelling dictionary, one Arabic letter form, single spaces and capitals.
  • English names are written in Title Case.
  • Change existing names only through Standardize Names, which previews every change. Untick a change or correct it, then apply.

Same-name contacts

  • Choose whether a contact with the same name as another warns, is refused, or the check is off.
  • Matching ignores spelling differences such as Arabic letter forms.
  • All matches are listed under Same-Name Contacts. Contacts are never merged automatically.

Who it is for

A good fit for

  • Companies that need a customer or vendor number on every contact, per company or per branch.
  • Businesses with contacts typed in Arabic and English, where the same name is spelled several ways.
  • Teams that keep finding the same customer in Odoo twice.

Not a fit for

  • Merging duplicate contacts: the app never merges.
  • Silently renaming your existing contacts: old names change only through Standardize Names, after a preview.
  • Databases on Odoo Online (SaaS), which cannot install third-party apps.

Install

Requires: Contacts (contacts), Discuss (mail)

  1. Buy Partner Codes & Name Standard on the Odoo Apps Store for Odoo 18, 19 or 20.
  2. Add the module to your Odoo.sh project or to the addons path of your on-premise server.
  3. Update the apps list in Odoo and install the app. The Contacts app is installed with it if it is missing.

Odoo Online (SaaS) does not allow third-party apps, so the app cannot be installed there. Use Odoo.sh or an on-premise database, Community or Enterprise.

Every purchase includes 90 days of free support from FlexCode Systems.

Configure

  1. Open Settings > General Settings > Contact Coding and enter a customer and a vendor template, the Company Code and the Code Number Digits.
  2. If a template uses {branch} or {class}, create them under Contacts > Configuration > Contact Coding > Customer Branches and Customer Classes. They then become required on the contact.
  3. Under Contact Names, switch on Standardize Contact Names, pick the Arabic letter forms and choose whether a same name warns or blocks.
  4. In Contacts, select the contacts you already have and run Assign Codes.
SettingWhat it does
Customer CodesTemplate for customer codes. Empty template: no customer codes.
Vendor CodesTemplate for vendor codes. Empty template: no vendor codes.
Company CodeReplaces {company} in the templates. Optional.
Code Number DigitsDigits of the running number: 5 gives 00001.
Standardize Contact NamesWrites new and edited names in the standard form on save.
Arabic LettersHow Arabic names are stored, for example One Alef Form.
Same-name checkWarn, block or off.

How to use it

Create a contact

  1. Create a customer or vendor from any app and set the Coding Role: Customer, Vendor, Both or None.
  2. Fill the branch or class if the template needs it, and save. The code is issued and the name is written in the standard form.
  3. If another contact has the same name, a warning with a Compare button appears, or saving is refused, depending on the setting.

Clean up existing names

  1. Open Contacts > Configuration > Standardize Names.
  2. Check Now and Becomes for each contact, untick or correct any proposal.
  3. Click Apply. Review Same-Name Contacts for names that now match.

Reissue a code

  1. Open the contact and click Reissue next to the code.
  2. The contact gets the next number of its current branch. The old code stays in the chatter.

Limits

  • Contacts are never merged automatically.
  • Existing names are not changed until you run Standardize Names.
  • Only contact managers can reissue a code.
  • It cannot be installed on Odoo Online (SaaS).

FAQ

Can a code repeat or be reused?

No. Each code pattern has its own counter, drawn under a database row lock, and a new counter starts after the highest code already issued in that pattern.

Does it change existing names automatically?

No. New and edited names are standardized on save. Existing names change only through Standardize Names, which previews every change before applying it.

Are contacts with the same name merged?

Never automatically. Depending on the setting, a same-name contact shows a warning or is refused, and all of them are listed under Same-Name Contacts.

Which parts can a code template use?

A company code, the branch prefix, the customer class, the state code of the address, the year the contact was created and the running number, which is required. The parts a template needs become required on the contact form.

Does it work with multi-company databases?

Yes. Templates are set per company, the module respects the active company and its records, and it has been tested in multi-company databases.

Need it set up or adapted?

We configure our apps for your process, train your team and build the extra pieces you need.