Setting Up Bitrix24 for Manufacturing: Where Accounting Breaks Down
The typical picture in manufacturing looks like this: orders live in spreadsheets, the shop floor learns about specification changes by phone, and cost is assembled manually by month-end.
Between the deal in CRM and actual output there remains a gap — deadlines, material batches, and hours by work area are lost in it.
The reason is not people, but that order accounting in Bitrix24 is kept only on the sales side. The shop floor works in its own logs and files, procurement — in email, and every edit requires manual retelling along the chain.
The more orders in progress at the same time, the more expensive the discrepancy: the part has already been started, while the system still shows the old version.
Setting up Bitrix24 for manufacturing closes this gap. An order stops being a row in a table and becomes an object with a route, stages, material composition, and owners by work area.
A status change, deadline shift, or specification edit is immediately visible to those working with the order now — without calls and clarifications.
Next comes automation of production accounting: actual material consumption and labor costs are recorded as work progresses, rather than reconstructed from memory at the end of the month.
Cost per order is assembled gradually and remains accurate, while deviation from plan is visible while the outcome can still be influenced.
Bitrix24 in manufacturing in this scheme works as a single circuit: from customer request to order closure, without parallel spreadsheets and manual reconciliation.
What a Configured Circuit Delivers: Deadlines, Data, Discipline
A configured circuit is not a set of enabled modules, but coordinated routes, reference data, and access rights.
The measurable effect of implementation is visible at three points: how long order approval takes, how many times the same data is entered manually, and how many orders come back for rework.
Order Approval Without Downtime
An order that travels by email and messengers waits in line for a specific person and waits until they are free. A route in Bitrix24 defines the stage, owner, and deadline at each step, and escalation triggers on its own — approval stops depending on who is available today.
Transparency of Order Statuses
The status in the card is updated by the person who physically completed the stage, not by someone who later remembered it. The manager sees work area load and bottlenecks without calling around, and the sales manager answers the client based on fact, not assumption.
Unified Item Reference
A single reference for sales, warehouse, and production removes discrepancies between systems: an item is created once and then used in all documents. A whole class of manual transfer errors disappears — wrong item picking, duplicated items, orders for the wrong material.
Manual Entry Is Reduced to a Single Touch
Data entered at the input then travels along the route on its own: a request turns into an order, an order into a task, a task into a shipment.
The share of orders without rework grows precisely because of this, and the work area summary is assembled from the system, not from spreadsheets.
Deployment Options: Cloud, Local Server, Hybrid
Deploying the circuit is an answer to two questions: where the data physically resides and how quickly the workplace on the shop floor is updated.
The cloud version of Bitrix24 is up in a matter of days and requires no infrastructure of its own, but part of the production data goes outside the company perimeter. A local Bitrix24 server removes this limitation and gives full control over exports from 1C.
| Option | When It Fits | Limitations |
|---|---|---|
| Bitrix24 cloud version | Distributed sites, fast start, exchange with contractors | Data on the service provider's side, dependence on the communication channel |
| Bitrix24 local server | Confidential product composition, data placement requirements | Own infrastructure, backup, scheduled updates |
| Hybrid implementation scheme | Document exchange outward and a closed circuit inside | Harder to connect the parts, synchronization control required |
A hybrid implementation scheme covers the most common case: the commercial block and correspondence with counterparties live in the cloud, while design documentation, cost, and exports from 1C remain inside.
Data placement requirements are usually formulated by the security service — they determine which reference data and registers must not leave the perimeter.
Total cost of ownership consists of infrastructure, updates, and support: in the cloud it is more even, on your own server it depends on whether the company has its own operations. We test the chosen option on a test circuit: exchange with 1C, roles, failure scenarios. Then the decision rests on measurements, not assumptions.
Work Sequence: From Process Review to Operation
We start not with licenses, but with the shop floor: walking the work areas, interviews with the foreman, process engineer, and procurement, exporting current registers from the accounting circuit.
The goal of production process assessment is not to describe "how it should be," but to capture where the flow breaks now: an order is manually rewritten into a specification, a route sheet is approved in correspondence, and defects surface only at the finished goods warehouse.
Then, from these breaks, we assemble a scheme of processes and roles: which objects live in Bitrix24, who sees them, which status the owner changes, and what goes back into accounting.
We approve the scheme before setup — an edit on paper costs hours, an edit in a deployed system costs weeks.
Stages
- Work area assessment: walkthrough, role-based interviews, reconciliation of regulations with actual documents. Output — a list of breaks with recurrence frequency and the cost of each.
- Scheme design: order status map from request to shipment, reference data, rights matrix, exchange points with the accounting circuit.
- Setup: pipelines, automation rules, document templates, notifications, exports, and print forms for the company's actual forms.
- Linking with accounting: items, specifications, orders, warehouse. We determine the exchange direction and conflict resolution rules for data discrepancies.
- Pilot operation on live orders: we run the flow end to end, reconcile amounts and statuses, and catch bottlenecks before the entire shift starts working in the system.
- Training owners and handing the system over to operation: exchange regulations, access rights, backup, change log, and modification procedure.
Handover Package: Roles, Regulations, Instructions
System handover is not issued access credentials or a list of logins.
The customer retains a set of artifacts that lets work continue without us: a new employee starts an operation according to the instructions, and editing one work area does not require reassembling the entire circuit. We fix the composition before work starts and accept the result against it.
- Process scheme — order flow map from request to shipment: at which stage the document is created, who confirms it, where the return point is when the specification is edited.
- Access rights matrix — roles by department (sales, procurement, production, warehouse, accounting): what they see, what they change, to whom they pass it on, what is fully closed.
- Configured routes — order stages and transition conditions, automatic assignments to owners, and notifications so a stage does not hang without an assignee.
- Order handling regulations — who moves the stage and at what point, how partial shipment and repeat orders are processed, who approves deadlines.
- Employee instructions — step-by-step guides for work area operations with system screens: request intake, release to production, kitting, shipment.
- Bitrix24 documentation — settings map: which fields, references, and fill rules are configured and what task each solves.
- Change regulations — how an edit enters the system: who approves it, on which circuit it is tested, how it is rolled back if it breaks a working scenario.
The acceptance criterion is simple: an employee who did not configure the system performs their operation according to the instructions, and a change in one work area does not drag a rework of the others with it.
Case: Order Circuit for an Assembly Area
Assembly production has a gap between the approved order and the shop floor: the manager closed the deal, while information reaches the area by phone.
We built a turnkey production circuit for a company assembling equipment to order: up to forty orders in progress, each with nine assembly stages.
Before implementation, orders lived in spreadsheets, statuses in correspondence, and actual progress by stage was entered retroactively.
This caused typical losses: an assembler starts on a unit that has not arrived yet, procurement learns about a shortage on the shipment day, and the manager assembles the picture by phone calls.
What We Changed in the Circuit
The basis is order accounting in the assembly area using a card with a fixed set of assembly stages. A stage closes only after a checklist: completeness confirmed, process sheet attached, permit issued — until the item is checked, the transition is unavailable.
Smart processes took over requests for tooling and component replacement, and rights were separated by work area: the foreman sees their shop, procurement sees only their tasks.
Exchange with 1C for items, warehouse, and cost runs on a schedule — balances in the card are always current.
Automation Results
Bitrix24 in this implementation case works not as a sales CRM, but as a production dispatcher:
- order lead time through stages — from 11 to 7 business days;
- share of orders with rework — from 19% to 5%;
- preparation of the load summary — from three hours manually to an automatic report;
- manual reconciliations with the warehouse — from six per shift to one.
How Accounting in Bitrix24 Differs from Spreadsheets and Custom Software
Spreadsheets support production accounting exactly until the first growth in volume. Batches, returns, and parallel edits to the same orders quickly show that a spreadsheet has no roles, change history, or write locking. Then balances diverge from actuals, and manual reconciliation appears instead of work.
Custom software removes some limitations but adds dependence on the code's author. Below are three paths that companies realistically choose between when configuring a production circuit.
| Option | When It Fits | Limitations |
|---|---|---|
| Accounting in spreadsheets | One work area, few people, no shared access | No roles or edit history, everything relies on manual reconciliation |
| Custom software | Non-standard process, ready-made objects do not fit | Support depends on the author, updates fall on the customer |
| Ready-made platform with configuration | Standard circuit: orders, specifications, batches, cost | Need to configure references and adapt part of the processes |
A ready-made solution versus custom development is not a binary choice. Configuration covers the standard circuit, while non-standard operations are added on top without modifying the core, so platform updates do not turn into rework.
Support for custom software rests on the person who wrote it; support for a production system on a ready-made platform rests on regulations and updates.
Bitrix24 is valuable here for its connections: order, specification, batch, and cost live in one model rather than being assembled from exports. We review what to migrate from spreadsheets and what to leave before setup.
Technical Concerns: Rights, Data Exchange, Integrations
Before the start, the same questions come up: how to migrate accumulated data, what about phone access on the shop floor, how to connect the portal with the accounting system, what will change when the hosting mode changes. Below are short answers on how this is handled in practice.
The general rule is the same: rights, exchange, and migration are first run on a copy and only then enabled on the working circuit — a configuration error must not block shipments or corrupt reference data.
How do I migrate data to Bitrix24 without losing history?
We export references, counterparties, items, and deals, map the fields, and reconcile the record count for each type. We resolve duplicates and broken links before enablement, not after. Old cards remain as a read-only archive.
How deeply is the portal connected to the accounting system?
Items and prices go to the portal; orders, payments, and stage statuses go back. If the accounting system is closed to external access, we configure scheduled exchange and a discrepancy log. Continuous synchronization is needed less often than it seems.
How do I separate access in manufacturing?
Rights are built by roles and departments: the foreman sees orders for their shop, procurement sees requests and balances, management sees the summary. Cost and payments are closed with separate rights.
Access is granted by groups, not individually — when an employee is transferred, the rights set changes with one edit.
Does mobile access to orders work?
Order cards, statuses, and attachments open from a phone, stages are confirmed on site, and a defect photo goes directly into the card. Printed forms with a code speed up finding the right order in the work area. With unstable connectivity, we enable offline work with deferred data submission.
Let's Discuss the Task: What to Prepare for the Conversation
The estimate for configuration work depends not on the number of users, but on how branched the production circuit is and what state the reference data is in.
Therefore we start the implementation conversation with a snapshot of the current state: what already works, where the data resides, who uses it. A full technical specification is not needed at this step — the inputs below are enough.
From them we will break the scope into stages, separately mark areas of uncertainty, and come back with an estimate and plan.
What to prepare for the discussion:
- Production circuit: work areas and processing stages, where output, defects, and work in progress are currently recorded.
- Data: items, specifications, consumption rates, units of measure — with an assessment of export volume and quality.
- Accounting: how warehouse, purchasing, and cost are linked, whether exchange with the accounting system occurs and in what form.
- Roles: who creates orders and closes stages, who needs reports and how often.
- Integration points: telephony, warehouse equipment, documents, external services.
- Acceptance criteria: by which metrics we consider the result working — cycle duration, share of orders without manual recalculation.
- Constraints: launch deadlines, whether work areas can be stopped, how many people work at the same time.
If some items on the list are not at hand, the conversation does not need to be postponed — some gaps are resolved right during the review.
Describe the task in a convenient form, and we will come back with an estimate for configuration work and a production implementation plan: stages, dependencies, and data connection sequence.