How to update chain information

You can update chain information manually or with XML and CSV files.

Add a branch to the chain

On the Businesses page, click next to the name of the chain and select Add branch to chain.
In the window that opens, select a branch from the list and click Add to chain.

You can also add a branch in the chain card. To do this, go to Branches, click New branch, and select Add branch.

Create a branch

On the Businesses page, click next to the name of the chain and select Create branch.
In the window that opens, enter the address, phone number, and business hours for the branch.

You can also create a branch in the chain card. To do this, go to Branches, click New branch, and select Create branch.

Edit branch information

You can edit branch information in the Branches section. To do this:

Go to the chain page and select the desired branches or the entire chain in the Branches section.
Click Edit and select the data from the list that you want to change.
In the window that opens, you can add or delete information about branches. For example, if you select Phone and delete a phone number from the suggested list, it will be deleted in all the branches you selected.

You can also edit photos and other data in the branch card. To do this:

Go to the branch card.
Click Edit data.
Make the changes.
Click Save.

Remove a branch

Go to Branches.
Select one or more branches.
Click Exclude from chain or Delete.

Exclude from chain: The branch will be excluded from the chain and closed on Yandex Maps, and you'll lose access to its card.

Delete: The branch will remain a part of the chain but will be closed on Yandex Maps, and you'll lose access to its card.

If you have more than 30 branches in your chain, we recommend updating chain information in Yandex Business using XML files.

Data about your branches will be updated based on the information in the XML file. New branches will be added to the database and shown in services with their attributes. Branch cards whose details weren't added to the XML file will be closed.

Step 1. Prepare an XML file

File requirements

The XML file must be UTF-8 encoded.
The standard XML header must start from the first line, from the zero character.
For example:
```
<?xml version="1.0" encoding="UTF-8"?>
```
To describe branches, use a set of mandatory and additional attributes. Each branch property should be wrapped in a separate attribute (see Sample file). If a property has multiple values (for example, phone numbers), pass multiple attributes with the same name.
All data in an XML file must be in the same language. Multilingual attributes are an exception (see Attribute description).

A multilingual attribute is an attribute in an XML file with values in several languages.

The language is defined by the lang attribute. For each new language, create an item with the corresponding lang attribute in a separate row.
Example
<address lang="en">87-135 Brompton Road, London SW1X 7XL England</address> <address lang="es">Paseo del Prado s/n, 28014 Madrid España</address>
You can find the current lang values in the XML schema. To add other languages, contact support.
The data can't contain HTML attributes. The XML standard doesn't allow ASCII characters in the value range from 0 to 31 in text fields. The exceptions are values 9 (tab), 10 (newline), and 13 (carriage return). The XML standard requires using & instead of &.

Attribute description


Attribute	Description	Multilingual element	Required field
companies	Root attribute.	Not applicable	Yes
company	Branch description. Nested in the root attribute. There can be any number of `company` attributes.	Not applicable	Yes
company-id	Permanent unique ID of the branch (assigned by the chain owner). Can contain any set of numbers and Latin letters.	No	Yes
name	Name of the branch. Specified without quotation marks, case-sensitive.	Yes	Yes
shortname	Short name of the branch to be displayed next to placemarks on Yandex Maps, up to 25 characters. Specified without quotation marks, case-sensitive.	Yes	No
name-other	Alternative name of the branch (if there are multiple names, list each one in a separate element). Specified without quotation marks, case-sensitive.	Yes	No
address	The branch address (on one line). Multilingual element. If the element contains only the street name and house number, use the `locality‑name` element specifying the locality.	Yes	Yes
country	Country. Specified in full, without abbreviations.	Yes	No
address-add	Additional address information that doesn't apply to other elements (shopping center, shopping and entertainment complex, shopping and entertainment center, floor, office, premises, boutique, entrance). For example, Roza shopping center, floor 2, office 203. Doesn't include a detailed description of the route to the address (100 meters from the metro station to the north, the blue building to the right of Pushkinsky Public Garden). Don't use brackets or quotation marks.	Yes	No
phone	Compound element. Phone number (if there are several phone numbers, specify each one in a separate element).	No	Yes
Elements nested in phone
number	The landline or mobile phone number. Formatted as follows: `[country code]` (`[city code]`) `[phone number]`.
ext	Extension, without comments, words, or delimiters.
info	Information about the phone number, such as "director" or "reception". This element shouldn't contain information about the phone type.
type	Phone type. Acceptable values: `phone`: Phone number. `fax`: Fax number. `phone-fax`: Phone/fax number.

