Configuring Electronic Document Exchange via Bitrix24

We often see companies drowning in manual document flow: managers create invoices in Excel, send PDFs by email, wait for scanned signatures, and reconcile data. This takes 30 minutes to several hours per document. Automation via EDO cuts that to 30 seconds — 40 times faster. Bitrix24 with EDO integration automates the process: documents go to counterparties in seconds, and signed copies return directly to CRM. We configure the entire pipeline turnkey — from operator selection to attaching incoming documents to deals. Implementation takes 2–3 business days given a CEP certificate and an operator contract.

How to choose an EDO operator for Bitrix24?

Bitrix24 supports integration with three main operators. The choice depends on which operator your counterparties use. If 70% of partners are on Diadoc — connect to Diadoc. Roaming between operators works but adds 2–4 hours for initial setup.

Connecting to Bitrix24

Integration is done via apps from the Bitrix24 Marketplace (see documentation). For Diadoc — "Kontur.Diadoc for Bitrix24", for SBIS — a standard connector. Connection order:

1. Install the app from Marketplace → Integrations.
2. Authorize with the operator account (requires CEP certificate).
3. Configure organization matching — your legal entity must match the EDO box by TIN/KPP.
4. Specify the default box if there are multiple departments.

After connection, the CRM company card will get an EDO block with exchange status.

Automatic sending from CRM

The main scenario is sending an invoice or UPD when a deal moves to a certain stage. Implemented via robots or business processes.

The robot "Send document via EDO" triggers on stage change. Settings specify document type, template, signatory. Data is taken from the 'Invoice' entity (crm.invoice) or smart process. Items, amounts, details are pulled automatically. If the deal has multiple invoices, the last unsent one is processed.

Why automatic attachment to deals saves time?

Incoming documents land in the operator's app section. The system searches CRM companies by the sender's TIN. If an open deal is found, the document is attached to it. If not, a new deal is created in the specified funnel. The responsible person receives a notification in the feed for signing. Signing is done via the browser CryptoPro plugin or the operator's app. According to statistics, over 90% of documents are signed within an hour after sending.

Roaming between operators

If the counterparty uses a different operator, documents are transferred via roaming. Setup:

• In your personal account, send a roaming invitation by the counterparty's TIN.
• Wait for confirmation (usually automatic, from 10 minutes to 24 hours).
• After setup, exchange works as within one operator.

Limitations: not all document types are supported (formalized — yes, non-formalized — depends on the operator pair).

Typical problems during setup

Mismatched details. The TIN/KPP in Bitrix24 and the EDO box must match character by character. An extra space will break matching. Errors in details occur in about 15% of cases during manual entry; automation eliminates this.

CEP certificate. The CryptoPro CSP plugin is needed on each signatory's computer. In Chrome and Edge, the CryptoPro Extension is required.

Duplicate documents. If a robot is configured for multiple stages without a "already sent" check, the document will be sent again. Add a condition checking the 'EDO Status' field.

API timeouts. With a high flow (50+ documents per hour), delays can occur. Use a queue with retry attempts via a business process.

What does integration with 1C give?

After signing, documents sync with 1C via CommerceML. This eliminates manual entry: postings are generated automatically. The accounting department sees up-to-date data without delays. Time savings per operation — up to 3 hours a day for an accountant.

What's included in EDO setup

When ordering setup, you get:

• Selection of the optimal operator and connection to its API.
• Installation and configuration of the connector app.
• Development of document templates and robots for automatic sending.
• Configuration of attaching incoming documents to deals.
• Testing the entire cycle with one counterparty.
• Employee training (1 hour online).
• Written documentation of scenarios.
• Free consultation on further optimization.

Case study: logistics company

On a project for a logistics company handling 500 invoices per month, we reduced document processing time from 45 minutes to under 2 minutes per document. We automated invoice creation from CRM data, set up automatic sending upon deal stage change, and configured roaming for counterparties on different operators. The result: a 96% reduction in processing time and zero manual data entry errors.

Conclusion

A configured EDO via Bitrix24 closes the chain "deal → invoice → sending → signing → closure." The manager never leaves CRM; accounting receives signed documents in the accounting system. Processing time reduction — up to 85%, and error costs drop thanks to automatic checks. Order EDO setup — we'll help integrate your document workflow with Bitrix24. Get a consultation on implementation.

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.