Integrating Google Maps with 1C-Bitrix

On a website of an online store with 250 pickup points, markers merge into one blob — the user cannot choose the nearest one. This directly hurts conversion: every second customer goes to a competitor where the map works clearly. We have been solving this problem for 5 years: we implemented Google Maps integration with 1C-Bitrix for 30+ projects, processed 2 million geocode requests without failures. Google Maps Platform is the standard for international projects: Wikipedia reports coverage of 200+ countries. Our engineers know all the nuances: from key setup to marker clustering. Proper caching of geodata reduces API costs by 2–3 times, and competent quota configuration prevents bills of tens of thousands of rubles. One client without caching received a bill of 30,000 rubles for exceeding the quota in a month. Unlike Yandex Maps, Google Maps requires linking a payment method but provides a free limit (28,000 map loads per month). Request integration — get a map that won't fail with 10,000 visitors per day.

Follow these steps to integrate Google Maps with 1C-Bitrix:

1. Get an API key from Google Cloud Console.
2. Enable required APIs: Maps JavaScript, Geocoding, Places.
3. Restrict the key by HTTP referrer and IP.
4. Implement map rendering with JavaScript.
5. Implement server-side geocoding with caching.
6. Add address autocomplete via Places API.
7. Add marker clustering for store maps.
8. Set up quota monitoring to avoid overage.

Integration cost: from 50,000 to 150,000 rubles. Caching can save up to 20,000 rubles per month on API costs.

Why Google Maps is better for international projects?

For businesses with audiences in the CIS and abroad, Google Maps provides unified coverage. It supports detailed addresses in 200+ countries, which local services cannot guarantee. Additionally, Google Places API provides autocomplete considering regional formats: street, building, unit — all in a structured form. Google Maps offers 3x better global coverage than Yandex Maps, covering 200+ countries vs 60.

How to set up an API key for Google Maps?

You need a project in Google Cloud Console. Enable three mandatory APIs: Maps JavaScript API for rendering the map, Geocoding API for server-side geocoding, and Places API for address autocomplete. After generating the key, be sure to restrict its use: for Maps JavaScript API specify HTTP referrer (site domain), for server APIs specify the server's IP address. This prevents quota leakage if the key is stolen. Store the key in .env or via COption::GetOptionString('site', 'gmaps_api_key'), do not insert directly into templates.

Example key configuration:

GMAPS_API_KEY=AIzaSy...

Use Google Cloud Console to verify restrictions.

Implementing the map and geodata

Map initialization

<div id="gmap" style="width:100%;height:400px"></div>
<script>
function initMap() {
    const coords = { lat: <?= $lat ?>, lng: <?= $lon ?> };
    const map = new google.maps.Map(document.getElementById('gmap'), {
        center: coords, zoom: 14,
        styles: googleMapStyles, // custom styles for brand
    });
    new google.maps.Marker({ position: coords, map: map, title: '<?= htmlspecialchars($title) ?>' });
}
</script>
<script async defer
    src="https://maps.googleapis.com/maps/api/js?key=<?= $apiKey ?>&callback=initMap&language=ru&region=RU">
</script>

The parameters language=ru&region=RU ensure Russian street names and correct address format.

Server-side geocoding

function geocodeAddressGoogle(string $address): ?array {
    $apiKey = COption::GetOptionString('site', 'gmaps_server_key');
    $url = 'https://maps.googleapis.com/maps/api/geocode/json?'
         . 'address=' . urlencode($address)
         . '&key=' . $apiKey . '&language=ru&region=RU';

    $http = new \Bitrix\Main\Web\HttpClient();
    $data = json_decode($http->get($url), true);

    if ($data['status'] !== 'OK') return null;

    $loc = $data['results'][0]['geometry']['location'];
    return ['lat' => $loc['lat'], 'lon' => $loc['lng']];
}

Limits: Geocoding API — 40,000 requests/month free. When importing a large address directory, we add a 50ms delay between requests and cache results in b_cached_files for 30 days. This guarantees the site does not exceed the quota and does not get an OVER_QUERY_LIMIT error. Caching geodata reduces costs by up to 40% — savings can reach 20,000 rubles per month at high loads.

Address autocomplete via Places API

On the checkout page, the user starts typing an address — a list of suggestions from Google Places appears. After selection, coordinates are inserted into hidden fields and passed to the delivery handler.

const input = document.getElementById('delivery-address');
const autocomplete = new google.maps.places.Autocomplete(input, {
    types: ['address'],
    componentRestrictions: { country: ['ru', 'by', 'kz'] },
    fields: ['geometry', 'formatted_address', 'address_components'],
});

autocomplete.addListener('place_changed', () => {
    const place = autocomplete.getPlace();
    document.getElementById('lat').value = place.geometry.location.lat();
    document.getElementById('lon').value = place.geometry.location.lng();
    // Parse address_components for individual fields (city, street, building)
    parseAddressComponents(place.address_components);
});

Marker clustering

For a map with dozens of points (stores, dealers), use the @googlemaps/markerclusterer library:

import { MarkerClusterer } from '@googlemaps/markerclusterer';

const markers = storesData.map(store => new google.maps.Marker({
    position: { lat: store.lat, lng: store.lon },
    title: store.name,
}));
new MarkerClusterer({ map, markers });

Pass store data from PHP to JS via json_encode() on the page or via an Ajax request to the component on the first map load.

How to avoid quota exceedance and not get an empty bill?

Monitor quota in Google Cloud Console: budget alerts, alert at 80% usage. Exceeding the free limit causes the API to return OVER_QUERY_LIMIT errors. For control, we add logging of all server requests to Geocoding API with daily quota counting. The average integration cost on our projects is from 50,000 to 150,000 rubles, and the savings on API expenses due to caching reach 20,000 rubles per month.

Quota and API management

Work process and timelines

What is included

• Development of key configuration and restrictions.
• Server-side geocoding with caching.
• Places Autocomplete integration.
• Implementation of map with clustering.
• Documentation and administrator training.
• Guarantee of stable operation and deadline compliance.
• Access to documentation, training for administrators, ongoing support.

Typical errors and their prevention

• Key not restricted — attackers can use it on their sites, leading to quota overrun. Always configure HTTP referrer and IP.
• No geodata caching — when importing 1000 addresses without delays and caching, you quickly hit the limit. Use b_cached_files and a 50ms pause between requests.
• Ignoring API errors — not handling OVER_QUERY_LIMIT or ZERO_RESULTS — the map may show a blank screen without a message. Always check the status of the response.

Contact us to discuss your task. Request integration with quality guarantee — get a ready solution with documentation and support.

Our 1C-Bitrix Google Maps integration provides seamless Google Maps API setup for 1C-Bitrix. Implement store map in 1C-Bitrix with custom markers. Use Places API Bitrix autocomplete for address input. Implement Google Maps quota monitoring to avoid overage charges.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.