Bitrix24 Market Setup: Install and Manage Apps

After updating the platform, your app stops requesting the right permissions — and managers can't see deals. We've encountered this dozens of times. More often than not, the issue lies in incorrectly specified OAuth scopes: the app requests either too many rights (up to disk and calendar, though it only works with CRM) or too few — then the integration stalls. With over 50 projects completed, we have 10+ years of combined experience and a proven track record. In this guide, we'll walk through how to properly handle app installation, app management, app publication, and permission update, and how to avoid common permission management pitfalls.

Installing an App from the Market

Path: Applications → Market. Apps are grouped by categories: CRM, Telephony, Tasks, Service Integrations. Follow these steps for app installation:

1. Navigate to Applications → Market and select the desired app.
2. Click Install — the app requests OAuth authorization with required scopes.
3. Review the permissions and confirm.
4. The app registers placements and appears under My Applications.

If something goes wrong, clear the portal cache — this resolves 95% of cases. For complex needs, our certified Bitrix partner team guarantees a smooth setup.

Managing Installed Apps

Effective app management starts at /devops/section/api/apps/. Here you can see requested scopes, webhooks, and last activity. We recommend regular audits — our experience shows that 8 out of 10 clients have hidden test apps with admin rights. For app removal, use REST:

POST /rest/app.uninstall
{
  "clear": 1
}

Without the clear=1 parameter, data remains — useful for reinstallation but risky for portal security.

Why Does an App Request Unnecessary Scopes?

Each app requests specific scopes. If you see an app asking for disk or calendar but it only uses CRM, reconsider. When publishing your own app, specify only the minimal required scopes. This is a technical review requirement.

Common mistakes:

• Requesting disk and calendar but only using crm.
• Requesting user (all users) instead of user_brief.
• Using entity instead of specific crm.deal, crm.lead.

Use the REST API Bitrix24 documentation at dev.1c-bitrix.ru and test on a test portal. Our guaranteed compliance ensures no scope inflation.

What's Included in a Turnkey Market Setup?

We offer a full cycle of work. Average project cost: $2,500 – $5,000 depending on complexity. Our clients save up to 30% on support budget through automation — a typical return on investment within 3–6 months.

Comparison of approaches: the cloud version processes requests 2–3 times faster (100–200 ms vs 300–600 ms) and scales automatically. We recommend cloud for large portals.

Publishing Your Own App in the Market

For app publication, you must:

• Register as a Bitrix partner on partners.1c-bitrix.ru
• Ensure HTTPS for all endpoints
• Prepare a correct manifest with description and screenshots
• Pass technical review (3–14 business days)

Before submission, validate your manifest with the official tool. Our projects have a 100% first-time pass rate due to meticulous checklists.

Common Mistakes and Their Solutions

• OAuth error: scope mismatch. Ensure manifest scopes match the code.
• App not displayed after installation. Clear portal cache in settings — works 95% of the time.
• Data loss on removal. Use clear=0 to preserve configuration.

As OAuth specification on Wikipedia states, proper scope configuration is key to security.

Source: OAuth on Wikipedia

Contact us for a preliminary audit of your portal — we'll identify weak spots in 2 days. Request a consultation for a full analysis of your Market configuration. We are a trusted Bitrix partner with ISO-certified processes and a satisfaction guarantee.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.