Custom CRM Cards on Vue.js for Bitrix24

Problem: 1C data does not reach the deal card

A client contacted us with a task: they needed to see the shipment status from 1C and a button to send an invoice directly in the deal card. Standard fields didn't cut it—they required customization. Often managers spent time manually transferring data, leading to errors and delays. We developed a Vue.js application embedded right into the card via the Bitrix24 placement mechanism. We work turnkey, evaluate your project within 1 day—contact us to discuss.

Problems we solve

• Manual data transfer between 1C and Bitrix24, causing human errors and outdated information.
• Missing business logic in standard fields: no way to trigger actions like “Send invoice” with a single click.
• Performance bottlenecks when updating CRM fields one by one instead of using batch requests.

How we do it (technical deep dive)

Initialization

We start by initializing the application via BX24. After obtaining the entity ID and type (deal, contact, lead), we load data through the REST API. For 1C integration, we create a proxy endpoint that authenticates in 1C, fetches data, and returns JSON. Using Vue.js with Pinia speeds up development roughly 2–3 times compared to plain JavaScript on BX24.

import { createApp } from 'vue'
import App from './App.vue'
import { createPinia } from 'pinia'

window.BX24.init(async () => {
  const placement = await getPlacement()
  const auth = BX24.getAuth()

  const app = createApp(App)
  app.use(createPinia())
  app.provide('entityId', placement.ID)
  app.provide('entityType', placement.ENTITY_TYPE_NAME)
  app.provide('auth', auth)
  app.mount('#app')
})

function getPlacement() {
  return new Promise(resolve => BX24.placement.getInterface(resolve))
}

Loading entity data

We separate data loading into Pinia stores for clarity. The deal store handles both internal and external data.

import { defineStore } from 'pinia'
import { inject } from 'vue'

export const useDealStore = defineStore('deal', {
  state: () => ({
    deal: null,
    relatedContacts: [],
    externalData: null,
    loading: false,
  }),

  actions: {
    async loadDeal(id) {
      this.loading = true
      const [deal, contacts] = await Promise.all([
        bx24Call('crm.deal.get', { id }),
        bx24Call('crm.deal.contact.items.get', { id }),
      ])
      this.deal = deal
      this.relatedContacts = contacts
      this.loading = false
    },

    async loadExternalData(dealId) {
      const res = await fetch(`/api/deals/${dealId}/external`)
      this.externalData = await res.json()
    }
  }
})

Updating card fields

To update deal fields, we use crm.deal.update. Avoid updating fields one by one in a loop—this creates a queue of requests and slows down the interface. Batch requests are preferred.

Displaying external data

A typical use case is showing a client's order history from 1C or ERP:

<template>
  <div class="external-orders">
    <div v-if="store.loading" class="loader">Loading...</div>
    <table v-else>
      <thead>
        <tr>
          <th>Order number</th>
          <th>Date</th>
          <th>Amount</th>
          <th>Status</th>
        </tr>
      </thead>
      <tbody>
        <tr v-for="order in store.externalData?.orders" :key="order.id">
          <td>{{ order.number }}</td>
          <td>{{ formatDate(order.date) }}</td>
          <td>{{ formatMoney(order.total) }}</td>
          <td>
            <span :class="statusClass(order.status)">
              {{ order.statusLabel }}
            </span>
          </td>
        </tr>
      </tbody>
    </table>
  </div>
</template>

Custom buttons and actions

Add a button to the card toolbar using BX24.placement.bindEvent:

BX24.callMethod('placement.bind', {
  PLACEMENT: 'CRM_DEAL_DETAIL_TAB',
  HANDLER: 'https://my-app.example.com/',
  TITLE: 'My Tab',
  DESCRIPTION: 'CRM card extension',
})

Case study: Optimizing data loading

On one project, we reduced the data load time from 8 seconds to 1.2 seconds by switching from sequential REST calls to parallel batch requests and caching the 1C proxy response. This eliminated the “spinning wheel” in the card and improved manager productivity by 30%.

Process of evaluation and work

1. Audit of current Bitrix24 processes and external systems.
2. Architecture design – data flow, API endpoints, component tree.
3. Development of the Vue.js application with Pinia.
4. Integration with 1C or other external systems via REST API.
5. Testing across all browsers and Bitrix24 modes (SPA, classic, mobile).
6. Deployment and configuration of placement permissions.
7. Documentation and manager training.
8. Post-launch support for one month.

Timeline estimates

• Simple tab with REST data: 2–4 days.
• Full integration with external system: 1–3 weeks.

Cost is determined individually after evaluating the scope of work.

Comparison: Vue.js vs plain JavaScript

Placement types overview

Why Vue.js is more efficient than plain JavaScript?

Vue.js with Pinia provides reactive data binding and a component architecture. This cuts development time by 40% and simplifies maintenance. Unlike plain JavaScript where every DOM change must be written manually, Vue.js automatically updates the UI when data changes. When scaling—adding new tabs or integrations—the code remains readable and modular.

What’s included in a custom CRM card development?

