1С/BAS ↔ Prom.ua integration

Prices, stock and the catalogue from 1С/BAS go to Prom.ua, marketplace orders come back as customer orders in 1С/BAS, and the status and waybill number return to the Prom cabinet

You sell on Prom.ua and keep the accounting in 1С/BAS. Orders are copied from the Prom cabinet by hand, stock is corrected with a file once in a while, and statuses in the cabinet are changed when someone has time. Prom describes remote access for a company to its orders and products, and 1С/BAS lets outside systems read and create its data, so the 1С/BAS ↔ Prom pair takes Prom orders into 1С/BAS, keeps prices and stock on Prom in line with the records and returns the status and waybill number to the cabinet. Access starts with a request to Prom: its remote access is a closed beta. Below: what moves and what we rely on.

Request an integration System page: 1С/BAS →System page: Prom.ua →

What moves between the systems

1С/BAS → Prom.uaPrices and stock on Prom are updated from 1С/BAS; products are matched by your own article number, so nobody has to know Prom's internal product numbers.
1С/BAS → Prom.uaA full catalogue from 1С/BAS can be loaded onto Prom as a file (xls, xlsx, csv or xml) by a link, and the exchange then checks how the import went.
Prom.ua → 1С/BASOrders from Prom arrive in 1С/BAS as customer orders with the buyer, address, chosen delivery and payment methods and items; the exchange asks Prom for orders created or changed since the last check.
Prom.ua → 1С/BASA changed or cancelled Prom order updates the same document in 1С/BAS, so the warehouse does not assemble what the buyer no longer wants.
1С/BAS → Prom.uaThe order status from 1С/BAS goes back to the Prom cabinet, for one order or a whole batch, so the buyer sees the current state on Prom.
1С/BAS → Prom.uaA waybill number created outside the Prom cabinet and entered in 1С/BAS at shipment is saved into the Prom order.

What we connect

We start with a request to Prom: the company access key is issued by Prom staff on request, because remote access is a closed beta for a limited number of companies.
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 by article number, choose the price type and warehouses for Prom, and match Prom statuses, delivery and payment methods to those in 1С/BAS.
All dates and times from Prom come in world time; the exchange converts them to Kyiv time so orders land in 1С/BAS on the right day.
As Prom recommends, we try the connection on a separate test company first, compare the result with the accountant, and only then switch to the real cabinet.

Automation scenarios

Orders copied from the cabinet

Before the manager opens the Prom cabinet in the morning and types every new order into 1С/BAS.

After Prom orders appear in 1С/BAS as documents with the buyer and items a few minutes after they are placed.

Stock fixed by file once a week

Before stock on Prom was refreshed by uploading a file when someone remembered, and sold-out goods kept getting orders.

After stock and prices on Prom follow 1С/BAS by article number on the exchange schedule.

Statuses left untouched in the cabinet

Before the order had long been shipped, but on Prom it still looked new, and the buyer worried.

After the status and waybill number from 1С/BAS go back to the Prom order without anyone opening the cabinet.

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
The documentation lists uploading order information into your own system and changing order statuses in the company cabinet among the API capabilities.
Source: public-api.docs.prom.ua ↗ checked 2026-09-27
The documentation lists receiving product information and changing it in the company cabinet among the API capabilities.
Source: public-api.docs.prom.ua ↗ checked 2026-09-27
A separate method saves the number of a declaration that was not generated in the prom.ua cabinet into the order.
Source: public-api.docs.prom.ua ↗ checked 2026-09-27
Products can be imported by a link to an xls, csv, xlsx or xml file.
Source: public-api.docs.prom.ua ↗ checked 2026-09-27
The public API documentation, version 1.0, is described as a closed beta test for a limited number of companies.
Source: public-api.docs.prom.ua ↗ checked 2026-09-27

Limits

The limits come from both systems. Prom's remote access is a closed beta: the key is issued by Prom staff on request, so the seller cannot switch it on alone. The documentation does not describe notices from Prom about new orders, so the exchange asks Prom for changes on a schedule, and an order reaches 1С/BAS a few minutes after it is placed rather than instantly. Revoking the key means changing the cabinet owner's password and asking Prom for a new one, and every tool that used the old key has to be updated at once. 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

Can we connect without contacting Prom?

No. The company key is issued by Prom staff on request, so the first step is a request to Prom from the cabinet owner. Until then, the catalogue can still be loaded from a 1С/BAS file by a link.

Why does an order arrive in a few minutes, not instantly?

Prom's documentation does not describe notices about new orders, so the exchange asks Prom for everything created or changed since the last check. Nothing is lost: the next check picks up whatever the previous one missed.

What about buyer messages on Prom?

They are not part of this pair: 1С/BAS keeps orders and stock, not conversations. Buyer messages stay in the Prom cabinet or go to your CRM if you have one.

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.