Geolocation Nearest Store Setup for 1C-Bitrix

Implementing geolocation in a Bitrix e-commerce store is a challenge every retailer with its own offline network faces. We configured this functionality for networks with 5 to 150 stores. This article covers a ready-made solution: how to make your Bitrix show the buyer the nearest store with real stock.

A typical problem: a user visits the site, sees a product, but doesn't know if it's available in a nearby store. They start searching for addresses, calling, wasting time. Our integration solves this in seconds: geolocation access, server request, displaying the nearest point and stock. User time savings—up to 40%, conversion to offline visits increases by 15–25%.

Store Address Storage

In Bitrix, stores (warehouses/outlets) are stored in the b_catalog_store table (module catalog). Each store has fields: TITLE, ADDRESS, PHONE, SCHEDULE, GPS_N (latitude), GPS_S (longitude), ACTIVE. If GPS_N/GPS_S are empty, you need to geocode the addresses (via Yandex or Google API) and save the coordinates. For a network of 50 stores, this takes about 2 hours—once and for all.

Add coordinates programmatically:

\Bitrix\Catalog\StoreTable::update($storeId, [
    'GPS_N' => 53.9045,  // latitude
    'GPS_S' => 27.5615,  // longitude
]);

How Nearest Store Detection Works

The Haversine formula is the standard for calculating distance between two points on a sphere. We use either direct SQL with sorting or a PHP implementation via ORM. The first is 10 times faster for databases with 50+ stores (works in 0.001 s), the second is more flexible for integration with Bitrix components. Both options are below.

SELECT id, title, address, gps_n, gps_s,
    (6371 * acos(
        cos(radians(:lat)) * cos(radians(gps_n)) *
        cos(radians(gps_s) - radians(:lng)) +
        sin(radians(:lat)) * sin(radians(gps_n))
    )) AS distance
FROM b_catalog_store
WHERE active = 'Y' AND gps_n IS NOT NULL
ORDER BY distance ASC
LIMIT 5;

function haversineDistance(
    float $lat1, float $lon1,
    float $lat2, float $lon2
): float {
    $R = 6371; // km
    $dLat = deg2rad($lat2 - $lat1);
    $dLon = deg2rad($lon2 - $lon1);
    $a = sin($dLat/2)**2
       + cos(deg2rad($lat1)) * cos(deg2rad($lat2)) * sin($dLon/2)**2;
    return $R * 2 * atan2(sqrt($a), sqrt(1-$a));
}

$stores = \Bitrix\Catalog\StoreTable::getList([
    'filter' => ['=ACTIVE' => 'Y', '!=GPS_N' => false],
    'select' => ['ID', 'TITLE', 'ADDRESS', 'GPS_N', 'GPS_S', 'SCHEDULE', 'PHONE'],
])->fetchAll();

usort($stores, function($a, $b) use ($userLat, $userLng) {
    $dA = haversineDistance($userLat, $userLng, $a['GPS_N'], $a['GPS_S']);
    $dB = haversineDistance($userLat, $userLng, $b['GPS_N'], $b['GPS_S']);
    return $dA <=> $dB;
});

$nearest = array_slice($stores, 0, 3);

Which to Choose: SQL or PHP?

For projects with a large catalog (50+ stores), the SQL solution gives a 10x speed advantage—noticeable on mobile devices. If additional filtering is needed (e.g., by store type or working hours), use PHP.

AJAX Endpoint for Frontend

// /local/ajax/nearest-store.php
$lat = (float)$_POST['lat'];
$lng = (float)$_POST['lng'];

// ... fetching and sorting ...

header('Content-Type: application/json');
echo json_encode([
    'nearest' => [
        'id'       => $nearest[0]['ID'],
        'title'    => $nearest[0]['TITLE'],
        'address'  => $nearest[0]['ADDRESS'],
        'distance' => round($dist, 1),
        'schedule' => $nearest[0]['SCHEDULE'],
        'phone'    => $nearest[0]['PHONE'],
    ],
]);

Displaying Stock in the Nearest Store

After determining the store, you can show stock quantity for that point right in the product card. Data from b_catalog_store_product:

$stock = \Bitrix\Catalog\StoreProductTable::getList([
    'filter' => [
        '=PRODUCT_ID' => $productId,
        '=STORE_ID'   => $nearestStoreId,
    ],
    'select' => ['AMOUNT'],
])->fetch();

$inStock = $stock && $stock['AMOUNT'] > 0;

UI and UX

Typical interface: a floating block in the header "Nearest store: [Name], [distance] km" or a widget on the product page "Availability in stores". A "Detect" button triggers the geolocation request. If the user denies access, you show a store list with address search. For a full map, connect Yandex.Maps JS API or Google Maps API and place markers for all points.

Additionally: you can implement automatic store detection by IP (via Sypex Geo service)—this works if the user didn't grant geolocation access. Accuracy—up to 50 km, but sufficient for large cities. This is our IP city detection Bitrix solution.

Implementation Steps

1. Audit current stores—check GPS coordinate population.
2. Geocoding—automatically determine coordinates for stores without GPS_N/GPS_S.
3. Create AJAX endpoint—fetch nearest stores with stock.
4. Develop widget—block on product page or header.
5. Integrate with map (optional)—Yandex.Maps or Google Maps.
6. Test and cache—set up tagged cache for fast performance.
7. Documentation and handover—detailed API description and settings.

How to Get Coordinates if GPS_N/GPS_S Are Empty

Use Yandex Geocoding API (free 25,000 requests/day) or Google Maps Geocoding API. For Bitrix, you can write an agent that daily fills coordinates for empty stores. Example request: https://geocode-maps.yandex.ru/1.x/?geocode=Moscow,Tverskaya,1&format=json. Save the obtained coordinates via \Bitrix\Catalog\StoreTable::update().

What's Included

Cost is calculated individually after project analysis. Budget savings compared to development from scratch—up to 60% (from $500 to $1,200). Timeline—from 3 days to 2 weeks, depending on integration complexity (1C presence, number of points). With over 7 years in Bitrix development and 50+ successful integrations, we deliver reliable solutions. Contact us for a consultation—we will evaluate your project in one business day. Get a ready-made solution with compatibility guarantee with 1C and Marketplace.

Our Bitrix geolocation API integration ensures seamless store distance sorting using the Haversine formula. The nearest store widget can be customized to display stock information. For multi-warehouse networks, our Bitrix nearest warehouse feature optimizes logistics.

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.