Yes. Krokul CRM integrates with Adobe Commerce (Magento). A placed sales order becomes a Krokul deal with lines matched by SKU, Krokul writes source item quantities back to the store, and a shipped deal creates the Magento shipment with its tracking number. Invoices and credit memos from Commerce show up on the deal. The link runs through the Krokul app in Zapier, Make, n8n or Albato, or through the Krokul API and webhooks together with the Commerce REST API.
Automation platformsZapierMaken8nAlbato
When a buyer places an order, Adobe I/O Events notifies the Krokul connector, which reads the sales order through the REST API. Krokul finds the customer as a contact, links the billing company to a client company and opens a deal whose items point to Krokul products with the same SKU. Its increment ID becomes the external key of the deal.
Each Krokul warehouse maps to an inventory source in Commerce. When stock moves in Krokul, the connector updates the source item quantity for that SKU, so the storefront and the sales team read the same balance.
When the deal ships with a tracking number, Krokul calls the ship action of the sales order with the shipped items and a track for the carrier. Commerce changes the order state, and the account manager adds no comment by hand.
An invoice created in Commerce records the amount on the deal payment. A credit memo records the refund and moves the deal to the stage you mapped, so finance and sales read one history.
| Adobe Commerce | Direction | Krokul | When |
|---|---|---|---|
| Sales order (order placed event, then REST read) | Adobe Commerce → Krokul | Deal with lines matched by SKU; increment ID as key | An order is placed |
| Sales order invoice | Adobe Commerce → Krokul | Payment on the deal | The order is invoiced |
| Credit memo | Adobe Commerce → Krokul | Refund on the deal, stage change | A credit memo is created |
| Shipment with track | Krokul → Adobe Commerce | Shipment of the deal | The deal ships |
| Source item quantity | Krokul → Adobe Commerce | Stock balance per warehouse | Stock changes in Krokul |
| Customer | Adobe Commerce ↔ Krokul | Contact and client company | A customer or client company is created |
Yes. The flow relies on the REST API, which Magento Open Source and Adobe Commerce share. Order notifications through Adobe I/O Events need an Adobe Commerce setup, so on Magento Open Source the flow reads new orders on a schedule.
You map each Krokul warehouse to one source. Krokul writes the quantity per source item, and Commerce calculates salable quantity as usual.
The billing company of an order becomes a Krokul client company. Shared catalogs, negotiable quotes and purchase order approvals stay in Adobe Commerce.
In the run history of your flow, which names the sales order and the failing step, such as an unknown SKU. On the Krokul side, the webhook delivery log shows each event sent and lets you redeliver it after the fix.
Adobe Commerce B2B features such as shared catalogs, negotiable quotes, requisition lists and purchase order approvals stay in Commerce. Krokul keeps the buyer, the deal, stock and delivery.
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.
Adobe Commerce and Magento are trademarks of Adobe Inc. Krokul is not affiliated with Adobe.