email	Email address (if there are multiple addresses, specify each one in a separate element).	No	No
url	The chain's main website. Specified in lowercase, in full, including http:// or https://.	No	Yes
add-url	Additional website of the chain (such as links to social media pages). The URL of the page with branch information on the chain website is specified in the `info-page` element.	No	No
info-page	URL of the page with branch information on the chain website. The address should contain the domain name of the chain website. Specified in lowercase, in full, including http:// or https://.	No	No
working-time	Opening hours. Days off and non-working days aren't specified.	Yes	Yes
rubric-id	The ID of the business category this branch belongs to. Branches can have up to three business categories, but at least one of them should match the chain category. If a branch has multiple business categories, specify each one in a separate element.	No	Yes
actualization-date	Date updated. Corresponds to the time of the last update. Used to avoid downloading information received during the previous check. The content can be specified in the following format: `DD.MM.YYYY`; UNIX-time: Specified in milliseconds from `00:00:00.000 01.01.1970`.	No	Yes
coordinates	Compound element. Coordinates (latitude and longitude).	No	Yes (if the address is inaccurate)
Elements nested in coordinates
lon	Longitude. Use a period as the decimal separator.
lat	Latitude. Use a period as the decimal separator.

photos	A link to the gallery or a page on the chain website with all photos. If there are multiple photos, specify each one in a separate `photo` element. It can contain the following attributes: `alt`: Text description of the photo in free form. `type`: Photo type. Takes only one value: `interior`.	No	No
Elements nested in photos
tag	Photo tag. Set inside the `photos` element. Acceptable values: `INTERIOR`: Interior. `EXTERIOR`: Exterior. `ENTER`: Entrance. `LOGO`: Logo. `FOOD`: Food, drinks. `GOODS`: Goods. `MENU`: Cafe or restaurant menu. `ACCESSIBILITY`: Ramps, lifts for people with disabilities, and more. `DEVICES`: Electronic devices. `SERVICES`: Services.

feature-boolean	Branch property. If there are multiple properties, specify each one in a separate element. Acceptable values: `0: No.` `1: Yes.`	No	No
feature-enum-single	Branch property.	No	No
feature-enum-multiple	Branch property. If there are multiple properties, specify each one in a separate element.	No	No
feature-numeric-single	A branch property with a numeric value.	No	No
feature-numeric-multiple	A branch property with a numeric value. If there are multiple properties, specify each one in a separate element.	No	No
feature-in-units-single	A branch property with a value defined in units.	No	No
feature-in-units-multiple	A branch property with a value defined in units. If there are multiple properties, specify each one in a separate element.	No	No
feature-range-single	A branch property that has a range value.	No	No
feature-range-in-units-single	A branch property with a range value in units.	No	No
feature-range-in-units-multiple	A branch property with a range value in units. If there are multiple properties, specify each one in a separate element.	No	No
feature-text-single	A branch property in text format.	No	No


Attribute	Description	Multilingual element	Required field
companies	Root attribute.	Not applicable	Yes
company	Branch description. Nested in the root attribute. There can be any number of `company` attributes.	Not applicable	Yes
company-id	Permanent unique ID of the branch (assigned by the chain owner). Can contain any set of numbers and Latin letters.	No	Yes
name	Name of the branch. Specified without quotation marks, case-sensitive.	Yes	Yes
shortname	Short name of the branch to be displayed next to placemarks on Yandex Maps, up to 25 characters. Specified without quotation marks, case-sensitive.	Yes	No
name-other	Alternative name of the branch (if there are multiple names, list each one in a separate element). Specified without quotation marks, case-sensitive.	Yes	No
address	The branch address (on one line). Multilingual element. If the element contains only the street name and house number, use the `locality‑name` element specifying the locality.	Yes	Yes
country	Country. Specified in full, without abbreviations.	Yes	No
address-add	Additional address information that doesn't apply to other elements (shopping center, shopping and entertainment complex, shopping and entertainment center, floor, office, premises, boutique, entrance). For example, Roza shopping center, floor 2, office 203. Doesn't include a detailed description of the route to the address (100 meters from the metro station to the north, the blue building to the right of Pushkinsky Public Garden). Don't use brackets or quotation marks.	Yes	No
phone	Compound element. Phone number (if there are several phone numbers, specify each one in a separate element).	No	Yes
Elements nested in phone
number	The landline or mobile phone number. Formatted as follows: `[country code]` (`[city code]`) `[phone number]`.
ext	Extension, without comments, words, or delimiters.
info	Information about the phone number, such as "director" or "reception". This element shouldn't contain information about the phone type.
type	Phone type. Acceptable values: `phone`: Phone number. `fax`: Fax number. `phone-fax`: Phone/fax number.

