1C:CRM and Customer Processes

1C:CRM is useful when the customer base is tied to real sales, warehouse, accounting, communications, and analytics. The system is available in several editions: a built-in CRM module in 1C:UNF, PRO for mid-sized businesses, CORP, and a module for 1C:ERP. The edition should be chosen before launch, because it determines the available integrations and the depth of custom development. The second launch requirement is customer data quality: duplicate records and missing fields will not be fixed by integration, but replicated across all connected systems.

We configure customer processes from inquiry intake through deal closure and repeat sales. We rely on standard 1C:CRM mechanisms to avoid custom code that breaks during updates.

• Sales funnels: stages aligned to the deal cycle, standard and manual deals, conversion tracking, and loss reasons by stage.
• Contact center: requests from the website, telephony, email, and messengers flow into a single queue with the source and request time recorded.
• Telephony and messengers: IP PBX integration, call recordings in the customer card, and WhatsApp and Telegram correspondence in the interaction history.
• Cards and discipline: required fields, responsible managers, and a customer data completeness indicator.
• Accounting integrations: invoices and payments from 1C:Accounting, stock and order statuses from UT/ERP, and management reporting.

CRM should not live separately from accounting: the manager needs current stock, prices, order statuses, payments, and interaction history in one card. For integrations, we use standard 1C platform mechanisms: exchange plans, EnterpriseData, OData, and web services. With three or more systems, we move routing to an integration bus (ESB) instead of direct point-to-point connections. This way, one failed integration does not drag down the others, and errors appear in monitoring before the customer notices them.

• Website and forms -> CRM: leads with the source and inquiry details.
• CRM <-> 1C:Accounting: invoicing and payment registration.
• CRM <-> UT/ERP: stock, prices, reservations, order statuses, and accounts receivable.
• CRM -> BI: conversion, manager workload, and loss reasons without manual exports.

Sales and service work from a single customer view, while management sees conversion, workload, and problem stages without manual exports. An order from CRM is automatically sent to accounting for invoicing and to the warehouse for picking, with no retyping of data between systems.

• A single source of truth for the customer: details, communication history, documents, and payments.
• Less manual entry and fewer duplicates: data comes from integrations, not from Excel.
• Transparent funnel: deals by stage, conversion, loss reasons, and revenue forecast.
• The architecture is scalable: a new channel connects to existing exchanges, not a new point-to-point link.