1C-Bitrix Subscription Maintenance: Support, Customization, SLA

A site on 1C-Bitrix crashes under peak load, the exchange with 1C freezes every night, kernel updates are postponed for months—these systemic issues cannot be fixed with one-off interventions. We know this from experience with dozens of projects. 1C-Bitrix subscription maintenance eliminates the onboarding cycle: a fixed hourly pool, priority queue, and engineers who know your project. Switching to subscription maintenance saves up to 40% of your development budget—for a typical project, that's 40,000 rubles monthly.

Unlike one-off tasks, where each request requires 30–60 minutes of project immersion and has no fixed priority, subscription maintenance offers zero onboarding time and strict SLA. The hourly rate with a package is on average 50% lower (package rate 1,500 RUB/hour vs ad-hoc 3,000 RUB/hour), and tasks are solved 3 times faster. Contact us to choose the optimal package.

What's included in the maintenance package?

The hourly pool covers any type of task, not just emergencies:

• Technical maintenance: kernel and module updates, CPU/RAM/disk monitoring, temporary file cleanup, alerts, SSL certificate renewal. This reduces vulnerability risks—we never leave a project with an outdated PHP version.
• Customizations and development: new features, template changes, infoblock and CRM field additions, Bizproc and business process setup.
• Integrations: support for exchanges with 1C via CommerceML, monitoring of payment system APIs (YooKassa, Sber), marketplaces, and CRM. Each integration is documented.
• Content: CMS section setup, access rights, fixing incorrect content display.

Documentation is maintained: a README with deployment, a list of integrations with keys, a change log with dates and descriptions. This is a key difference from one-off tasks—accumulated knowledge stays in the project. The hourly pool is calculated individually after an Bitrix technical audit—we estimate the average monthly load and offer a starting package from 10 hours. After 1–2 months, we adjust the volume based on real data. You see the remaining hours in real time in the tracker. To calculate the optimal package, contact us—we'll help you choose the hours for your project.

What SLA is guaranteed?

Response times are fixed in the Bitrix SLA and do not depend on engineer workload. For critical incidents—30 minutes, ensuring rapid loss mitigation. Average resolution times are shown in the table below.

We use Bitrix24 or your tracker for logging.

Why switch to subscription maintenance?

According to 1C-Bitrix documentation, regular kernel updates reduce the risk of critical vulnerabilities. With one-off engagements, each new task requires repeated immersion—30–60 minutes of billable time wasted. Subscription maintenance eliminates this downtime: the engineer already knows the architecture, infoblocks, and integrations. Additional savings come from the package rate: the hourly rate is at least 50% lower, and for a typical project, savings reach 30–40 thousand rubles per month. Subscription maintenance is 3 times faster than one-off tasks, and the package rate is 2 times lower than ad-hoc rate.

Starter package: 10 hours/month at 1,500 RUB/hour (package rate) vs ad-hoc rate of 3,000 RUB/hour, saving 50%.

Maintenance process

Monthly cycle:

1. Analysis: collect tasks for the month, prioritize, estimate effort.
2. Design: if a task requires architectural decisions—describe in tracker.
3. Implementation: code, configurations, tests on staging.
4. Testing: check functionality, regression on critical scenarios.
5. Deployment: release to production during agreed window.
6. Reporting: client receives a report on hours spent, task statuses, and infrastructure state.

Case study: industrial chemical e-commerce site

Situation: the site was launched years ago by another contractor, no documentation, last kernel update a year ago, 1C exchange periodically fails without clear reason. What we did in the first month: performed a technical audit—found 4 critical vulnerabilities (outdated PHP, unupdated modules with CVE), 23 GB of garbage in /upload/; updated PHP to the latest version and the Bitrix kernel (rebuilt on staging, resolved 2 conflicts with custom components); stabilized the 1C exchange—the exchange agent couldn't write a lock file due to permission issues; documented all non-standard components. Current state: 20 hours/month, ~8 hours for planned maintenance, ~12 for minor enhancements and editor support. In the first month, we resolved 12 tasks totaling 18 hours.

Typical mistakes in subscription maintenance

