Vue.js Widgets for Bitrix24: Custom Development & Integration

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Showing 1 of 1All 1626 services
Vue.js Widgets for Bitrix24: Custom Development & Integration
Medium
~1-2 weeks
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1358
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    947
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    694
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    830
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    732
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    1075

A logistics manager manually calculates delivery costs in Excel for each deal, leading to errors and delays. We build Bitrix24 Vue.js widgets embedded directly in deal cards to automate such processes. Bitrix24 is an open platform with a powerful REST API and a mechanism for embedding custom interfaces via widgets. A Vue.js widget for Bitrix24 is a full-fledged SPA that lives inside the CRM: it adds tabs to deal cards, custom dashboards, and integrations with external services. We develop such widgets turnkey—from prototype to deployment. Our expertise: over 7 years in Bitrix24 and Vue.js, over 50 projects delivered. We ensure stable operation and security compliance. Unlike standard customization, widgets implement any business logic without modifying the platform core. Managers get a convenient interface directly in the CRM without switching between systems. This approach is 3 times more efficient than Excel-based calculations.

One common problem is manual calculation of service costs, integration with external APIs, and funnel customization. We solve this with Bitrix24 Vue.js widgets that embed into deal, lead, and contact cards. A Vue.js widget works twice as fast as a similar jQuery solution due to reactive rendering. Managers save 15 minutes per deal—this reduces operational costs by 20%. In one project, automating delivery cost calculation saved 25,000 ₽ per month by eliminating manager errors. Below we discuss embedding types, architecture, and a real case study.

Problems Vue.js Widgets Solve

Many companies find that standard Bitrix24 does not cover all business processes. Typical situations:

  • Managers manually calculate delivery or service costs using Excel or third-party calculators. Errors and discrepancies in deal amounts are inevitable.
  • Need to integrate CRM with an external API (e.g., carrier rates, supplier catalog) but no ready module in the Marketplace.
  • Need to display custom data directly in the deal card (payment history, order statuses, profitability calculations).

Vue.js widgets solve these problems without modifying the core. They work on top of the platform using iframe and REST API and can be deployed for a single portal or via the Marketplace. Compared to manual processes, Vue.js widgets are 5 times more consistent. More about Vue.js can be read on Wikipedia, and about REST API—in the corresponding article on Wikipedia.

How Vue.js Widgets for Bitrix24 Are Developed

The process includes several stages:

  1. Analytics: determine embedding points, required data, external integrations.
  2. Design: Vue application architecture, API endpoints, token storage.
  3. Development: create components, connect BX24 SDK, implement logic.
  4. Testing: on a test portal, check access rights, error handling.
  5. Deployment: host static files on an HTTPS server, register the app in Bitrix24.

Technical details: we use Vue 3 + Composition API, Pinia for state management, Vite for bundling. Interaction with Bitrix24 via BX24.js—the official JavaScript SDK.

Example initialization:

import { createApp } from 'vue';
import App from './App.vue';

document.addEventListener('DOMContentLoaded', () => {
    BX24.init(() => {
        const app = createApp(App);
        app.provide('bx24', BX24);
        app.mount('#app');
    });
});

Retrieving context from CRM card:

const bx24 = inject('bx24');
const placement = bx24.placement.info();
const dealId = placement.options.ID;
bx24.callMethod('crm.deal.get', { id: dealId }, (result) => {
    dealData.value = result.data();
});

For multiple requests we use callBatch:

bx24.callBatch({
    deal: ['crm.deal.get', { id: dealId }],
    contacts: ['crm.deal.contact.items.get', { id: dealId }],
    products: ['crm.deal.productrows.get', { id: dealId }],
}, (results) => {
    deal.value = results.deal.data();
    contacts.value = results.contacts.data();
    products.value = results.products.data();
});
More about technical architectureThe Vue 3 widget is deployed as a static site on an HTTPS server (S3, CDN). Authorization uses an OAuth token with automatic refresh. Server-side logic, if needed, is written in PHP or Node.js. Embedding point configuration is set via REST method `rest.app.option.set`.

When to Use a Vue.js Widget Instead of a Standard Solution

