Catalogue, prices and stock from 1С/BAS go to the Horoshop store, orders come back as customer orders in 1С/BAS, and the status and waybill number return to the store
The store runs on Horoshop, the accounting on 1С/BAS, and between them someone retypes orders and fixes stock by hand. An item that ran out is still on sale, the price on the site differs from the price list, and the buyer asks where the parcel is. Horoshop opens its products, orders and customers to accounting and warehouse systems, and 1С/BAS lets outside systems read and create its data, so the 1С/BAS ↔ Horoshop pair makes 1С/BAS the source for the catalogue, prices and stock and brings every store order into 1С/BAS without retyping. Below: what moves, which scenarios we cover and what we rely on in both systems.
1С/BAS → HoroshopItems from the 1С/BAS catalogue are created or updated in the store as products with the same code, name and category, so a new item is entered once.
1С/BAS → HoroshopThe chosen price type and the stock of the agreed warehouses go from 1С/BAS to the store, so the site shows the price list price and what is really in stock.
Horoshop → 1С/BASA new store order arrives in 1С/BAS as a customer order with items, quantities, delivery and payment details, without anyone retyping it.
Horoshop → 1С/BASThe buyer from the store is found among 1С/BAS counterparties by phone or created as a new one, so the directory does not fill up with duplicates.
1С/BAS → HoroshopThe order status from 1С/BAS («assembled», «shipped») is written back to the Horoshop order, so the buyer sees the real state in the store.
1С/BAS → HoroshopIf the waybill is created outside the store and its number is entered in 1С/BAS at shipment, the number is written into the Horoshop order.
What we connect
We check your Horoshop plan first: data exchange with outside systems is available from the PRO plan.
In the Horoshop admin panel you create a separate user for the exchange (Settings → Admins) and share its login with us; your own password stays with you.
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 is which product in the store, which price type and warehouses go to the site, and which 1С/BAS statuses match which store statuses.
New order statuses in Horoshop are switched on by its support after you create them, so we agree on the status list before the launch.
We run several test orders end to end: order → 1С/BAS → status back in the store, compare with the accountant, and only then switch the exchange on for real orders.
Automation scenarios
01
Sold-out item still on sale
Beforethe last unit was shipped in the morning, the store kept selling it until someone updated stock in the evening.
Afterthe balance from 1С/BAS reaches the store on the next exchange pass, and the item stops being offered as in stock.
02
Orders retyped by hand
Beforethe operator opens each Horoshop order and types it into 1С/BAS, sometimes with the wrong quantity.
Afterthe order appears in 1С/BAS as a document with the items and quantities the buyer chose.
03
Price on the site differs from the price list
Beforeprices were changed in 1С/BAS, but the site was updated a week later, and the manager had to explain the difference.
Afterthe chosen price type goes from 1С/BAS to the store, so both show the same number.
04
«Where is my parcel?»
Beforethe goods left the warehouse, but the store order still said «new», and the buyer called.
Afterthe status from 1С/BAS reaches the Horoshop order, and the waybill number is there too.
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.
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.
The limits come from both systems. Exchange with outside systems in Horoshop needs the PRO plan; writing a waybill number from another system into an order through the exchange also needs Pro. New order statuses are switched on by Horoshop support, so the status list is planned in advance. The Horoshop documentation we rely on does not describe instant notices about new orders, so the exchange collects them on a short schedule, and prices and stock go to the store in batches rather than 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.
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.
Which side is the master for products: the store or 1С/BAS?
Usually 1С/BAS: items, prices and stock are kept there, and the store shows them. Descriptions and photos can stay in Horoshop if the content team works there; we agree on this per field at the mapping step.
We create Nova Poshta waybills right in Horoshop. Does that still work?
Yes. Horoshop has its own Nova Poshta link, so if waybills are made in the admin panel, the number is already in the order and the exchange only carries statuses. Writing the number from 1С/BAS is needed only when waybills are created outside the store.
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.