Yes. Krokul CRM integrates with ShipHero. A won deal becomes a ShipHero order, or a wholesale order for pallet and freight shipments, with the ship-to address and lines by SKU. ShipHero picks, packs and ships it, and the tracking number comes back to the deal. Stock held in ShipHero warehouses shows in Krokul as its own stock location, so managers quote from real availability.
Automation platformsMake
When a deal is won in a pipeline that ships from a ShipHero warehouse, Krokul calls order_create with the deal number as partner_order_id, the shipping address of the client company and each product line with its SKU and quantity. Large B2B orders go through wholesale_order_create, where freight details such as carrier and bill of lading live. ShipHero returns the order ID, and Krokul keeps it on the deal.
ShipHero fires the Shipment Update webhook once a package leaves. Krokul matches the deal by partner_order_id, reads tracking_number and shipping_carrier from each package label, records the shipment and moves the deal to the delivery stage. One order split into two boxes gives two tracking numbers on the same deal.
Each Inventory Update webhook carries the SKU, the inventory and on-hand counts and the warehouse ID. Krokul writes those numbers to the stock location tied to that ShipHero warehouse. A manager building a quote sees what ShipHero can ship today, and reserves on open deals keep counting against it in Krokul.
The Order Backorder and Order Canceled webhooks turn into a task for the deal owner with the order number and the affected SKUs. The manager calls the client before the delivery date slips.
| ShipHero | Direction | Krokul | When |
|---|---|---|---|
Order (order_create, partner_order_id, shipping_address, line_items) | Krokul → ShipHero | Won deal with lines and client company address | A deal is won |
Wholesale order (wholesale_order_create) | Krokul → ShipHero | Won B2B deal shipped by freight | A deal is won in a freight pipeline |
| Order update or cancel | Krokul → ShipHero | Edited or lost deal | Before the order ships |
| Shipment Update (tracking_number, shipping_carrier) | ShipHero → Krokul | Shipment of the deal, delivery stage | A package ships |
| Inventory Update (sku, inventory, on_hand, warehouse) | ShipHero → Krokul | Stock levels of the ShipHero stock location | Stock changes in the warehouse |
| Order Backorder, Order Canceled | ShipHero → Krokul | Task for the deal owner | ShipHero cannot ship as ordered |
order_create.order_create at public-api.shiphero.com/graphql.webhook_create mutation and save the shared_signature_secret it returns once.Yes. Krokul integrates with ShipHero through the Krokul app in Make and through the Krokul API and webhooks together with the ShipHero GraphQL API.
ShipHero. Krokul keeps a separate stock location for each ShipHero warehouse and updates it only from ShipHero events, while your own warehouses stay under Krokul stock moves.
Yes. Deals in a freight pipeline go to ShipHero as wholesale orders with carrier, shipping method and bill of lading fields.
The Order Backorder webhook creates a task for the deal owner with the missing SKUs, so the client hears about the delay from the manager.
Goods stored in a ShipHero warehouse are counted by ShipHero, and Krokul mirrors those levels without moving them by hand. Picking, packing, label buying and warehouse staff stay in ShipHero. ShipHero meters its API with a credit pool per account, which caps heavy queries.
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.
ShipHero is a trademark of ShipHero, LLC. Krokul is not affiliated with ShipHero.