Store Geolocation in 1C-Bitrix: Setup and Sorting

Imagine: a user visits the 'Stores' page and sees a list of 30 addresses sorted alphabetically. They live in Minsk, but the first five are Moscow. The customer leaves for a competitor that has geolocation working. We've faced this task dozens of times: a client from Yekaterinburg sees a store in St. Petersburg first, because Bitrix has no built-in distance sorting. Finding the nearest store—seemingly trivial—comes down to coordinate accuracy, storage, and the calculation algorithm. In 1C-Bitrix, this problem is solved by combining IP geolocation for initial sorting and the browser API for accuracy down to 50 meters. We integrate the geolocation module and deliver a ready component with documentation, adapted to your network. With this enhancement, offline visit conversion typically increases by 15–20%. The cost is determined after analyzing your specific requirements—savings compared to self-implementation are obvious.

How to Store Store Coordinates in Bitrix?

In Bitrix, stores are stored in two places depending on the functionality used.

• Sale module, trade points: table b_sale_store with fields ID, TITLE, ADDRESS, GPS_N (latitude), GPS_S (longitude). This is the standard structure for pickup points. For example, for a chain of 200 stores, the fields are already filled during 1C integration—just use them.

• Store infoblock: if stores are infoblock elements, coordinates are usually stored in user properties. For distance calculation, numeric coordinates are needed. If stored as a string like "53.9045, 27.5615", they have to be parsed during queries—which is inconvenient. The correct approach is to store latitude and longitude in two separate numeric properties, or use b_sale_store.GPS_N / b_sale_store.GPS_S.

The choice between storing in the sale module and infoblock depends on architecture. For pickup points, the b_sale_store table is more convenient: coordinate fields already exist, queries are fast, and integration with 1C via CommerceML works out of the box. However, if stores are infoblock elements with additional attributes (business hours, contacts, photos), it's easier to add two numeric properties for latitude and longitude. In this case, queries run 3-4 times faster than with string storage.

What to Choose: IP Geolocation or Browser Geolocation?

Each method has its strengths and weaknesses. The table below compares key parameters.

Browser geolocation is accurate but requires user permission and is asynchronous—cannot be used in server-side rendering. IP geolocation works without permission; accuracy is at city/district level. Bitrix has a built-in location module with a GeoIP database. The method \Bitrix\Main\Service\GeoIp\Manager::getLocationByIp() returns approximate coordinates.

$location = \Bitrix\Main\Service\GeoIp\Manager::getLocationByIp(
    \Bitrix\Main\Context::getCurrent()->getRequest()->getRemoteAddress()
);

$userLat = $location['LATITUDE'] ?? null;
$userLon = $location['LONGITUDE'] ?? null;

Combine them: first IP, then AJAX with browser data. This gives instant results on page load, then precise sorting after 1–2 seconds.

Distance Calculation: Haversine Formula in SQL

The most efficient approach is to calculate distances directly in the SQL query. The Haversine formula (see Wikipedia) for PostgreSQL:

SELECT
    id,
    title,
    gps_n AS lat,
    gps_s AS lon,
    (
        6371 * acos(
            cos(radians(:user_lat)) * cos(radians(gps_n)) *
            cos(radians(gps_s) - radians(:user_lon)) +
            sin(radians(:user_lat)) * sin(radians(gps_n))
        )
    ) AS distance_km
FROM b_sale_store
WHERE active = 'Y'
  AND gps_n IS NOT NULL
  AND gps_s IS NOT NULL
ORDER BY distance_km
LIMIT 5;

For MySQL, the syntax is similar. In PostgreSQL, you can also use the earthdistance extension with cube, which is faster for large point sets. To call raw SQL through Bitrix ORM, use \Bitrix\Main\Application::getConnection()->query(). There is no built-in Haversine expression in D7 ORM; you'll need to use ExpressionField with raw SQL or a native query.

Frontend: Two Steps

1. On page load—show stores sorted by IP geolocation (server-side sorting, instant).
2. After obtaining precise coordinates via navigator.geolocation.getCurrentPosition()—re-sort via an AJAX request to the component with lat and lon parameters.

navigator.geolocation.getCurrentPosition(function(pos) {
    fetch('/ajax/nearest-stores/?lat=' + pos.coords.latitude + '&lon=' + pos.coords.longitude)
        .then(r => r.json())
        .then(stores => renderStoreList(stores));
});

The AJAX handler component reads lat/lon from GET, executes the SQL with Haversine, and returns JSON. In Bitrix, this is implemented via a component with parameter ajax_mode = Y or a custom endpoint in /local/ajax/.

Implementation Stages for Geolocation

1. Audit of current store data—check coordinate completeness, active points.
2. Create or modify infoblocks / trade points—add numeric properties for latitude and longitude.
3. Implement SQL query with Haversine formula—for distance sorting.
4. Integrate IP geolocation via GeoIp\Manager—for initial load.
5. Create AJAX endpoint for browser geolocation—for precise re-sorting.
6. Develop output and sorting component—with caching considerations.
7. Cache result for each coordinate pair—by rounding to 0.01 degrees to reduce unique queries.
8. Deliver setup and documentation.

What's Included in the Work

• Audit of existing trade points and coordinates
• Modification of infoblock or tables for numeric coordinate storage
• Implementation of SQL query with Haversine formula (with option for earthdistance extension)
• Integration of IP geolocation via GeoIp\Manager
• Development of AJAX endpoint for browser geolocation
• Creation of output component with dynamic sorting and tagged caching
• Cache configuration with coordinate rounding
• Delivery of documentation and staff training

Optimizations to Speed Up Queries

Our team has over 5 years of experience in 1C-Bitrix development. We have implemented geolocation for chains ranging from 5 to 300 stores. Once, we configured the component for a federal chain in 3 days: IP geolocation on load, then browser geolocation—offline visit conversion increased by 15%. We provide a guarantee on the code and offer post-implementation support. Contact us for a consultation—we'll assess your project and suggest a timeline from 2 to 5 days.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.