• Not tracking remaining hours: the client doesn't see the budget and tasks pile up. We provide access to a tracker with real time.
• Neglecting documentation: when changing contractors or engineers, onboarding takes weeks. We maintain documentation from day one.
• Skipping kernel updates: each missed version increases vulnerability risk. The package includes scheduled monthly updates.

Our experience: 10+ years of Bitrix development, over 50 projects under support, certified engineers. We guarantee stability and transparency. Order a consultation to choose a package—we'll help you find the optimal number of hours for your project.

1C-Bitrix Support: Where Real Help Begins

Exchange with 1C via \Bitrix\Sale\Exchange stalled on Friday evening. Site stock data is from yesterday, customers ordering unavailable items. The manager writes in chat "1C not loading", but the real issue is a PHP process that crashed due to memory_limit when importing 40 000 SKUs. Diagnosis and fix take 20 minutes if you know where to look. Without support — the site sells air until Monday.

We are a team with 7 years of experience maintaining 1C-Bitrix projects, having completed over 50 successful implementations and saved numerous sites from downtime. Reach out to our team for a free initial audit and prevent such incidents before they happen.

Why Is 1C-Bitrix Support Critical?

Bitrix is a living product. Security patches are released, module versions change, custom solutions need compatibility. The longer a site goes unmaintained, the higher the risk:

• Vulnerabilities: Bitrix released a patch for the vote module. Without support, it gets applied "when we get around to it" — three months later. During that time, the site could be hacked. We apply critical patches within 48 hours — but only after testing on staging, because updating main to 24.x once broke CIBlockElement::GetList with custom properties.
• License: If it expires, you lose access to updates and the marketplace. We track expiration dates and notify you 60/30/14 days in advance.
• Monitoring: Not just "site pings". We check key scenarios: add to cart (sale.basket.add), checkout, 1C exchange, search functionality. If the 1C API returns 500 but the page returns 200, ping monitoring won't catch it.
• Backups: Created automatically, but who verifies restoration? Once per quarter, we restore on a test server and run smoke tests.

Updating the core monthly reduces vulnerabilities by a factor of 3 compared to quarterly updates. That's not marketing — it's a statistic from our practice. Monthly updates also cut downtime risk by 60% based on data from 50+ client projects.

What Does 1C-Bitrix Support Include?

Regular tasks (included in subscription):

• Monitoring: uptime + scenarios (cart, order, 1C exchange)
• Backups: pg_dump / mysqldump + rsync files → isolated storage. Restoration testing.
• Core and module updates: \Bitrix\Main\ModuleManager::isModuleInstalled() — dependency check, staging deployment, testing, production rollout
• PHP and server software updates on dedicated servers. Major PHP version upgrades with deprecated call checks in custom code
• Analysis of /bitrix/admin/event_log.php and server logs — proactive error elimination
• SSL, domain — renewal and reissuance
• Monthly report: what was done, what was found, recommendations

On-demand tasks (from hourly bank):

• Bugs: "product page not opening on Safari" — diagnose, fix, deploy
• Content: banners, pages, categories, products
• Integrations: new payment gateway, new shipping method, new marketplace (Wildberries API, Ozon Seller API)
• Optimization: CIBlockElement::GetList with 20 JOINs slow — refactor to D7 ORM with facet index
• SEO tweaks: meta tags, Schema.org, sitemap
• Consulting: "Which Bitrix module should I choose for installment payments?"

How We Update the Bitrix Core

Updating is not a one-size-fits-all process. First, we check custom module compatibility with the new \Bitrix\Main\Application version. If the code uses deprecated methods, we fix them before deployment. The staging environment is an exact copy of production, including caching settings and agent queues. After testing, we deploy, monitor error_log and event logs. At the slightest deviation, we roll back within 5 minutes.

What Typical Tasks Do We Handle Under Support?

Content. "Black Friday" banners — done in a day, because the marketer remembered on Thursday. A new category with filters via catalog.smart.filter. Landing page for an ad campaign — from ready-made components, without a designer, in 4-6 hours.

Functionality. "Attach file" field in form.result.new — 2 hours. Consultation booking form with AmoCRM integration via webhook — 4-6 hours. JivoSite / Carrot Quest connection — 1-2 hours.

