# BigCommerce + Krokul CRM

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.

**Status:** Via API and webhooks. **Automation platforms:** Zapier, Make, Albato.

## What your team gets

### The connector reads the order the webhook points to

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.

### Order status in the store moves the deal

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.

### A shipped deal creates the BigCommerce shipment

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.

### Abandoned carts reach the account manager

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.

## What moves between BigCommerce and Krokul

| BigCommerce | Krokul | Direction | When |
|---|---|---|---|
| Order (store/order/created, then GET order) | Deal with lines matched by SKU | BigCommerce → Krokul | An order is placed |
| Order status (store/order/statusUpdated) | Deal stage and reserve | BigCommerce → Krokul | Staff change the status |
| Order Shipment with tracking number | Shipment of the deal | Krokul → BigCommerce | The deal ships |
| Variant inventory level | Stock balance of the product | Krokul → BigCommerce | Stock changes in Krokul |
| Cart (store/cart/abandoned) | Task with the cart items | BigCommerce → Krokul | A known customer leaves a cart |
| Customer | Contact and client company | BigCommerce ↔ Krokul | A customer or client company is created |

## How to connect today

### Krokul app in Zapier, Make or Albato

1. Add the Krokul app and connect it with a Krokul API key.
2. Start from the BigCommerce trigger Order Created and run the Krokul action Create Deal, or Abandoned Cart with Create Task for the account manager.
3. Start from the BigCommerce trigger Shipment Created and run the Krokul action Add Comment to post delivery news on the deal.
4. From the Krokul trigger Company Created, run Find or Create Customer in BigCommerce.

### Custom flow through the Krokul API and webhooks

1. In the BigCommerce control panel, create a store-level API account with scopes for orders, products, customers and carts. In Krokul, create an API key for deals, contacts and client companies.
2. Register a BigCommerce hook for store/order/created, read the order by its ID, then add the buyer with contact/api-create and open the deal with card/api-create.
3. Store the BigCommerce order ID on the deal through externalRef/api-upsert.
4. Subscribe a Krokul webhook to card.statusChanged, check x-crm-signature with your secret, and create the order shipment with the tracking number when the deal reaches the shipped stage.

**Triggers:** Order Created; Order Status Updated; Order Updated; Abandoned Cart; Customer Created; Shipment Created.

**Actions:** Create Customer; Create Customer Address; Create a Product; Find or Create Customer.

### For integrators

BigCommerce creates webhooks only through its API, delivers them to port 443 with the custom headers you set, and deactivates a hook after 48 hours of failed retries. Krokul answers every BigCommerce callback fast and reads the object afterwards. On the Krokul side you get a REST API, signed webhooks with a delivery log, external keys for order and customer IDs and a sandbox company.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Why does Krokul call BigCommerce after each webhook?

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.

### Which BigCommerce statuses can move a deal?

Any order status the store uses. You map each status to a Krokul stage once, and the connector applies it on every status update.

### Does Krokul update stock for product variants?

Yes. The connector writes the Krokul balance to the inventory level of the variant whose SKU matches the Krokul product.

### Does Krokul integrate with BigCommerce?

Yes. Krokul integrates with BigCommerce through the Krokul app in Zapier, Make and Albato, and through its API and webhooks.

## Limits

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.

## Related services

- [Shopify](https://krokul.com/en/integrations/shopify/index.md)
- [WooCommerce](https://krokul.com/en/integrations/woocommerce/index.md)
- [Adobe Commerce](https://krokul.com/en/integrations/adobe-commerce/index.md)
- [Amazon](https://krokul.com/en/integrations/amazon/index.md)
- [ShipStation](https://krokul.com/en/integrations/shipstation/index.md)

[Commerce platforms](https://krokul.com/en/integrations/category/ecommerce/index.md)

BigCommerce is a trademark of BigCommerce Pty. Ltd. Krokul is not affiliated with BigCommerce.

Updated: 2026-10-12

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs