# Extensiv 3PL Warehouse Manager + Krokul CRM

Yes. Krokul CRM integrates with Extensiv 3PL Warehouse Manager. When your goods sit in a 3PL warehouse that runs Extensiv, each won deal becomes an order in 3PL Warehouse Manager with your customer and facility IDs and lines by SKU. The confirmation of the shipped order, inbound receipts and stock summaries come back to Krokul, so sales knows what left the warehouse and what is left to sell.

**Status:** Via API and webhooks.

## What your team gets

### Won deals become 3PL orders

A manager wins a deal for goods stored at the 3PL. Krokul creates the order in 3PL Warehouse Manager with your customer ID, the facility ID, the deal number as the reference number, the ship-to address of the client company and each line by SKU. The Extensiv order ID stays on the deal, and the warehouse team sees the order in its normal queue.

### Order confirmation closes the delivery step

The warehouse confirms the order once it ships, and 3PL Warehouse Manager sends the OrderConfirm event with a link to the order resource. Krokul reads the order through that link, records the shipment on the deal with the carrier details the warehouse entered and moves the deal to delivered. An OrderCancel event becomes a task for the deal owner.

### Stock summaries for quoting

On each Inventory Summary Update, Krokul reads the stock summaries for your customer at that facility and writes on-hand and available quantities to the matching Krokul stock location. Reserves on open deals keep counting in Krokul. Managers stop promising goods the warehouse has already allocated.

### Inbound receipts from suppliers

When the warehouse confirms a receipt, the Receipt Confirm event reaches Krokul with the receiver transaction. Krokul notes the receipt on the supplier order and comments on deals that wait for those SKUs.

## What moves between Extensiv and Krokul

| 3PL Warehouse Manager | Krokul | Direction | When |
|---|---|---|---|
| Order (customer, facility, reference number, lines by SKU) | Won deal with client company address | Krokul → Extensiv | A deal is won |
| Order update or cancel | Edited or lost deal | Krokul → Extensiv | Before the warehouse confirms the order |
| OrderConfirm event, order resource | Shipment of the deal, delivered stage | Extensiv → Krokul | The warehouse ships and confirms |
| OrderCancel event | Task for the deal owner | Extensiv → Krokul | The warehouse cancels an order |
| Inventory Summary Update, stock summaries | Stock levels of the 3PL stock location | Extensiv → Krokul | Quantities change at the facility |
| Receipt Confirm event, receiver | Receipt on the supplier order | Extensiv → Krokul | Inbound goods are received |

## How to connect today

### Custom flow through the Krokul API and webhooks

1. Ask your 3PL for a REST API Client ID, Client Secret and user login, then request a token from secure-wms.com/AuthServer/api/Token with the client_credentials grant. In Krokul, issue an API key for deals, products and stock.
2. Subscribe a Krokul webhook to card.won with a pipelineUuid filter, check x-crm-signature, read the deal with card/api-read and create the 3PL order with the deal number as the reference. Store the order ID through externalRef/api-upsert.
3. Ask the warehouse to add a webhook under Customers > Event Notifications for OrderConfirm, OrderCancel, Receipt Confirm and Inventory Summary Update, scoped to your customer, with your https endpoint.
4. Verify the Signature header against the public key from secure-wms.com/events/webhook/key, reply at once, then follow resource.href and write to Krokul with card/api-updateStatus, task/api-create and stock/api-adjust.

### For integrators

Extensiv signs webhook messages with RSA SHA-256 and publishes the PEM public key at a fixed URL. The receiver has three seconds to answer. Failed deliveries retry for about six hours and then sit in a dead letter queue for about three days. Events can arrive out of order, so Krokul sorts them by eventDateTimeUtc. On the Krokul side there is a public REST API, signed webhooks with a delivery log, external keys for Extensiv order IDs and a sandbox company.

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

## Questions and answers

### Does Krokul integrate with Extensiv 3PL Warehouse Manager?

Yes. Krokul integrates with Extensiv 3PL Warehouse Manager through the Krokul API and webhooks together with the Extensiv REST API and event notifications.

### Who owns the stock at the 3PL?

The 3PL warehouse. 3PL Warehouse Manager keeps the inventory record, and Krokul mirrors the stock summaries in a separate stock location that only Extensiv events update.

### Can I connect without my warehouse?

No. The 3PL issues the API credentials and the user login, and webhooks are set up in its 3PL Warehouse Manager account for your customer.

### Why does Krokul read the order after each event?

The Extensiv event carries the event type, a few fields and a link to the resource. Krokul follows that link to get the full order or receipt unless the warehouse turned on full resources in the payload.

## Limits

The 3PL warehouse owns the inventory record in 3PL Warehouse Manager, and Krokul shows those quantities in a separate stock location without changing them. API credentials and the user login come from your warehouse, which also decides which events it shares. Billing between you and the 3PL stays in Extensiv.

## Related services

- [ShipHero](https://krokul.com/en/integrations/shiphero/index.md)
- [ShipStation](https://krokul.com/en/integrations/shipstation/index.md)
- [Shippo](https://krokul.com/en/integrations/shippo/index.md)
- [Shopify](https://krokul.com/en/integrations/shopify/index.md)
- [Amazon](https://krokul.com/en/integrations/amazon/index.md)
- [FedEx](https://krokul.com/en/integrations/fedex/index.md)

[Shipping and logistics](https://krokul.com/en/integrations/category/shipping/index.md)

Extensiv and 3PL Warehouse Manager are trademarks of Extensiv, Inc. Krokul is not affiliated with Extensiv.

Updated: 2026-10-15

---

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