How to record a multi-location customer in your CRM

Short answer

Do not keep a multi-location customer as a single CRM record. Create one parent account for the head office, a separate linked record for every location, and open opportunities at the location level. With one flat record the locations disappear and so does the revenue you have not won. Structured properly, you can see which locations buy, which do not, and where the revenue comes from on one screen.

What is a multi-location customer?

A multi-location customer is one legal entity that operates from several sites and makes part of the buying decision at those sites.

Retail chains, multi-plant manufacturers, hospital groups, hotel groups, distributors with regional warehouses. They all behave the same way: the contract is signed centrally, the demand is born locally.

So a multi-location customer is not one customer, it is a network. If your CRM or your ERP does not see it as a network, it cannot see half of your sales.

Why does one flat record cause problems?

A single record throws every location's activity into the same bucket. Three things break at once.

First, visibility. Look at a customer with 12 locations through one record and the screen says "we have this account", while you may only be selling to 2 of them.

Second, ownership. Different reps talk to different locations, and because there is only one record the notes overwrite each other. Nobody can tell who discussed what.

Third, forecasting. Revenue is summed into one line, so you cannot see which site is growing and which has stopped. The report is accurate and the decision is still wrong.

How do you structure the records correctly?

A simple three-layer structure is enough for most B2B companies.

1. Parent account: the legal entity and head office. Contract, payment terms and the head-office relationship live here.
2. Location record: each site as a separate record linked to the parent. Address, site contact and usage volume live here.
3. Opportunity: what gets sold to which location. The opportunity links to the location, the location links to the parent.

The critical rule: never repeat the same data on two layers. What belongs centrally stays central, what is born at a site stays there. Once data repeats, duplicate records come back within months.

Should the opportunity sit on the head office or the location?

The opportunity belongs where the buying decision is made.

If the head office buys centrally and the sites are only delivery points, the opportunity stays central. If locations buy from their own budget, each deserves its own opportunity.

In a mixed model both run together: an umbrella contract centrally and separate opportunities at the sites. What matters is that the same amount is never counted twice.

How do you calculate the opportunity per location?

Example: the customer has 12 locations and you sell to 2. The locations you sell to generate an average of 150,000 a year each. Ten locations are uncovered.

Current revenue is 2 × 150,000 = 300,000. The theoretical ceiling is 12 × 150,000 = 1,800,000. Open opportunity is 1,500,000, which is five times your current revenue inside one existing account.

This number never appears if your CRM has no location records, and because it never appears nobody chases it. It is not an industry statistic; it is a calculation you can run on your own data in two minutes.

Which fields should be mandatory on a location record?

Adding fields is not the fix. Four are usually enough.

• Parent account link. Leave it empty and the record is orphaned.
• Location. City and district, the basis of all reporting.
• Site contact and their role. Who actually moves the work forward.
• Coverage status. Selling, not selling, or lost.

Before adding a fifth field, ask: if this field is empty, which decision cannot be made? If there is no answer, the field is not needed.

How do you fix location records that are already broken?

A four-step cleanup is enough.

1. List records created with the same tax number or a similar trading name.
2. Decide which one is the head office and which are locations, then make the head office the parent.
3. Link the rest to the parent instead of merging them. Merging destroys the location data.
4. Move open opportunities to the right location and close the ones with no owner.

After the cleanup, push your segmentation rules down to the location level so the structure holds.

Why does location data never get filled in?

Because the data entry sits with the person who gets none of the benefit.

A rep leaves the meeting knowing the site name, the contact and the volume. Writing it into the CRM gains them nothing today; the gain goes to the manager reading a report three months later. So the field stays empty.

The real problem is not that data entry is hard. It is that good data is never produced at all. The fix is not more mandatory fields, it is pulling the data out of the conversation itself.

How does this change sales decisions?

What you already have: a working relationship with this customer, a payment history and a reference.

What you are giving away: the revenue in the uncovered locations, lost without noticing because nobody kept location records. In most companies it was available for far less effort than winning a new customer.

What you get back: a clear answer to "how many locations are there, and how many are ours" for every account. That question changes target planning and how you split territories.

Closync AI is an AI layer that turns sales conversations into high-quality CRM/ERP data and that data into sales decisions. It extracts location, decision maker and coverage details from the conversation itself, so the structure is not left to manual entry.

FAQ

Should each location get its own customer record?

Yes, but not a standalone one. Every location is a separate record linked to the parent account. Break the link and the record is orphaned.

Is tagging locations inside one record enough?

It works short term, not long term. Tags do not carry opportunities or revenue, so you cannot forecast or assign ownership per location.

Who should you talk to at a multi-location customer?

Both. The head office sets the contract, the location decides usage. A central meeting goes nowhere if you do not know the site contact.

Can the ERP keep one record while the CRM keeps locations?

Yes. The ERP invoices the legal entity, the CRM attaches the relationship to the site, and the two are matched through the parent account.

Last updated: 20 October 2026