1C Integration
with Your Website
1C (1С:Предприятие) is the ERP and accounting suite that the overwhelming majority of companies across Belarus, Russia, and Kazakhstan run their operations on — and it can talk to your website on its own. Stock, prices, and orders sync automatically. No more manual exports in the evening, and no more calls apologizing that an item was already out of stock after the customer paid.
When you need this
If even one of these sounds familiar, you needed this yesterday.
- Stock shown on the site doesn't match what's actually in the warehouse
- Prices change in 1C, but the website keeps living its own life
- Orders get copy-pasted into the accounting system by hand
- A new product shows up on the site a week after it arrives
- The same product is entered in the database three different ways
- A manager calls customers to say the item they bought is out of stock
What moves between the systems
The exchange, direction by direction
How it's built
There's no such thing as "just set up the sync."
- Format. CommerceML for standard configurations, REST API when you need full control over the logic
- Schedule. Products and prices sync once a day, stock every 15-30 minutes or on every sale
- Queue. If 1C goes offline, data piles up and gets sent once it's back — nothing gets lost
- Identifiers. Matching runs on 1C's internal item code, not the product name — otherwise renaming a product breaks the link
- Logs. Every exchange gets recorded: you can see what went out, what came back, and where it broke
- Load. Syncing shouldn't slow 1C down during business hours — we push the heavy jobs to nighttime
Where it usually breaks
The pitfalls everyone steps on
Beyond the website
The same goes for marketplaces and CRM.
If a system doesn't have a ready-made API, we build one. It's extra work, but it's what makes the connection possible where off-the-shelf modules give up.
- Wildberries and Ozon — the two biggest marketplaces in Russia and Belarus — as one more destination for the same data
- One shared stock count: a sale on the marketplace reduces what's available on the site
- Leads from the site go straight into the CRM, no manual re-entry
- Telephony: an incoming call pulls up the customer's card with their order history
- EDI — electronic document exchange with suppliers and partners
How we work
Audit first, code second.
A standard exchange of products, prices, and stock takes 3-5 days. Add orders, statuses, and documents, and it's a week and a half to two weeks.
- We look at your 1C configuration and whatever custom changes have been made to it
- We check the catalogs: duplicates, units of measure, warehouses
- We map out the exchange schema and sign off on it before writing any code
- We build it in a test environment, not on your live database
- We run it in parallel with your manual process until we're confident it works
- You get the logs and a runbook — what to do if the exchange stalls
Keep reading
Related services
FAQ
Frequently asked questions
How long does a 1C-to-website integration take?
A standard exchange of products, prices, and stock takes 3-5 days. Add orders, statuses, and documents, and it stretches to a week and a half or two weeks. The slowest part is never the code — it's cleaning up the catalogs. As long as the same product is entered three times in 1C, no amount of syncing will fix that.
Which 1C configuration do you need?
We work with the standard configurations: Trade Management, Retail, Small Business, Integrated Automation, and Accounting. We also work with customized configurations — we just start by reviewing exactly what's been changed. Custom-written processing modules built by someone else are usually where the problems come from.
Does the exchange run both ways?
Usually, yes. From 1C to the website: products, prices, stock, attributes. From the website to 1C: orders, customers, payments. Each direction is configured separately — you can keep it one-way if you handle orders some other way.
How often does stock update?
It depends on the schedule. Prices and products usually update once a day — they don't change often. Stock updates more frequently: every 15-30 minutes, or on every sale if you have high turnover. Real-time sync is possible, but it puts more load on 1C, and it's not always worth it.
What happens if 1C goes offline or the connection drops?
The website keeps running on the last data it received, and the exchange queues up and catches up once the connection is back. Orders aren't lost either — they accumulate on the website's side. This is a core design principle: the integration should never take the storefront down along with the accounting system.
Can we sync to marketplaces at the same time?
Yes, and it's a common setup. Wildberries, Ozon, and other CIS marketplaces connect as one more destination for the same data. The hard part isn't the connection itself — it's keeping stock counts from drifting apart between the site and the marketplaces when sales happen on both at once.
Contact
Let's Scope
Your Project.
40 minutes, and you'll know the price, the timeline, and whether it's worth doing at all.
+375 (44) 516-94-93blackpanthersby@bk.ru