email	Email address (if there are multiple addresses, specify each one in a separate element).	No	No
url	The chain's main website. Specified in lowercase, in full, including http:// or https://.	No	Yes
add-url	Additional website of the chain (such as links to social media pages). The URL of the page with branch information on the chain website is specified in the `info-page` element.	No	No
info-page	URL of the page with branch information on the chain website. The address should contain the domain name of the chain website. Specified in lowercase, in full, including http:// or https://.	No	No
working-time	Opening hours. Days off and non-working days aren't specified.	Yes	Yes
rubric-id	The ID of the business category this branch belongs to. Branches can have up to three business categories, but at least one of them should match the chain category. If a branch has multiple business categories, specify each one in a separate element.	No	Yes
actualization-date	Date updated. Corresponds to the time of the last update. Used to avoid downloading information received during the previous check. The content can be specified in the following format: `DD.MM.YYYY`; UNIX-time: Specified in milliseconds from `00:00:00.000 01.01.1970`.	No	Yes
coordinates	Compound element. Coordinates (latitude and longitude).	No	Yes (if the address is inaccurate)
Elements nested in coordinates
lon	Longitude. Use a period as the decimal separator.
lat	Latitude. Use a period as the decimal separator.

photos	A link to the gallery or a page on the chain website with all photos. If there are multiple photos, specify each one in a separate `photo` element. It can contain the following attributes: `alt`: Text description of the photo in free form. `type`: Photo type. Takes only one value: `interior`.	No	No
Elements nested in photos
tag	Photo tag. Set inside the `photos` element. Acceptable values: `INTERIOR`: Interior. `EXTERIOR`: Exterior. `ENTER`: Entrance. `LOGO`: Logo. `FOOD`: Food, drinks. `GOODS`: Goods. `MENU`: Cafe or restaurant menu. `ACCESSIBILITY`: Ramps, lifts for people with disabilities, and more. `DEVICES`: Electronic devices. `SERVICES`: Services.

feature-boolean	Branch property. If there are multiple properties, specify each one in a separate element. Acceptable values: `0: No.` `1: Yes.`	No	No
feature-enum-single	Branch property.	No	No
feature-enum-multiple	Branch property. If there are multiple properties, specify each one in a separate element.	No	No
feature-numeric-single	A branch property with a numeric value.	No	No
feature-numeric-multiple	A branch property with a numeric value. If there are multiple properties, specify each one in a separate element.	No	No
feature-in-units-single	A branch property with a value defined in units.	No	No
feature-in-units-multiple	A branch property with a value defined in units. If there are multiple properties, specify each one in a separate element.	No	No
feature-range-single	A branch property that has a range value.	No	No
feature-range-in-units-single	A branch property with a range value in units.	No	No
feature-range-in-units-multiple	A branch property with a range value in units. If there are multiple properties, specify each one in a separate element.	No	No
feature-text-single	A branch property in text format.	No	No

Additional attributes

You can pass additional parameters for your chain or branch in an XML file. For example, you can show if there is parking available near your shopping center or which currency can be withdrawn from your ATM.

To get an XML file with a list of possible attributes for your business category:

On the chain page, go to Branches.
Under Branch management, choose File.
Click Download data → Download attributes.

If you have questions about downloading the file with additional parameters, contact us.

Sample file

Note.

To open the description of an attribute from a sample file, click any highlighted attribute.

