OdooWiki OCA HUB

United States - Counties

l10n_us_crm_county folder_open OCA/l10n-usa open_in_new
Localization License: LGPL-3

Imported from U.S. Census Bureau data. https://www.census.gov/library/publications/2011/compendia/usa-counties-2011.html

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Adds a County field to CRM leads and opportunities, so US sales teams can record the county of a contact and keep it in sync with the customer address.

This module extends the CRM leads and opportunities screens with a new County field, useful for US-based businesses that need to track the county of a prospect or customer.

Where it appears: - On the lead/opportunity form, the County field is placed just before the Country field, both in the main contact block and in the lead detail page. - In the leads and opportunities list views, the County column is available but hidden by default, so users can show it when needed.

The County field is linked to the state: only counties belonging to the selected state can be chosen, which prevents mismatched state/county combinations.

Automatic behaviour: - The county is kept in sync with the related customer address, so when the address changes the county follows. - When a lead is converted into a customer, the county recorded on the lead is copied onto the new customer record. - A county cannot be deleted while it is still used on a lead, protecting data integrity.

It touches the crm.lead model and the county reference data provided by the base US counties module.

Depends on

Models and fields (1)
  • crm.lead · extends an existing modelcounty_id

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-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 1 confirmed, 8 with no information of 9 versions.

terminal Installation and usage

No verified information

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.

info

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.