CRM for manufacturing: what the system must handle when a deal becomes a shop-floor order

A CRM for manufacturing is a sales system in which a deal, once paid, continues as a production order with a specification and a lead time, and the sales manager can follow that order through the shop floor. Beyond the pipeline and customer history, it does four things a typical CRM doesn't. It calculates the cost price and lead time in a quote based on production standards and plant load, and passes the order to 1C, the accounting and ERP platform most Russian companies run on, or to an ERP system, with lines from the same item master. The manager sees the order status from production records, and a customer's repeat orders are managed within that customer's history. Until these links exist, a CRM at a plant remains the sales team's address book: the manager gets the price, lead time and status from the process engineer and the foreman over the phone.

Below we look at where a standard CRM breaks down in manufacturing and B2B sales. How a manufacturing deal differs from a trading deal, and what happens to it after payment. How to calculate price and lead time in a quote without pulling in the process engineer, and how a manager can see an order's status on the shop floor. How to connect the CRM to 1C and ERP, and which system owns which data. How to manage the long cycle of repeat orders with one customer, and which signs show the system isn't coping. At the end: what to prepare before starting, and why an off-the-shelf product covers only part of the job here. Choosing a CRM in general and how the production stack is structured are covered separately, in the articles how to choose a CRM and ERP for manufacturing; this one is about where sales meets the shop floor.

How is a CRM for manufacturing different from a regular one?

In short: a regular CRM tracks a deal until payment, a manufacturing CRM tracks it until shipment, and along the way it needs data the sales team doesn't have: the specification, standards, shop-floor load and the actual order status.

A typical pipeline looks like this: inquiry, qualification, quote, invoice, payment. For trading, that's enough: the goods are in the warehouse, the price is on the price list, the lead time is the delivery time. In manufacturing, at every step the question leaves the sales department. What exactly the customer is ordering is defined by the specification, sometimes a new one for this order. The price depends on materials and operations, the lead time on what the shop floor is busy with right now.

After payment comes the longest part: release, material purchasing, manufacturing, quality control, shipment, documents. Throughout, the customer calls the sales manager, because that's who they made the deal with. If the CRM ends at payment, the manager answers the customer based on what the shop manager told them.

The gap between sales and production shows up in government statistics too. According to the collection “Digital Economy Indicators: 2025” by HSE University's Institute for Statistical Studies and Economics of Knowledge (ISSEK), the Ministry of Digital Development and Rosstat (table 12.6, 2023 data), in the “Manufacturing” row ERP systems are used by 38.2% of organizations and CRM systems by 27.2%. In wholesale and retail trade the picture is different: CRM at 37.8% of organizations, ERP at 37.6%. Software for managing sales of goods, works and services is used by 39.7% of manufacturing organizations, more than CRM. Judging by the difference in figures, some plants run sales in separate software rather than in a CRM.

At a plant, accounting and production get automated before sales, and the CRM, if there is one, often lives apart from the accounting stack. Manufacturing companies are nonetheless a noticeable share of CRM users. In a survey by J'son & Partners Consulting, conducted together with Bitrix24, a Russian CRM and collaboration suite, and published in the vendor's journal on August 19, 2026 (1,000 companies, November 2025 to January 2026), manufacturing made up 13% of the sample, the second segment after trade at 26%.

What happens to a deal after payment?

In short: it becomes a production order and gets two owners: the sales manager, who answers to the customer, and production, which is responsible for making the product.

The order's path after payment usually runs like this: specification or drawing approval, release, material supply, manufacturing operation by operation, quality control, packing, shipment, closing documents. At every handoff, information can get lost. The specification was approved by email, but the shop floor got a spreadsheet from the process engineer's folder. The customer changed the coating after release, and only the manager knows. Shipment goes in two batches, but the invoice was issued as one.

The specification version causes the most trouble. A change that arrives before release costs some correspondence. A change in the middle of manufacturing costs material, a changeover and a shifted lead time, and the customer has to be told before shipment. So a CRM in manufacturing does the following:

• Stores the approved version of the specification with the date, author and method of approval. A “but we agreed on something else” dispute is settled by the order record.
• Passes the order to accounting in one operation. Lines are taken from the 1C or ERP item master, and the order goes into production without being re-keyed by hand.
• Accepts changes as a new version. You can see at what stage of manufacturing the change came in, who approved it, and how the price and lead time changed.
• Splits the order into shipments and payments. Prepayment, payment on completion, partial shipment and post-payment are tied to order stages.
• Stores closing documents. Acceptance certificates, waybills, certificates and product passports sit with the order, and nobody has to dig through email for them a year later.

