Custom CRM Card Development for Bitrix24

When the standard deal card falls short

A sales manager for equipment sees the same fields as a rental manager: fields are not grouped, no computed values, no conditional display logic. We've encountered such requests dozens of times and have accumulated expertise that allows us to solve the task in 3–7 days instead of months. Our engineers guarantee: a custom card will show the manager exactly what is needed at the current stage, without extraneous information.

Custom CRM cards: two levels of customization

Bitrix24 offers two ways to modify the CRM entity card, and they are fundamentally different in depth.

Level 1: UI settings. In the deal card (contact, smart process), click "Card settings" → "Edit fields and sections". Here you can: rename sections, drag fields between sections, hide unnecessary fields, set field required by stages (for deals). This is free and covers ~40% of requests. But you cannot add computed fields, conditional logic, custom widgets, or data from external systems.

Level 2: Development via REST Placement API. This embeds arbitrary HTML/JS content into specific zones of the card. This is where real customization begins.

What can be embedded via Placement API?

The CRM entity card has several zones (placements) where you can embed custom content:

• CRM_DEAL_DETAIL_TAB — a tab in the deal card. Full area for any UI.
• CRM_DEAL_DETAIL_ACTIVITY — a block in the timeline. Suitable for custom actions.
• CRM_CONTACT_DETAIL_TAB, CRM_COMPANY_DETAIL_TAB — analogously for contacts and companies.
• CRM_DYNAMIC_ITEM_DETAIL_TAB — a tab in the smart process card.

Register a placement via REST:

BX24.callMethod('placement.bind', {
    PLACEMENT: 'CRM_DEAL_DETAIL_TAB',
    HANDLER: 'https://your-app.com/deal-tab.html',
    TITLE: 'Margin calculator'
});

After registration, a new tab appears in the card. When opened, Bitrix24 loads the HANDLER in an iframe and passes the context: ENTITY_ID (deal ID), AUTH_ID, REFRESH_ID.

Deep dive: custom tab with data

Consider a typical case — a "Finance" tab in the deal card that shows: total by product items, cost from external 1C, margin, payment history.

Step 1: get deal data

BX24.init(function() {
    var dealId = BX24.placement.info().options.ID;

    BX24.callBatch({
        deal: ['crm.deal.get', {id: dealId}],
        products: ['crm.deal.productrows.get', {id: dealId}]
    }, function(result) {
        var deal = result.deal.data();
        var products = result.products.data();
        renderFinanceTab(deal, products);
    });
});

Step 2: request cost from external API

The tab makes a request to your backend, passing product SKUs. The backend proxies to 1C or ERP and returns the cost.

Step 3: render

Calculate margin client-side and display a table. For visual consistency, use B24 CSS variables or the @bitrix24/b24-ui library.

Why conditional field logic doesn't work out of the box?

A frequent request: show/hide fields based on another field's value. E.g., "Reason for rejection" field visible only on "Lost" stage. Standard functionality allows making a field required by stage, but not hiding it.

Solution — a custom handler via placement CRM_DEAL_DETAIL_TAB or embedding JS code via a user field type. In the on-premise version, you can modify the bitrix:crm.deal.detail component template and add JS logic to script.js.

For the cloud version, the only clean way is a placement with full redrawing of the required field section. This means: you fetch data via REST, render fields with conditional logic in your iframe, and on save, send changes back via crm.deal.update.

Timeline widgets

Placement CRM_*_DETAIL_ACTIVITY embeds a block directly into the activity feed of the card. Suitable for:

• Displaying delivery status (data from a transport company API)
• Showing client balance from an accounting system
• Displaying the latest tickets from helpdesk

The widget updates on every card open. For caching, use BX24.appOption — the app storage on the B24 side.

Performance: approach comparison

Iframe tabs load on activation (click on the tab). For heavy tabs, this is fine — the user doesn't wait for something they haven't opened. But if you embed a widget in the main card area, it loads immediately. Every REST request from an iframe is a network round-trip. Use BX24.callBatch to batch requests: one batch instead of five sequential calls. Custom tabs via Placement API are 3 times faster to develop than overriding templates in the on-premise version and do not require core updates.

Custom card development stages

What's included

• Development of technical specification and card prototype
• Placement registration and REST integration setup
• Implementation of custom tab/widget with testing
• Integration with 1C (CommerceML) or other external systems
• API documentation and access transfer
• Employee training on the new card
• 1 month support after launch

Cloud version limitations

In the cloud, you cannot modify standard card sections — only add new tabs and widgets. You cannot remove standard fields from the main view (only hide via card settings). For full interface control, use the on-premise version with component template override (crm.deal.detail).

Estimate your project in one day

We develop custom CRM cards turnkey. 10+ years of Bitrix24 experience, over 50 successful projects. Development cost is calculated individually, manager time savings after implementation reach 30%. Order custom CRM card development — we'll send a preliminary estimate of timeline and cost. Get a free engineer consultation.

How to ensure CRM implementation success?

We have been working with Bitrix24 for over 10 years — during that time we have completed 500+ projects. Every second one starts with the same problem: a company buys CRM, sets it up "by the book," and three months later managers fill two out of twelve fields, deals stall at "Negotiations" for months, and management cannot extract analytics. The root is not bad software — it's the approach. CRM is configured without auditing real processes, without considering staff objections, and without a step-by-step automation plan. In this article — a step-by-step guide on how we avoid this.

