1C website integration: how products, prices and orders sync

Обмен сайта с 1С: товары, цены и остатки на сайт, заказы обратно в учёт

The short answer: a 1C website integration moves data in two directions. From 1C to the site go products, specs, photos, prices and stock, and for a B2B portal also customer accounts and their terms. From the site back to 1C go orders, which become accounting documents as soon as they're placed. The catalog syncs on a schedule (hourly in our projects) and on demand, from a button in the admin panel. The rule is simple: prices and stock live in 1C, and the website only displays them. When a sync goes wrong, the cause is usually the data inside 1C, not the code.

A quick note for readers outside the region: 1C is an accounting and ERP platform widely used in Moldova and other post-Soviet countries to run sales, stock and invoicing. If you sell online here, there's a good chance your catalog starts life in 1C.

Below: the mechanics, a WooCommerce or Bitrix module versus an API sync, four of our Moldovan projects, and what to settle before work starts.

What moves, in which direction, and how often

WhatDirectionHow often in our projects
Categories, products, specs, photos1C → siteHourly or on demand
Prices and stock1C → siteHourly
Exchange rates1C → siteHourly (SCOP)
Business customers and their terms1C → siteFour times a day (SCOP), hourly (Flor)
OrdersSite → 1CRight after checkout, as a document in accounting
Stock reservationNot transferred1C does it once the order arrives

Pick the frequency to match how fast your data changes. If prices get reviewed once a week, there's no point pulling them every five minutes. If an item can sell out in a day, agree on the interval up front, before someone orders stock that's already gone.

How the exchange works under the hood

"1C is the only source of prices and stock" is written into the Numina project results, and it should hold for any project. The site calculates nothing on its own: it takes finished data from accounting and sends orders back.

1C can expose that data in three common ways:

  • CommerceML. An XML format that standard 1C configurations and plenty of off-the-shelf store engines understand. Catalog and orders travel as files.
  • OData. 1C's standard REST interface. You switch it on in settings, without changing the configuration, but the data comes out exactly as it's stored in accounting.
  • HTTP services. A custom API built inside the 1C configuration. A 1C developer has to write it, but the site gets exactly the data it needs.

We build the exchange through an API on the 1C side. Which data moves and how often is agreed with your 1C developer at the brief stage. They know the configuration, we know the website.

Then there's timing. Catalog, prices and stock are easiest to pull on a schedule: once an hour the site asks 1C what changed. Orders are better sent on an event, the moment a customer checks out, so the sales team isn't waiting for the next hourly run. You also want a "sync now" button: you update prices before a promotion, press it, and skip the wait. A full sync of the Flor catalog, 940+ products and 150 customers, takes about 10 seconds.

Off-the-shelf module or API sync

Bitrix ships with a built-in 1C exchange, WooCommerce has plugins for it, and both usually run on CommerceML. With a standard configuration, one price for everyone and a plain catalog, that route can be the cheapest. If you already run Bitrix and the sync isn't failing, rebuilding your site just for the integration makes no sense.

A ready-made module starts getting in the way once your business stops being standard. Every dealer has their own price list. A customer orders under several legal entities. Your 1C configuration has been customized with extra fields, and orders must land in accounting as a specific document type. The module piles up patches, and every engine update means checking whether the sync survived.

We build websites and stores on our group's own platform (Garm CMS, with stores on Garm Ecom) and connect them to 1C through an API. The sync doesn't depend on a third-party plugin, platform updates don't wait on anyone outside, and under a support contract your 1C syncs are monitored alongside site uptime.

Four projects: what moves between the site and 1C

Hansa: a catalog without a cart, synced every hour

Hansa is a European home appliance brand. In Moldova it sells through partner stores, so the brand site takes no orders and the sync runs one way. Every hour, categories, products, stock, photos and specs arrive from 1C over an API, and the catalog pages and sitemap refresh on their own. An edit in 1C reaches the site within an hour at most.

A detail few people plan for: filter URLs use a word, not a 1C attribute ID, so renaming a spec in 1C doesn't break links.

Numina: 2,900 items and two alphabets

The Numina catalog holds more than 2,900 furniture hardware items, and names in 1C are typed however someone felt like it, with Latin and Cyrillic letters mixed together. Look-alike characters get normalized both on import from 1C and in the search query. So "ABS" turns up even if 1C has it spelled with a Russian letter. Products, prices, stock and specs come from 1C, and editors only add copy and banners.

SCOP: a dealer's order becomes a 1C document on the spot

The SCOP portal serves a distributor's dealers and lists more than 1,900 items. Products, stock, prices and exchange rates update every hour, customer accounts four times a day. A dealer sees prices from their own price list in its currency, orders by code and quantity or uploads a file, and the order creates a document in 1C. 1C handles the stock reservation itself. It took 10 weeks from first commit to launch.

Flor: a full sync in 10 seconds

Flor.md sells houseplants wholesale, and each buyer type gets its own price. Categories, products and customers come from 1C every hour or at the click of a button in the admin panel, and every run is logged. Buyer accounts are created from 1C switched off, and a manager turns them on. Being a customer in 1C doesn't automatically mean you should see wholesale prices yet.