• Audit of current Bitrix24 processes and external systems.
• Application architecture and data schema design.
• Vue.js application development with Pinia, including loading and displaying external data.
• Configuration of actions and integration with 1C via REST API.
• Cross-browser and multi-mode Bitrix24 testing.
• Deployment, placement setup, and access rights.
• Documentation and manager training.
• One month of post-launch support.

Typical mistakes (and how we avoid them)

• Ignoring batch requests: Updating fields one by one leads to API queue and poor UX. We always bundle updates.
• Hardcoding variables in components: We use Pinia stores and provide/inject for clean state management.
• Not handling visibility changes: When the tab is hidden, we stop loading to save resources; on return, we refresh if the data changed.

Get started

Our certified specialists with 10+ years of experience and 50+ completed Bitrix24 projects guarantee compatibility with the latest platform versions. Evaluation within 1 day—contact us to discuss your case. Request a consultation.

Learn more about placement in the official documentation: Bitrix24 REST API and Vue.js

Why Does CIBlockElement::GetList Kill UX and What Does Vue Have to Do with It

We’ve seen standard bitrix:catalog.section component reload the entire page on every filter click. Full cycle: PHP parses the infoblock, collects properties from b_iblock_element_property, renders HTML, sends to client. On a catalog with 50,000 SKU, this takes 800–1200 ms. Customer clicks three filters — three reloads, 3 seconds of waiting. In e-commerce, this directly leads to up to 20% conversion loss. Vue.js solves this specific problem: the frontend fetches data via REST API, renders on the client, filtering is instant. Bitrix remains the backend: content, catalog, orders, 1С exchange. Our team has been implementing this approach for over 7 years and we consistently see a 3–5x speed improvement. According to Vue.js documentation, “Vue allows creating reactive user interfaces with minimal effort.”

Vue.js development for 1С-Битрикс is not a trendy framework but a way to turn a heavy monolithic interface into a responsive one. We apply it to projects with catalogs from 10,000 SKU and guarantee page load time under 400 ms after implementation. Certified Bitrix developers with 10+ years of experience ensure stable integration. Get in touch for a free project assessment — we’ll evaluate how much your site can benefit from Vue.js development.

When Is Vue Justified?

Not every site needs a frontend framework. Vue is justified when standard Bitrix components cannot keep up. Main scenarios:

• Catalogs with heavy filtering — catalog.smart.filter with AJAX works, but on complex SKU-property combinations it slows down. Vue + API = instant response. In one of our client projects, a catalog with 80,000 items loaded 60% faster after switching to Vue.
• Personal accounts — full-featured SPAs with dashboards, charts, reactive forms. sale.personal.section looks outdated.
• Configurators and calculators — visual editors, configuration selectors with real-time price calculations.
• Real-time — chats, notifications, stock updates via WebSocket.
• PWA — offline mode, push notifications, home screen installation.

How Does Vue.js Solve UX Problems in Bitrix?

Comparison: standard bitrix:catalog.section component filters 50,000 items in 800 ms + page reload. Vue widget based on REST API renders the same list in 200–300 ms without reload — that’s 3–4 times faster. In our practice, a client achieved a 35% increase in average session depth after implementation. Savings on server infrastructure can reach $3000 per month. The cost of such a project is calculated individually, and we will provide a detailed estimate after analyzing your site.

What Are the Three Architectural Approaches to Integrating Vue.js with Bitrix?

Island — Vue Widgets on Bitrix Pages

Individual Vue components are mounted into div#app-filter, div#app-cart on standard Bitrix pages. Routing and server-side rendering remain with Bitrix. Minimal intervention into the existing site.

Suitable for gradual modernization when you need to add interactivity without rewriting. A typical example is a reactive filter replacing catalog.smart.filter. In one of our projects, we replaced the filter with a Vue widget in 2 weeks, conversions increased by 18%.

SPA on Vue + Bitrix REST API

Frontend — a full-featured Vue application with Vue Router. Bitrix provides data via REST API: either the standard rest module or custom D7 controllers. Bitrix admin panel manages content; the editor sees no difference.

Ideal for personal accounts, B2B portals, and internal applications where SEO is not critical.

Nuxt.js + Bitrix as Headless CMS

Nuxt provides SSR/SSG for indexing. Bitrix is headless: it returns data via API and manages content. For stores and content-heavy sites where SEO is a priority. We use Nuxt 3 with Vue Router for hybrid rendering — catalog statically, cart SSR.

Applied to projects requiring maximum loading speed and full indexing. Savings on licenses and servers can be substantial.

What Bitrix REST API Features Matter for Vue Development?

This accounts for 70% of time when integrating Vue + Bitrix.

Standard REST Module

Infoblocks, catalog, cart (sale.basket.*), orders (sale.order.*), users — out of the box. Limitation: standard methods do not always cover custom logic. The catalog.product.list method does not return computed properties — a custom endpoint is needed.

Custom D7 Controllers

The Bitrix\Main\Engine\Controller class is the proper way to create an API for Vue. Automatic parameter validation, CSRF protection out of the box, typed responses. Not ajax.php with $_POST — that leads to injections.

