What is exchanged and how often

Not everything needs real-time synchronisation. Frequent exchange of large catalogues loads both the site and the accounting system.

Stock levels

Every 10 to 15 minutes, from 1C to the site. Most often to avoid selling something that is no longer in stock.

Prices

Several times a day, from 1C to the site. They change less often than stock levels, so frequent exports are unnecessary.

Catalogue and specifications

Once a day, at night, from 1C to the site. A heavy export puts noticeable load on the accounting system.

Orders

Immediately after checkout, from the site into 1C. Sales staff must see the order immediately, in the interface they are used to.

Statuses and payments

Every 15 minutes, from 1C to the site. The customer sees the order progress in their account.

More than half of data exchange problems are not technical, they are about the data itself. Duplicate products, mismatched units of measure, missing SKUs and categories invented on the fly. That is why we always review the 1C reference data before integrating: sometimes tidying it up is cheaper than writing a handler for the mess.

How we connect it

The exchange is first run on a copy, not straight on the live database. A sync error in the live catalogue costs more than a couple of days of preparation.

01

Reference data review

We review the product list, units of measure, warehouses and price types, and record what needs tidying up before the start.

02

Matching rules

We agree what counts as a unique product, which prices are exported and what to do with out-of-stock items.

03

Exchange on a test copy

We run the full cycle on a copy of the database and a staging site, checking the order flow from cart to receipt.

04

Switching to live operation

We switch to live data, set the schedule and exchange error alerts, and watch it for the first week.

Frequently asked questions

Usually yes, but the scope depends on the version and on how heavily the configuration has been customised. A standard configuration exchanges data almost out of the box, while a heavily modified one needs a bespoke handler. At the start we look at the database and give a definite answer.

The site keeps running on the last data it received and we get an error alert. Orders accumulate on the site and go into 1C once the exchange is restored, so nothing is lost.

If you sell only online, a cloud POS is enough: it generates and sends receipts with no hardware in the office. A physical till is needed when you take cash or settle payments at the point of sale.

Yes, that is the whole point of the integration. Stock is deducted in the shared system regardless of where the order was placed. We also configure reservations so the same last item is not sold on two marketplaces at once.

We will quote the integration

Tell us which 1C you run, where you sell and what you currently do by hand. We will estimate the scope of work and the timeline.