What happens when a sync breaks

Someone restarts 1C mid-export, the connection drops, a product gets entered without a price. What matters is who finds out first: you, from monitoring, or a customer who just bought something that isn't in stock.

On our side every run is written to a log, an interrupted run picks up again on its own, and the failure shows up in monitoring. Support starts at €250 a month and covers monitoring of 1C syncs along with site uptime and queues.

Six questions to answer before you start

  1. Which 1C do you run, and who looks after it? You need someone who knows the configuration: an in-house developer or the contractor who maintains your 1C.
  2. What needs to reach the site? Just prices? Stock, specs, photos too? Photos and descriptions often aren't in 1C at all, so decide where they'll be managed.
  3. Should orders go back to accounting, and as what document? Catalog only and catalog plus orders are different amounts of work and different quotes.
  4. One price for everyone, or a price per customer? If it's per customer, customers come from 1C and the site needs accounts. At that point you're looking at a B2B portal.
  5. How often do prices and stock change? That decides the sync schedule.
  6. What shape is your data in? Duplicates, empty specs and mixed alphabets will show up on the site within the same hour as everything else.

Mistakes we keep seeing

Leaving 1C for later. The storefront gets designed first, and someone remembers accounting a week before launch. In an online store, most of the time and money goes into the link with accounting, not the storefront.

Prices in two places. The sync works, but a manager still edits a price on the site out of habit. An hour later the sync overwrites it, and a customer has already seen a different number. Prices get edited in 1C. Full stop.

Messy accounting data. The site faithfully shows whatever is in 1C. If one spec goes by three names and product names mix alphabets, search and filters will stumble. We clean some of it on import, as for Numina, but fixing it in 1C is cheaper.

A sync with no log. Then it's a customer who tells you prices haven't updated in a week.

"Sync everything." If the site only needs a price list, don't order orders, customers and exchange rates on day one. Start with prices and stock and add the rest when you actually need it.

What a 1C integration costs

We quote a standalone 1C integration after a brief and don't put a "from" figure on it. It can be a single price feed or ten data streams with orders and customer accounts, and the scope differs several times over.

When the sync is part of a bigger project, here are the starting points: an online store with catalog, prices and stock from 1C starts at €5,000, and a B2B portal where orders land in 1C as documents starts at €10,000. Prices exclude VAT, and the exact figure goes into the contract after the brief.

What moves the quote most:

  • how many data streams there are and in which direction (catalog only, or orders back as well);
  • how many price types and buyer types you have;
  • whether site accounts need to be created from 1C customer records;
  • whether partners pull your catalog through an API;
  • how clean the data in 1C is.

For what's included, see our 1C integration and API page.

Want to know what a sync with your 1C would cost? Tell us which configuration you run, how many items you have and what needs to go to the site and back. We'll tell you which exchange method fits, what we'll need from your 1C developer, and show you a similar project. Phone +373 79 97 3000, email info@webx.md, or use the form on our contacts page.


FAQ

Do we need a 1C developer on our side?

Yes, or the contractor who maintains your 1C. We build the exchange through an API on the 1C side and agree which data moves and how often with someone who knows your configuration. We start that conversation at the brief.

How often do prices and stock update on the site?

As often as the business needs. In our projects products and prices update every hour and customer accounts several times a day, and you can trigger a sync manually too. On the Hansa catalog, an edit in 1C reaches the site within an hour at most.

What happens if a sync fails halfway?

The run is written to the log, the interrupted sync resumes automatically, and the failure shows up in monitoring. If your site is on our support plan, the 1C sync is monitored along with site uptime.

Does a small online store need a 1C integration?

Not always. The XOXO cosmetics store has 430+ products from 48 brands, and the owner manages the catalog herself in the admin panel. A 1C sync makes sense once products and prices already live in accounting and copying them over by hand gets slow and error-prone.

Can outsiders see dealer prices?

No. On Flor a single server-side mechanism calculates the price, and the dealer figure never reaches a guest, not even inside the page data. On our portals a guest sees the retail price or no price at all.

All postsDiscuss a project

Read also

  1. 8 min read

    Business website, online store or B2B portal: what your business actually needs

    The short answer: a business website is right when customers call or write to you before they buy. An online store is right when people pick a product and pay for it on their own. A B2B portal is right when you sell to other companies, every customer has their own prices, and orders have to land straight in your accounting system (in Moldova that's usually 1C). Most mistakes happen before development starts, at the choosing stage: a store gets built for a business that sells over the phone, and dealers stay in spreadsheets for years.

  2. 15 min read

    How to choose a CMS for your website or online store in 2026

    There is no best CMS for everyone. For a blog or a small business website, WordPress is usually enough.

  3. 14 min read

    How to choose an ERP system for a business in Moldova

    If you're choosing an ERP system for a business in Moldova, there's no single best option, but the choice usually comes down to five: 1C:UNF, 1C:ERP, SAP Business One, Microsoft Dynamics 365 Business Central and Odoo, plus custom development.

Fill in the brief

Leave a request or contact us directly

Project type
Budget
Tell us about your project
Contact details

Give us a phone number or an email — at least one.