1С/BAS ↔ OpenCart integration

Catalogue, prices and stock from 1С/BAS go to the OpenCart store, orders come back as customer orders in 1С/BAS, and the status returns to the store

The store runs on OpenCart, the accounting on 1С/BAS, and between them someone retypes orders and uploads stock by hand. OpenCart issues access for outside applications such as inventory and ERP systems, and 1С/BAS lets outside systems read and create its data, so the 1С/BAS ↔ OpenCart pair makes 1С/BAS the source for the catalogue, prices and stock and brings store orders into 1С/BAS. OpenCart does not report a new order to outside systems by itself, so we choose with you between a small store extension and a short check schedule. Below: what moves and what we rely on.

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

What moves between the systems

1С/BAS → OpenCartItems from the 1С/BAS catalogue are created or updated in the store as products with the same code, name and category.
1С/BAS → OpenCartThe chosen price type and the stock of the agreed warehouses go from 1С/BAS to the store, so buyers do not order what is already gone.
OpenCart → 1С/BASA new store order arrives in 1С/BAS as a customer order with items, quantities, delivery and payment methods; if several stores share one admin panel, the order carries which store it came from.
OpenCart → 1С/BASThe buyer from the store is found among 1С/BAS counterparties by phone or e-mail or created as a new one.
1С/BAS → OpenCartThe order status from 1С/BAS («assembled», «shipped») is written back to the OpenCart order, so the buyer sees the current state in the store.

What we connect

We check which OpenCart you run: the documentation covers version 4.x, and a store on 3.x is connected differently or upgraded first; we decide this together before promising anything.
Your administrator creates an access key for the exchange in the admin panel (System → Users) and limits it to our server's address. The key is shown once, so it is handed over right away.
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 choose how new orders are noticed: a small extension in the store that sends a notice on each order, or a check of the store on a short schedule, depending on how many orders you get.
We map product codes, price type, warehouses, order statuses, payment and delivery methods and, for several stores, which store maps to which 1С/BAS organisation or warehouse.
We test on a few real orders next to your current process, compare with the accountant, and then switch over; if the store or 1С/BAS refuses a record, the responsible person gets a notice with the reason.

Automation scenarios

Orders retyped into 1С/BAS

Before the operator copies each OpenCart order into 1С/BAS and sometimes misses one on a busy day.

After every order appears in 1С/BAS as a document with the items and quantities the buyer chose.

Stock uploaded once a day

Before stock was uploaded to the store in the morning, and by evening the site sold items that were gone.

After balances from 1С/BAS reach the store on every exchange pass during the day.

Several stores, one accounting

Before orders from two stores in one OpenCart panel were mixed in 1С/BAS, and nobody knew which site sold what.

After each order arrives in 1С/BAS with the store it came from.

How it works technically

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

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
In the admin panel (System → Users → APIs) OpenCart creates credentials for outside applications — inventory systems, ERP, mobile apps and other services.
Source: docs.opencart.com ↗ checked 2026-09-28
Each API key has configurable access restrictions and a usage history for security monitoring.
Source: docs.opencart.com ↗ checked 2026-09-28
OpenCart 4.x is built on an event system that lets developers extend and change behaviour without touching the core.
Source: docs.opencart.com ↗ checked 2026-09-28
Extensions add modules, payment gateways, shipping methods, themes and reports without editing core files.
Source: docs.opencart.com ↗ checked 2026-09-28
Multi-store: several stores are managed from one admin panel, with any currency and automatic rate updates.
Source: www.opencart.com ↗ checked 2026-09-28

Limits

The limits come from both systems. OpenCart recommends restricting each access key to specific server addresses, so the connecting server needs a fixed address. The key is shown only once and has to be reissued if lost. OpenCart has no ready-made outgoing notice to outside systems: either a small extension is added to the store, which is development work on the store's side, or the exchange checks the store on a schedule. The documentation covers version 4.x; a store on 3.x is a separate case with its own upgrade path. 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

Our store is on OpenCart 3. Can it be connected?

It is a separate case: the documentation we rely on covers 4.x. We look at your store first and say honestly whether it connects as is or should be upgraded before the exchange.

Extension or schedule: which is better?

With many orders, an extension that reports each order is faster. With a few orders a day, a check every few minutes is simpler and does not touch the store's files. We choose together at the start.

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

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

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.

Request an integration

What you can order

Four services people come to us for most often. Each page explains what we do, how the work goes and where to start.

CRM implementation

Choose the system, set up the pipeline, migrate data, train the team.

Learn more →

CRM integration

Accounting, telephony, website, payments and messengers feed the CRM on their own.

Learn more →

Telegram chatbots for business

Orders, requests and answers around the clock, straight into your CRM.

Learn more →

n8n and Make automation

Flows between CRM, email, spreadsheets, payments and AI, on your own server.

Learn more →

What you can order from CoreviaFlow →

Each system on its own

Accounting & ERPUA

1С/BAS

Already running your accounting in 1С/BAS? We automate the work around it

See scenarios →

E-commerce platformsEU

OpenCart

An order from your OpenCart store appears in the CRM within minutes, the manager calls the customer with the full cart in front of them, and the delivery status goes back to the store on its own.

See scenarios →