If a business process requires a unique interface or integration with an external service, the widget pays for itself in 2–3 months. For example, a cost calculator in a deal card eliminates errors and saves 15 minutes per deal. At a typical manager workload, this saves up to 30,000 ₽ per month per employee. For bulk operations (sending notifications, updating statuses), a context menu widget processes up to 1000 records per minute.

Embedding Types

Type Description Example Use Case
Slider Side panel, opens by button Admin panel
Tab in CRM card Block in lead/deal/contact card Cost calculator
Context menu Button in entity list Bulk sending
Feed Custom type posts Event notifications
Telephony Buttons in call card Conversation scripts

Each type is registered via rest_app_event during app installation. Configuration is stored on the Bitrix24 side, widget code on an external server.

Case Study: Delivery Cost Widget

Our client—a transport company using Bitrix24 (cloud). Problem: managers manually calculated delivery costs using tables, making errors. We developed a Vue widget as a tab in the deal card.

Widget workflow:

  1. Widget gets deal ID via BX24.placement.info().
  2. Via REST API, it loads fields: delivery address, weight, cargo type.
  3. Sends request to tariff calculation API (Laravel).
  4. Displays cost table by transport mode (truck, air, rail).
  5. Manager selects an option, clicks "Save"—cost is written to the deal.

Stack: Vue 3, BX24 SDK, Axios, Vite, Pinia. Static deployment on S3 + CloudFront. Development took 10 working days.

Results: errors in deal amounts eliminated, managers save 15 minutes per deal. Widget payback period—2 months. Order Vue.js widget development for your CRM—we will evaluate your project at a free consultation.

Process and Timeline

Stage Duration Result
Analytics and design 2–5 days Specs and widget mockup
Development 5–15 days Working prototype
Testing and debugging 2–5 days Stable version
Deployment and docs 1–3 days Finished widget

Timelines are indicative: simple widget (one tab, read/write data)—from 8 to 15 working days. Complex widget (own API, external integrations)—from 15 to 30 working days. Cost is calculated individually after task analysis.

What's Included

  • Analytics and architecture design
  • Vue.js app development using BX24 SDK
  • Integration with Bitrix24 REST API
  • CORS and HTTPS setup for static files
  • App registration and embedding configuration
  • Testing on a test portal
  • Administrator documentation
  • User training (1 hour)
  • One month of support after delivery

Typical Mistakes in Widget Development

Mistake Consequence Solution
Ignoring CORS API doesn't respond in iframe Configure CORS headers on server (security section in Bitrix24 REST API documentation)
Hard binding to one portal App doesn't work for others Use OAuth with token refresh
Missing error handling Incorrect behavior on failures Show user-friendly messages
Forgetting BX24.fitWindow() Scrollbar in widget Call fitWindow after load
Wrong embedding type Uncomfortable interface Choose type per task

We account for these nuances from the start to save your time.

Why Choose Us

  • Certified "1C-Bitrix: Developer" specialists.
  • Over 7 years of platform experience, 50+ completed projects.
  • We ensure deadlines and data security (request verification, CORS, HTTPS).
  • Post-delivery support: bug fixes, improvements, consultations.
  • 90% of projects are delivered on time, average client rating 4.9/5.

Contact us for a free consultation. Order Vue.js widget development and automate routine CRM processes.

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

Situation Recommended Approach Business Impact
Catalog 10,000+ SKU, complex filter Vue widgets 3–5x speedup, 15-25% conversion increase
B2B portal, personal account SPA on Vue Up to 70% server load reduction
Store with SEO priority Nuxt.js + headless 100% page indexing, 0.8s load speed
Approach Timelines Deliverables
Vue widgets (2–5 components) 1–3 weeks Reactive elements on existing site
SPA for personal account 4–8 weeks Vue application + API on D7 controllers
Catalog on Vue + Bitrix API 4–10 weeks Filtering, cart, comparison without reloads
Nuxt.js + Bitrix headless 6–12 weeks SSR/SSG, full functionality, SEO

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.
Detailed technical considerations
  • Script loading order: Bitrix core scripts must not conflict with Vue. Use window.BX24 only after Vue app is mounted.
  • EventBus pattern: For cross-widget communication, prefer Pinia over $emit chains.
  • Error handling: Wrap REST calls in a global Axios interceptor that retries on 503 and logs to Bitrix admin log.

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.