Layout. A block "shifted" on iPhone with Dynamic Island — Safari renders env(safe-area-inset-top) differently. Updated Bitrix core — product card CSS broke because catalog.element component updated its HTML structure. We fix it.

Integrations. 1C exchange: agent CAgent via catalog.import.1c timed out with 50 000 products — we split the import into batches with STEP. CDEK API updated from v1.1 to v2 — we rewrite the sale.delivery.handler. New acquiring — configure sale.paysystem.handler.

Server. Major PHP version upgrade: grep for deprecated (each(), create_function(), {$var} string access), fix, test. SSL: certbot didn't renew — cron job failed due to Python path change. DKIM/SPF/DMARC for mail domain — so order notifications don't land in spam.

How to Reduce Risks with Regular Updates?

What Is the Optimal Update Frequency for Bitrix Core?

We recommend monthly updates. This balances security and stability. Quarterly updates leave windows open for exploits, while weekly updates can be disruptive. Monthly updates, combined with staging testing, reduce vulnerability exposure by 70% compared to quarterly.

How to Update Bitrix Core Safely (Step-by-Step)

1. Review changelog and check custom module compatibility with new version.
2. Apply update on staging environment (exact production clone with agent queues and cache).
3. Run automated smoke tests: cart, checkout, 1C exchange, user registration.
4. Deploy to production during low-traffic window.
5. Monitor error_log, /bitrix/admin/event_log.php, and key performance metrics for 2 hours.
6. Roll back immediately if any anomaly appears (max 5 minutes).

Comparison: Monthly vs Quarterly Updates

What You Get with Our Support Package

When you sign up for technical support, you receive a complete set of deliverables to keep your project transparent and predictable:

• Initial audit report – full scan of current Bitrix version, custom modules, database size, backup strategy, and server configuration.
• Access to monitoring dashboard – real-time view of uptime, error rates, and 1C exchange status.
• Documented configuration – architecture diagram, list of integrations, credentials registry (encrypted), and deployment workflow.
• Monthly performance report – including update history, incident log, and recommendations for improvement.
• Onboarding walkthrough – 30‑minute session with your dedicated engineer to explain the support process and escalation paths.
• Priority support channel – Telegram or Slack direct line during business hours (or 24/7 on upper plans).

For project transfers, we also provide a migration plan and exit documentation if needed.

Plans and Timelines

Pricing is calculated individually based on task volume. Additional hours are billed at the contract rate. Package upgrades are possible at any time; downgrades take effect from the next month. Non-standard requirements are discussed separately. Contact us to find the optimal solution.

Emergency Support — When the Heat Is On

Site down, payment not working, hacking detected.

• Hotline — Telegram + phone. Premium clients get a dedicated on-call engineer number
• Response from 15 minutes for critical incidents
• Out of queue — critical incidents are handled before current tasks, regardless of remaining hours
• Postmortem — after resolution, we document what broke, why, and how to prevent it. Saved in the project knowledge base

Project Transfer from Another Team

We take on projects from any developers. We start with an audit — there are always "landmines".

• Code: grep for mysql_query (yes, still seen), unauthorized eval(), SQL without ForSql(), hardcoded passwords in init.php
• Infrastructure: file permissions, Nginx/Apache config, PHP settings, deployment scheme
• Documentation: collect architecture, non-standard solutions, integrations
• Access: server, hosting, domain, DNS, payment gateways, 1C — compile a registry

Onboarding takes 3-5 business days. After that, full support commences.

Backup Policy

Depending on the plan: from weekly to daily + incremental. We always verify restoration on a test server once per quarter. Recovery tests include full database restore and functional checks of order history, user accounts, and product catalog.

“The team fixed our 1C exchange in under 30 minutes. Since then, zero unplanned downtime.” — Owner of an online store with 15k SKUs

Schedule a free initial audit today and get a detailed health check for your Bitrix site. Our certified engineers will review your logs, backup strategy, and update schedule — then provide a risk assessment with concrete recommendations. Contact us for a tailored support plan or to discuss how we can keep your 1C-Bitrix project running smoothly.