Integrations
1C and Bitrix24 integration
Deals, products, prices and payments move between 1C and Bitrix24 without retyping and without duplicates.
When you need a 1C and Bitrix24 integration
A custom integration makes sense when:
- the process is non-standard;
- a website, a warehouse or a marketplace joins 1C and Bitrix24;
- you need a guarantee that a network failure will not create a duplicate order or payment;
- managers retype orders from one system into the other.
If the process is standard, the data is clean and a discrepancy once every few days is not critical, start with the free 1C Connector (app page in Russian) from 1C-Bitrix. If it covers the task, there is no reason to pay for development.
What moves between 1C and Bitrix24
Deals, products, prices, stock, invoices and payments can be exchanged. Each has its own rules, so start with the one direction that removes the most manual work, for example sending deals to 1C.
Reference data is mapped before launch: products, counterparties, deal and document statuses. If the same field is edited in both 1C and Bitrix24, we agree up front whose edit wins.
How I build it
I start from the process: which system owns each field, who counts as the same customer, and what must never be created twice.
The exchange runs through a separate service backed by PostgreSQL. Every operation gets its own key and is stored before the target system sees it, so if 1C times out and the request is sent again, the order is still created once. Every exchange is logged: what was sent, what was not and why.
Tests run against a real database, and you get instructions and a handover call.
Experience
1C and Bitrix24 integrations are work I do often.
I also worked with the Bitrix24 REST API in an online booking service. It creates contacts and deals with product rows in Bitrix24, looks up contacts by phone to avoid duplicates and syncs the product catalog both ways. Details are in Booking platform connected to Bitrix24.
What such an integration costs and what makes it more expensive is covered in How much a 1C and Bitrix24 integration costs.
Packages
Prices are fixed for the described scope. Larger scope gets its own estimate.
Basic
$250
- One webhook or a one-way exchange, for example deals into 1C
- Log of every exchange
- Instructions and handover
Standard
$600
- Two-way exchange between 1C and Bitrix24
- Retries on failure and duplicate merging
- Log search by order number
Premium
$1,200
- Everything in Standard
- Scheduled reconciliation with a discrepancy report
- Alert when the exchange stops
How we work
From a short message to a working version
- 01
Describe the process
A few paragraphs: which systems, what goes wrong, what the result should be.
- 02
Get the approach and a price
Within 24 hours: how I would build it, the first risk to settle and a fixed estimate.
- 03
See a first working version
On your real data, early, so we correct course before the budget is spent.
- 04
Take it over
Tests, a README and a handover call. Support after launch if you need it.
Questions
Does the exchange need to be real-time?
Not always. An hourly exchange is simpler and cheaper than updates within seconds, so the frequency affects the price.
Does our data need cleaning first?
Yes. Duplicate counterparties and mismatched SKUs have to be sorted out before launch, or the exchange will multiply the errors.
How do we hear about a failure before customers do?
Without an exchange log and a discrepancy report, failures are noticed only through customer complaints. The Premium package adds a scheduled reconciliation with a discrepancy report and an alert when the exchange stops.
What should we send to get a price?
Your 1C configuration and version and whether it has custom changes, whether your Bitrix24 is cloud or on-premise, what data should move and in which direction, how many products, counterparties and deals you have per month, and what is done by hand today.