A CRM for a distributor tracks repeat orders from retail outlets rather than one-off deals: the rep's visit plan, the price matrix for each customer, stock on hand, the credit limit and the balance owed. A classic sales funnel is of little help here, because the customer does not close once — they order every week, and the system exists to keep those orders steady and on time.
Key takeaways
Wholesale is not a narrow niche in Uzbekistan, and disorder in order taking starts costing money at a few dozen outlets.
A distribution deal does not end when the invoice is paid: the first delivery starts a cycle of repeat orders, shipments and settlements that runs for years. That is why the central object in the system is not the deal but the outlet, with its history, terms and debt.
Everything else follows from that.
| What we compare | One-off sale | Wholesale distribution |
|---|---|---|
| Customer | A new buyer who has to be convinced | An outlet that already works with you and orders regularly |
| Rep's goal | Close the deal | Hold order frequency and order value, never miss a visit |
| Price | One price list plus a negotiated discount | A price matrix by channel, volume and payment terms |
| Money | Payment against an invoice | Deferred payment, a credit limit and a payment schedule per outlet |
| Stock | The goods are normally available | Orders are filled from stock, some lines get substituted |
| Reports | Conversion and revenue | Territory coverage, active customer base, receivables |
The working minimum covers four areas: the outlet database, the order with its price and stock, field work by reps, and money. Go through the list and mark what the system does on its own and what your staff will keep doing in spreadsheets.
Field work runs on a visit plan: each rep has a weekly list of outlets, and the system compares plan with fact. Without it, a lost outlet surfaces a month later, once it is already buying from another supplier.
The cycle is built in this order.
Tip Do not ask a rep to fill ten fields on a phone. Leave the order, the reason for a refusal and the shelf stock — the system fills in the rest. A long form means visits get logged from memory in the evening, and the data stops meaning anything.
Debt is controlled by the limit and the term stored in the outlet record: once the limit is breached, the system holds the next order until a manager decides. Otherwise deferred payment turns into an interest-free loan with no due date.
Four rules apply in distribution.
Mistake Keeping receivables in a separate file on the accountant's desk. A rep books a new shipment without knowing the outlet has not paid for two months, and the conversation about the debt starts when the amount already matches a month of revenue from that customer.
Terms belong in the system as rules rather than files: sales channel, order volume and payment method set the price by themselves. A price list sent as a file is out of date the day it goes out, and part of the orders come in at old prices.
Five things are described as rules.
When the rules sit in the system, a rep stops negotiating prices in chat, and the owner can see how much the company gave away in discounts over the month.
A CRM does not replace the accounting program: it owns the customer relationship, while stock, shipments and documents stay in accounting. The split is simple — the CRM holds what was agreed with the outlet, accounting holds what actually happened.
In Uzbekistan there is a legal requirement on top of that. Article 47 of the Tax Code states that an invoice is, as a rule, issued in electronic form in the electronic invoice information system — the text on lex.uz. For a distributor this means an order from the CRM has to reach the electronic invoice without anyone retyping line items.
Data is usually divided like this.
How such exchanges are built is covered in the article on CRM integration with 1C, telephony and messengers, and an owner is best served by daily figures where they already read messages — that is 1C reports in Telegram.
Part of the order flow can be taken off the rep: the outlet builds its order in a Telegram bot and sends it, and the CRM treats it like any order taken in the field. This works where the product range is stable and goods are reordered.
What changes in day-to-day work.
The bot does not cancel field work. It takes the routine on steady lines, while the visit stays where someone has to look at the shelf, discuss a wider range and collect the money.
Rolling out a ready platform for a sales team starts at $3,000, building a CRM around your processes starts at $12,000, and putting an already purchased system in order starts at $2,000; the entry points are listed on the CRM systems page. The final figure is set by the scope of work, not by the name of the platform.
Subscriptions are counted separately, and platforms charge in different ways. Bitrix24 sells cloud plans per organisation: the Basic plan for five employees is $49 a month on annual billing, Standard for 50 employees is $99. Kommo charges per user: the Base plan is $25 per user a month, with a six-month minimum subscription. A distributor has many users, and on the second model costs grow along with the field team.
Five things drive the cost of the project.
After launch you are left with hosting and maintenance: support for production systems starts at $700 a month. If the platform is not chosen yet, the criteria are collected in the article on how to choose a CRM system for your business, and the cases where a ready platform cannot carry the process are covered in the piece on a custom CRM.
We start with a single route: we ride along with a rep, watch how orders are taken today, where they get lost and at what point the debt comes up. Then we describe the rep's day and the manager's screen, and only after that decide whether to configure a ready platform or build a system around your processes.
Next we connect the CRM to accounting, the warehouse and electronic invoices, add order taking in Telegram where it is needed, and set up reporting on territory coverage and receivables. Data is hosted in a data centre in Uzbekistan or on your own servers, and after launch we stay on support and keep developing the system as the customer base grows.
Let’s discuss your project
Tell us what you need, and we will estimate the timeline and cost and suggest a solution.
With a review of one route: how the rep takes an order, where it ends up and when the outlet's debt comes to light. In parallel, clean the outlet and product reference data — duplicates otherwise move into the new system and spoil the reports.
A ready platform is enough while the price matrix fits a few channels and discounts and field work stops at a visit plan. If an order depends on dozens of individual terms, building a system around the process costs less than working around the platform.
No. The CRM keeps what was agreed with the outlet, while the accounting system keeps stock, shipments and documents. The exchange is set up so items and stock flow from accounting into the CRM, and orders and new counterparties flow back.
That depends on the billing model. Bitrix24 sells cloud plans per organisation: Standard for 50 employees is $99 a month on annual billing. Kommo charges per user: the Base plan is $25 per user a month, so with a large team costs grow in proportion.
By four numbers: visit plan completion, the share of visits that end in an order, the active customer base and receivables broken down by outlet. If the system collects them by itself instead of someone assembling a spreadsheet before the weekly meeting, order has been restored.
The bot picks up repeat orders on a steady product range, but it does not replace the visit. Checking the shelf, discussing a wider range and collecting the money stay a person's job.
In a data centre in Uzbekistan or on the company's own servers — this is decided before launch, together with the exchange scheme with the accounting system. Support for production systems at Syntra Systems starts at $700 a month.
Sources
Cover photo: Julius Weidenauer, Pexels