<?xml version="1.0" encoding="UTF-8"?> 
<companies>
  <company>
    <company-id>770704034</company-id>
    <name lang="en">Anchor</name>
    <shortname lang="en">Anchor</shortname>
    <address lang="en">101 Baker Street, London</address>
    <country lang="en">United Kingdom</country>
    <address-add lang="en">Rosa Mall, Floor 2, Suite 203</address-add>
    <phone>
      <number>020 1234 5678</number>
      <ext>555</ext>
      <info>Secretary</info>
      <type>phone</type>
    </phone>
    <phone>
      <type>phone</type>
      <number>034 2202 3303</number>
      <info/>
    </phone>
    <email>info@anchor.com</email>
    <url>http://www.anchor.com</url>
    <add-url>http://www.anchor.com</add-url>
    <info-page>http://www.test.com/anchor</info-page>
    <working-time lang="en">every day, 10:00-21:00</working-time>
    <rubric-id>184106414</rubric-id>
    <rubric-id>184106394</rubric-id>
    <actualization-date>1511724300</actualization-date>
    <photos gallery-url="http://test.com/anchor/gallery">
      <photo url="http://test.com/anchor/11_b.jpg" alt="Hotel restaurant" 
      type="interior"></photo>
      <photo url="http://test.com/anchor/19_b.jpg">
        <tag>EXTERIOR</tag>
      </photo>
      <photo url="http://test.com/anchor/25_b.jpg"></photo>
      <photo url="http://test.com/anchor/26_b.jpg"></photo>
      <photo url="http://test.com/anchor/17_b.jpg"></photo>
      <photo url="http://test.com/anchor/drink1.jpg" alt="A cocktail at the hotel bar">
        <tag>FOOD</tag>
      </photo>
    </photos>
    <feature-boolean name="internet" value="1"/>
    <feature-enum-single name="star" value="five"/>
    <feature-numeric-single name="room_number" value="15"/>
    <feature-enum-multiple name="hotel_type" value="art_hotel"/>
    <feature-numeric-multiple name="license_number" value="004555"/>
    <feature-in-units-single name="minimum_order" unit="money" unit-value="gbp" value="30"/>
    <feature-in-units-multiple name="ats_by_type" unit="apartment_type" unit-value="single" value="200"/>
    <feature-range-single name="number_seats_banquet_hall" from="15" to="20"/>
    <feature-range-multiple name="tickets" unit="money" unit-value="gbp" from="10" to="15"/>
    <feature-range-in-units-single name="price_1_min" unit="money" unit-value="gbp" from="7" to="10"/>
    <feature-range-in-units-multiple name="tea" unit="money" unit-value="gbp" from="100" to="300"/>
    <feature-text-single value="Anchor_free_wi-fi" name="ssid"/>
  </company>
  <company>
    <company-id>7707040070</company-id>
    <name lang="en">Anchor Bank</name>
    <shortname lang="en">Anchor Bank</shortname>
    <name-other lang="en">Branch 2</name-other>
    <address lang="en">46 Mathew Street, Liverpool, United Kingdom</address>
    <phone>
      <ext/><type>phone</type>
      <number>040 9988 7444</number>
      <info/>
    </phone>
    <url>http://www.anchorbank.com/</url>
    <working-time lang="en">weekdays 8:30–18:00, Sat 9:00–14:30</working-time>
    <rubric-id>184106974</rubric-id>
    <actualization-date>Sep 23, 2019</actualization-date>
    <coordinates>
      <lon>48.295532</lon>
      <lat>55.616051</lat>
    </coordinates>
  </company>
</companies>

The file can be checked:

In the Webmaster validator. Choose Business as the document validation option and a source of XML data for validation — a file, link, or text.
Manually on your computer using the schema (XML Schema Definition).

Step 2. Upload the file to your website

Upload the file to your website using an updatable link. The data should be accessible via HTTP or HTTPS.

Step 3. Add a link to the file in Yandex Business

On the chain page, go to Branches.
Under Branch management, choose File.
Add a link to the file, select the XML type, and click Check. Checking the file may take several hours.
If the file is verified successfully, click Publish. In the window that opens, check the changes in the branches. The map can show up to 50 branches with changes. Click Yes, start the upload. The file data will be moderated and uploaded to the Yandex Business database. If the file is large, the data upload may take several days.

If errors are found when checking the file, you'll see an error message. Fix the errors and re-submit the file for review.

To view the branch changes uploaded to the Yandex Business database from the file, click Upload history. The button will be available 24 hours after the first upload.

Yandex Maps will show new branches and other changes in a few days.

