CRM Team ZIP Assignment

Assignment Logic

The assignment is triggered on partner create/write when ZIP, company, country, state, or exclusion flag changes. A contextual action is also available from partner views for manual assignment. The system:

1. Finds all active teams with ZIP assignment enabled in the partner’s company
2. Filters teams by matching countries and states (if specified)
3. For each eligible team, evaluates the optional pre-zip match condition (Odoo domain expression). If the partner does not satisfy the condition, the team is skipped.
4. Tests each remaining team’s regex patterns against the partner’s ZIP code
5. Selects the team with highest priority if multiple matches exist
6. Logs assignment activity for audit purposes

Assignment Rules

1. Only active teams with “Active ZIP Assignment” enabled are considered
2. Only teams in the same company as the partner are considered
3. Teams must have matching countries (partner’s country must be in team’s countries)
4. Teams must have matching states (partner’s state must be in team’s states, if team has states defined)
5. If a team has a pre-zip match condition, the partner must satisfy the condition (Odoo domain) before ZIP regex matching is performed. If not set, all partners are considered.
6. Partners without a company, ZIP code, country, or state are not assigned
7. Partners with “Exclude from ZIP Assignment” checked are not assigned
8. When multiple teams match, the team with highest priority is selected
9. Invalid regex patterns are prevented by validation constraints at input time

Table of contents

Geographic Coverage

• Countries: Teams will only be considered for partners located in the selected countries
• States: Teams will only be considered for partners in the selected states
• Domain Filtering: State selection is automatically filtered based on selected countries

Pre-Zip Match Condition

You can further restrict team assignment by specifying a domain condition in the “Pre-Zip Match Condition” field. This uses Odoo’s domain syntax (e.g., [(‘is_company’, ‘=’, True)]). Only partners matching this condition will be considered for ZIP pattern matching for this team.

Pre-Zip Match Condition Examples

Some example domain conditions:

• [(‘is_company’, ‘=’, True)] — Only assign to partners that are companies
• [(‘type’, ‘=’, ‘contact’)] — Only assign to contacts
• [(‘industry_id’, ‘!=’, False)] — Only assign to partners with an industry set

You can combine multiple conditions, e.g. [(‘is_company’, ‘=’, True), (‘country_id’, ‘=’, ref(‘base.us’))]

ZIP Pattern Examples

All patterns are validated in real-time to ensure they are valid Python regular expressions:

• ^1[0-5].* - ZIP codes starting with 10-15
• ^2[0-9].* - ZIP codes starting with 20-29
• ^751.* - ZIP codes starting with 751
• .*123$ - ZIP codes ending with 123
• ^[1-3].* - ZIP codes starting with 1, 2, or 3
• ^(10|20|30).* - ZIP codes starting with 10, 20, or 30

Pattern Validation

The system validates regex patterns when they are entered:

• Invalid patterns will show an error message immediately
• Error messages include the specific regex error for debugging
• Only valid patterns can be saved to the database

Automatic Assignment

Partners are automatically assigned to CRM teams when:

• A partner is created with complete geographic information (ZIP, country, state)
• A partner’s ZIP code is modified
• A partner’s country or state is changed
• A partner’s company is changed
• The exclusion flag is modified

For each team, if a “Pre-Zip Match Condition” is set, the partner must match this condition before ZIP pattern matching is performed. If not set, all partners are considered for ZIP matching.

Manual Assignment

You can also trigger assignment manually:

• Use the contextual action available in partner views
• This is useful for reassigning existing partners after updating team configurations or after addon installation

Assignment Requirements

For automatic assignment to work, partners must have:

• A ZIP code
• A country
• A state
• A company
• “Exclude from ZIP Assignment” must be unchecked

Authors

• Binhex

Contributors

• Adasat Torres de León <a.torres@binhex.cloud>
• Rolando Pérez Rebollo <r.perez@binhex.cloud>

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/crm project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.