The contract, specification and change amendments often go through a separate approval route; how to set it up is covered in the article “Contract document workflow”.

How do you calculate price and lead time in a quote without pulling in the process engineer?

In short: the price is built from the consumption rates and operations already in 1C or the ERP, and the lead time from material availability and workcenter load. The process engineer is needed where the product is new.

Manufacturing inquiries usually fall into three types, and the calculation works differently for each:

1. A serial product from the catalog. The price is calculated from the standard cost plus markup, the lead time from the standard cycle and the current queue. The system does the calculation; the manager checks it and sends it.
2. A variant of a standard product. A different size, material, coating or configuration. The parameters go into a configurator, rules assemble the specification and routing from them, and the price is recalculated automatically. The process engineer describes the rules once and is no longer involved in each quote.
3. A new product. The inquiry goes to the design or process engineer as a task inside the CRM with a response deadline. The manager and the customer can see that the quote is waiting for a calculation and by what date.

The cost price in the calculation is made up of materials at consumption rates and the latest purchase prices, operations at standard hours and workcenter rates, overhead and markup. The minimum margin is set by a rule: a discount below the threshold goes to a manager for approval, and the “send quote” button doesn't work until then. Whether the sales manager sees the cost price itself or only the final price and margin is the owner's decision; the system should support both.

The lead time is calculated from the latest of the constraints. A hypothetical example: the welding workcenter has a queue of six working shifts, the order needs two more, and the sheet metal arrives in four days. The manufacturing lead time is set by the welding queue, and painting, inspection and delivery are added to it. This is an estimate based on aggregate workcenter load. A machine-level schedule with changeovers is built by planning in the ERP or an APS, and how that differs from the accounting stack is covered in the article on ERP for manufacturing.

The quote records the calculation date and the version of the rates and prices used. Prices for metal and purchased components change, and when the customer asks again six months later, you can see exactly what went up. The quote itself is generated from system data using a template, without manually copying tables into a document; the Auto Documents solution from our catalog works the same way.

How can a sales manager see an order's status on the shop floor?

