Automating Document Exchange Between Bitrix24 and EDMS

Managers lose hours daily manually transferring documents from CRM to EDMS. According to our data, up to 75% of approval time is spent on file forwarding and status updates. We automate this exchange by integrating Bitrix24 with an electronic document management system. Result: documents are created and approved without a single copy-paste, the deal cycle is cut by 80%. In practice: for a company with 50 deals per month, the integration reduced the approval cycle from 3 days to 4 hours — saving 1.2 million rubles annually. Another client with 200 monthly deals saved over 4 million rubles per year using our Bitrix24 EDMS integration solution. A document is generated in the deal card, sent to the EDMS, goes through the route, and the status returns — all automatically. Our expertise includes over 10 integrations with Bitrix24 REST API and various EDMS (REST API). Typical issues: broken routes after CRM updates, lost statuses, duplicate documents. Integration eliminates these risks. With 10+ years of experience in CRM-EDMS integration and guaranteed data integrity, we provide a reliable solution. Request an engineer consultation for analysis of your process.

What We Integrate With

How the Integration of Bitrix24 with Electronic Document Management Systems Is Done

Integration Points in Bitrix24

• crm.documentgenerator.* — document generation based on templates.
• Bitrix24.Drive — uploading and downloading signed files.
• Business processes — automatic webhook trigger on stage change.

Step-by-step data exchange setup:

1. Create a document template in the Bitrix24 generator, populating deal fields.
2. Set up a business process: when a deal moves to the "Pending approval" stage, send a webhook with document data to the middleware.
3. The middleware receives the request and sends the document to the EDMS via its API.
4. The EDMS starts the approval route and sends a webhook back upon completion.
5. The middleware updates the deal stage via crm.deal.update and uploads the signed file to the Drive.

This process cuts processing time by 80% compared to manual entry — 5 times faster than traditional methods. The official Bizproc documentation describes all available actions.

Why Choose Middleware for Bitrix24–EDMS Integration

A simple integration (one EDMS, linear route) can work without middleware. But middleware is 3 times more reliable in error handling — it unwinds and retries requests, logs everything, and prevents data loss. The cost of manual data entry is about 40,000 rubles per month for an average sales department. The integration pays for itself within half a year.

Architecture with middleware:

Bitrix24 -> Middleware -> EDMS

Middleware is a separate service (Laravel or Node.js) that stores document_id↔deal_id mapping, processes queues via Redis/RabbitMQ, and logs every step.

Deep-dive: Approval Routes and Status Mapping — Integration Development

Approval is the central process. Routes are of three types: sequential, parallel, and conditional. In sequential, each next approver gets the document after the previous approves. In parallel, the document goes to several simultaneously, approval from all is required. Conditional routes depend on the contract amount or counterparty type.

Status mapping:

Webhook from EDMS:

POST /api/sed-webhook
{
    "document_id": "DOC-4521",
    "new_status": "approved",
    "approved_by": "[email protected]",
    "timestamp": "March 12, 11:45",
    "comments": "No comments",
    "signed_file_url": "https://sed.company.ru/files/DOC-4521-signed.pdf"
}

Conflicts and Locks

Scenario: a manager edits the contract while the document is being approved. Three strategies:

• Lock — editing is forbidden (check UF field). The most reliable method.
• Versioning — each change creates a new version, approval restarts.
• Notification — warn the manager.

In practice, locking eliminates discrepancies.

Document Metadata and Legal Storage

The EDMS stores the document with metadata: number, date, counterparty, amount. Mapping deal fields:

Signed copies are returned to Bitrix24, but the master copy lives in the EDMS.

Widget in the Deal Card

We embed a widget via REST placement CRM_DEAL_DETAIL_TAB: approval status, route, history. The manager sees everything in one window.

What the Work Includes

• Configuration of approval routes in the EDMS
• Setup of webhook notifications between systems
• Middleware development (queues, logging, status mapping)
• Widget in the deal card for tracking approval
• Integration with Bitrix24 document generator
• Documentation on architecture and settings
• User training (2 hours)
• 30 days of post-launch support

Stages and Timelines

Result

CRM–EDMS integration eliminates manual work at the systems' boundary. The manager works in Bitrix24 — generates a document, moves the deal. The lawyer and managers approve in the EDMS. The document goes through the route automatically, the status returns to the CRM, and the signed version is saved on the Drive. Contact us for a project evaluation — get an engineer consultation within a day. Fill out the form on the website — we'll select the optimal architecture in 1 day.

Why is 1C-Bitrix the flagship of e-commerce?

