CoreviaFlowCOREVIAFLOWDIGITAL PROJECT COMPANY Leave a request
EN UA RU

1С/BAS ↔ WordPress integration

Prices and stock from 1С/BAS go to the WordPress site, orders and form requests from the site come back as documents in 1С/BAS

The site is on WordPress, the accounting is in 1С/BAS, and between them sits an employee who updates prices by hand once a week and copies requests from the site into the accounting system. Prices on the site lag behind the price list, sold-out items keep being ordered, and a request from the contact form can sit in the mailbox for a day. The 1С/BAS ↔ WordPress pair gives both sides one picture: the catalogue, prices and stock on the site come from 1С/BAS, and every order or form request from the site appears in 1С/BAS as an order with a counterparty. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.

What moves between the systems

  • 1С/BAS → WordPressItems from the 1С/BAS catalogue are created or updated on the site as products or catalogue pages: name, description, group and the photo from the item card.
  • 1С/BAS → WordPressThe chosen price type from 1С/BAS is written to the site on a schedule, so the site price and the price list are the same number.
  • 1С/BAS → WordPressStock balances by the agreed warehouses go to the site: an item that ran out is marked «on request» or hidden, without anyone touching the site by hand.
  • WordPress → 1С/BASAn order placed on the site becomes a customer order in 1С/BAS with items, quantities, delivery details and a counterparty found by phone or created anew.
  • WordPress → 1С/BASA request from the contact or quote form on the site is written to 1С/BAS as a customer request or a new counterparty with a note, so it does not get lost in the mailbox.
  • 1С/BAS → WordPressThe order status from 1С/BAS («assembled», «shipped») is shown in the client's account on the site, so the client does not call to ask.

What we connect

  • We look at your site: plain WordPress with a catalogue plugin, or WooCommerce on top of it, and which forms plugin collects requests; this decides where orders and requests come from.
  • In WordPress the administrator creates a separate application password for the exchange under a user with the rights it needs; it can be revoked at any time from the profile.
  • 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 corresponds to which product on the site, which price type and which warehouses go to the site, and what to show when the balance is zero.
  • We set the rhythm: prices and stock go to the site on a schedule (every few minutes to once an hour), orders and form requests are picked up from the site every couple of minutes.
  • We test it on a copy of the site with a handful of items and test orders, compare with the accountant, and only then switch the exchange to the live site.

Automation scenarios

01

Prices on the site are a week old

Before the price list changed on Monday, the site was updated on Friday, and clients ordered at the old price for four days.

After the price type from 1С/BAS is written to the site on a schedule, and the site and the price list show the same number.

02

Orders for sold-out items

Before the item ran out on Tuesday, the site kept selling it until the weekend, and the manager called every client to apologise.

After a zero balance in 1С/BAS marks the item «on request» on the site within minutes.

03

Requests lost in the mailbox

Before the contact form sends a letter to a shared mailbox, and a request from Friday evening is found on Tuesday.

After every form request appears in 1С/BAS as a customer request with the phone number, and the manager sees it in the morning list.

04

Orders re-typed into 1С/BAS

Before the site sends the order by mail, the operator re-types it into 1С/BAS and mixes up the quantity once a week.

After the order arrives in 1С/BAS as a document with the same items and quantities the client chose on the site.

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
  • WordPress has an official interface through which outside applications exchange data with the site — and through it the site's content can be brought into completely separate applications such as a CRM.

    Source: developer.wordpress.org ↗ checked 2026-09-28
  • The rights are the same as on the site itself: what is public on the site is publicly readable, and private content needs a signed-in user.

    Source: developer.wordpress.org ↗ checked 2026-09-28
  • Since version 5.6 WordPress ships with application passwords — a separate password for an integration, generated on the user's page.

    Source: developer.wordpress.org ↗ checked 2026-09-28
  • From the user's page the administrator can view and revoke existing application passwords — the connection's access is cut without changing the main password.

    Source: make.wordpress.org ↗ checked 2026-09-28

Limits

The limits come from both systems. WordPress does not report new form submissions by itself: we pick them up through the forms plugin or on a schedule, so a request reaches 1С/BAS within minutes, not instantly. Application passwords work only over a secure connection, so the site must be on HTTPS. Prices and stock go to the site in batches at an interval, not on every change in 1С/BAS. 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.

  1. 01

    Leave a request

    Describe the task in the form — in text or by voice. Budget and timing are optional.

  2. 02

    We review and estimate

    A developer studies the brief, asks about anything unclear and sends an estimate.

  3. 03

    We start

    Once scope and price are agreed, the work begins.

or write to info@coreviaflow.space

Questions

We have WooCommerce. Is that the same thing?
Almost: WooCommerce runs on top of WordPress and adds a cart, orders and stock to it. The exchange uses the same site access, but orders come from the shop rather than from a form. We check which of the two you have at the first step.
Will the exchange slow the site down?
Prices and stock are written in batches at an interval you choose, and only for items that changed. On a catalogue of a few thousand items this is a short background task, not a constant load on the site.
Which system is the source of truth for the catalogue?
Usually 1С/BAS: items, prices and stock come from it, and the site only shows them. Descriptions and photos can be edited on the site if you want, and then we mark those fields as «site wins» so the exchange does not overwrite them.
We have several sites on WordPress. Is that one link or several?
Each WordPress site has its own address and its own access, so each is connected separately, but they can all read the same 1С/BAS catalogue and write orders into the same database.

Tell us what needs to be connected

Describe the task in text or a voice message. We look at your setup and reply with a plan.