In short: the status comes from the system where production records progress (an ERP, a MES or a simple foreman's terminal), and the CRM shows it to the manager and the customer without a call to the shop floor.

The typical picture without this link: the customer calls the manager, the manager calls the shop manager, who walks over to the foreman and an hour later answers “in a few days.” Every round like this takes time from three people and gives the customer nothing but an approximate date.

The source of the status depends on what the plant has. If production orders are kept in the ERP, the CRM reads the stages from it: released, materials issued, operation completed, inspection passed, received into the warehouse. If there is a MES, the status arrives almost in real time. If there is neither, the foreman marks stages with a button in a bot or on a tablet at the workcenter. How such bots for staff who work away from a desk are built is covered in the article “Chatbots for business”.

The third option is more common than presentations suggest. APKIT's Council for Digital Technology Development in Industry (APKIT is a Russian IT industry association), with the support of the Ministry of Industry and Trade, surveyed 39 machine tool and tooling manufacturers between November 2025 and February 2026. According to the results published on May 4, 2026, 10% of the surveyed enterprises use real-time solutions to manage core production, and 41% rely mainly on manual work with minimal automation. The sample is small and industry-specific, so it can't be extrapolated to all of industry. A broader view comes from the same table 12.6 of the HSE collection: software for managing automated production and technological processes is used by 28.9% of manufacturing organizations. Where there is neither such software nor production orders in the ERP, the status starts with a person's check-in, and it has to be designed to take seconds.

The manager and the customer don't need every operation in the routing. Five or six clear statuses are enough: accepted, materials secured, in production, ready, shipped. Deviations matter more than statuses. If material didn't arrive by the release date or an operation is behind plan, the manager gets an alert and calls the customer first, before the customer calls. In our project for a wholesale and manufacturing company, customers see their contract prices, order statuses and documents in a customer portal.

How do you connect a CRM to 1C and ERP?

In short: each type of data has one owning system, and the others read it. Items, standards, material prices, stock, production orders and money live in 1C or the ERP; customers, contacts, deals and correspondence live in the CRM.

Most integration problems arise where the same data is edited in two places. A manager created a customer in the CRM, an accountant created one in 1C, and a month later the customer has two records with different details. So before talking about the integration technology, you agree on owners:

Technically, 1C has built-in integration mechanisms: the 1C:Enterprise platform automatically generates a REST interface via the OData protocol for the entire application, and for non-standard scenarios there are HTTP services. The integration channel itself is the smaller part of the work. More time goes into the rules: what to do if an item exists in the CRM but was deleted in 1C; how to handle an order if the accounting system is unavailable; who resolves the conflict when details in the two systems diverge. Ways of connecting systems are covered in detail in our piece on system integration.

For the Russian CRM market, the link to 1C is the main scenario. In the same J'son & Partners survey, one company in five, 20%, runs sales in 1C:CRM, that is, on the same platform as accounting. Bitrix24 is used by 49% of companies and amoCRM, another Russian CRM, by 9%; the source caveat is essential: the survey was conducted together with Bitrix24, and the figures show prevalence among respondents, not market share. A CRM on the 1C platform removes part of the integration, because it shares reference data with accounting. Quote calculation rules, production statuses and a specific plant's exceptions still have to be configured separately.

At many plants, the accounting stack is itself being rebuilt right now. According to an Interfax report of February 28, 2026, the government updated the strategic direction for the digital transformation of industry (Order No. 378-r of February 26, 2026). By 2030, at least 80% of manufacturing enterprises must switch to domestic software in their systems for core production and management processes. If a plant is changing its accounting system, it makes sense to design the CRM integration for the new stack from the start, so it doesn't have to be redone a year later. How to avoid losing the customer base and creating duplicates in the process is covered in the article “Customer database in CRM”.

How do you manage repeat orders and a long cycle with one customer?

In short: a manufacturer's B2B customer orders for years, and the CRM keeps their history as a chain of contracts, specifications and orders. A new order is created from a previous one, and the system itself flags when a customer has missed their usual interval.

The first deal with an industrial customer is rarely quick. Supplier qualification, samples, testing, a tender or request for quotation, a framework agreement: each stage takes weeks, and different people on the customer's side are involved: the buyer, the process engineer, the chief engineer, accounting. The pipeline for such a deal is built around these stages, and the customer record lists all participants with their roles. If only the manager knows all this, the company loses both the contacts and the agreements when that manager leaves.

A repeat order is almost always a variation of a previous one. The customer record holds:

• The contract and contract prices. A quote for a repeat order is calculated from them without searching through email.
• Order history with specifications. A new order is created as a copy of a previous one and recalculated at current rates and prices, and the difference from the previous price is visible right away.
• Claims and their causes. Tied to the order and batch, so at the next release the process engineer can see what has gone wrong before.
• Order rhythm. If a customer orders once a quarter and misses the date, the manager gets a task to get in touch. That's cheaper than finding out six months later that the customer has gone to a competitor.

For framework agreements, the CRM tracks limits and call-off orders within them: how much has been drawn, how much is left, which shipments are planned. From such a database, the owner can see which customers keep the plant loaded and whose order frequency is dropping. How to bring these figures onto one screen is covered in the article “The owner's dashboard”.

How do you check that the CRM handles a manufacturing deal?

In short: with six indicators, each calculated by querying the data, without surveying the managers.

Each plant sets the threshold for each row itself: the share of new products in orders differs from plant to plant, and the normal share of manual calculations changes with it. The first two rows usually show where money is being lost right now. Manual calculation eats the process engineer's time, and a missed lead time costs customer trust and the next order.

Where do you start?

In short: with a description of one typical order from inquiry to shipment. It shows what data the CRM needs to get from accounting and production, and most of the preparation can be done by the plant itself.

1. A documented order path. The stages from inquiry to closing documents, who is responsible at each one, where decisions on price, lead time and changes are made. Describe the real path, with all the workarounds through email and messengers.
2. A clean item master. One item, one record; specifications with versions. If the item master in accounting is messy, a CRM connected to it will inherit the duplicates. Why manufacturing projects most often stumble right here is covered in the article on ERP for manufacturing.
3. Pricing rules. Which standards are current, where material prices and workcenter rates come from, what the minimum margin is, who approves a discount beyond the threshold. The business makes the decision; the developer puts it into the system.
4. Access to the accounting system. A technical user in 1C or the ERP, read and write permissions, a test database for checking the integration. Without a test database, the very first integration error lands in the live accounting system.
5. The status source. Where production records progress: in ERP production orders, in a MES, or nowhere yet. In the last case, before starting, you decide who will mark the stages and with what.
6. A permissions matrix. Who sees the cost price, who sees the margin, who sees other customers' contract prices, what the customer sees in the portal. A list of roles is easier to draw up before development than to fix afterwards.
7. An owner after launch, and support. An employee responsible for the reference data and pricing rules, and an agreement on system support. Standards, material prices and product composition change, and without an owner the quote calculation will start lying within six months.

The first three items require no development budget and on their own deliver a noticeable part of the result. They also explain why the cost of a CRM for manufacturing can't be quoted over the phone: it is determined by the number of integrations, the depth of quote calculation and the number of exceptions in your process. If a CRM has already been bought and hasn't taken hold, the causes more often lie in the process than in the software; they are covered in the article “Why CRM doesn't take hold”.

Off-the-shelf or a system built around your process?

In short: an off-the-shelf CRM covers the pipeline and communications. Quote calculation from standards, passing orders to accounting and statuses from the shop floor have to be built around a specific plant's reference data, permissions and exceptions.

An off-the-shelf CRM handles the common part well: inquiries from different channels, calls and correspondence, managers' tasks, the pipeline and its reporting. At this stage there is almost no difference between a plant and a trading company, and there's no reason to pay for developing what already exists in a ready-made product.

They diverge on the production side. Every plant has its own procedures, reference data, access rights and exceptions. One calculates price from standard cost, another from comparable past orders, a third through a variant configurator. One shows the manager the cost price, another only the margin. At one plant a specification change after release is approved by the process engineer, at another by the production manager. An off-the-shelf product handles all this according to its own model, and the difference is filled in either by customizations on top of someone else's architecture, which have to be re-tested after every update, or by people manually. We've covered the choice between a ready-made product and a system built around your process separately: custom system or off-the-shelf.

A hybrid often turns out to be the workable option. Accounting stays in 1C, while the area that determines money and lead times is built separately and connected to accounting through data exchange. That's how our project for a wholesale and manufacturing company was done. Orders from email, messengers and the customer portal are merged into a single queue, reservations are made against actual stock, and order shortfalls turn into purchase and production requests. Items, stock, shipments and payments are synchronized with 1C in both directions. Order processing went from hours to minutes.

At INCUBE AI we do both. Standard tasks are covered by ready-made solutions from our catalog, each adapted to the client's process. When sales need to be linked to production, we build it as custom development: quote calculation from your standards, passing orders to accounting, statuses from the shop floor, a customer portal and integration with 1C or the ERP. We work under contract, data stays in Russia, and we support the system after handover. If your managers still get prices and lead times from the process engineer, tell us about your task: we'll walk through one of your orders from inquiry to shipment and use it to estimate the scope of work.

Sources and links

• HSE University ISSEK, Ministry of Digital Development of Russia, Rosstat. “Digital Economy Indicators: 2025”, statistical collection — table 12.6 “Use of specialized software in organizations' business processes by type of economic activity: 2023”, as a percentage of the total number of organizations. “Manufacturing” row: ERP systems 38.2%, CRM systems 27.2%, software for managing sales of goods, works and services 39.7%, software for managing automated production and technological processes 28.9%. “Wholesale and retail trade” row: CRM 37.8%, ERP 37.6%
• J'son & Partners Consulting: how companies choose a CRM in 2026, Bitrix24 journal, August 19, 2026 — survey of 1,000 companies, conducted together with Bitrix24, November 2025 to January 2026: manufacturing 13% of the sample, trade 26%; prevalence among respondents: Bitrix24 49%, 1C:CRM 20%, amoCRM 9%
• APKIT, May 4, 2026. Study of IT in machine tool and tooling manufacturing — survey of 39 enterprises from November 2025 to February 2026 with the support of the Ministry of Industry and Trade: real-time solutions for managing core production at 10%, mainly manual work at 41%
• Interfax, February 28, 2026 — update of the strategic direction for the digital transformation of industry: by 2030, at least 80% of manufacturing enterprises switch to domestic software in systems for core production and management processes, 95% in companies with more than 50% state ownership
• Order of the Government of the Russian Federation No. 378-r of February 26, 2026, Garant — amendments to government orders No. 1512-r (2020) and No. 3113-r (2023)
• REST interface and HTTP services, 1C:Enterprise 8 platform website — built-in mechanisms for exchanging data with external systems, an automatic REST interface via the OData protocol