In Kyrgyzstan, as across the region, many companies keep their records in 1C, a widely used accounting and trade system: products, prices, stock, sales, bookkeeping. When a website, online store, CRM or app comes along, the first question is how to avoid moving data by hand. Below: what usually moves between 1C and other systems, how often, who is responsible for what, where problems arise and what drives the price.
Why connect a website or CRM to 1C
Without an integration someone enters the same product, price or order twice: in 1C and on the website. That costs staff time and causes errors: the website shows a product that sold out long ago, the price on the site is out of date, an online order was never entered in 1C.
An integration solves three things:
- The same data everywhere. Prices and stock change in 1C and reach the website, the app and the CRM on their own.
- Orders without manual entry. An order from the website or app appears in 1C straight away, where the warehouse picks it and accounting records it.
- The full picture of a customer. A manager in the CRM sees the purchase history stored in 1C.
What data usually moves
Most often the exchange looks like this.
From 1C outward:
- the catalog: products, groups, SKUs, attributes like size and colour;
- prices, including separate retail and wholesale prices;
- stock by warehouse and store;
- order statuses: picked, shipped, paid.
From the website, CRM or app into 1C:
- orders with items, prices, delivery and payment method;
- new customers and their contacts;
- payments, if the customer paid online. How to set up payments: online payments in Kyrgyzstan.
Photos, customer-facing descriptions and search texts are usually not kept in 1C. They live on the website, and only what relates to accounting is taken from 1C.
How often to update data
The exchange does not have to run constantly. A sensible setup for most businesses:
| Data | How often |
|---|---|
| Orders into 1C | Right after checkout |
| Stock and prices | Every 5–15 minutes or hourly |
| Catalog and attributes | Daily or on demand |
| Order statuses | Every few minutes |
Real-time exchange is needed when stock is low and sells out fast, for example during sales. Otherwise updating every few minutes is enough, and it costs less.
How the exchange works
The details matter mostly to developers, but a few things are useful for a business owner to know.
- The standard exchange for online stores. The trade editions of 1C include a ready-made exchange with websites. If your 1C is standard, this is the fastest route.
- A custom exchange. If your 1C has been customised or you need to send something the standard exchange does not cover, a 1C programmer sets up an exchange for the task and the website or CRM developer connects to it.
- Where 1C runs. 1C often sits on a computer or server in the office. Then you need to decide how the website will reach it, or make 1C push data out on its own. If 1C runs in the cloud, this is usually simpler.
A good integration starts with an agreement on which system is the source of truth for each kind of data. Prices live in 1C, descriptions live on the website, orders are born on the website and then live in 1C.
Who is responsible for what
An integration almost always involves two parties:
- A 1C programmer — your in-house specialist or the company that services your 1C. They are responsible for what 1C sends and accepts.
- The website, CRM or app developer — responsible for how the data gets into the system and is shown to customers and staff.
Without an agreement up front, each side will assume the problem is on the other. So before work starts, write down the exchange format, the frequency, what to do on errors and who checks the exchange after 1C updates.
Common problems
- Messy reference data. Duplicate products, empty SKUs, different spellings of the same thing. An integration carries that mess onto the website, so the reference data often has to be cleaned first.
- Product variants. One product in five sizes and three colours can be set up in 1C in different ways. Decide in advance how to show it on the website.
- 1C updates. After an update a customised exchange sometimes stops working. It needs a check after every update.
- Silent failures. The exchange broke overnight and nobody noticed for a week. An integration needs a log and an alert to the person in charge when an exchange fails.
How much a 1C integration costs
The price depends on several things:
- whether data moves one way or both;
- how many kinds of data move: just the catalog and stock, or also orders, customers and payments;
- whether your 1C is standard or customised;
- how clean the reference data is;
- where 1C runs and how to reach it.
A simple export of the catalog and stock to the website costs far less than a two-way exchange of orders, payments and customers. At NOVO we price the integration as part of the project: a website or web service, a CRM or a mobile app. We give an accurate estimate after looking at your 1C and your data.
How an integration affects the overall CRM budget: how much a CRM costs.
How to prepare
- List the data — what should go out of 1C and what should come in.
- Decide which system is the source of truth for each kind of data.
- Introduce your 1C programmer to the developer before work starts.
- Clean up the reference data: duplicates, SKUs, units of measure.
- Agree on a check after 1C updates and put it in the support contract.
In short
- An integration removes double entry: prices and stock come from 1C, orders go into 1C.
- Orders move instantly, stock and prices every few minutes, the catalog once a day.
- Two people do the work, a 1C programmer and the website or CRM developer, and they need to agree on the format in advance.
- The main risks are messy reference data, 1C updates and failures without alerts.
- The price depends on the amount of data, the direction of the exchange and how standard your 1C is.