1С/BAS ↔ WooCommerce integration

Catalogue, prices and stock from 1С/BAS go to the WooCommerce shop, orders from the shop come back as customer orders in 1С/BAS, and statuses return to the buyer

The shop runs on WooCommerce, the accounting on 1С/BAS, and between them an operator copies orders by hand and updates stock once a day. Sold-out items keep selling, prices on the site lag behind the price list, and the buyer calls to ask where the parcel is. The 1С/BAS ↔ WooCommerce pair makes 1С/BAS the source for the catalogue, prices and stock, turns every shop order into a customer order in 1С/BAS the moment it is placed, and sends the order status back to the shop. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.

Request an integration System page: 1С/BAS →System page: WooCommerce →

What moves between the systems

1С/BAS → WooCommerceItems from the 1С/BAS catalogue are created or updated in the shop as products with name, description, category, attributes and the photo from the item card.
1С/BAS → WooCommerceThe chosen price type from 1С/BAS is written to the shop on a schedule, so the shop price and the price list are the same number.
1С/BAS → WooCommerceStock balances by the agreed warehouses go to the shop's stock field: an item that ran out becomes «out of stock» or «on backorder» without anyone touching the site.
WooCommerce → 1С/BASA new shop order arrives in 1С/BAS the moment it is placed as a customer order with items, quantities, delivery and payment details, and the counterparty found by phone or created anew.
WooCommerce → 1С/BASOrder edits and cancellations in the shop update the same document in 1С/BAS, so the warehouse does not assemble an order the buyer already cancelled.
1С/BAS → WooCommerceThe order status from 1С/BAS («assembled», «shipped», with the tracking number) is written back to the shop order, and WooCommerce sends its usual notification to the buyer.

What we connect

We look at the shop: WooCommerce version, which plugins add fields to products and orders, how variations and delivery are set up; this decides what exactly is mapped.
In WooCommerce the administrator creates a separate key for the exchange under a dedicated user with read-and-write rights; the key can be revoked at any time.
We subscribe to shop events for orders, so a new or changed order is delivered to the exchange immediately, and each delivery is checked by its signature before anything is written to 1С/BAS.
On the 1С/BAS side we use the open exchange interface the platform builds itself, under a separate user with rights to read the catalogue and create orders.
We map the catalogues: which 1С/BAS item is which product or variation in the shop, which price type and warehouses go to the shop, and which shop statuses match which 1С/BAS statuses.
We test on a copy of the shop with a handful of products and test orders, compare with the accountant, and only then switch the exchange to the live shop.

Automation scenarios

Sold-out item keeps selling

Before the last unit left the warehouse at noon, the shop sold three more by evening, and the manager wrote apologies.

After a zero balance in 1С/BAS switches the product to «out of stock» in the shop within minutes.

Orders re-typed into 1С/BAS

Before the operator opens each shop order and types it into 1С/BAS, mixing up a quantity once a week.

After the order appears in 1С/BAS as a document with the same items and quantities the buyer chose, before the operator has seen it.

«Where is my parcel?»

Before the buyer calls or writes because the shop still says «processing» two days after shipping.

After the status and tracking number from 1С/BAS reach the shop order, and the buyer gets the shop's own «shipped» notification.

New products added twice

Before a new item is entered into 1С/BAS and then again into the shop with a different name, so the two never match.

After the item is created in 1С/BAS once and appears in the shop with the same code, name and photo.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

The official BAS support portal documents its integration technologies under the title «Технології інтеграції 1С:Підприємства 8.3» — BAS is built on the 1C:Enterprise 8.3 platform.
Source: its.bas-soft.eu ↗ checked 2026-09-25
According to the same documentation, the platform automatically builds a REST interface using the OData protocol, through which outside systems can read, change, create and delete data over HTTP.
Source: its.bas-soft.eu ↗ checked 2026-09-25
WooCommerce 2.6 and newer is fully integrated with the WordPress REST API: store data can be created, read, updated and deleted through JSON requests using standard HTTP verbs.
Source: developer.woocommerce.com ↗ checked 2026-09-27
API keys are tied to a specific WordPress user and follow that user's roles and rights; each key has a read, write or read-and-write level, and if the user is deleted the key stops working.
Source: developer.woocommerce.com ↗ checked 2026-09-27
WooCommerce can send webhook notifications each time orders, products, coupons or customers are added, edited or deleted, when purchases are made, and on other events; the delivered webhook carries a hash made from a secret key in its request headers.
Source: woocommerce.com ↗ checked 2026-09-27
WooCommerce automatically disables a webhook after more than five consecutive delivery failures, and keeps a log of every event that fired a webhook so delivery and the receiving server's response can be checked.
Source: woocommerce.com ↗ checked 2026-09-27

Limits

The limits come from both systems. Orders arrive as events from the shop, but prices and stock go to the shop in batches at an interval, not on every change in 1С/BAS. A shop built on the old removed interface needs the separate legacy plugin or a move to the current one first. If our server does not answer, WooCommerce retries and after several failures switches the event off; the exchange watches for this and reports it, so a missed order is picked up on the next pass rather than lost. 1С/BAS is on the official prohibited software list: we do not take projects for state bodies, critical infrastructure or systems with state data, and with private businesses we discuss the risk openly.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

Which side is the master for products: the shop or 1С/BAS?

Usually 1С/BAS: items, prices and stock are kept there, and the shop shows them. Descriptions and photos can be the other way round if the content team works in the shop; we agree on this per field at the mapping step.

We have product variations (sizes, colours). Do they work?

Yes, if 1С/BAS keeps them as characteristics of the item or as separate items with a common parent. Each variation gets its own stock and price; we check how your catalogue is structured at the first step.

What if 1С/BAS is switched off at night?

Orders placed at night are kept by the exchange and written to 1С/BAS as soon as it is reachable again, in the order they came in. Nothing is lost and nothing is written twice.