Solution · Integrations
1C integration with websites, online stores and CRMs
Many companies in Azerbaijan keep their accounting, warehouse and pricing in 1C. When an online store, a B2B portal or a CRM is added, the question is always the same: how do products, prices, stock and orders move between 1C and the new system without someone retyping them? We design and build that exchange.
[ 01 ]
In short
In short
- 01
First decide which system is the master for each type of data: products and prices usually in 1C, orders created on the website, customers sometimes in the CRM.
- 02
Exchange can run on a schedule (every few minutes or hours) or in near real time, depending on how fast stock and prices change.
- 03
Standard exchange formats exist for common 1C configurations; custom configurations often need custom work on the 1C side too.
- 04
Every exchange needs logging and alerts, because a silently failed sync means selling stock you do not have.
- 05
A 1C specialist on your side, or one we work with, is usually needed for changes inside 1C.
[ 02 ]
Scope
What is usually exchanged
- Products: names, descriptions, attributes, categories, images where stored.
- Prices: retail, wholesale, price lists per client group, discounts.
- Stock by warehouse or store.
- Orders from the website or portal into 1C, with customer details, items, payment and delivery.
- Statuses back from 1C: confirmed, shipped, delivered, cancelled.
- Customers and contracts for B2B portals, including credit limits and outstanding balances.
- Documents such as invoices, where the portal needs to show them.
How the exchange is built
Direction and ownership
For each data type we agree on the master system. If prices can be edited both in 1C and on the website, sooner or later someone's change will be overwritten. The rule is usually one master per field.
Method
- Standard exchange — many 1C configurations support a standard catalog and order exchange that e-commerce platforms understand.
- 1C HTTP services or OData — 1C can expose an API that the website calls directly.
- An intermediate service — a small application between 1C and other systems that transforms data, queues changes and retries failures. This is often the most robust option when several systems are involved.
Frequency
Catalog content changes rarely and can sync every few hours. Stock and prices change often and may need to sync every few minutes or on each change. Orders should reach 1C immediately.
Monitoring
Each run is logged. If an exchange fails or returns suspicious data — zero stock for the whole catalog, prices missing — the team is alerted before customers notice.
E-invoicing and tax reporting
Companies in Azerbaijan registered for VAT issue electronic invoices (e-qaimə) through the State Tax Service's portal. 1C and other accounting systems may handle part of that workflow. If invoices must be generated from orders placed online, we plan the data flow with your accountant. Background in e-invoicing (e-qaimə) for software.
Several sales channels
When you sell through a website, a marketplace and physical stores at the same time, stock must be shared across all of them. 1C is often the natural central point. See inventory sync and multichannel inventory sync.
What we need from you
- The 1C configuration and version you use, and whether it has been customised.
- Access to a copy of the 1C database for testing.
- Your 1C specialist's contact, or permission to involve one.
- Rules for prices, stock reservation and order statuses.
[ 03 ]
FAQ
Frequently asked questions
Can the website work if 1C is temporarily unavailable?
It should. The website keeps its own copy of the catalog, prices and stock, and orders are queued until 1C is back. That is one reason we prefer an intermediate exchange layer.
How often should stock be updated?
As often as it changes meaningfully. For a store with fast-moving stock, every few minutes; for a slow-moving catalog, hourly may be enough. The goal is to avoid selling items that are already gone.
Do we need to change our 1C configuration?
Sometimes. If standard exchange covers your needs, changes are minimal. Custom fields, special pricing rules or new document types usually need work inside 1C.