CSV is a text format for representing tabular data. The first row contains column names and the next rows contain data itself. The contents of the columns are separated from each other by a comma.

File data must be UTF-8 encoded.

You can download a sample CSV file.

To see the example in LibreOffice, import the text: select UTF-8 encoding, comma as a separator, and double quotes as a text qualifier.

To see the example in Excel, open it in Data → Get external data → From text. Select UTF-8 encoding, comma as a separator, and double quotes as a text qualifier.

Step 1. Prepare a CSV file

To set up automatic daily updates for branch data, create a CSV file. The data must be UTF-8 encoded.


Attribute	Description	Required field
`name`	Name of the branch. Specified without quotation marks, case-sensitive.	Yes
`country`	Country. Specified in full, without abbreviations.	Yes
`address`	The full address for the branch, including the building number.	Yes
`address-add`	Additional address information that doesn't apply to other elements (shopping center, shopping and entertainment complex, shopping and entertainment center, floor, office, premises, boutique, entrance). For example, Roza shopping center, floor 2, office 203. Doesn't include a detailed description of the route to the address (100 meters from the metro station to the north, the blue building to the right of Pushkinsky Public Garden). Don't use brackets or quotation marks.	No
`phone`	A phone number with the country and area code. If there are multiple phone numbers, separate them with a semicolon (;).	Yes
`rubric-id`	The ID of the business category this branch belongs to. If there are multiple business categories, separate them with commas. Branches can have up to three business categories, but at least one of them should match the chain category.	Yes
`url`	The chain's main website. Specified in lowercase, in full, including http:// or https://.	Yes
`add-url`	An additional website for the chain (for example, a link to a social media page).	No
`working-time`	Opening hours. Days off and non-working days aren't specified.	Yes
`lat`	Geographical latitude of the branch location. Use a dot as the decimal separator.	Yes (if the address is inaccurate)
`lon`	Geographical longitude of the branch location. Use a dot as the decimal separator.	Yes (if the address is inaccurate)


Attribute	Description	Required field
`name`	Name of the branch. Specified without quotation marks, case-sensitive.	Yes
`country`	Country. Specified in full, without abbreviations.	Yes
`address`	The full address for the branch, including the building number.	Yes
`address-add`	Additional address information that doesn't apply to other elements (shopping center, shopping and entertainment complex, shopping and entertainment center, floor, office, premises, boutique, entrance). For example, Roza shopping center, floor 2, office 203. Doesn't include a detailed description of the route to the address (100 meters from the metro station to the north, the blue building to the right of Pushkinsky Public Garden). Don't use brackets or quotation marks.	No
`phone`	A phone number with the country and area code. If there are multiple phone numbers, separate them with a semicolon (;).	Yes
`rubric-id`	The ID of the business category this branch belongs to. If there are multiple business categories, separate them with commas. Branches can have up to three business categories, but at least one of them should match the chain category.	Yes
`url`	The chain's main website. Specified in lowercase, in full, including http:// or https://.	Yes
`add-url`	An additional website for the chain (for example, a link to a social media page).	No
`working-time`	Opening hours. Days off and non-working days aren't specified.	Yes
`lat`	Geographical latitude of the branch location. Use a dot as the decimal separator.	Yes (if the address is inaccurate)
`lon`	Geographical longitude of the branch location. Use a dot as the decimal separator.	Yes (if the address is inaccurate)

Step 2. Upload the file to the website

Upload the file to your website using an updatable link. The data should be accessible via HTTP or HTTPS.

Step 3. Add a link to the file in Yandex Business

On the chain page, go to Branches.
Under Branch management, choose File.
Add a link to the file, select the CSV type, and click Check. Checking the file may take several hours.
If the file is verified successfully, click Publish. In the window that opens, check the changes in the branches. The map can show up to 50 branches with changes. Click Yes, start the upload. The file data will be moderated and uploaded to the Yandex Business database. If the file is large, the data upload may take several days.

If errors are found when checking the file, you'll see an error message. Fix the errors and re-submit the file for review.

To view the branch changes uploaded to the Yandex Business database from the file, click Upload history. The button is available within 24 hours of the first upload.

To update the data once, save the file in CSV or XSLX format and send it using the form. Include your business's email address and phone number in the message. If we have any questions about the uploaded file, we will contact you.

The new data will appear in Yandex Maps within a few days, provided the file is properly formatted.

Write to support