Skip to main content
Free 20-minute marketing audit
Limited spots available

Have a question?

We usually reply within 5 minutes.

WWhatsApp TTelegram

ERP for a Small Business in Uzbekistan: Minimal System, Phases and Budget

ERP for a 5–50 person operation in Uzbekistan: which modules now and which later, off-the-shelf vs custom, a phased budget template and a readiness checklist.

ERP for a Small Business in Uzbekistan: Minimal System, Phases and Budget

Short answer: a local operation of 5–50 people in Uzbekistan does not need a large ERP. It needs a minimal system that answers three questions precisely: how much cash there is, how much stock there is, and who owes whom. Sales and checkout, stock on hand and receivables and payables are enough for that. Other modules come six months later or even after that. In most cases the right start is off-the-shelf software or a cloud service. A custom build is only justified for a genuinely unique process. Split the budget into phases and make each phase earn the next one.

This guide is written for foreign companies that run a small entity in Uzbekistan: a sales office, a distributor, a showroom, a service point or a small production site. How a full system is designed and built from scratch is covered in the main guide on custom ERP development: when you need it and how it is built. Here the question is narrower: how a small local team moves to orderly records with minimal money and time.

What "ERP" really means for a small operation

In a large enterprise, ERP means dozens of modules, hundreds of users and a dedicated IT department. A small local team does not need that. It has neither the time nor the people to configure and maintain it.

For a small operation, ERP is one database. Sales, receipts of goods, stock and debts are recorded in it. Everything sits in one place and every employee sees the same numbers. The country manager, or head office, knows the position without phoning the warehouse.

A typical picture looks like this. A local building materials outlet employs seven people. Sales are written in a notebook and in a spreadsheet on someone's phone. Goods given on credit are remembered by the salesperson. At month end the stock count does not match the notebook. Nobody knows who made the mistake. The problem is not the absence of software. The problem is that the data is not in one place.

A quick test will tell you whether you already need a system. You will find it in the article on the signs that a business needs ERP. If several signs look familiar, read on.

A small entity also has an advantage. Processes are still simple. There are few people. Decisions take a day, not a quarter. A well-chosen minimal system can therefore be running within a few weeks.

For a foreign-owned company there is one more point. Head office often expects the local team to "just use the group ERP". In practice the group system rarely covers local checkout rules, local payment systems and day-to-day credit to small customers. A light local system next to the group ERP is often the faster and cheaper answer.

The minimal system: now, in six months, later

The main rule is simple: do not switch everything on at once. Every module brings new data, new rules and a new habit for staff. A small team can absorb one or two changes at a time.

Also read Your Customer Calls Twice and Still Has to Spell Their Name: Connecting IP Telephony to ERP in Uzbekistan Technology · 10 min

The table below gives a general direction for trading, services and small production. Adapt it to your operation.

  • Sales and checkout (receipts, payment types) — Now: ✓
  • Stock: receipts, issues, stock on hand — Now: ✓
  • Customer and supplier debts — Now: ✓
  • Product and price master data — Now: ✓
  • Purchasing: orders and minimum stock — In 6 months: ✓
  • Customer base and repeat sales (simple CRM) — In 6 months: ✓
  • Reconciliation with payment systems and bank — In 6 months: ✓
  • Daily 5–7 number report for management — In 6 months: ✓
  • Barcodes and scanners — In 6 months: ✓
  • Payroll and bonuses — Later: ✓
  • Production and bills of materials — Later: ✓
  • Branches and transfers between warehouses — Later: ✓
  • Advanced analytics and BI — Later: ✓

Why this order? The first column closes the flow of money and goods. Without it every other module works with wrong numbers. The second column makes the system pay off: purchasing on time, customers coming back, payments reconciled quickly. The third column only makes sense once the first two run steadily.

For some businesses the order shifts. In a small garment workshop, production moves into the first column, because fabric consumption and finished units are where the money is. In a service business, stock moves down and bookings and schedules move up. The logic stays the same: start with the process through which money comes in.

