Typical connections
Website and 1C: products, prices and stock go to the site, orders come back to 1C. CRM and 1C: a deal in amoCRM or Bitrix24 becomes an invoice in 1C, and the payment returns to the deal. Bot or Mini App and 1C: customers see real stock and prices. Bank and accounting: statements arrive by themselves and payments are matched to invoices. Payment providers: every payment status reaches its order. Marketplaces: Uzum Market stock and orders stay in sync with the warehouse. Courier services, including Yandex Delivery, receive orders without retyping. Google Sheets and Excel update themselves for teams that live in spreadsheets.
What drives the price
Link is two systems with one-way exchange, for example stock from 1C to the website: start there if one place hurts. Data bus connects up to six systems with two-way exchange, a queue and retries, so 1C, CRM, website, bank and payments behave as one. API platform is a public API for partners with keys, rate limits, documentation and webhooks. Price is driven by the number of systems, the direction of exchange, the volume of reference data and how far your 1C has drifted from the standard configuration: a heavily customised base takes longer to analyse. The configurator gives the total, and the contract fixes it.
How the work runs, and what happens on a mismatch
Week one is analysis: which data, in which direction, how often, and which system is the master for each reference list. That matters more than code: if nobody decides where the truth about a price or stock level lives, systems overwrite each other. We build against a copy of your 1C base, test on real documents and launch. Every exchange is logged: what went out, what came in, what was rejected. With a queue in place, a failed record is retried and the person responsible gets a Telegram alert. You see a working version every two weeks; the timeline from 2 weeks is in the contract, and each day of delay cuts the invoice by 2%, up to 10% of the contract in total.
Local rails and common mistakes
In Uzbekistan integration almost always involves local services: 1C for Uzbekistan, e-invoices through Didox, Payme, Click and Uzum, online cash registers issuing fiscal receipts, and local banks. Three mistakes are typical. The first is a script that exports data on a schedule and fails silently: the website shows last week’s stock and orders never reach 1C. The second is exchange without duplicate protection, so one payment is posted twice. The third is an AI-written integration with 1C passwords in plain code. The exchange log comes with every level; the queue and alerts come with Data bus or as add-ons. Bugs are fixed free with no time limit, and your engineer may audit the code: any unfulfilled item means a 10% refund.