MAINTENANCE AND DEVELOPMENT
Maintenance
and refinement of sites
on 1C-Bitrix
We support projects on 1C-Bitrix: 1C exchange, programming improvements, updates, and error control. We agree on tasks and hours, verify changes on a staging environment, and release on schedule.
TASK
SCENARIO
DATA
VERIFICATION
LAUNCH
HANDOVER
in both directions
1C EXCHANGE
CHANGE CONTROL
MAINTENANCE
projects
of studio
models
Premier Partner status
marketing, analytics
Website support with clear procedures
We accept a project with its current code, modules and integrations. First, we check the platform version, license, accesses and critical scenarios: catalog, cart, checkout and exchange with 1C. We turn the found limitations into a work plan.
We separate tasks by content and priority. Content edits and programming changes have different rates; the monthly package includes an agreed reserve of hours and a response procedure. Before starting a task, we show an estimate, and after completion — the result and time accounting.
For software changes, we use a test environment and version control. Before release, we verify agreed scenarios and the possibility of rollback. We first check core or PHP updates for compatibility with specific modules and custom code.
- Introductory project and critical scenario audit
- Separate content and programming tasks
- Pre-start estimate and time report
- Test bench, Git, and release plan
- 1C exchange control and agreed monitoring
Stand
Software fixes are checked separately first
Exchange
Error is checked against both sides of the integration
Hours
Estimate and consumption are visible by task
Regulations
Reaction and service hours fixed
We analyze exchange failures step-by-step
We check export, delivery, processing, and the result on the site considering documentation on exchange with 1C. If the cause is in the 1C configuration, we pass diagnostic data to the responsible specialist. Responsibility boundaries are agreed upon in advance.
Development without random edits
Support takes into account the specifics of the project, third-party modules, and work scenarios.
Compatibility before update
We verify 1C-Bitrix system requirements and project dependencies. Updates are tested on a copy; PHP compatibility with third-party modules and custom code is checked separately.
Old code analysis
We identify non-standard changes and problem areas. We perform refactoring by priority, maintaining verifiable behavior rather than a complete overhaul without assessment.
Release control
We coordinate the release window, backup, and rollback conditions. It is noted in documentation on backups that the update changes kernel files and database structure. We check the order and exchange after release; the absence of downtime depends on the architecture and the nature of the change.
From project acceptance to regular releases
For every task, there is an estimation, verification, and clear result.
Project acceptance
We collect access, versions, and a list of integrations. We check critical scenarios and current limitations.
Stand and backup
We prepare the test environment and Git. We check the backup and restoration order in the agreed volume.
Monitoring and priorities
We agree on checks, maintenance calendar, and incident channels. We separate response time from resolution time.
Task estimate
We describe the result and hours volume. We clarify dependencies on 1C, providers, and third-party developers.
Development and verification
We apply changes on the staging environment. We verify agreed-upon scenarios, data exchange, and access rights.
Release and report
We move changes according to the plan and check the result. We show completed tasks, hours, and next priorities.
Platform, exchange and change control
Work is built on a specific version of the site and available interfaces.
1C-Bitrix and PHP
Components, modules and D7 where appropriate for the project. We check environment requirements according to the vendor's current documentation.
Exchange with 1C
CommerceML and other agreed interfaces. We analyze identifiers, statuses, upload errors, and re-exchange.
Stand and monitoring
Git, test environment, logs, and external checks. We limit and anonymize sensitive data on the staging environment according to an agreed procedure.
Hourly refinements
Two formats of one-off tasks. We agree on estimation and results before starting; SLA and on-call services are connected separately.
Content modifications
2 000 ₽ / hour
Goods, texts, images, and metadata without changing program logic. Volume and task result are agreed upon before start.
Software development
4 000 ₽ / hour
Components, 1C exchange, integrations, and code fixes. We agree on the assessment, test scenarios, and release before starting.
— COST
Pricing
to Bitrix support
Monthly packages with a reserve of hours. Specific priorities, calendar, and SLA rules are fixed in the contract.
| Scope of work | Basic Bitrix Corporate site or small catalog 75 000 ₽/month month of maintenance | POPULAR Business e-Commerce Store with active 1C synchronization 135 000 ₽/month month of maintenance | Corporate Enterprise Portal with an extended support protocol 220 000 ₽/mo month of maintenance |
|---|---|---|---|
|
Monthly hour reserve
|
Up to 15 hours | Up to 30 hours | Up to 55 hours |
|
Reaction to a critical failure
|
Up to 4 working hours | Up to 1–2 hours per SLA calendar | Up to 15–30 minutes, 24/7 per SLA |
|
1C exchange control
|
Basic log control | CommerceML error monitoring | Queue and stock monitoring |
|
24/7 availability checks
|
Every 5 minutes | Every minute | Every 15 seconds and order scenarios per task |
|
Backups to external storage
|
Weekly | Daily | Daily and before releases |
|
Security and updates
|
Quarterly check | Monthly check | Incident monitoring and WAF per task |
|
Test environment and Git
|
Included; server separate | Included; server separate | Included and CI/CD per assignment |
|
Communication
|
Email / Telegram | Work chat and calls | Lead specialist and manager |
Monthly cost of services. Bitrix licenses and modules, servers, and third-party services are paid separately. Reaction means the start of processing a registered incident, not the recovery time. Calendar, priorities, hour usage, and limit overages are stipulated in the contract.
— QUESTIONS AND ANSWERS
Everything that matters
before start
Scope of work, source materials, approval order, and launch conditions.
-
Do you take over projects from other developers?
Yes, we start by checking code, modules, and integrations. We describe found limitations and priorities. We estimate documentation recovery and refactoring volumes separately. -
Is it possible to work without a valid license?
We check the possibility of modifications and access to updates for a specific product and license. Before core updates, we clarify the right to receive updates from the vendor; renewals are paid separately. -
Who fixes errors on the 1C side?
We diagnose the agreed exchange chain and localize the cause. Configuration changes in 1C are performed by a responsible specialist in an agreed volume. We pass data for reproduction to them without unnecessary information. -
How are hours accounted for?
Every task receives a description and estimate before starting. In the report, we show the completed work and actual time according to the accepted procedure. Overruns and new tasks are agreed upon separately; rules for carrying over unused hours are recorded in the contract. -
What to choose: a package or hourly work?
The hourly format is suitable for individual tasks at 2 000 ₽ for content and 4 000 ₽ for programming. The monthly package adds a reserve of hours, monitoring and an agreed response protocol. The priority of one-time tasks is determined separately. -
Do you guarantee zero downtime?
There is no universal guarantee for any change. We check compatibility on the staging environment and prepare a release and rollback plan. Database or environment changes may require an agreed-upon maintenance window.