In a small garment workshop in Margilan, the forewoman checks the count of cut fabric bundles while seamstresses keep working

Where to start: the first 30 days

Before choosing software, do some preparation. It delivers more than the software itself.

  1. Appoint one internal owner. Not a programmer. Someone who knows the business well and likes order. This person is accountable for the data.
  2. Clean the product list. If one item is recorded under three names, merge them. Fix units of measure: pieces, metres, kilograms.
  3. Count opening stock. If wrong opening stock goes into the system, trust disappears on day one. Run the count on a day off or before opening hours.
  4. Collect the debts. Notebooks, salespeople's memory, messenger chats. One balance per customer and per supplier.
  5. Write the rules on one page. Who grants discounts, who may buy on credit, how returns are processed.
  6. Launch one process first. For example, sales and checkout only. Run it for one or two weeks, then add stock.

Check the checkout rules separately. Cabinet of Ministers Resolution No. 943 of 23 November 2019, "On measures to ensure the use of online cash registers and the virtual cash register system", governs the use of online cash registers and virtual cash registers in Uzbekistan. Under it, only online cash registers or virtual cash registers included in the state register may be used. Receipts must show the identification codes from the unified national electronic catalogue of goods and services. Check the text and later amendments on lex.uz. Requirements for electronic invoices and mandatory product marking depend on the type of activity. Confirm them for your sector on soliq.uz and lex.uz, ideally with a local accountant. Ask in advance whether the software you choose supports these requirements.

Off-the-shelf, SaaS or custom: where the line is

A small operation has three routes. Each has its place, and they do not exclude each other.

Cloud service (SaaS). A monthly subscription, used from a browser or a phone. Enough for sales, stock and checkout. Quick to launch, no server needed. The downside: you adapt your process to the software, not the other way round.

Boxed software or a standard platform. Runs on your own computer or server. Convenient for accounting and standard records. It can be adapted, but you need a specialist for that.

Custom component. Built around your process. In a small business this is usually not a whole ERP. It is one part: for example, a Telegram bot that takes orders, or a specific calculation connected to standard software.

Use these questions to find the line:

  • Is my process similar to others in the sector? — If yes: Off-the-shelf; If no: Consider a custom component
  • Does standard software cover 80% of requirements? — If yes: Handle the other 20% manually or change the process; If no: Look at other software or a custom part
  • Does at least one important process rely on retyping data? — If yes: Integration or a small custom module; If no: Off-the-shelf is enough
  • Does adapting the product cost about as much as building the part? — If yes: Estimate a custom build; If no: Keep adapting
  • Is there someone internally to run the system? — If yes: A more complex solution is possible; If no: Stay with simple SaaS

A detailed total-cost-of-ownership comparison of a standard platform such as 1C, off-the-shelf software and a custom ERP is in custom ERP vs 1C vs off-the-shelf software.

Cloud versus own server is a separate question. For a small operation the cloud is often cheaper and easier to run, because backups and updates are the provider's job. But you must know where data is stored, who can access it and how you get it back if you leave. Foreign companies should also check what group IT policy says about data location. These trade-offs are covered in cloud ERP versus your own server.

When choosing a provider, questions beyond price matter. Can data be exported? In which languages does support respond, and how fast? What happens when the contract ends? A full list of questions is in the article on how to choose an ERP vendor.

Sector differences: same logic, different emphasis

The minimal-system logic is the same for everyone, but the first module depends on the sector.

  • Retail outlet or small wholesale. The starting point is checkout, stock and debts. With a wide assortment, plan barcodes early: fewer checkout errors and faster stock counts.
  • Training or education centre. Almost no stock. What matters is groups, class schedules, monthly fees and students who are behind on payment. More: CRM and ERP for education centres.
  • Small hotel or guesthouse. Bookings, room occupancy and extra services. With many booking channels, the main pain is the risk of selling the same room twice. More: hotel management systems.
  • Car service. Work orders, spare parts stock and mechanics' pay are linked. That is why payroll is needed earlier here, not "later". More: ERP for car service centres.
  • Small production or workshop. Raw material receipts, consumption norms and finished goods. Without consumption norms, unit cost is a guess rather than a calculation.