A faceted index on a catalog of 200,000 SKUs is not built — bitrix:catalog.smart.filter takes 4 seconds instead of 200 ms, and the customer leaves. Our online store development on 1C-Bitrix eliminates such scenarios: from infoblock architecture and price types to cluster balancing under peak loads. With over 12 years of experience and 200+ completed e-commerce projects, we have solved every performance bottleneck.

Two-way synchronization with 1C via CommerceML — catalog, prices, balances, orders, and statuses. Configured from the admin panel via the catalog module -> 'Exchange with 1C'. Export to marketplaces via YML feeds (catalog.export) for Yandex.Market, Google Shopping, Ozon, Wildberries. According to Wikipedia, 1C-Bitrix is used by more than 70,000 commercial sites in Russia and the CIS (https://en.wikipedia.org/wiki/1C-Bitrix). Contact us to evaluate your current architecture.

How do we solve key performance problems?

bitrix:catalog.smart.filter without faceted index generates queries that bring down MySQL. Solution: build b_catalog_iblock_index — response time drops from 4 seconds to 100–200 ms. For SEO filters, we use catalog.seo.filter — indexable filter intersection pages with unique meta tags.

Composite cache (bitrix:main.composite) speeds up page loading by 3–5 times compared to regular. Goal — product card TTFB < 200 ms. For sessions we use Redis (SESSION_SAVE_HANDLER = redis in .settings.php). Lazy load images, CDN for static, SQL optimization (especially JOINs on b_iblock_element_property). As noted in the official Bitrix documentation, composite cache delivers a page from HTML, bypassing PHP execution and database requests, giving a speed advantage of up to 5x.

Why is caching critical for an online store?

Each second of page load delay reduces conversion by an average of 7%. At TTFB > 400 ms, 32% of users leave the site. Composite cache delivers a page from HTML, bypassing PHP execution and database requests — this gives a speed advantage of up to 5 times. For product cards with frequent price and stock changes, we use tagged caching: invalidation occurs only for affected entities. In practice, we have reduced TTFB from 1.2 seconds to 180 ms. Time savings on catalog loading — up to 60%.

Store types and their features

Integrations: payment systems, delivery, CRM, marketplaces

Payment systems. Handlers in sale.handlers: YooKassa, CloudPayments, Tinkoff, Sberbank, Apple Pay, Google Pay, installment. Callback sale.payment.notify for status confirmation. Delivery. Handlers sale.delivery for CDEK, Boxberry, Russian Post, DPD — real-time cost calculation via API, tracking. Warehouse management. Reservation (RESERVED = Y in b_sale_basket), automatic write-off upon shipment, notifications when stock falls below threshold, pre-order for goods in transit. CRM. Bitrix24 or amoCRM — orders from b_sale_order are sent automatically, client base is synchronized. Triggers: abandoned cart, review request, reactivation. Marketplaces. Export via YML to Ozon, Wildberries, Yandex.Market. Orders flow into a single system. Analytics and marketing. GA4, Yandex.Metrica, email newsletters (Unisender, SendPulse). Logistics. MyWarehouse, Antor — labels, picking lists.

Migration from other CMS

Migration from OpenCart, WooCommerce, Shopify, MODX: transfer of catalog (elements, properties, sections, images, SEO-URLs), migration of client base (b_user) and order history (b_sale_order), 301 redirects via urlrewrite.php. Parallel operation during the transition period — old site sells, new one is accepted. Team experience — 50+ migration projects.

What is included in the work (deliverables)

Stages and timelines

Average project duration — 2 to 4 months:

1. Analytics (1–2 weeks) — business requirements, catalog structure, integrations, technical specification
2. Design (2–3 weeks) — prototypes, design system, layouts
3. Development (4–8 weeks) — components, templates, integrations, content
4. Testing (1–2 weeks) — functional, load, acceptance
5. Launch (2–3 days) — deployment, monitoring, operational support

Budget range: from $10,000 for a basic store to $60,000+ for a complex marketplace with multiple integrations. Clients typically see a 20–30% increase in conversion after optimization. Contact us for a precise estimate — we tailor the solution to your specific catalog size and business logic.

Loyalty program and conversion

Bonus system: points for purchases, reviews, recommendations. Accrual rules by categories, points payment limit, expiration period — all in personal account. VIP levels (bronze, silver, gold, platinum) with increased cashback and free shipping. Recommendations 'You may also like', 'Complete your purchase' — built-in Bitrix tools + RetailRocket or Mindbox. Triggers: birthday discount, promo code for return, interest chain. Personalization via catalog.recommended.products and catalog.viewed.products. A/B testing of two card variants on real traffic. Enhanced E-commerce in GA4 and Yandex.Metrica — full path from click to return visit.

Request a free technical audit of your current store. Our engineers will identify performance bottlenecks and migration risks. Order turnkey online store development — get a ready solution with warranty and support.