Yes, natively. Krokul CRM receives orders from an online store on Horoshop by webhook or by polling the API. An order becomes a deal with items from your catalog, and the buyer becomes a contact. The order status syncs both ways, and stock and prices from the Krokul warehouse go back to the store.
Automation platformsZapier
Horoshop sends the order to the Krokul connection address as soon as the buyer places it. Krokul creates a deal «Horoshop #…» in the chosen pipeline and matches each order item to a Krokul catalog item by SKU. The stock reservation is made the same way as for a deal a manager creates.
A manager moves the deal to another stage, and Krokul changes the order status in Horoshop. If the status changes in the store admin, the Horoshop webhook about an order status change moves the deal to the matching stage. You map stages to statuses in the connection settings.
Krokul sends Horoshop the stock level and price of an item when they change in the Krokul warehouse or price list. The store does not sell items that are physically out of stock, and the manager updates a price in one place.
Krokul checks the phone and email from the order against existing contacts, and the Horoshop customer update webhook refreshes the contact data. The Horoshop order number is the external key of the deal, so the webhook and polling together never create two deals.
If the plan offers no webhooks, Krokul polls orders through the Horoshop API with the API login and password. The first pass only remembers the latest order, so a fresh pipeline does not fill up with the whole store history. A separate switch lets you import the history.
| Horoshop | Direction | Krokul | When |
|---|---|---|---|
| Order (number, amount) | Horoshop → Krokul | Deal «Horoshop #…» with an external key | Store webhook or API polling |
| Order items (SKU, quantity, price) | Horoshop → Krokul | Deal lines with catalog items | Together with the deal |
| Buyer (name, phone, email) | Horoshop → Krokul | Contact, found or new | Together with the deal and on the customer update webhook |
| Order status | Horoshop ↔ Krokul | Deal stage | A stage change in Krokul or the status change webhook |
| Order comment | Horoshop → Krokul | Entry in the deal feed | New comment webhook |
| Item stock and price | Krokul → Horoshop | Krokul warehouse and price list | Stock or price changes |
Yes, a native one. Krokul turns orders into deals with catalog items, syncs the order status both ways and sends stock and prices back to the store.
On the Pro plan, webhooks deliver status changes, customer updates and comments at once. Krokul fetches new orders by polling the API, so they appear with a short delay. On other plans, polling covers everything.
By default, no. The first pass only remembers the latest order. If you need the history, turn on «Import existing orders on the first pass».
Yes, with the New Order and New User triggers. You do not need it to connect Horoshop to Krokul, because the native connection receives orders directly.
Horoshop offers webhooks on the Pro plan. On other plans, Krokul fetches orders by polling the API with a login and password, so an order arrives at the next pass. Horoshop runs the storefront, checkout and payment on the site, and Krokul runs the sale after the order.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
Horoshop is a trademark of its owner. Krokul is not affiliated with Horoshop.