How to Keep Multiple Business Locations in a Lead List

Two branches can share a website while serving different territories and handling different operational needs. If you remove one because the domain matches, you may erase a legitimate prospect.

Use one row per relevant branch, with a stable location ID, address, and source link. Connect branches through a parent-company ID. A shared website alone is not a reason to combine separate locations.

The parent-and-location example below keeps branches distinct without losing their account relationship.

Choose the unit of the list

A company-level list works when you are researching a single account relationship. A location-level list works when you sell a service delivered to individual sites, assign geographic territories, or need to understand branch coverage.

Do not switch between those units silently. Label each row's record type or keep company and location records on separate sheets. Otherwise, a total of 80 rows could mean 80 companies, 80 branches, or a mixture that nobody can explain.

For an early-stage list, one location sheet with a parent-company field is often sufficient. More complex account structures can move into linked tables or a CRM later.

Use separate parent and location identifiers

Create a stable parent-company ID and a separate location ID. IDs should survive corrections to names, addresses, or domains. Avoid using the spreadsheet row number as the permanent identifier because sorting changes positions.

Consider this fictional structure:

The two supply branches remain distinct even though their parent and domain match. Their contact details, territory, and next action can now differ without creating contradictory company records.

Preserve evidence for the specific branch

Save the branch's location-page URL or Maps source link, not just the corporate homepage. Record the full address as it appears in the source and keep any branch-specific telephone number separate from a central switchboard.

When information conflicts, retain a short note about the discrepancy and its source. Do not replace a local address with headquarters simply because the headquarters address is easier to find.

Prospect describes support for keeping separate Maps business locations even when they share a website. Review those location records after capture, then add your parent IDs and territory fields in the working list.

Do not assume a location controls purchasing

A branch is a potential service location, not automatically an independent buyer. Record purchasing authority as Confirmed local, Confirmed central, or Unknown only when the evidence supports that label.

If a contact explains that purchasing is centralized, preserve the branch record and link it to the parent account. That branch may still matter for service delivery, requirements, or a later account expansion.

A useful next question is: Who decides which supplier this location uses? It is more precise than treating the person answering the phone as the buyer.

Review duplicates using location evidence

Compare domain, address, source link, and branch name together. Two slightly different names at the same address may be duplicates, but they might also be separate businesses in a shared facility.

Likewise, one company may have moved. Before combining an old and new address, determine whether the sources describe a relocation or two active sites. Keep an old source note when it explains why the change was made.

Flag likely duplicates for review before deleting anything. Merge useful notes into the retained record and record the retired ID so future imports can be reconciled.

Decide whether to keep two similar rows

Use the following examples as review decisions, not automatic deletion rules:

If the parent is unknown, leave Parent ID blank and add a relationship-research note. A location does not need a guessed parent to remain useful in a territory list.

Count companies and locations separately

Report both counts when the distinction affects planning. In the fictional table above, you have two parent companies and three locations. You should not describe that as three independent company accounts.

This becomes especially important when handing a list to another rep. Include the unit of the list, the parent relationship, and any known restrictions on contacting branches. A clear structure prevents accidental double coverage and preserves the locations you actually meant to research.

Related Questions

Should branches share one website field?

They may share the same company domain, but each row should also retain a location-specific source where available. The shared website identifies the parent; it does not replace the branch address or local contact route.

Can I deduplicate by company name alone?

Use the name as a review signal, not a deletion rule. Compare location evidence and parent relationships first. Similar names may describe different branches, unrelated companies, or a business that has relocated.

See duplicate review before deleting rows, and multi-location company research for a fuller account structure.