Bitrix24 for Distributors and Dealer Networks: Orders, Partners, and Fulfillment
O Bitrix24 (Alaio) reúne em um único ambiente o CRM da rede de revendedores, a entrada e o acompanhamento de pedidos B2B, o controle de estoque e a integração bidirecional com o ERP - eliminando planilhas paralelas e a perda de informação entre vendas, expedição e compras.
Why Generic CRM Falls Short for Distribution
Distribution and wholesale operations span at least three distinct workflows - dealer onboarding, order fulfillment, and post-sale replenishment - and a generic CRM that tracks only "leads and deals" misses two of the three.
Most out-of-the-box CRM setups are designed for single-step sales: a prospect becomes a customer and the deal closes. A distributor's reality is different. The same dealer company reorders monthly, carries stock on behalf of the brand, operates under a negotiated price agreement, and expects automated dispatch notifications. The gap between what a vanilla CRM offers and what distribution actually needs is where inefficiency hides - double-entry between CRM and ERP, order statuses that no one trusts, and account managers who spend time chasing warehouse updates instead of selling.
Bitrix24 (Alaio) addresses this through a combination of configurable deal pipelines, smart processes (SPAs), product catalogue management, automation robots, and two-way ERP integration - all within a single platform.
Dealer and Partner Network Management in Bitrix24
A well-configured Bitrix24 dealer card holds every attribute a channel manager needs: sales channel type, region, active/inactive status, annual turnover, B2B revenue share, partnership start date, and a linked contract history - all searchable and filterable without leaving the CRM.
Based on real implementation work, the company card for a dealer typically includes the following structured fields:
| Field | Type | Purpose |
|---|---|---|
| Sales channel | Multi-select list | B2B direct, retail, distributor, omnichannel, trade reseller, etc. |
| Region / Country | Searchable list | Territory assignment and reporting |
| B2B revenue share (%) | Number | Segment dealers by channel mix |
| Online sales share (%) | Number | Identify omnichannel partners |
| Partnership start date | Date | Calculate tenure for loyalty tiers |
| Status | List | Active / inactive (closed) / inactive (potential) |
| Cumulative turnover (period) | Number / SPA | Rolling revenue tracking per reporting cycle |
The contract pipeline is kept separate from the sales pipeline. Dealer agreements live in their own funnel (or a dedicated Smart Process), so the history of signed contracts is accessible from the company card without polluting the active order view. Historical contracts from before the Bitrix24 go-live can be imported and linked retroactively.
For organisations managing dealers across multiple countries, region and country fields make it straightforward to segment reporting by territory and assign account managers without custom development.
B2B Order Pipeline: Stages and Automation Logic
A typical wholesale B2B pipeline in Bitrix24 runs from "New deal" through invoice sent, payment confirmed, order assembly, and shipment - with ERP status updates pushing automatically into the deal card at each fulfillment stage.
From implementation experience with wholesale clients, a production-ready B2B deal pipeline looks like this:
- New deal - created from an inbound lead or manually; each deal gets a unique ID; flag set if this is the account's first order.
- Invoice sent - invoice dispatched via email or WhatsApp; ERP order created automatically; stock reserve applied (typically 5 business days, with automatic release if unpaid).
- Invoice paid / part-paid - deal advances automatically on payment confirmation; payment percentage field updated from ERP.
- Order assembly - ERP status ("order being prepared") syncs into Bitrix24.
- Dispatched - shipment status passes from ERP into the deal card; manager receives an automated follow-up task (e.g. 3 weeks after dispatch) to check reorder needs.
- Completed - deal closes when 100% paid and dispatched.
- Lost - reason field mandatory; feeds conversion analytics.
Automation robots handle the repetitive steps: creating the ERP order when the deal reaches a trigger stage, sending payment links, updating stock reserves, notifying the warehouse supervisor, and scheduling follow-up calls. This removes the manual handoff between sales and warehouse that typically causes delays in wholesale operations.
For the fulfillment side, a parallel pipeline - "Assembly and Delivery" - covers warehouse pick/pack and last-mile status, keeping the sales team informed without needing ERP access.
Product Catalogue, Stock Visibility, and Price Lists
Sales managers in Bitrix24 can see live stock levels and reserve status for every product directly inside the deal card - eliminating the situation where a product is sold to two customers simultaneously.
The product catalogue in Bitrix24 supports custom fields at catalogue level (visible inside deal cards) for attributes like product category, SKU identifiers used for ERP matching, and price tier. When a manager adds a product to a deal, the system can display:
- Whether the item is currently reserved under another open deal, and by whom
- The price applicable under that dealer's agreement
- Availability flag based on ERP-synced stock
The "goods on reserve" view scans all open deals and surfaces a consolidated list of reserved items - useful for warehouse staff doing availability checks and for managers quoting realistic lead times to customers.
For distributors managing multiple price lists (by dealer tier, region, or volume bracket), Bitrix24 supports catalogue-level pricing rules that apply automatically when a specific dealer company is linked to the deal.
Procurement automation is also supported: when a deal reaches a defined stage, a smart process can auto-generate a procurement checklist for the supply team, listing the items that need to be sourced or confirmed for that order.
ERP Integration: Two-Way Order Synchronisation
The core integration pattern for a distributor is bidirectional: Bitrix24 triggers order creation in the ERP system, and the ERP pushes status updates (payment percentage, shipment percentage, order number, order state) back into the deal card in real time.
Bitrix24 sits between the commercial front end and the ERP back end in a typical distributor setup.
The system receives incoming B2B inquiries from website forms, email, telephony, or a dealer portal. Deals are managed in Bitrix24 pipelines. When a deal reaches the appropriate stage, an order is pushed to the ERP. The ERP then returns the order number, payment status, assembly status, and shipment confirmation - all written back into the corresponding deal card fields.
flowchart LR
WEB[Website / Forms] --> B24[Bitrix24 CRM]
PHONE[Telephony / Email] --> B24
PORTAL[Dealer Portal] --> B24
B24 -->|Create order, products, discounts| ERP[ERP System]
ERP -->|Order number, payment %, shipment %, status| B24
B24 --> WH[Warehouse / Fulfillment]
B24 --> DOCS[Quotes / Invoices / Contracts]
Key data fields synchronised from Bitrix24 to ERP:
- Deal ID (Bitrix24 identifier stored in the ERP order)
- Contact / company details (with duplicate check by phone or email)
- Product list with prices, discounts, and tax values
- Comments and deal notes
Key data fields synchronised from ERP back to Bitrix24:
- ERP order number and order date
- Order status / fulfilment state
- Payment percentage and amount paid
- Shipment percentage
- Product list updates (if the ERP modifies the order)
This two-way sync eliminates the need for managers to log into the ERP to check order progress. It also ensures that if the ERP modifies an order (adjusts quantities, applies discounts, splits shipments), the deal card in Bitrix24 reflects the current state automatically.
For organisations using accounting or ERP platforms common in their market, the integration is built via Bitrix24's REST API or a dedicated middleware connector. See our Bitrix24 ERP & Accounting Integration guide for technical architecture options.
Turnover Tracking and Dealer Performance Reporting
Bitrix24 can display cumulative dealer turnover per reporting period directly in the company card, enabling account managers to monitor whether a dealer is on track against their sales plan without switching to a spreadsheet.
This is one of the more nuanced configuration tasks in a distributor setup, because Bitrix24 does not natively maintain a rolling-period counter. The practical approaches used in real implementations:
- Business process (workflow) on deal closure - a BP automation rule reads the deal value, adds it to a custom "period turnover" field on the company card, and updates the running total.
- Smart Process as a period register - a new SPA entity is created for each reporting period, storing the period total separately. This preserves history across periods and avoids the reset complexity of a single cumulative field.
- Universal list inside the company card - a structured list linked to the dealer company stores one row per period, allowing managers to see the trend over time.
The second and third approaches are preferred when historical turnover visibility matters - for example, when a distributor needs to compare a dealer's Q1 performance year-over-year.
Sales target plans can be loaded per dealer (via Excel import or API from an external planning system) and compared against actual turnover automatically. Reporting can break down by product category, territory, or sales channel type.
For dashboards that go beyond standard CRM reports, Bitrix24's BI Constructor connects directly to deal and product data - see How to Create a BI Report in Bitrix24 with BI Constructor for setup details.
Post-Sale Workflow: Repeat Orders and Reactivation
After a B2B shipment is confirmed, Bitrix24 can automatically schedule a follow-up task for the account manager and, if no reorder is placed within a defined window, route the dealer into a reactivation pipeline.
The post-sale stage is where many wholesale CRM implementations underperform. The deal closes, the invoice is marked paid, and the customer file goes quiet until the dealer calls in again. Bitrix24 automation changes this:
- At the "Dispatched" stage, a robot schedules an outbound call task for the account manager (typically 3 weeks post-shipment) to check satisfaction and probe reorder timing.
- If no new deal is created within a configurable period, a separate "Repeat sales" or "Reactivation" funnel captures the dealer for proactive re-engagement.
- The repeat sales pipeline mirrors the primary pipeline stages but starts from "Purchase date confirmed" - the moment the dealer indicates their next restocking date.
For dealers who go silent, the reactivation funnel provides a structured process: it flags the account, assigns a task, and tracks the re-engagement outcome. This is especially valuable for distributor networks with hundreds of dealers, where manual follow-up is impractical.
AI call analysis features in Bitrix24 - powered by BitrixGPT - can score post-sale calls automatically and flag dealers showing signs of churn, giving managers an early warning before a relationship goes cold.
Dealer Portal and Self-Service Order Entry
A dealer portal built on Bitrix24 gives trade partners a self-service interface to submit orders, check stock availability, download price lists, and track shipment status - reducing inbound call volume to the sales team.
For distributors with large dealer networks, the volume of inbound order-taking calls and emails becomes a bottleneck. A dealer portal addresses this by moving routine transactions online:
- Dealers log in to submit new orders directly, which create deals in the Bitrix24 pipeline automatically.
- Live stock and reservation data (synced from ERP) is visible to the dealer at time of ordering.
- Current price lists, applicable to that dealer's tier, are accessible from the portal.
- Order history and shipment tracking status are visible without contacting the sales team.
- Document downloads (invoices, delivery notes, certificates) are available per order.
Portal access rights are configured per dealer company, so each partner only sees their own order history and the product catalogue relevant to their channel type.
This is directly relevant for distributors operating across multiple markets - UAE, Brazil, Portugal, or wider MENA - where dealers may be in different time zones and language-specific portal content reduces friction.
Implementation Scope and Realistic Timelines
A Bitrix24 distribution setup covering dealer management, B2B pipeline, product catalogue, and basic ERP integration typically requires 80-160 hours of configuration and development work, depending on the number of pipelines, custom fields, and integration complexity.
The work breaks down roughly as follows:
| Component | Typical effort |
|---|---|
| CRM structure (pipelines, fields, card layouts) | 20-40 hrs |
| Automation robots and business processes | 15-25 hrs |
| Product catalogue and price list configuration | 8-15 hrs |
| ERP integration (API / middleware development) | 30-60 hrs |
| Reporting and BI dashboards | 8-15 hrs |
| Testing, UAT, and training | 10-20 hrs |
ERP integration is the largest variable. A straightforward one-way product sync is at the lower end; a full bidirectional sync covering orders, payments, shipments, and stock levels adds significant development effort, particularly if the ERP requires custom API handling.
If you are migrating from a previous CRM, the Bitrix24 implementation cost and timeline data from 1,300+ real projects gives useful benchmarks. For a detailed question-by-question discovery of your distribution setup before starting, the Bitrix24 onboarding questionnaire covers the key process decisions.
For growing networks with data residency requirements - common in UAE (under the UAE Personal Data Protection Law) and in Brazil (under LGPD) - a self-hosted Bitrix24 deployment keeps all dealer and order data on infrastructure you control. See self-hosted vs cloud Bitrix24 TCO analysis for a cost and compliance comparison.
ACP Group is a Bitrix24 Gold partner with distribution and wholesale implementations across UAE, Brazil, and Portugal. For a scoped proposal based on your specific network size and ERP stack, visit acp-24.com.
Running a distribution or dealer network? ACP Group INT delivers Bitrix24 CRM for distributors in the UAE - partner pipelines, pricing tiers and order flows.
Frequently asked questions
Can Bitrix24 handle multiple price lists for different dealer tiers?
Yes. Bitrix24's product catalogue supports multiple price types that can be assigned per company or deal type. When a dealer company is linked to a deal, the applicable price tier is applied automatically to products added in that deal card.
How does Bitrix24 prevent overselling when stock is limited?
A 'goods on reserve' view scans all open deals and shows which products are already allocated. Combined with ERP integration that syncs live stock levels, managers can see real-time availability before confirming an order - and stock reserves are set automatically when an invoice is issued, with automatic release if unpaid after a configurable period.
What happens to the Bitrix24 deal when the ERP updates an order?
With a properly configured two-way integration, changes made in the ERP (revised product quantities, updated payment status, shipment confirmation) are written back into the corresponding Bitrix24 deal card fields automatically, so the sales team always sees the current order state without ERP access.
Can dealers submit orders themselves without contacting the sales team?
Yes. A dealer portal built on Bitrix24 allows trade partners to log in, submit orders, check stock and price lists, and track shipment status. Orders submitted through the portal create deals in the CRM pipeline automatically and trigger the standard fulfillment workflow.
How is dealer turnover tracked across reporting periods?
Turnover per dealer is tracked using one of three approaches: a business process that accumulates deal values into a custom company-card field, a Smart Process entity that creates a new record per reporting period (preserving history), or a universal list inside the company card. The Smart Process approach is preferred when year-over-year comparisons are needed.
Is self-hosted Bitrix24 necessary for a distribution company?
Not always - cloud Bitrix24 covers the majority of distribution use cases. Self-hosted becomes relevant when local data residency regulations apply (e.g. UAE PDPL, Brazil LGPD), when deep ERP integration requires on-premise network access, or when the company needs source-code customisation beyond cloud limits. Cloud is often the more cost-effective starting point for smaller networks.
Based on real practice
This article is based on 13 internal documents from ACP Group's practice - work plans, specifications and Bitrix24 implementation cases.
Need help with Bitrix24?
ACP Group is a Bitrix24 Gold Partner. We'll review your task, estimate the effort in hours and propose a plan - free of charge.