1C ↔ website integration

1C ↔ website is the setup of data exchange between your 1C and the website: products, attributes, prices, stock and orders move between the systems automatically. You add items and change prices in 1C — they are pulled to the website; a customer places an order on the website — it lands in 1C as a document. We set up the exchange via the standard protocol (CommerceML / website exchange) or via an API, define a schedule or event-based exchange, product-matching rules and error handling. The point is to keep your accounting in one place (1C) and not re-enter data on the website by hand, where it is easy to make a mistake and forget. Importantly and honestly: almost every 1C is unique. Configurations are often customized for the business, so “connect it in an hour” does not happen — first we look at your configuration, version (UT, UNF, Roznitsa, KA, ERP or a custom one) and how your products are set up; the timeline and the price depend on that. Also honestly about synchronization: data can conflict — for example, the price in 1C and on the website have diverged. You need to decide in advance who is “the boss” for each field (usually 1C is the source of prices and stock, the website is the source of orders), otherwise the exchange will overwrite what you need. We talk these rules through and set them up rather than leaving it to chance. And about reliability: the exchange depends on 1C being available and published (often via a web server or an exchange service — that is, 1C has to run as an accessible server, not just “click export”); if 1C is on a local computer that is turned off at night, the exchange will stall — we will advise how to set this up properly. We set up access to 1C for the exchange with security in mind: exposing it to the open internet is not required — a protected channel or VPN, with limited rights for the exchange. And honestly about scope: if you have a dozen products that change once a month, a full exchange may be excessive — sometimes a manual upload is enough, and we will say so. An exchange is justified when the catalog is alive: hundreds or thousands of items, prices and stock change often, orders come in a stream. Picture this: a manager changes a price in 1C, a few minutes later it is on the website, and an order from the website is already in 1C as a ready document — without manual transfer. The base price starts from 50,000 ₽; it depends on the 1C configuration, the catalog size and what is synchronized.

• Products, prices and stock are re-entered on the website by hand — slow and error-prone.
• The website shows one price, 1C another — the data diverges and clients see outdated info.
• Orders from the website are transferred to 1C by hand — they get lost and processed late.
• Stock does not match — you sell what is no longer in the warehouse.

• Exchange of products, attributes and categories 1C → website
• Synchronization of prices and stock on a schedule or by event
• Passing orders from the website to 1C as documents
• Product-matching rules and conflict resolution (who is “the boss”)
• Setup of 1C publishing (web server / exchange service)
• Error handling and notifications about exchange failures
• Accounting for your configuration (UT/UNF/Roznitsa/KA/ERP or customized)
• Documentation and (by agreement) support of the exchange

• Accounting in one place — you keep 1C, the website updates itself
• Prices and stock on the website are current — fewer errors and returns
• Orders land in 1C right away — faster processing, nothing is lost
• Less manual work and human error

• We look at your 1C (version, configuration, how products are set up) and the website
• We design the exchange: what, where, how often, who is “the boss” per field
• We set it up, test on real data, launch and support the start

• Our 1C is customized — is that harder?

  Often yes, but that is normal: almost all working 1C installations are customized for the business. So we do not promise to “connect it in an hour”; first we look at your configuration and version (UT, UNF, Roznitsa, KA, ERP or a custom one) and how the catalog is set up. The timeline and price depend on that — we will estimate honestly after a review, not at random. If the configuration is custom-built or heavily modified, the timeline and cost can differ significantly — we discuss that right after the review, with no surprises later.

• What happens if the data in 1C and on the website diverges?

  That is a typical situation, and it must be solved in advance, not at the moment of a failure. We agree who is the “source of truth” for each field: usually 1C is the boss for prices and stock, and the website for orders. Then the exchange does not overwrite what you need. Without such rules any synchronization will sooner or later overwrite something important — so we build them in from the start.

• Do we definitely need automatic exchange?

  Not always. If you have a dozen products and prices change once a month, a manual upload may be enough — and we will honestly say so. Automatic exchange pays off when the catalog is alive: many items, frequent changes in prices and stock, a stream of orders. Then manual transfer is more expensive and more error-prone than a configured exchange.