1С/BAS ↔ Shopify integration

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

The store is on Shopify, often for buyers abroad, while the accounting and the warehouse are in 1С/BAS at home. Orders are copied into 1С/BAS by hand, stock in the store is updated once a day, and the fulfilment status is set by a person who sometimes forgets. The 1С/BAS ↔ Shopify pair makes 1С/BAS the source for products, prices and stock, delivers every store order to 1С/BAS the moment it is placed, and marks the order fulfilled in Shopify with the tracking number when the warehouse ships it. 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: Shopify →

What moves between the systems

1С/BAS → ShopifyItems from the 1С/BAS catalogue are created or updated in the store as products and variants with name, description, options and the photo from the item card.
1С/BAS → ShopifyThe chosen price type from 1С/BAS is written to the store on a schedule, in the store currency, so the store price and the price list agree.
1С/BAS → ShopifyStock balances by the agreed warehouses go to the store's inventory, so a variant that ran out stops being sold without anyone touching the store.
Shopify → 1С/BASA new store order arrives in 1С/BAS the moment it is placed as a customer order with line items, quantities, delivery address and payment status, and the counterparty found by e-mail or created anew.
Shopify → 1С/BASOrder cancellations and refunds in the store update the same document in 1С/BAS, so the warehouse and the accountant see the real state of the order.
1С/BAS → ShopifyWhen the warehouse ships the order in 1С/BAS, the store order is marked fulfilled with the carrier and tracking number, and Shopify sends its usual shipping notification to the buyer.

What we connect

We look at the store: how products and variants are structured, which locations hold inventory, which apps already touch orders; this decides what is mapped and in which order.
In Shopify the owner installs the exchange as a custom app for this store only, with access limited to products, inventory, orders and fulfilments; access can be revoked at any time.
We subscribe to store events for orders, cancellations and refunds, so they reach the exchange right away, and every 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 and shipments.
We map the catalogues: which 1С/BAS item is which product and variant, which price type and warehouses feed which store location, and which 1С/BAS status means «fulfilled» in the store.
We test on a development store with a handful of products and test orders, compare with the accountant, and only then switch the exchange to the live store.

Automation scenarios

Orders re-typed into 1С/BAS

Before the operator opens each Shopify order in the morning and types it into 1С/BAS, and the warehouse waits until noon.

After the order is in 1С/BAS minutes after the buyer paid, and the warehouse starts assembling it right away.

Overselling the last units

Before stock in the store is updated by hand once a day, and the last two units get sold four times.

After the balance from 1С/BAS reaches the store inventory within minutes, and the variant stops selling at zero.

Forgotten fulfilment

Before the parcel left on Monday, but the store still shows «unfulfilled» on Thursday, and the buyer opens a dispute.

After the shipment in 1С/BAS marks the order fulfilled with the tracking number the same hour, and the buyer gets the store's notification.

Refund the accountant never saw

Before the refund is made in Shopify, but 1С/BAS still counts the sale, and the month closes with a wrong figure.

After the refund updates the order in 1С/BAS the same day, and the accountant sees it before closing the month.

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
The orders query returns the store's orders with status, customer and line items, and Shopify itself suggests using it to automate fulfillment workflows.
Source: shopify.dev ↗ checked 2026-09-27
An app can subscribe to store events (webhook topics) and receive data about them in near real time, instead of polling the store.
Source: shopify.dev ↗ checked 2026-09-27
Each webhook delivery carries an HMAC signature in the X-Shopify-Hmac-Sha256 header that must be verified before processing.
Source: shopify.dev ↗ checked 2026-09-27
If the receiver doesn't respond, Shopify retries the delivery 8 times over the next 4 hours; after 8 consecutive failures an API-created subscription is deleted.
Source: shopify.dev ↗ checked 2026-09-27

Limits

The limits come from both systems. Orders arrive as events from the store, but products, prices and stock go to the store in batches at an interval, not on every change in 1С/BAS; Shopify also meters requests, so a very large catalogue is loaded in portions. If our server does not answer, Shopify retries for a few hours and then drops the subscription; the exchange watches for this and re-reads missed orders on the next pass. Prices are written in one store currency; other currencies are handled by the store's own markets settings. 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

We sell in euros, the accounting is in hryvnias. How are prices handled?

A separate price type in 1С/BAS in the store currency is the cleanest way: it is set there and written to the store as is. Orders come back with the amount in the store currency and the payment status, and the accountant books them the way they book any foreign-currency sale.

Our store already has an app that syncs inventory. Will they conflict?

Two writers to the same inventory field will fight. At the first step we look at what that app does; either it stays and the exchange leaves inventory alone, or the exchange takes over and the app is switched off for those locations.

Do we need the newer Shopify interface or does the old one still work?

We build on the current one, which Shopify requires for new apps since 2025. That is invisible to you: the store looks and works the same, and nothing in it has to be changed.