1C integration
NDDev connects 1C with your website, CRM, marketplaces and warehouse software, so orders, stock, prices and payments reach the right system on their own. We build the exchange on queues with a log of every operation and agree the field mapping with your accountant. 1C is among our most frequent integrations, and our team has 100+ projects behind it.
Who it is for
Retailers, distributors and manufacturers who keep their books in 1C while orders arrive from a website, a CRM or marketplaces and get retyped by hand.
- Website, CRM and marketplaces linked to 1C
- Orders, stock, prices and payments
- A log of every exchange
- Automatic retry when a link drops
What the exchange will carry
The work starts with a mapping table: which 1C field holds the item, price, stock level, counterparty and order status in each connected system. We sign the table off with your accountant or 1C administrator and later test the result against it.
- catalogue, prices and stock from 1C to your website
- orders from the website and marketplaces into 1C, with their statuses
- deals and counterparties synced both ways between 1C and your CRM
- payment statuses from Kaspi and other payment providers
- exchange on a schedule or on events, through an API or files
- an operations log and failure alerts in Telegram or by email
- the exchange source code and a description of the data flows
We write the exchange as a separate service in Python and FastAPI. Every message goes through a queue, gets an entry in the log and is retried with a growing pause when 1C or the other system is briefly unavailable. An order that arrives twice is recognised by its key and enters the books once.
How we connect 1C
The exchange runs on a copy of your database first and moves to the live 1C only after acceptance.
Review of your books
We look at your 1C configuration, its reference lists and the documents created on a sale, a payment and a shipment.
Field map
We draw up the mapping table and rules for edge cases: a new item, a deleted item, a partial payment.
Exchange on a copy
We run the service on a test copy, replay real orders from past months and check the result with your accounts team.
Switch to live
We turn the exchange on for the live 1C, set up alerts and hand over the log and the data flow description.
Common questions about 1C integration
Will it work with our 1C configuration?
We build the exchange around the configuration you run. At the first review we look at its reference lists and documents and tell you how best to connect them: through an API, scheduled exports or file exchange.
How often will stock update on the website?
We pick the frequency for the task: stock and prices can go out on a schedule, and orders can reach 1C right after checkout. The more often the exchange runs, the more load it puts on the database, so we agree the interval with your administrator.
What happens when 1C is down?
Messages wait in the queue and go through as soon as the database answers again. Every operation stays in the log, and a long outage triggers an alert.
How much does 1C integration cost?
Where the work starts is shown in the price block. From there three things move the price: how many systems we link to 1C, how large the reference lists are and whether data flows both ways. The final price and timeline go into the specification, and the specification itself is part of the project price.
Can you connect 1C to Bitrix24 or amoCRM?
Yes, it is a common request. Deals, counterparties and invoices sync both ways, and the sales manager sees the payment right in the deal card.
from $1,200
- Free warranty
- 10 days
Prices are starting prices for information only and are not a public offer. The final price is fixed in the specification.
Integrations
Related
Tell us what your team still types into 1C by hand
Describe the systems you use and where the time goes. We will propose an exchange scheme and give you a price.
We reply within 24 hours