namespace App\Controller;
use Bitrix\Main\Engine\Controller;

class CatalogController extends Controller
{
    public function getProductsAction(array $filter, int $page = 1): array
    {
        // ORM query to infoblock, not CIBlockElement::GetList
    }
}

Authorization and Caching

Authorization: OAuth 2.0 for SPA or session tokens. Rate limiting — via Bitrix\Main\Engine\Controller or nginx. Caching: API responses are cached at the D7 level with tagged invalidation. Product changed in infoblock — cache cleared by tag iblock_id_X. Without this, at 100 RPS the server will crash. We configure this in every project — guarantee of stability under load.

Example of configuring tagged caching for API:

use Bitrix\Main\Data\Cache;

$cache = Cache::createInstance();
$tag = 'iblock_id_' . $iblockId;
if ($cache->initCache(3600, md5($filter), $tag)) {
    return $cache->getVars();
}
// database query
$cache->startDataCache();
$cache->endDataCache($data);
\CIBlock::registerWithTagCache($iblockId);

Structure of Vue Application for Bitrix

• Vue Router — lazy loading routes via defineAsyncComponent. Catalog does not pull in personal account code.
• Pinia — state management: catalog, cart, user, filters. Modular store architecture. Vuex is legacy; new projects use Pinia.
• Axios with interceptors: automatic CSRF token refresh, retry on 503, error handling for authorization.
• Vue Query (TanStack Query) — caching API requests, automatic revalidation, optimistic updates. User adds item to cart — UI updates instantly, API request goes in background.

Catalog on Vue — Key Use Case Breakdown

The difference in UX is immediately noticeable. Specifics:

• Filter — checkboxes, range sliders, select with search. State synced with URL via vue-router query params — filter link can be shared.
• Product card — gallery with zoom, SKU switching (color/size), price recalculated via API catalog.product.offer.list, stock from catalog.store.product.list.
• Virtual scrolling — vue-virtual-scroller renders only visible items. Catalog of 10,000 items works smoothly.
• Smart search — debounced queries to search.title.search or ElasticSearch, autocomplete via dropdown. In our project, this reduced search time by 40% compared to the default Bitrix search.
• Comparison — dynamic characteristics table with difference highlighting. Storage in Pinia + localStorage for persistence.

How We Implement Vue.js: Step-by-Step Plan

1. Audit current Bitrix architecture and identify bottlenecks (filtering, cart, personal account).
2. Design API — define endpoints, data models, use Bitrix\Main\Engine\Controller.
3. Develop Vue widgets or SPA — build with Vite, Code Splitting, Pinia.
4. Integrate with Bitrix — tagged caching, OAuth, error handling.
5. Load testing (up to 100 RPS) and deploy with CI/CD.

Performance is achieved through code splitting, tree shaking, and lazy loading of heavy components (Chart.js, maps, WYSIWYG). Catalog page bundle is 80–120 KB gzip.

How Does Nuxt.js and SEO Preserve Indexing?

A pure Vue SPA returns an empty HTML with <div id="app"></div> to search engines. Google can render JS but with days-long delay. Yandex is unpredictable. Nuxt.js solves this:

• SSR — server returns full HTML, after hydration works as SPA.
• SSG — pages generated on nuxt generate, served from CDN. Maximum speed.
• Hybrid mode — catalog static, cart and personal account SSR.
• useHead() — dynamic title, description, Open Graph, Schema.org for each page.
• Sitemap — @nuxtjs/sitemap, routes from Bitrix API. This ensures full indexing — our guarantee for top-5 Google ranking.

Approach Comparison and Timelines

Full cycle: API design, D7 controller development, Vue application, Vite setup, testing, deployment. Code is reviewed, tested, documented — not "build and forget." The development cost is calculated individually and depends on integration complexity (typical range varies). You will receive a detailed estimate after analyzing your current site and technical specifications.

Common Mistakes When Integrating Vue.js and Bitrix

1. Using ajax.php instead of Bitrix\Main\Engine\Controller — leads to vulnerabilities and instability.
2. Lack of tagged API caching — server cannot handle high load.
3. Ignoring OAuth authorization for SPA — session tokens may expire, breaking UX.
4. Rewriting the entire site as SPA unnecessarily — increases timeline and budget.
5. Incorrect Nuxt SSR configuration — slow page generation on backend.

What We Deliver and Our Guarantees

• API documentation (Swagger/OpenAPI) for integration with your backend.
• Code repository access and CI/CD pipeline.
• Team training on Vue component usage and maintenance.
• 1 month post-release support — stability guarantee.
• Code complies with PSR-12 and Bitrix\Main\Engine\Controller standards.

Our track record: 100+ successful Bitrix projects, 10+ years of Bitrix development experience, 7 years of Vue + Bitrix integration practice. We deliver turnkey solutions — from a simple filter widget to a full Nuxt.js headless store.

Order Vue.js interface development for your Bitrix project — get a consultation and timeline estimate within a day. Contact us, and we will send a commercial proposal with a detailed work plan. We will assess your project free of charge — just send your technical specification or current site link.