1С/BAS ↔ SalesDrive integration

A confirmed SalesDrive order becomes a document in 1С/BAS with the client and items, products and payments from 1С/BAS return to SalesDrive, and the manager sees the real order state

Sales run in SalesDrive, where orders from the site, calls, Rozetka and Prom.ua already gather, while the accounting is in 1С/BAS. Between them the manager retypes confirmed orders, and the accountant marks payments twice. SalesDrive sends an order's data out on a new order or a status change and lets outside systems update orders, products and payments, and 1С/BAS lets outside systems read and create its data, so the 1С/BAS ↔ SalesDrive pair turns a confirmed order into a 1С/BAS document and brings products, payments and statuses back to SalesDrive. Below: what moves and what we rely on.

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

What moves between the systems

SalesDrive → 1С/BASAn order moved to the agreed status in SalesDrive becomes a customer order or sales document in 1С/BAS with the client, items, quantities and prices; SalesDrive sends the order's data itself on that status change.
SalesDrive → 1С/BASThe client from SalesDrive is found among 1С/BAS counterparties by phone or code or created as a new one, so the directory does not double.
SalesDrive → 1С/BASOrders that come into SalesDrive through its ready connections with Rozetka and Prom.ua go on to 1С/BAS by the same path as orders from the site and calls.
1С/BAS → SalesDriveProducts and categories from the 1С/BAS catalogue are added or updated in SalesDrive, so the manager picks items with the same codes the accounting uses.
1С/BAS → SalesDriveA payment recorded in 1С/BAS is added to the SalesDrive order as a payment, so the manager sees that the client has paid without asking the accountant.
1С/BAS → SalesDriveThe shipment status from 1С/BAS («assembled», «shipped») updates the order status in SalesDrive.

What we connect

In SalesDrive settings you create a separate access key for the exchange and hand it to us; it can be replaced at any time.
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 agree on the condition: which SalesDrive status sends an order to 1С/BAS, which 1С/BAS document it becomes, and what happens to that document when the order is cancelled.
We map the catalogues, payment and delivery methods and statuses of both systems, and check how your SalesDrive keeps stock before promising stock updates.
We set the exchange rhythm within SalesDrive's limits: orders arrive as SalesDrive sends them, and the order list is re-read only rarely to catch anything missed.
We run a test batch of orders and a test client, compare with the accountant, and only then switch the whole flow on.

Automation scenarios

Confirmed orders retyped

Before the manager confirms the order in SalesDrive and then types it into 1С/BAS or sends it to the accountant.

After the order in the agreed status appears in 1С/BAS as a document with the same client and items.

«Has the client paid?»

Before the manager writes to the accountant to find out whether money arrived before shipping.

After the payment recorded in 1С/BAS is visible on the SalesDrive order.

Marketplace orders stuck in the CRM

Before orders from Rozetka and Prom.ua reached SalesDrive, but the accounting learned about them only at the end of the day.

After they go to 1С/BAS by the same rule as all other orders.

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
API requests are authorised with a key sent in the Form-Api-Key header, created in the system's settings.
Source: salesdrive.ua ↗ checked 2026-09-25
The order-list method is rate-limited: 10 requests a minute, 100 an hour, 1000 in 24 hours; this limit applies only to that one method.
Source: salesdrive.ua ↗ checked 2026-09-25
The open API covers adding and updating orders, products and categories, currency rates, payment and delivery methods, order statuses, payments and calls.
Source: salesdrive.ua ↗ checked 2026-09-25
Webhooks send an order's data to an external service in POST JSON format, triggered either by a new order or by a status change, and several webhooks with different trigger conditions can run at once.
Source: salesdrive.ua ↗ checked 2026-09-25
SalesDrive has ready-made native connections with Binotel, Ringostat and Zadarma telephony, and with Rozetka, Prom.ua and Nova Poshta.
Source: salesdrive.ua ↗ checked 2026-09-25

Limits

The limits come from both systems. SalesDrive caps how often the order list can be read, so the exchange relies on the order data SalesDrive sends itself and re-reads the list only to catch misses. The SalesDrive documentation we rely on lists products and categories among what can be updated, but does not describe stock separately, so we check how your SalesDrive keeps stock before promising it. Ready connections of SalesDrive with Rozetka and Prom.ua bring orders in, but prices and stock on those marketplaces are a separate question. 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 orders and for products?

Orders are born in SalesDrive and go to 1С/BAS once confirmed. Products and payments are usually kept in 1С/BAS and shown in SalesDrive. We fix this per field at the mapping step.

Our Rozetka and Prom.ua orders already come into SalesDrive. Do we need separate links for them?

For orders, no: they reach 1С/BAS through SalesDrive by this pair. Prices and stock on the marketplaces are a different flow, described on the 1С/BAS ↔ Rozetka and 1С/BAS ↔ Prom.ua pages.

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.