All specialists are certified by 1C-Bitrix, the methodology is proven on hundreds of cases. 1C-Bitrix is a platform that, when paired with Bitrix24, provides real end-to-end analytics if configured correctly.

Reality of CRM implementations: 80% fail to deliver results

Why do employees sabotage CRM?

Managers are accustomed to Excel and notepads — they perceive CRM as total control. Our solution: involve key employees at the design stage, show personal benefits — automatic reminders, ready-made proposal templates, less routine. We train on real scenarios, not abstract examples. Resistance drops 4 times faster than with "command" implementation.

How to prevent incomplete data entry?

Mandatory fields are filled, others are ignored — familiar picture? We solve it on three levels:

• Set mandatory fields per funnel stage (only relevant data at each stage).
• Implement auto-fill from UTM tags, email parsing, data from open databases.
• Remove redundant fields — fewer fields, higher quality.

According to our practice, field optimization reduces omission rates by 70% within the first month.

How to design funnels correctly?

Too many stages, no transition criteria, duplicate stages — typical mistakes. We design the funnel based on reality: how sales actually work, not as written in textbooks. We use CRM data from the first 2 weeks of audit to identify real stages and loss points. This shortens the deal cycle by 25–40%.

What automation should be done first?

We set up robots and business processes from day one — so the team immediately feels the difference. For example, lead distribution, sending emails after status changes, creating tasks for colleagues. Companies that implement automation at the start achieve plan targets 3 months faster.

What Bitrix24 features accelerate sales?

• Inquiries from all channels (phone, email, messengers, forms) are captured automatically.
• Leads are created and distributed without manual intervention.
• Visual kanban with custom stages — drag a card to the next stage, an email is sent automatically, a task is created.
• Omnichannel: unified window for telephony, email, WhatsApp, Telegram, Viber, VK, Instagram, online chat.
• Robots and business processes: mailings, document generation, reminders, escalations — no coding required.
• Analytics: funnel, conversions, lead sources, manager workload, average handling time.

What does integrating a 1C-Bitrix website with Bitrix24 CRM provide?

Synergy of the two products yields measurable results, and we implement it through direct data exchange. Site forms transfer leads to CRM instantly with full UTM markup — you see where the client came from. Online chat connects via open lines: a visitor writes on the site, the manager responds from CRM. Orders in the store based on infoblocks v2.0 become deals with full purchase history, enabling cross-selling. Call tracking with number substitution links calls to advertising channels. We use CommerceML to exchange data with 1C Trade Management/ERP: nomenclature, stock balances, prices — synced via agents without manual intervention. End-to-end analytics collects advertising costs, visits, leads, sales in one report — ROI per channel. For non-standard logic, we use REST API and high-load blocks to store arbitrary data (e.g., tech support interaction history). In one project, we configured this bundle for a retail chain: 1C cash register integration with CRM created contacts automatically upon loyalty card purchase, and CRM marketing via Bitrix24 increased repeat purchases by 18% in six months.

How we set up CRM: the process

1. Audit. We analyze how sales work currently. Where are leads lost? Which channels bring clients? We form recommendations before technical implementation.
2. Design. Multiple funnels for different directions, custom fields, mandatory stages and transition conditions. Structure reflects the real process.
3. Integrations. Connect to website, telephony, email, messengers, Yandex.Direct, Google Ads, 1C.
4. Custom modules. When standard is not enough — applications for Bitrix24: specific reports, non-standard business logic, integrations with industry systems.
5. Migration. Transfer databases from amoCRM, Megaplan, Salesforce, HubSpot, Excel. Relationships, communication history, attachments — everything intact.
6. Training. Trainings tailored to your configuration, video instructions, documentation.

What is included in the work?

Cloud or on-premise: which to choose?

Comparison: the cloud version is 2–3 times cheaper initially, but for B2B companies with large data volumes, on-premise pays off in 1.5–2 years due to no per-user subscription fee.

Metrics we track for your business

• Funnel stage conversion. If 80% are lost at the proposal stage — the problem is pricing, not managers. Norm: 5–15% for B2B, 1–5% for high-ticket B2C.
• Lead response time. A 5-minute response increases conversion 10x compared to a 30-minute response. We set alerts — if a manager doesn't respond within 15 minutes, the lead is reassigned.
• LTV. CRM segments clients by lifetime value — managers focus on the most valuable.
• Average deal cycle. If it increases, something is broken. Reasons for rejections are gold for product and script adjustments.

Our case studies

Manufacturing company (B2B). A plant with high annual turnover. Leads were lost in email; management only learned about large deals post-factum. We set up automatic inquiry capture, a funnel "qualification → calculation → proposal → approval → contract → payment," and robots that generate proposals from templates. Conversion increased by 23%, lead processing time dropped from 4 hours to 20 minutes. Manager payroll savings exceeded $1,000 per month due to reduced routine.

IT service company. Three funnels: new clients, upselling, tenders. Auto-generation of contracts and invoices, integration with Jira — after signing, tasks automatically appear in the development department. Management received a weighted revenue forecast with 90% accuracy. The project paid off in 4 months.

Implementation timeline and cost

The cost is calculated individually based on your scope of work. After implementation — tech support with SLA (response from 1 hour), regular usage audits, and feature development.

Ready to discuss your situation? Contact us — we'll conduct a free audit of your current CRM within 2 days and propose an implementation architecture with a result guarantee. Request a consultation — we'll show you in numbers how much you'll save with proper setup.