Загрузка…
1C, the website, the CRM, the warehouse and the marketplaces exchange data on their own. Nobody exports a file to import it somewhere else, and no figure exists in two versions at once.
from20 000₽
The total depends on how many systems are being connected, whether they have a usable API, and which way the data flows: a standard one-way exchange is several times cheaper than two-way sync with conflict resolution
A lower bound, not a final price. We work out the exact sum after breaking the problem down and fix it before the work starts.
A list of work, not a description of an approach. The scope is adjusted to the job: anything unnecessary comes off and anything missing goes on at the estimate stage.
Items, stock, prices, documents and settlements move between 1C and the other systems automatically.
Requests from the website land in the pipeline immediately, with every field and the source intact, instead of being copied over by a manager.
Acquiring and payment providers on the merchant side: payment, refunds, reconciliation of incoming funds.
Ozon, Wildberries and other platforms: orders, stock and prices stay in sync with the accounting system.
MoySklad, delivery services and shipment statuses inside one loop, with no manual reconciliation.
If the external system is unavailable, nothing is lost: the exchange queues up and retries, and the person responsible is notified.
Tick the work you need and see the order of magnitude. The estimate goes along with your enquiry.
| Include in estimate | Work | Price |
|---|---|---|
| System review and exchange designWhat connects to what, which data flows which way, and who owns each field. | 30 000–275 000₽ | |
| Standard exchange, built-in methodWhere the systems have a native exchange format and it closes the job: catalogue export, website leads into CRM. | 30 000–375 000₽per system | |
| One-way exchangeData travels in one direction under its own rules: leads into CRM, stock from 1C to the website. | 55 000–550 000₽per system | |
| Two-way exchangeBoth systems read and write. More expensive than one-way: conflict resolution rules are required. | 110 000–1 100 000₽per system | |
| A system with no APIExchange through files or straight into the database, when no native method exists. | 85 000–1 050 000₽per system | |
| MarketplaceOzon, Wildberries and similar: orders, stock, prices. | 30 000–4 500 000₽per platform | |
| Accepting paymentsAcquiring on the merchant side: payment, refunds, reconciliation of incoming funds. | 20 000–950 000₽ | |
| Handling exchange failuresQueue, retry and a notification to the owner when the other system is down. | 50 000–425 000₽ | |
| An exchange control panelA screen showing completed and stuck exchanges, with manual retry. | 90 000–650 000₽ |
This is an order-of-magnitude estimate, not a costed quote and not an offer. Bundled together, some work gets cheaper and some gets more expensive depending on the specifics: the exact sum is worked out after we break the problem down, and it is fixed before the work starts.
Verifiable facts instead of claims about ourselves. There is not a single invented case in this catalogue.
Exchange with 1C, Bitrix24, amoCRM, MoySklad, marketplaces and payment providers. The technology register is on the Technology page.
An integration counts as delivered not when the data goes through once, but when the exchange survives the other system being down.
The other system has no API.
The only option left is imitating a person in someone else's interface, and that link breaks with every update on their side. We will tell you before work starts.
Tell us what is happening now. We reply within one business day, and the first conversation commits you to nothing.