CRM for Horoshop
X10 CRM pulls orders from your Horoshop store, writes the status and waybill number back, and synchronises stock and prices by SKU.
A lead is created with items, delivery details and buyer contacts every five minutes.
Store and CRM products are matched on the SKU — Horoshop has no numeric product ids.
A bundle enters the cart as one item, so the lead total matches the order.
Inventory lives in the CRM and the store receives current availability without manual files.
Horoshop sells well but does not run the sale: past a few dozen orders a day a store needs calls, stock, operators and a funnel. X10 CRM pulls the orders in and returns only the status and the waybill number to the store.
#Orders become leads
The CRM polls the store every five minutes. An order turns into a lead with the buyer, cart items, total and chosen delivery method — in one dashboard with leads from marketplaces, landing pages and calls.
- Order items land in the cart with quantities and prices.
- The delivery method is recognised and prefilled into the waybill form.
- A waybill number created in the store is picked up into the lead.
- One order is one lead, permanently, however many times the import runs.
#What goes back to the store
- 01
The operator changes the lead status
Confirming the order after a call, or moving it to rejected.
- 02
The CRM writes the status to Horoshop
The status mapping is configured once, to fit your process.
- 03
A waybill is created — the number follows
The tracking number reaches the store order right after it is created on the lead card.
#Catalogue, stock and prices
Once an hour the CRM reconciles the store catalogue with its own product directory. Because Horoshop has no numeric identifiers for listings, the link rests on the SKU — the only field by which the CRM and the store recognise the same product.
| Direction | What is synced | Frequency |
|---|---|---|
| Horoshop → CRM | Orders, items, delivery, buyer | every 5 minutes |
| Horoshop → CRM | Product listings, matched by SKU | hourly |
| Horoshop → CRM | Product images | separate queue, in batches |
| CRM → Horoshop | Order status, waybill number | immediately after the change |
| CRM → Horoshop | Stock and prices | hourly |
#What you need to connect it
- Your store's domain — the Horoshop gateway lives on it
- The API login and password issued in the store admin
- SKUs filled in on your products — the whole catalogue link rests on them
- The warehouse to write to, if unit stock counting is enabled
The domain here is as much a credential as the login and password: Horoshop has no shared API host, and every store answers on its own address.
Everything after that happens inside the CRM: statuses, groups and transitions describe the pipeline, the cart, products and prepayments cover stock and reservations, and the lead card covers the operator's work.
#Alongside your other order sources
A Horoshop store rarely runs alone: Rozetka and Prom.ua are usually enabled next to it, while landing page leads arrive through the API. They all land in one dashboard — the CRM for an online store page covers it in full.
Frequently asked questions
- What do I need to connect Horoshop to the CRM?
- Your store's domain plus the API login and password from the store admin. The domain is required: Horoshop has no shared API host, and each store's gateway lives on its own address.
- How does the CRM match store products with its own?
- By SKU. Horoshop has no numeric identifiers for listings, so the SKU must be filled in — both the catalogue sync and the stock write depend on it.
- Is an order containing a bundle priced correctly?
- Yes. Horoshop sends both the bundle and its components, but only the bundle enters the lead's cart — otherwise the total would be doubled.
- Is store stock updated?
- Yes, hourly. If unit counting is enabled in the store, the integration settings need the warehouse the CRM should write quantities to.
- Can I run several Horoshop stores?
- Yes. Each store is connected separately with its own domain and credentials, and its leads carry the source logo in the dashboard.