Google Business Profile Store Codes for Multiple Locations

One wrong character in a location identifier can break a local product inventory feed, confuse a bulk upload, or attach data to the wrong store. Google Business Profile store codes prevent that by giving each physical location its own consistent identifier.

Store codes aren’t public, and they don’t directly improve local rankings. Their job is operational. They connect profiles, spreadsheets, Merchant Center data, and location management workflows so multi-location teams know which information belongs to which store.

Key Takeaways

• Google Business Profile store codes are unique, business-defined identifiers that connect each physical location to spreadsheets, profiles, and Merchant Center data.
• Store codes are internal operational keys, not customer-facing information or direct local SEO ranking factors.
• Business Profile and Merchant Center store_code values must match exactly, including capitalization, spacing, spelling, and leading zeros.
• Keep codes stable, document every change, and use a master location register to prevent duplicate profiles, bulk upload errors, and feed mismatches.
• For code-only updates, use the current Business Profile export and avoid changing address information in the same upload process.

What Google Business Profile store codes actually do

A store code is a unique identifier assigned to one physical business location in Google Business Profile. It can include letters and numbers, and your business chooses the format.

A value might identify a branch by its internal store number, location name, or another system your company already uses. Google’s spreadsheet examples include G1, G2, G3, Goog101, and GClaremont.

The identifier must point to one location only. Two profiles in the same account shouldn’t share it.

Store codes are internal identifiers

Customers don’t normally see this value in Google Search or Google Maps. They see customer-facing information such as the business name, address, phone number, hours, photos, reviews, and services.

A store code is used behind the scenes when your team imports or exports locations. It also helps Google connect a Business Profile location with local product data in Merchant Center.

That makes the value similar to a filing key. It isn’t information customers use, but it tells your systems which record to open.

Choose a format your team can maintain

Google lets you use a place name or a random number, provided the value is unique and consistent. For a multi-location organization, a structured format is easier to manage than random characters.

Keep the identifier:

• Unique across every location in the relevant Business Profile account.
• Short enough for staff and systems to read accurately.
• Stable for the life of the location.
• Limited to letters and numbers when possible.
• Consistent in capitalization.

For local inventory work, Google documents store_code as a text value between 1 and 64 characters. Avoid changing the value because a new naming convention looks cleaner. A stable identifier is usually more useful than a new one that requires updates across several systems.

Why multi-location businesses need store codes

Managing one profile manually is manageable. At 25, 100, or 1,000 locations, multi-location management requires a reliable way to identify each row in a spreadsheet.

Store codes help teams apply updates to the correct location during bulk imports. They reduce confusion when several stores have similar names, share a brand, or operate in the same city.

A location record may include the business name, street address, phone number, website, hours, categories, and a store code. This stable identifier keeps profile, spreadsheet, and Google Merchant Center shopping-location records aligned when other details change.

Store codes support bulk location management

A franchise operator may have several branches with the same brand name and similar service categories. Addresses can also change when a business relocates. Store codes give the team a stable internal value to carry through those updates.

Google’s bulk Business Profile import guide recommends using the same store codes and location information when working with multiple profiles.

That doesn’t mean every identifier fixes every upload problem. It means your location data has a clear structure before you send it to Google.

They don’t directly improve local SEO rankings

Adding one won’t move a business into the Local 3-Pack. It isn’t a customer-facing local SEO ranking signal, and it doesn’t replace complete business information, accurate categories, strong reviews, or relevant content.

The value is indirect. Clean identifiers help prevent data errors that can affect how a location is managed. They also support local inventory programs that can place nearby products in front of shoppers.

Treat store codes as data management infrastructure, not as an optimization trick.

Store code, Place ID, and location ID are different

Multi-location teams often use several Google identifiers at the same time. They aren’t interchangeable.

Identifier	Who creates it	Main use	Can your team choose it?
Store code	Your business	Bulk uploads and Merchant Center matching	Yes
Place ID	Google	Maps, Places, and place-related API requests	No
Business Profile location ID	Google	Business Profile account and API records	No

A store code is the only one of these values your team normally defines. You can use a store code such as GClaremont for a location, but you can’t replace a Google-generated value with it in a Maps API request.

The same rule applies to a Business Profile record. Keep a master record that stores every identifier in its own column. This prevents a marketer from copying the Maps value into a Merchant Center store_code field or using a Google-generated record value in a bulk upload.

How to find an existing store code

Google’s current interface places the code inside individual Business Profile settings, with paths that can vary by account type and permissions. Older Google My Business instructions may mention the info tab and an advanced information area, but those labels aren’t always shown with today’s path. The current path uses More, business profile settings, and Advanced settings.

Find one code in the profile

1. Sign in to the Google account that manages the location.
2. Open the Business Profile you want to review.
3. Select More.
4. Open Business Profile settings.
5. Select Advanced settings.
6. Find the Store code field.
7. Select the pencil icon to view or edit the value.

If you manage locations across several branches, select the correct profile before opening settings. Similar business names can make it easy to edit the wrong branch.

