Yes. Krokul CRM integrates with BigCommerce. A BigCommerce webhook tells Krokul that an order exists, the order is read in full through the API, and Krokul opens a deal with lines matched to the Krokul catalog by SKU. Krokul sends variant stock to the store, and a shipped deal creates the shipment with its tracking number on the BigCommerce order. You set it up with the Krokul app in Zapier, Make or Albato, or with the Krokul API and webhooks.
Automation platformsZapierMakeAlbato
BigCommerce fires store/order/created with the order ID and nothing else. The Krokul connector calls the Orders API for the billing address, the products and the totals, finds or adds the contact and opens a deal. Each order product with a SKU known to Krokul becomes a catalog line that reserves stock.
store/order/statusUpdated reaches Krokul when staff set an order to Awaiting Fulfillment, Cancelled or Refunded. The connector maps each BigCommerce status to a stage you choose, so a cancelled Order closes the deal as lost and releases the reserve.
When the deal ships in Krokul with a tracking number, the connector creates a Shipment on the BigCommerce order for the shipped items with the carrier and that number. The store marks the order as shipped, and the buyer sees the tracking link in the account.
store/cart/abandoned brings the Cart ID. When the cart belongs to a known customer, Krokul reads its contents and creates a follow-up task with the items for the manager of that trade buyer.
| BigCommerce | Direction | Krokul | When |
|---|---|---|---|
| Order (store/order/created, then GET order) | BigCommerce → Krokul | Deal with lines matched by SKU | An order is placed |
| Order status (store/order/statusUpdated) | BigCommerce → Krokul | Deal stage and reserve | Staff change the status |
| Order Shipment with tracking number | Krokul → BigCommerce | Shipment of the deal | The deal ships |
| Variant inventory level | Krokul → BigCommerce | Stock balance of the product | Stock changes in Krokul |
| Cart (store/cart/abandoned) | BigCommerce → Krokul | Task with the cart items | A known customer leaves a cart |
| Customer | BigCommerce ↔ Krokul | Contact and client company | A customer or client company is created |
BigCommerce webhooks carry the scope and the ID only. The connector reads the order, cart or customer by that ID to get the buyer, the items and the amounts.
Any order status the store uses. You map each status to a Krokul stage once, and the connector applies it on every status update.
Yes. The connector writes the Krokul balance to the inventory level of the variant whose SKU matches the Krokul product.
Yes. Krokul integrates with BigCommerce through the Krokul app in Zapier, Make and Albato, and through its API and webhooks.
Storefront design, promotions and checkout settings stay in BigCommerce. BigCommerce webhooks carry only IDs, so every order detail comes from a follow-up API read by the connector.
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.
BigCommerce is a trademark of BigCommerce Pty. Ltd. Krokul is not affiliated with BigCommerce.