> For the complete documentation index, see [llms.txt](https://docs.kernel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kernel.ai/data/firmographics/location.md).

# Location

{% embed url="<https://pub-8e1d08f439ec43bdbb79f1055a273a02.r2.dev/location-operating-registered-53a294c8.mp4>" %}

Location sounds like one field. In Kernel, it is deliberately two: where the entity operates, and where it is legally registered.

The operating address is where the entity actually works. Think headquarters, head office, main office, or the physical site your CRM account is meant to track. The registered address is the legal address from a corporate registry or another authoritative filing.

For most companies, these addresses are the same. Kernel mirrors them unless the evidence says there is a real split.

## How Kernel determines location

Kernel researches location from company websites, regulatory filings, news reports, business registrations, and other evidence tied to the resolved entity.

The split matters in common cases. A company may be registered at an agent address but operate from another city. A branch, store, plant, or office may operate at one street address while the legal entity is registered somewhere else. A remote-first company may have no operating street address but still have a registered office.

Use operating location for territory assignment, routing, and understanding where work actually happens. Use registered location for legal identity, compliance, and incorporation context.

## Key data points

Kernel returns each of these fields for both <mark style="background-color:$warning;">operating and registered locations</mark>.

| Label     | Description                                                                            |
| --------- | -------------------------------------------------------------------------------------- |
| Address   | Street address for the operating or registered location.                               |
| City      | City or locality for the address.                                                      |
| State     | State, province, region, or other administrative area for the address, when available. |
| Country   | Country for the address.                                                               |
| Reasoning | Why Kernel selected the location and which evidence supports it.                       |

The useful part is not just having two addresses. It is knowing which question each address answers.

See the [Kernel Account object reference](/integrations/salesforce-integration/kernel-account-object-reference.md#location) for field types and help text.