Google’s store code instructions cover the current settings path and the spreadsheet workflow for adding or changing codes.

Find codes for many locations

For a larger account, checking locations one by one is slow and increases the chance of a copy error. Use business profile manager to download your locations and review the store code column in a spreadsheet.

The export gives your team one working file for auditing names, addresses, profile status, and codes. Don’t treat the spreadsheet as a casual copy. Save the untouched export, record who edited it, and keep the upload result with the same project files.

If the field is blank, confirm that you selected the right location and have manager access. If the code still isn’t available, use the bulk spreadsheet process rather than creating a second profile.

How to add or change a store code

A store code belongs to a Business Profile location. You don’t create a separate public listing for the code.

To add one location’s code, open the profile settings path above, select the pencil beside Store code, enter a unique value, and save the change. Use the exact value your internal location system will send to Merchant Center or other connected tools.

Before saving, check three details:

• The value isn’t already assigned to another location.
• Capital letters and numbers are correct.
• The value follows your company’s naming policy.

Google says this value can be added or changed at any time. That doesn’t make frequent changes a good idea. Every connected feed, spreadsheet, script, and reporting file must replace the old value with the new one after a change.

What happens after a code changes?

The public profile name, reviews, photos, and customer-facing listing don’t change because you edited the value. The internal match does change.

If Merchant Center still contains the old value, Google can’t reliably connect that inventory row to the updated location. A feed may show a mismatch, fail validation, or stop associating products with the intended store.

Don’t reuse the old value for another branch. Retired values should remain documented as retired. Reusing them can make historical files difficult to audit and point old data to the wrong location.

Bulk upload store codes without creating duplicates

For many branches, this process is safest when it starts with your current data, not a new spreadsheet built from memory.

Prepare the spreadsheet

1. Download the manage locations export from Business Profile Manager.
2. Save an untouched copy of the export.
3. Review the current store code for every location.
4. Add codes only to rows that need them.
5. Use one unique code for each location.
6. Keep addresses and other matching information unchanged during a code-only update.
7. Check capitalization, spaces, and blank cells.
8. Upload the completed file through the manager.

Google’s Business Profile spreadsheet guide provides the supported column structure and examples for this field.

When adding new locations, assign the code before the upload. When updating existing locations, keep the existing code unless there’s a documented reason to replace it.

Avoid duplicate location records

A common mistake is to create a new row with a new code and altered location information, then upload it as an update. Google may treat that row as a new location instead of editing the existing profile.

For a code-only change, don’t change the address in the same spreadsheet process. Google gives this instruction because the address helps identify the existing location.

After the spreadsheet upload, review the result instead of assuming every row was accepted. Look for rejected rows, duplicate warnings, missing fields, and locations that remain unchanged.

A good file has:

• One row per physical location.
• One unique store code per row.
• No accidental blank codes.
• No duplicated capitalization variants.
• Current addresses that match existing profiles.
• A record of the upload date and responsible team member.

How store codes connect to Merchant Center

Google Merchant Center uses the store_code attribute to identify the physical store with a product available. This field is required for local inventory ads and free local listings.

Your Business Profile store code and Merchant Center store_code must match exactly. Google treats the field as case-sensitive, so Store123 and store123 aren’t safe substitutions.

The Merchant Center store code documentation describes this field as a unique alphanumeric identifier for a local store. It also lists the 1-to-64-character limit.

The matching process

The integration normally works like this:

1. Your business verifies its physical locations in Google Business Profile.
2. Each location has a unique store_code.
3. The Business Profile account connects to Merchant Center.
4. Your local product inventory feed includes the matching store_code.
5. Product data includes the item, price, availability, and store association.
6. Google checks the data before showing local product information.

The code doesn’t tell Google whether the product is in stock. Your inventory source supplies the product, price, and availability details. The code tells Google which store the product data belongs to.

Local programs must be set up separately

A store code alone doesn’t activate local inventory ads. Google requires the relevant Merchant Center setup, including enrollment in a local program, a linked Business Profile, and verified business information.

The local inventory data specification explains the fields Google uses to associate inventory with stores. Check that documentation before building a feed because required attributes and validation rules can change.

If your account uses free local listings rather than paid local inventory ads, the same location-matching discipline still applies. Keep the code identical across the profile and feed.

Build a dependable store-code mapping

A store code is a business-owned identifier, so it should never live in one person’s memory or one disconnected spreadsheet. For multi-location management, create a master location register that your local SEO, operations, ecommerce, and engineering teams can all reference.

Useful columns include:

Field	Purpose
Store code	Shared identifier used in profile and inventory data
Business Profile location ID	Google-generated account or API reference
place ID	Google-generated Maps and Places reference
Store name	Internal and customer-facing name
Full address	Location validation
Merchant Center account	Feed ownership and access
Feed source	File, API, or platform producing inventory
Status	Open, temporarily closed, relocated, or retired
Last verified	Date of the most recent audit

The mapping file should have one owner. Changes should include the old value, new value, date, reason, and person who approved the change.

