Your own ERP or 1C:ERP
1C is the accounting standard across much of the CIS, and we do not suggest throwing it out: the books can stay in 1C while operations, meaning warehouse, production, purchasing and plan versus actual, run in a system built around your process. A custom ERP is justified when customising the standard configuration costs more than building, when your process does not fit standard documents, or when staff need simple workstations instead of dozens of forms. If your processes are standard and the team knows 1C, implementing 1C:ERP may be wiser, and we will say so at the first meeting. Either way, the systems are connected and the numbers match.
What drives the price
Module is one area: warehouse, finance or HR, plus a bank integration. Start there if one place hurts. ERP brings warehouse, purchasing, finance, HR and Didox exchange together: the whole operational picture. Holding covers a group of companies with consolidation, production, departmental plan-versus-actual budgets and BI. Price moves with rules rather than screens: how cost price is calculated, how many warehouses and legal entities, which documents and approvals. Face ID turnstiles, material planning, quality control, fleet, fixed assets and AI purchase forecasting are add-ons; the configurator gives the total and the contract fixes it.
How the work runs
We start with a survey: how receiving, shipping, production and month-end close work today, and where the numbers diverge. We describe the process as it is and as it should be, then agree the data model on your real documents. Development goes area by area, most painful first, and each area goes into use as soon as it is ready. You see a working version every two weeks. Before go-live we run a trial migration of balances and reference data with reconciliation, train storekeepers and accountants, and run both systems in parallel until the numbers match. The timeline from 12 weeks is in the contract; every day of delay cuts the invoice by 2%, up to 10% of the contract in total.
Local rails and risks
In Uzbekistan accounting runs on local services: e-invoices go through Didox, statements come from local banks and the books usually live in 1C. An ERP must exchange data with all of them without manual entry. Warehouse and checkout workstations run on Windows without internet and sync when the connection returns; interfaces are in Uzbek and Russian. The main ERP risk is data, not code: a system launched without reconciling balances shows figures nobody trusts in its first month. Systems without access control also open stock and money to every employee. We set roles and permissions by job. Bugs are fixed free with no time limit, and your engineer may audit the code: any unfulfilled item means a 10% refund.