Whatever the sector, the test question is the same: in which process is money being lost? That is where the system starts.

Phased budget: template and illustrative example

The riskiest move for a small operation is to spend a large sum at once and wait a year for results. Split the budget into phases. Move to the next phase only after the previous one is working.

The budget has three lines: one-off costs, monthly costs and contingency. Count internal time too: the internal owner and the manager will spend a few hours a week on it.

Illustrative example. A trading operation with 8 users in phase 1, growing to 12 in phase 2 as purchasing and warehouse staff join. All figures only show the logic of the calculation. They are not market prices.

  • 1. Months 0–3 — Scope: Sales, checkout, stock, debts; data entry and training; One-off: UZS 6m setup + UZS 4m scanner and printer; Monthly: 8 × UZS 150k = UZS 1.2m; Phase total: 10 + 3 × 1.2 = UZS 13.6m
  • 2. Months 4–9 — Scope: Purchasing, customer base, payment reconciliation; One-off: UZS 15m integration; Monthly: 12 × UZS 150k = UZS 1.8m; Phase total: 15 + 6 × 1.8 = UZS 25.8m
  • 3. Month 10 onwards — Scope: Payroll, a branch or a custom component; One-off: Estimated separately; Monthly: —; Phase total: Once requirements are clear

The first two phases together: 13.6 + 25.8 = UZS 39.4m. Add a 15% contingency: 39.4 × 0.15 ≈ UZS 5.9m. The plan for the first nine months comes to about UZS 45.3m. Three more months of subscription to year end add 3 × 1.8 = UZS 5.4m. The first-year total is about UZS 50.7m.

Now compare this with losses. Suppose monthly turnover is UZS 400m. Unrecorded debts, shortages and wrong purchases cost 1% of turnover: UZS 4m a month, or UZS 48m a year. No system closes the whole gap. Run two scenarios.

  • 80% of losses closed. Savings are UZS 3.2m a month. Monthly costs are UZS 1.8m, so the net gain is UZS 1.4m a month. One-off costs plus contingency: 6 + 4 + 15 + 5.9 = UZS 30.9m. They pay back in about 22 months (30.9 ÷ 1.4).
  • Half of losses closed. Savings are UZS 2m a month and the net gain only UZS 0.2m. At that rate the one-off costs practically never pay back.

The lesson: the heaviest line is the UZS 15m integration in phase 2. Do not start it until phase 1 has delivered results. Staff time saved is not included; if there is some, the picture improves. From year two mainly the monthly costs remain: 12 × 1.8 = UZS 21.6m. Use the same formula with your own numbers: one-off costs ÷ (monthly savings − monthly costs) = payback in months.

Budget template:

  • Subscription or licence (monthly × months)
  • Setup and data entry
  • Hardware (scanner, printer, tablet)
  • Integrations
  • Training
  • Support
  • Contingency 10–20%
  • Internal time (hours × people)

What each line consists of and how to compare proposals is explained in what drives ERP cost.

At a family spice stall under a trading dome in Bukhara, a father weighs spices while his daughter counts the filled bags into a crate

Rolling out the system: a sequence for a small team

In a small business the rollout is shorter than in a large project. The phases are the same, though: preparation, setup, testing, training and go-live. The full sequence is in ERP implementation stages. A short version for a small team:

  • Week 1. Products, prices and debts go into the system. The internal owner checks everything.
  • Week 2. One or two salespeople work in the system. The notebook runs in parallel. At day end the two are compared.
  • Weeks 3–4. Everyone moves to the system. The notebook stops. The manager looks at one short report every day.
  • Month 2. The first stock count is done from the system. Any difference is traced to its cause: which transaction was not recorded.

