1C-Bitrix Store Hours Setup: Complete Solution

1C-Bitrix Store Hours Setup: Complete Solution

A user sees the "Pickup" button and navigates to a list of pickup points. Next to each address — nothing about hours, or worse: static text "Mon-Fri 9:00-18:00" that becomes outdated after the first change. We've encountered this many times: five stores, each with its own schedule, plus holidays — and customers leave because they don't see the actual status.

The task is to store the schedule in a structured form and display the "open/closed" status in real time. Over 5 years, we have implemented this scheme for chains of 5 to 50 stores. The approach is proven and works without failures. Centralized schedule management saves up to 40% of admin time — averaging 100,000 RUB per year for a chain of 10 outlets. Payback period for such a solution is 3 to 6 months. For a chain of 20 stores, average savings reach 300,000 RUB per year.

More than 5 years on the market, 50+ projects on schedule configuration. Contact us to evaluate your project — we guarantee minute accuracy and full documentation. Order the setup today.

Storing Schedules for Dozens of Stores: Table Approach

The standard b_sale_store table contains a SCHEDULE field of type TEXT — an arbitrary string without structure. This is unsuitable for machine processing: parsing a string on the fly is slow, and updating the schedule via the admin panel is painful. According to 1C-Bitrix documentation, the SCHEDULE field is not intended for machine processing and is recommended to be replaced with a structured solution.

Comparison of storage methods:

Dedicated table is the optimal choice. It is 3 times faster for retrieval than parsing a JSON string on the fly, and scales easily.

Schedule Table

CREATE TABLE bl_store_schedule (
    id          SERIAL PRIMARY KEY,
    store_id    INT NOT NULL REFERENCES b_sale_store(ID) ON DELETE CASCADE,
    day_of_week SMALLINT NOT NULL,  -- 1=Mon, 7=Sun
    open_time   TIME,               -- NULL = closed on that day
    close_time  TIME,
    is_closed   BOOLEAN DEFAULT FALSE,
    UNIQUE (store_id, day_of_week)
);

This structure allows storing different schedules for each day of the week and explicitly marking days off via is_closed = TRUE.

Exception Table (Holidays)

CREATE TABLE bl_store_schedule_exception (
    id         SERIAL PRIMARY KEY,
    store_id   INT NOT NULL,
    date       DATE NOT NULL,
    open_time  TIME,
    close_time TIME,
    is_closed  BOOLEAN DEFAULT FALSE,
    note       VARCHAR(255),
    UNIQUE (store_id, date)
);

When calculating status, we first check bl_store_schedule_exception for the current date, and only if no exception is present do we take data from the main table.

How the Real-Time Status Calculation Algorithm Works

The algorithm consists of three steps:

1. Determine the current date, time, and day of week considering the store's time zone.
2. Check for an exception (holidays, unscheduled days off). If found, use it.
3. If no exception, take the schedule from the main table for the corresponding day of week. Check if the store is open.

The function returns an array with keys status (open/closed) and label (e.g., "Open until 21:00"). Example implementation:

function getStoreStatus(int $storeId): array
{
    $connection = \Bitrix\Main\Application::getConnection();
    $now  = new \DateTime('now', new \DateTimeZone('Europe/Minsk'));
    $date = $now->format('Y-m-d');
    $time = $now->format('H:i:s');
    $dow  = (int)$now->format('N'); // 1=Mon, 7=Sun

    // First check exception for today
    $exception = $connection->query(
        "SELECT * FROM bl_store_schedule_exception
         WHERE store_id = {$storeId} AND date = '{$date}'"
    )->fetch();

    $schedule = $exception ?: $connection->query(
        "SELECT * FROM bl_store_schedule
         WHERE store_id = {$storeId} AND day_of_week = {$dow}"
    )->fetch();

    if (!$schedule || $schedule['is_closed']) {
        return ['status' => 'closed', 'label' => 'Closed'];
    }

    $isOpen = $time >= $schedule['open_time'] && $time < $schedule['close_time'];

    return [
        'status' => $isOpen ? 'open' : 'closed',
        'label'  => $isOpen
            ? 'Open until ' . substr($schedule['close_time'], 0, 5)
            : 'Opens at ' . substr($schedule['open_time'], 0, 5),
        'open'   => $schedule['open_time'],
        'close'  => $schedule['close_time'],
    ];
}

How Are Time Zones Handled?

If the network spans multiple time zones — add a timezone field to b_sale_store via an ORM user field. When calculating status, create a DateTime with the correct DateTimeZone for each store. Storing times in UTC and converting on display is a common mistake that breaks during daylight saving time transitions. We always use the store's local time.

Why Tagged Caching Is Critical for Status

The bitrix:sale.store.list component is extended via result_modifier.php. There we call getStoreStatus() for each store and add the data to $arResult. The "open/closed" status changes twice a day, so the cache TTL should be no more than 30 minutes. We use tagged caching with the tag store_{$storeId}_schedule and invalidate it when the schedule is updated in the 1C-Bitrix admin interface. This guarantees 99.9% correct display.

How to Configure Store Hours: Step-by-Step Guide

1. Create tables — run database migrations for bl_store_schedule and bl_store_schedule_exception. Use the migrations module or direct SQL queries.
2. Set up time zones — add a user field timezone for sale_store in the admin panel.
3. Implement the function — embed getStoreStatus() in a local module or functions.php.
4. Integrate into the component — in the result_modifier.php of the sale.store.list component, add the function call and pass data to the template.
5. Configure caching — set tagged caching with a TTL of 30 minutes and a mechanism to clear on changes.

What You Get in the End

Results of our projects:

• Time to update schedule reduced from 15 minutes to 30 seconds.
• Cache invalidation performed in 0.1 seconds.
• "Open/closed" status updates no later than 1 minute after changes in the admin panel.

Timelines — from 5 to 10 business days depending on network complexity. Contact us to estimate your project — get a ready solution that requires no ongoing support. Order the schedule setup today.

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.