Setting up Bitrix24 for a wholesale company
A wholesale company operates on a long deal cycle: from first contact to shipment takes 2-4 weeks, orders are recurring, and each client has individual terms for prices, deferred payment, and limits.
Standard Bitrix24 without customization loses this context: the manager does not remember what discount was promised three months ago and asks the client again. The result is protracted negotiations, lost orders, and overdue payments that are discovered too late.
We solve this problem in 3-4 weeks: we configure CRM taking into account wholesale specifics, automate pipelines, integrate with 1C, and control accounts receivable. The manager sees the entire interaction history, client terms, and debt status in a single card.
What is included in the setup?
| Component | Details |
|---|---|
| Process audit | Analysis of current business processes, sales structure, typical deals, identification of bottlenecks |
| CRM design | Extension of company cards with custom fields, creation of reference books, pipelines |
| Integration with 1C | Synchronization of products, stock, invoices, and payments via CommerceML or REST API |
| Robots and automation | Setup of robots for accounts receivable control, invoicing, reminders |
| Training | Individual training for managers and executives, process memo, instruction recording |
| Support | One month of technical support after launch, 30-day warranty for revisions |
| Documentation | Description of settings, user instructions, integration scheme |
Why is standard Bitrix24 not suitable for a wholesale company?
Standard CRM is focused on retail: the contact is an individual, deals are short, prices are fixed. In wholesale, the history of relationships with a legal entity, individual terms, and long cycles are important.
Without modifications, the system does not manage accounts receivable, does not distinguish between initial and repeat sales, and does not pull dealer prices. Customization for wholesale solves these problems.
How do we configure CRM for wholesale?
- Audit: We study current processes, client structure, typical deals, and growth points.
- Design: We create the data structure — custom fields, reference books, pipelines.
- Implementation: We configure the catalog, robots, integrations. We test each connection.
- Training: We conduct trainings for sales and procurement departments.
- Launch: We migrate the company to the new CRM within a day, monitor the first deals.
This approach is 2 times faster than regular custom development, as we use ready-made templates and standard solutions.
Client base structure
For wholesale, CRM is configured with an emphasis on the company, not the contact. The company is a legal entity, the payer, it has details, credit limit, dealer type. The contact is the specific procurement employee who calls.
We add custom company fields: UF_CLIENT_CATEGORY (wholesale, distributor, retail chain), UF_PRICE_TYPE (which price list applies), UF_CREDIT_LIMIT, UF_PAYMENT_DELAY (deferred payment in days), UF_REGION, UF_ASSIGNED_MANAGER.
The official Bitrix24 documentation on custom fields recommends this approach for accounting for business specifics.
Such a structure allows building reports by client categories, automatically substituting prices when creating invoices, and setting up robots for overdue payments.
Wholesale sales pipeline
For wholesale sales, we use a two-level pipeline: initial sales and repeat orders. Initial pipeline: Cold contact → Qualification → Proposal sent → Negotiations → Terms agreement → Contract → First shipment → Regular client.
Repeat order pipeline: Request accepted → Stock confirmation → Invoice issued → Payment received → Shipped. Robots automatically create a deal in the repeat order pipeline when a request is received from a regular client.
As a result, invoice issuance time is reduced by 2-3 times, and errors due to forgotten terms are eliminated.
Catalog and invoices
In Bitrix24, we connect the Product Catalog with wholesale items and prices. Invoices and proposals are generated directly from CRM with items and dealer prices pulled in. For different client groups — different price lists via the UF_PRICE_TYPE field.
Integration with 1C (if available): via the exchange module “1C:CRM” or REST API. Invoices issued in 1C are duplicated in CRM via a webhook. Payment in 1C → automatically changes the deal stage in Bitrix24.
Accounts receivable control
We add debt fields to the company card (UF_DEBT_AMOUNT, UF_DEBT_DAYS). Robot: if UF_DEBT_DAYS > 5 → task to manager “Remind about payment”. If > 14 → task to supervisor. Data is synchronized from 1C via an agent or webhook.
According to our data, implementing such a scheme reduces losses from overdue payments by 80%. Average losses before setup amount to a cost calculated after audit per year — this sum goes to manual control and writing off bad debts. After setup, you save a portion of that.
Comparison before and after setup
| Parameter | Before setup | After setup |
|---|---|---|
| Invoice issuance time | 15-30 minutes | 2-3 minutes |
| Terms agreement | 2-3 days | 1 day |
| Accounts receivable control | manual, missed | automatic, 100% |
| Repeat orders | via email | in CRM in 1 click |
Timelines and guarantees
Setup of the client base structure, two pipelines, catalog, robots, and basic integration with 1C: 3-4 weeks. Complex integrations (multiple systems, custom reports) may take up to 2 months. The budget is calculated individually depending on the scope of work.
We will estimate the project within a day. We work under a contract, warranty for all revisions — 30 days.
Contact us for a preliminary project estimate. Get a consultation: our engineers will help select a configuration for your business.