If there is no local IT person, outsource the technical work. That can be the software provider or an external specialist. Accounting is often outsourced too, especially for foreign-owned entities. In that case the system must exchange data with the external accountant. Which functions to keep in-house and which to hand over is covered in outsourcing business functions.

One rule does not change: responsibility for data quality stays inside the company. An external specialist will configure the software. But only your own employee knows whether a product was entered correctly.

Six common mistakes in small operations

  1. Choosing the biggest software. More modules mean more configuration. Staff use a small share of the functions, and you pay for all of them.
  2. Starting with dirty data. Duplicate products and wrong stock are carried into the system. After a month staff stop trusting it.
  3. Not closing the notebook. If parallel running lasts more than two weeks, two versions of the truth appear.
  4. Managers not using the system themselves. If the manager still asks for numbers by phone, staff will not take the system seriously either.
  5. Not checking data ownership. If the subscription ends, can you export the database? Find out before signing.
  6. Trying to build everything custom. A fully custom ERP rarely pays off for a small operation. Start with a standard core, then add custom parts only where they are really needed.

Self-assessment checklist

Before choosing software or paying for it, tick the items:

  • ☐ The three questions the system must answer are written down.
  • ☐ There is a list of "now", "in 6 months" and "later" modules.
  • ☐ One internal owner is appointed and has time for the job.
  • ☐ The product list is clean and units of measure are consistent.
  • ☐ Opening stock and debts have been counted.
  • ☐ Discount, credit and return rules are written on one page.
  • ☐ Checkout, e-invoice and marking requirements are confirmed for your sector.
  • ☐ It is clear whether the software can export data and what happens when the contract ends.
  • ☐ The budget is split into phases with a contingency.
  • ☐ Each phase has a success criterion, for example a smaller stock count difference.
  • ☐ Management is ready to read the daily report from the system.

If fewer than 8 items are ticked, postpone the software decision by a week or two. Finish the preparation first. That time comes back during setup and rework.

Conclusion

ERP for a small operation is not a scaled-down copy of a large system. It is a minimal system that shows cash, stock and debts in one place. Start there. Add other modules once results are visible. Off-the-shelf software and cloud services cover most needs. A custom build is only needed for the genuinely unique part. Split the budget into phases, compare each phase with the losses it addresses and keep the data clean from day one.

Frequently asked questions

Our group already runs a global ERP. Does a small Uzbek entity need a local system?

Often it does. A group ERP handles consolidation and group reporting well, but a small local team usually needs fast day-to-day tools: a fiscal checkout, stock on hand, local payment systems and customer debts. A lightweight local system can run these and send summarised data to the group ERP, which is usually cheaper than extending the global system to every local detail.

Which modules does a small operation need first?

Usually three: sales and checkout, stock on hand, and receivables and payables. Together they answer the core questions about cash, goods and debt. Payroll, production and advanced analytics can wait for a later phase.

Off-the-shelf software or a custom build — where should a small entity start?

In most cases with off-the-shelf software or SaaS. It is affordable, quick to launch and forces the team to tidy up its processes. A custom component makes sense when a process is genuinely unique or when adapting the standard product costs about as much as building that part. Even then it is usually one component, not the whole system.

How should we structure the first-year budget?

Use three lines: one-off costs (setup, data entry, hardware), monthly costs (subscription, connectivity, support) and a 10–20% contingency. Approve each phase separately and move to the next one only after the previous phase has delivered a measurable result.

Who runs the system if there is no local IT person?

Appoint one internal owner who is responsible for data quality and user questions. Technical work such as updates, backups and integrations goes to the software provider or an external specialist. Make sure each party's responsibilities are written into the contract.

Want to define your minimal system?

Let's review calmly which modules your Uzbek operation needs right now, which can wait, and what a realistic first-phase budget looks like.

Discuss a minimal system →

Let's work out where to start

Free consultation with a DORA specialist

Message on Telegram

Let's discuss your project

Leave your number and a specialist will get in touch.

Send a request via Telegram

Your details are used only to contact you.