1C and business system integration 1C integration

1C, your CRM, website, bank and cash registers exchange data on their own instead of through an employee with Excel. Connecting two systems starts from $2,500 and from 2 weeks, and every exchange is written to a log you can open at any time.

Price
from $2,500
Timeline
from 2 weeks

Price and deadline are fixed in the contract before work starts

Colonnade. Glass

What is included

  • 01Exchange with 1C and MoySklad: products, prices, stock
  • 02Connection to amoCRM, Bitrix24 or your own CRM
  • 03Website and online store orders and stock
  • 04Bank statements: payments matched automatically
  • 05Payment statuses from Payme, Click and Uzum
  • 06Didox e-invoices, online cash registers and fiscal receipts
  • 07Exchange log, queue and retries on failure
  • 08Telegram alert when an exchange stops

Who it is for

  • Online stores whose website stock disagrees with the warehouse in 1C
  • Sales teams in amoCRM or Bitrix24 retyping invoices into 1C
  • Accountants matching bank and payment-provider transactions by hand
  • Sellers on Uzum Market and other marketplaces

Three levels and prices

Pick the level that fits the task and budget. The exact scope is assembled in the configurator and fixed in the contract.

Link

Two systems, one-way exchange

$2,500–6,000

≈ UZS 30M · from 2 weeks

Data bus

Up to 6 systems, two-way exchange, queue and retries

$10,000–25,000

≈ UZS 120M · from 6 weeks

API platform

Public API, partner keys, documentation, webhooks

$30,000–70,000

≈ UZS 360M · from 12 weeks

UZS amounts are indicative, at the Central Bank of Uzbekistan rate on 14.11.2026. Contracts are in USD, or in UZS at the rate on the invoice date.

In detail

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.

What the contract says

2%

for every day we are late

If we are late, your invoice drops by 2% a day, up to 10% of the contract. So we only name deadlines we can keep.

1

company per niche per city

For a year we do not take on your competitor in your city. What we build for you does not end up next door.

10%

refund after an outside review

Bring your own engineer. They check the code against the contract. If a contracted item is missing, we refund 10%.

Questions

How much does 1C integration cost?

From $2,500, with a timeline from 2 weeks for a link between two systems with one-way exchange. A data bus for up to six systems with two-way exchange, or an API platform, costs more; the ranges are in the level table above. The exact amount is fixed in the contract before work starts.

How long does an integration take?

A link takes from 2 weeks; a data bus or API platform takes longer, as the table shows. The main variable is how customised your 1C is. You see a working version every two weeks, and every day of delay cuts the invoice by 2%, up to 10% of the contract in total.

Will it work with a localised 1C configuration?

Yes, including 1C for Uzbekistan and customised bases. Before quoting we look at a copy of the base and the list of changes made to it.

Do we need a 1C developer on our side?

Usually not. We need access to a copy of the base and someone who knows what has been customised in it. If a 1C partner maintains your base, we agree changes on the 1C side with them.

Can 1C be connected to Bitrix24 or amoCRM?

Yes, it is one of the most common pairs: a deal becomes an invoice in 1C, payment and shipment return to the deal, and customer and product lists stay in sync.

What happens if the exchange breaks?

Every operation is visible in the exchange log. With the queue and alerts from the Data bus level, failed records are retried and the person responsible gets a Telegram message, so no failure goes unnoticed. Bugs on our side are fixed free with no time limit.

Other solutions

Practice: CRM & ERP