This matters most during acquisitions, franchise transfers, relocations, rebrands, and retirements. Those projects often involve several systems at once. A clear register prevents one team from changing a code while another continues sending the old value.

Keep the store code as a permanent key across systems, even when records change:

Treat each identifier as a permanent key. If one system changes the key and another doesn’t, the data may fail to match or point to the wrong location.

Use APIs and automation with change control

Spreadsheets work well for occasional updates. Large retailers and franchise networks may use scripts, connectors, or APIs to keep location and inventory data synchronized.

The integration should read from one approved source of truth, such as a database. It shouldn’t generate a new store code each time a location record is processed.

Separate these values in your technical design:

• The business-owned store_code.
• Google’s Business Profile profile record ID.
• Google’s Maps identifier.
• The product ID or SKU.
• The inventory source identifier.

For Google Merchant Center inventory records, treat the store code as a stable association. If a Business Profile code changes, update the source mapping and feed configuration together. Don’t assume a product upload will repair an old location match automatically.

Test updates with one location before sending changes across the entire account. Confirm that the selected profile, Merchant Center store, product, price, and availability all remain connected.

For local inventory data, use Google’s local inventory upload guidance to confirm where your data source is managed and how the upload is processed.

Troubleshoot missing codes and feed mismatches

Most store code errors come from identity problems, not product problems. Start with the location match before changing price, availability, or product attributes.

When a store code is missing

Check the following in order:

1. Open the intended profile, not the account’s general location list.
2. Confirm that your account has the required manager access.
3. Check More, Business Profile settings, and Advanced settings.
4. Review the store code field for blank values or unexpected spaces.
5. Export the locations and inspect the spreadsheet.
6. Confirm that the upload file uses the correct code column.
7. Look for duplicate codes across the account.

Older instructions may call this area advanced information, while the current menu may show Advanced settings.

A missing field may indicate that the code hasn’t been assigned. It can also result from viewing a different location, using a restricted account, or working in an outdated spreadsheet.

Don’t create a duplicate profile to solve a missing code. Fix the existing location record first.

When Merchant Center reports a mismatch

Compare the values character by character. Check capitalization, spelling, spaces, punctuation, and leading zeros.

For example, these values should be treated as different:

• Store123
• store123
• Store 123
• Store0123

Then confirm that the code is attached to the intended Business Profile location. A technically valid code can still be wrong if it belongs to another branch.

Next, confirm that the Business Profile is verified and linked to the correct Merchant Center account. Review the local inventory source after correcting the mapping. Google will need to process the updated data before the error disappears.

Use the local inventory upload documentation when checking the source and upload status.

A store-code checklist for local SEO teams

Run this review before every bulk upload, feed launch, or location migration:

• Every physical location has one store code.
• No two active profiles share the same identifier.
• Identifiers follow the approved naming format.
• Capitalization is consistent.
• Business Profile and Merchant Center values match exactly.
• The value is no longer than 64 characters in the required field.
• The correct profile is verified and linked.
• The address remains unchanged during a code-only update.
• Retired identifiers are documented and never reused.
• The feed source, spreadsheet, or script uses the latest mapping file.
• One test location was checked before a network-wide upload.
• Upload results and error reports were saved.

Keep customer-facing profile work separate

These identifiers keep location data organized. They don’t replace customer-facing work, including accurate hours, useful photos, complete services, posts, and review responses.

Once location data is stable, your team can spend less time repairing identity errors and more time maintaining the profiles themselves. If you want automated support for posts and review responses, Learn More about the platform’s Google Business Profile tools.

Teams that want to keep those updates running on a regular schedule can Sign Up when the profile workflow is ready.

Frequently Asked Questions

What is a Google Business Profile store code?

A store code is a unique identifier that your business assigns to one physical location. It helps connect Business Profile records, spreadsheets, Merchant Center data, and local inventory feeds.

Do store codes improve local SEO rankings?

No, store codes don’t directly improve rankings or help a business enter the Local 3-Pack. They support accurate location management and can indirectly reduce data errors in local programs.

Can two locations use the same store code?

No, each active location should have its own unique store code within the relevant Business Profile account. Duplicate codes can cause bulk upload confusion and attach inventory or updates to the wrong branch.

How should a store code match Merchant Center data?

The Business Profile store code and Merchant Center store_code must match exactly. Check capitalization, spaces, spelling, punctuation, and leading zeros because values such as Store123 and store123 are different.

Can I change an existing store code?

Yes, but changes should be rare and coordinated across your spreadsheets, feeds, scripts, and reporting systems. Document the old and new values, update every connected source, and don’t reuse the retired code for another location.

Keep every location tied to the right code

Google Business Profile store codes are internal identifiers, but multi-location operations depend on them. They connect each physical branch to the correct spreadsheet row, Merchant Center record, and local inventory feed.

Use a unique format, keep capitalization consistent, and document every change. Most importantly, don’t change an existing code casually. A stable identifier gives your teams a reliable reference as customer-facing location details change. Coordinate updates across spreadsheets and feeds to keep every location connected.