Why a CRM Alone Is Not Enough for Manufacturing
A standard CRM implementation covers the sales pipeline well. For a manufacturing business, however, the deal does not end when the contract is signed — it ends when the goods are shipped, accepted, and paid for. That gap between "contract signed" and "shipment confirmed" is where most B2B manufacturers lose visibility.
The core challenge is that two systems run in parallel:
| System | What it owns |
|---|---|
| CRM (Bitrix24) | Leads, deals, contacts, communication history |
| ERP / Accounting (e.g., 1C) | Orders, production tasks, shipments, invoices, stock |
Without integration, sales managers work blind: they cannot see whether an order has entered production, whether components are in stock, or whether the shipment date has slipped. Clients get inconsistent answers, and internal escalations multiply.
The solution is not to replace the ERP — it is to connect Bitrix24 to it so that deal cards in CRM automatically reflect the real status from the production system.
Building the B2B Order Funnel in Bitrix24
Manufacturing deals typically follow a longer, multi-stage cycle that differs from a standard retail funnel. A practical funnel structure based on our project experience:
- Lead / Inquiry — inbound request, pre-qualification
- Commercial offer sent — pricing, lead time confirmed
- Awaiting supply confirmation — order entered in ERP, stock/production capacity checked
- Contract signed — legal documents executed, dealer agreement created in ERP if applicable
- In production / In fulfilment — ERP drives status
- Ready to ship — full production complete, awaiting logistics
- Shipped — transfer document (UPD/shipping note) issued
- Closed / Won — full shipment confirmed, payment received
In practice, two separate pipelines often make sense:
- A Sales pipeline for direct B2B orders
- A Dealer agreements pipeline for distributor/channel contracts
When a deal in the dealer pipeline reaches the "Contract signed" stage, a corresponding contract and supplementary agreement is automatically created in the ERP — no manual re-entry required.
ERP / Accounting System Integration: Architecture and Data Flow
The diagram below shows how order and document data flows between Bitrix24 and the ERP system. Understanding the direction of each data stream is critical: most manufacturing integrations treat the ERP as the master system for financial and legal data, while Bitrix24 owns the sales communication layer.
The following diagram illustrates the typical data flow: orders created in the ERP trigger deal creation in Bitrix24; status changes in the ERP automatically move deal cards through the pipeline stages; product catalogue, invoices, and shipping documents flow one-way from ERP to CRM; and counterparty (client) data is kept in sync bidirectionally with strict deduplication rules.
flowchart LR
ERP[ERP / Accounting\n1C or equivalent]
B24[Bitrix24 CRM]
MGR[Sales Manager]
CLIENT[Client / Dealer]
ERP -- "Order created → Deal created\n(stage: Awaiting supply)" --> B24
ERP -- "Status change → Stage move\nShipped amount, order number" --> B24
ERP -- "Product catalogue\none-way sync" --> B24
ERP -- "Invoices, contracts,\nshipping docs (PDF)" --> B24
B24 -- "New counterparty\n(on invoice/contract trigger)" --> ERP
MGR -- "Works in Bitrix24\n(pipeline, tasks, chat)" --> B24
CLIENT -- "Communication\nvia CRM" --> MGR
Key architectural principles from our implementations:
- Direction is mostly ERP → Bitrix24. The ERP is the source of truth for order numbers, shipped amounts, and financial documents. Bitrix24 reflects this data — it does not generate it.
- Sync interval: every 5 minutes for order status updates. Changes in the ERP are pushed to Bitrix24 practically in real time; the reverse direction uses a scheduled polling mechanism.
- Manual deal card moves in Bitrix24 do NOT change the ERP status. Only an ERP status change will move the deal card. This prevents salespeople from accidentally corrupting production records.
- Counterparty deduplication: companies are matched by tax ID (or equivalent national identifier), contacts by phone number. This prevents duplicate records from polluting the ERP.
- New counterparties flow to ERP only on a contract or invoice trigger — not on every new CRM contact. This protects the ERP from unqualified or test records.
Tracking Production and Shipment Status in Real Time
The deal card in Bitrix24 becomes the live dashboard for a B2B order. Fields populated automatically from the ERP typically include:
- Order number (assigned by ERP, written back to Bitrix24)
- Shipped amount — the ERP sums the value of shipped line items and pushes this figure to a dedicated CRM field
- Shipment status — when a transfer document (UPD or equivalent) is posted in the ERP, the linked deal moves to "Shipped"
- Payment date — when a bank receipt is posted in the ERP, the payment date field in the CRM deal card is populated automatically
The "Ready to close" condition — meaning the deal can be marked Won — equals full shipment confirmation from the ERP side. Sales managers cannot prematurely close deals; the ERP controls the gate.
For manufacturers working with product kits or assemblies, the integration can also surface available stock of finished assemblies. When components are consumed and the assembly is completed in the ERP, the available quantity appears in the Bitrix24 product card — giving the sales team accurate availability information without accessing the ERP directly.
Managing Delivery Timelines and Deadlines
Delivery deadline control is one of the most requested features from manufacturing directors. In Bitrix24, this is handled through a combination of:
- Custom date fields on the deal card (planned shipment date, confirmed delivery date, actual delivery date)
- Automated tasks and reminders triggered when a deal enters the production stage
- Smart processes that link the order to a production work order or a logistics record, each with its own deadline and responsible person
Based on our project experience, the following fields are typically synchronised from the ERP to support timeline tracking:
| Field | Source | Direction |
|---|---|---|
| Planned shipment date | ERP | ERP → Bitrix24 |
| Actual shipment date | ERP (on UPD posting) | ERP → Bitrix24 |
| Payment due date | ERP | ERP → Bitrix24 |
| Production start date | Bitrix24 (set by manager) | Bitrix24 → ERP |
| Responsible manager | Bitrix24 | Bitrix24 → ERP |
When the planned shipment date changes in the ERP, the corresponding Bitrix24 field updates automatically, and an automated notification can be sent to the account manager and the client via the CRM communication tools.
Product Catalogue and Stock Synchronisation
Managing product data across two systems is a common pain point. The standard approach:
- Product catalogue sync is one-way: ERP → Bitrix24. The ERP is the master for item names, SKUs, units of measure, and retail prices.
- Sales managers may create new product positions from within Bitrix24 (useful for custom or project-specific items), but editing existing items is only allowed in the ERP.
- Stock levels and warehouse reserves are optionally synced. Some companies deliberately choose not to sync stock to Bitrix24 to avoid overloading the CRM — availability checks remain in the ERP. Others sync stock every 10 minutes via scheduled POST requests.
- For companies working with complex assemblies or kits, the ERP sends the "available finished quantity" field rather than raw component stock — so managers see a ready-to-sell number, not a bill-of-materials breakdown.
Automating Documents: Invoices, Contracts, Shipping Papers
One of the clearest productivity wins in manufacturing CRM projects is eliminating manual document handoffs between sales and accounting. A properly configured integration handles:
Invoices (Sales orders): - The manager creates an invoice record inside the deal card in Bitrix24. While in "Draft" status, no ERP exchange occurs. - On moving the invoice to "Issued" status, the ERP creates the corresponding customer order and returns the official ERP-assigned number to the Bitrix24 card. - After partial or full payment, the invoice in Bitrix24 is locked for editing. All subsequent changes are made in the ERP and pushed back to CRM. - Sequential invoice numbering is generated exclusively by the ERP — Bitrix24 never assigns financial document numbers independently.
Contracts: - Contracts signed in the ERP are automatically pushed to the linked deal card in Bitrix24 as a PDF attachment, with contract number, date, and validity period. - For dealer agreements, the contract is created in the ERP when the Bitrix24 deal reaches "Contract signed" stage.
Shipping documents (UPD / delivery notes): - When a transfer document is posted in the ERP, the shipment status is pushed to the Bitrix24 deal, and the PDF of the document is attached to the deal card for easy access by the account manager.
What the integration targets (from real client briefs): - Sales analytics by SKU and product category - Revenue and margin reporting by period, client, and business unit - Automated document flow between sales and accounting teams
Implementation Roadmap: From Audit to Go-Live
Integrating Bitrix24 with an ERP for a manufacturing company is one of the more complex CRM project types — it touches two systems with different data models, different user bases, and different business logic. Rushing the technical build without aligning business logic first is the most common reason these projects fail.
A typical project follows this sequence:
- Business logic discussion — an analyst session to map the desired workflow: which system is master for which data, what triggers what, what constraints exist.
- Live walkthrough of current ERP usage — the client's team demonstrates how they currently work in both systems so the integration team can model the target state accurately.
- Technical specification (TS) sign-off — field mapping tables, sync directions, trigger conditions, and error handling rules are documented and agreed before any development starts.
- Technical audit of the ERP base — structure of reference books, document types, and readiness for API exchange are assessed. Required custom fields in the ERP are identified.
- Development — custom integration handler written on the ERP side; Bitrix24 webhooks, smart processes, and business process automations configured.
- Testing and demonstration — end-to-end scenarios tested with real data; adjustments made based on client feedback.
- Training — typically a two-hour group remote session, recorded for future onboarding.
- Go-live and handover
Typical project timelines: 6 weeks from contract signing for a mid-complexity integration (order sync, document flow, product catalogue). More complex scenarios involving multiple legal entities or production planning modules take longer and are scoped individually.
Off-the-shelf "universal" ERP–CRM connector modules are not recommended for manufacturing scenarios. They are built for all configurations simultaneously, which means they carry unresolved edge cases for any specific setup — and fixing bugs in a highly interconnected module is significantly harder than maintaining a purpose-built integration.