1C Integration with Website, CRM and Other Systems
We connect 1C with your website, online store, CRM, bank, Kaspi and mobile app. Products, stock, prices, orders and customers flow automatically, on a schedule or the moment an event happens, with no person in the middle.
- 1C data exchange on a schedule or instantly on an event
- Standard OData or a custom HTTP service inside 1C
- Exchange log and an alert if something fails to arrive
- The standard configuration stays on vendor support
1C integration with a website or another system starts at 350,000 tenge and takes from two weeks. A two-way exchange of products, prices and orders usually takes three to six weeks.
What 1C integration gives you
Data is entered once and then spreads to every system on its own.
When 1C is not connected to your website, CRM and marketplaces, the same data is entered several times. A manager copies an order from the website into 1C, a content manager edits stock on the website by hand, an accountant posts bank payments. Every manual step costs time and produces errors: selling an item that is out of stock, a wrong price, a lost order.
1C integration removes that layer. 1C stays the single source of truth for products, prices and stock, and external systems get an up-to-date picture automatically. In the other direction, orders, customers, payments and statuses flow back into 1C.
Another effect is less visible but important: the argument about which number is right disappears. When stock on the website, in the CRM and in the manager's report comes from one place, the conversation moves from reconciling to decisions: what to reorder, what to discount, where money is leaking.
The first thing people notice: staff stop reconciling spreadsheets, and management sees real sales from every channel in 1C instead of yesterday's data.
What we integrate 1C with
The main 1C data exchange directions for companies in Kazakhstan.
| System | What we transfer | Direction |
|---|---|---|
| Website and online store | products, prices, stock, orders, customers | both ways |
| Kaspi and marketplaces | stock, prices, orders, statuses | both ways |
| CRM (Bitrix24, amoCRM and others) | counterparties, deals, invoices, payments | both ways |
| Bank | statements, payment orders | both ways |
| Mobile app | catalog, stock, orders, cashback | both ways |
| Telegram and WhatsApp | notifications, daily totals, order statuses | from 1C |
| Another 1C database | catalogs, documents | both ways |
Some directions have dedicated pages: 1C Kaspi integration, 1C bank integration, 1C and Bitrix24 exchange (in Russian). Mobile apps and bots that work with 1C are built by our team at Applications.kz.
1C integration with a website and online store
The most common task, and the most common reason for selling items that do not exist.
Integrating 1C with a website starts with deciding which system owns what. Usually products, prices and stock live in 1C, while descriptions, photos and SEO texts live on the website. We split the fields so the exchange never overwrites the content manager's work.
For large catalogs, the speed of the first load matters too. A full export of tens of thousands of items with attributes and photos runs in batches, and after that only changes are sent: a new product, a changed price, a stock movement. That keeps the exchange within minutes even for a big assortment.
Products, attributes, prices by type and stock by warehouse go from 1C to the website. Orders with their contents, delivery and payment method, plus new customers, come from the website into 1C. An order status changed in 1C goes back to the website, and the buyer sees it in their account.
Prices get special attention. 1C often has several price types: retail, wholesale, dealer, promotional. Website integration sends the right type to each customer group, so after logging in a wholesale client sees their own prices, not retail ones. Discounts and promotions calculated in 1C match on the website to the tenge.
We work with websites on 1C-Bitrix, WordPress and WooCommerce, OpenCart, Tilda and custom engines. If there is no suitable exchange module for the engine, we write one and hand over the source code with documentation. For custom websites we build, we design the exchange from day one so nothing has to be redone later. How stock synchronization works is explained in 1C integration with an online store (in Russian).
How 1C data exchange works: three approaches
The approach determines the speed, reliability and price of the integration.
Standard OData interface. Built into the 1C 8.3 platform, it exposes data over REST with no programming inside 1C. It suits reading: catalog, stock, prices. Fast to launch, from 350,000 ₸ in 2-3 weeks. The downside: the external system has to know the internal structure of the configuration.
A custom HTTP service inside 1C. We write an entry point in the 1C language that sends and receives data in the JSON format you need. The external system works with a simple, stable API, while all validation logic stays in 1C. This is the main approach for two-way exchange. More on the 1C API page.
File exchange and standard formats. XML or CSV exports on a schedule, the EnterpriseData universal format for exchange between 1C databases, and the 1CClientBankExchange format for banks. Reliable and simple where instant transfer is not required.
A comparison of OData and HTTP services with examples is in 1C website exchange: OData or HTTP services (in Russian).
1C integration stages
The same order for any system, from a website to a bank.
- Data map. Which objects we transfer, in which direction, which system is the source of truth and how often. A single page agreed before any code.
- Catalog matching. Products on the website and in 1C must match by code, SKU or barcode. Duplicates and mismatches often surface here, and we clean them up before the exchange goes live.
- Development on a copy. An HTTP service or exchange data processor in an extension, on a copy of the database, with a test website or the external system's sandbox.
- Initial load. A full catalog transfer and reconciliation: how many items were sent, how many accepted, where the errors are.
- Scheduled launch. A scheduled job or event-driven exchange. For the first week we check the log every day.
- Handover. Exchange documentation, a guide to the error log, contacts in case of failure.
How much 1C integration costs
The price depends on the number of directions, data volume and the state of the database.
| Task | Timeline | Price |
|---|---|---|
| Reading catalog and stock via OData | 2-3 weeks | from 350,000 ₸ |
| HTTP service for one task | 2-3 weeks | from 350,000 ₸ |
| Two-way website exchange | 3-6 weeks | 600,000-1,200,000 ₸ |
| Kaspi or another marketplace | 3-4 weeks | from 600,000 ₸ |
| Exchange with queues and notifications | 6-10 weeks | 1,500,000-3,000,000 ₸ |
| Exchange support | monthly | from 80,000 ₸/month |
We quote 1C integration services in writing after the data map: the estimate shows what each direction costs, so you can start with the most important one.
Integration works well in stages. First a one-way export of catalog and stock, which immediately removes the main pain of editing the website by hand. Then orders flowing into 1C, then statuses and payments. Each stage is paid for and accepted separately, and you see the result before investing in the next one.
What raises the cost: duplicates in catalogs, a modified standard configuration without documentation, a requirement for instant transfer instead of a schedule, multiple warehouses and price types. What barely matters: the number of 1C users.
Exchange reliability: what happens when something fails
An exchange that fails silently is worse than no exchange at all.
The worst scenario: the exchange stopped a week ago and you found out from a customer who bought an item you did not have. That is why every 1C integration we build includes three things.
- Exchange log. Every transfer is recorded: when, what, how many objects, with which error. You can view it right in 1C.
- Retry on error. If the external system is unavailable, data is not lost but sent on the next attempt.
- Alert. If the exchange fails several times in a row, the responsible person gets a message in Telegram or by email.
We also limit the load. A large catalog export must not slow down the accounting team, so heavy operations run in batches during quiet hours while small changes go out immediately. For high-load exchanges we add a queue that smooths out peaks.
For exchanges that sales depend on, we offer support: we watch the log ourselves and fix issues before you notice them.
1C integration with CRM
Sales live in the CRM, accounting in 1C. Connecting them removes double work.
A typical setup: a manager runs a deal in the CRM and issues an invoice, then the accountant creates the same counterparty and invoice again in 1C. Payment arrives in 1C from the bank, and the manager hears about it by phone. 1C CRM integration closes that loop.
A separate question in CRM integration is which system owns the counterparty. If the manager edits details in the CRM and the accountant in 1C, the exchange has to know whose edit wins. Usually document details are kept in 1C, while contacts and communication history live in the CRM. We fix this rule on the data map before development begins.
Counterparties and invoices go from the CRM to 1C; payments, shipments and stock come back from 1C to the CRM so the manager does not sell what is not there. Bitrix24 has its own page, 1C and Bitrix24 exchange (in Russian); amoCRM and other systems are connected through their APIs and an HTTP service on the 1C side.
Companies where integration pays off fastest
The sign is simple: data is copied between systems by hand every day.
Online stores and trading companies with a catalog of several hundred items or more and sales in several channels. Without an exchange, stock on the website and on Kaspi drifts from reality by lunchtime.
Distributors with sales reps and B2B orders. Orders come from the app or customer portal straight into 1C with the client's correct prices.
Companies with several 1C databases, for example retail and a central accounting database, or several legal entities. We set up exchange between databases with standard rules and extend them where needed.
Service and manufacturing companies that receive requests from the website or messengers. A request immediately becomes a document in 1C, and the client gets a status notification without calling a manager.
If manual copying takes an employee at least an hour a day, integration usually pays for itself within a few months on salary alone, before counting the errors.
What makes us different
We build both sides of the exchange, not just the 1C part.
A common problem with integrations: one contractor works on 1C, another on the website, and when something breaks each points at the other. We build websites and mobile apps and also program 1C, so we are responsible for the whole exchange, on both sides.
The second difference: we start with data, not code. Most integration problems grow out of messy catalogs: one product entered three times, half the items without an SKU, duplicated counterparties. We find this during matching and suggest cleaning it up before launch, otherwise the exchange will faithfully copy the mess into every system at once. For large volumes there is a dedicated service: data migration and cleanup in 1C.
We build customizations as extensions, so the standard configuration stays on vendor support. Source code and exchange documentation are handed to the client. The estimate is in writing and before work starts; any prepayment is credited toward the first stage.
FAQ about 1C integration
Exchange methods, timelines and reliability.
How much does 1C website integration cost?
Reading catalog and stock via OData from 350,000 ₸ in 2-3 weeks. A two-way exchange of products, prices and orders costs 600,000-1,200,000 ₸ over 3-6 weeks.
How often is stock updated on the website?
On a schedule from once every 5 minutes, or instantly when it changes in 1C. Instant exchange costs more but is needed where items sell out quickly.
Which systems can be integrated with 1C?
Any system with an API or file exchange: websites, CRMs, banks, Kaspi, marketplaces, mobile apps and other 1C databases.
Which is better: OData or an HTTP service?
OData is faster to launch for reading data. An HTTP service is more reliable for two-way exchange because the validation logic stays in 1C.
Will the exchange break after a 1C update?
We build the exchange in an extension and check it after updates. Under a support plan that is our responsibility, and the log shows right away if something goes wrong.
What happens if the website is temporarily down?
No data is lost: the exchange resends on the next attempt, and after several failures in a row the responsible person gets an alert.
Do you integrate 1C with CRM systems?
Yes: Bitrix24, amoCRM and others. We transfer counterparties, invoices, payments, shipments and stock.
Do you work with companies outside Almaty?
Yes, across all of Kazakhstan. Integration is done remotely; we connect to a copy of the database through access you control.
More 1C services
Related tasks that usually go together.
1C Kaspi integration
Products and stock to Kaspi, orders back to 1C.
1C API
HTTP services, OData and REST API for apps.
1C bank integration
Statements and payments without manual import.
1C and Bitrix24 exchange
Counterparties, invoices and payments between CRM and accounting.
1C developer
Custom 1C development priced per task.
1C support
Exchange monitoring and fixes on a subscription.
Send a request
Describe the task: we reply within one business day and quote before any work starts.