Who it is for
Companies where the same goods, prices and orders live at once in the accounting system, on the website, on the marketplaces, in a CRM or in spreadsheets — and someone keeps them identical by hand.
What hurts
Orders have to be carried across
The website or the marketplace already knows what the client bought, yet the manager creates that order again in the accounting system.
Stock drifts apart
A client can order what is already gone, or fail to see something that is in fact in the warehouse.
Prices are changed in several places
An exchange rate, a markup or a promotion changes once, and then someone carries the new price into every channel separately.
One set of product and order data, in every channel
- Stock and prices from the accounting system to the website — automatically, on a schedule or on an event.
- Orders from the website straight into the accounting system as a document, with the right counterparty and the right article numbers.
- Listings, stock and prices onto the marketplaces (Rozetka, Prom, OLX) from the accounting system instead of a file; orders from there travel back the same way.
- Bulk price changes: the rule is set once, and new prices reach accounting, the website, the marketplaces and the shops at the same time.
- Exchange rates in the price list, on the website and in the invoices, all by one rule.
- Order statuses travel back to the channel the order came from.
- CRM: if you have one, I connect it to accounting — counterparties, statuses, payments. If you do not, I build a light one on top of the accounting system.
- Control: if something did not sync, you get a message rather than silence.
What else can be automated on top
Because current goods and prices are already available in one place, the same data can drive quotations, price lists and other documents — a specification becomes a laid-out PDF in a minute.
Publishing to social networks belongs here too: text, photo and link go into every channel at once, and drafts can be prepared automatically — from suppliers' news, incoming goods or promotions.
What you get
Stock and prices come from a single source, and orders do not have to be carried across by hand. The sales manager sees current data without "let me check with the warehouse".
What it plugs into: Horoshop and other websites with an API, the Rozetka, Prom and OLX marketplaces, accounting systems — 1C / BAS and others, CRM (KeyCRM, SalesDrive, Bitrix24 and others), National Bank exchange rates, messengers, social networks
FAQ
Questions we hear most often
- There is a ready-made Horoshop ↔ BAS module for eight thousand hryvnia, about $200. Why you?
- If all you need is the standard sync between the website and BAS, a ready-made module will most likely be the cheaper solution. Custom automation is for when the process runs further: marketplace → CRM → accounting → e-documents → carrier → bank, or when you have rules of your own that a ready-made module does not cover. Working modules stay where they are — there is no sense in rewriting them.
- Our website runs on Horoshop. Does that work?
- Yes — Horoshop is exactly what my own company runs on: stock, prices and orders move between it and the accounting system automatically. Any other platform with an API works the same way.
- We use KeyCRM. Are you replacing it?
- No. KeyCRM, SalesDrive and Bitrix24 are good at collecting orders from marketplaces and messengers — I connect them to the accounting system, so that an order becomes a document, stock and prices come from accounting, and payments from the bank close the invoices. The CRM stays yours.
- We already have stock sync, but someone starts it by hand and it breaks now and then.
- That is typical. The difference is not that sync exists, but that it runs by itself, reports its failures and needs no person. That is the part I build.
- We sell on Rozetka and Prom and upload listings and prices as a file.
- The marketplaces have an API, so listings, stock and prices are updated from the accounting system, and orders arrive as documents in accounting instead of emails in an inbox. The file stays as a fallback, not as daily work.
- We change prices shop by shop and it takes a day.
- The pricing rule is set once: markup on cost, rounding, promotional exceptions. New prices reach accounting, the website, the marketplaces and every shop at the same time, instead of being carried across by hand one at a time.
- Instead of a CRM we have a spreadsheet.
- Then I build you a CRM of your own, a light one on top of the accounting system: the counterparties are already in accounting, and on top of them goes whatever your sales managers actually need. A client card with their rules and contacts, the history of emails and documents, order statuses, a one-click jump into their messenger — the set is put together out of what the managers actually open every day. No separate SaaS subscription per user, and no data migration. If you later want a “big” CRM, I connect that too.
- What access do you need, and whose code is it?
- Limited access: a separate accounting-system user with rights to what is needed and nothing more; the website and marketplace API keys stay on your side. The code, the settings and the documentation are yours — after the rollout the access can be taken away, and any other developer can maintain the system.
- Our prices are in a foreign currency, our invoices are in hryvnia.
- The rate — the National Bank's or your own — is pulled in automatically, and the price list, the website and the invoices are recalculated by one rule. Nobody re-types numbers in Excel.