Krokul CRM integrates with SAP Ariba (SAP Business Network) and Coupa over cXML, and to SPS Commerce through the SPS Transaction API. A purchase order becomes a deal keyed by the PO number, and Krokul sends the order confirmation, ship notice and invoice back from the deal. Other procurement networks and EDI providers connect through the Krokul app in Zapier, Make, n8n and Albato and the Krokul API.
A purchase order opens a deal for the buying client company, and a new buyer fires clientCompany.created. The manager checks quantities and dates and wins the deal, and card.won sends the confirmation with each line accepted, changed or backordered. It goes out as a cXML ConfirmationRequest or as an 855 through SPS Commerce.
When the deal ships, Krokul sends the ship notice with lines, cartons and tracking number. The invoice document fires document.created and goes out with the same PO number and lines, so the buyer matches it to the order and the receipt.
Krokul matches each PO line to a product by supplier part number or item number, and the deal reserves stock like a direct order. A line without a match appears in the sync journal before the confirmation goes out.
Network setup stays with the buyer and the network. On SAP Business Network, cXML needs an enterprise supplier account, each Coupa customer enables cXML for its suppliers, and SPS Commerce keeps retailer setup and EDI translation. Krokul keeps the account, the deal, stock and the documents.
No. SPS Commerce translates documents for each retailer, and SAP Ariba and Coupa exchange cXML with Krokul directly.
Coupa and SPS Commerce are set up per buying customer or retailer. On SAP Business Network cXML order routing comes with your enterprise supplier account.
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.
Product names are trademarks of their owners. Krokul is not affiliated with the services listed unless a page says otherwise.