Yes. Krokul CRM integrates with FedEx through the FedEx APIs. A manager compares FedEx rates and transit times on the deal, Krokul creates the FedEx shipment with its label and tracking number, and books the courier pickup. FedEx tracking webhooks then push each scan to Krokul, so the deal shows where the parcel is and moves on delivery.
While the deal is still open, the manager enters the package weight and Krokul sends the client company address to the FedEx Rates and Transit Times API. Krokul lists each FedEx service with your account rate and the expected transit time. The chosen service is kept on the shipment of the deal.
After the deal is won, Krokul calls the FedEx Ship API with the sender, the recipient from the client company and the packages. FedEx returns the tracking number and the label. Krokul stores both on the deal, ready to print in the warehouse.
The warehouse picks a ready time, and Krokul sends a Pickup Request for that FedEx account and address. The pickup confirmation is saved next to the shipment. FedEx rejects ready times in the past, so Krokul offers only future slots.
Krokul subscribes each new tracking number to FedEx Advanced Integrated Visibility. Every scan arrives as a webhook and appears on the shipment with its time and place. A delivery event moves the deal to the next stage, and an exception opens a task for the account manager.
Krokul sends the client company address to the FedEx Address Validation API before the label is made. For the United States and Canada the answer also says whether the address is business or residential, which changes the rate.
| FedEx | Direction | Krokul | When |
|---|---|---|---|
| Rates and transit times | FedEx → Krokul | Shipment of the deal (service and price) | The manager prepares the offer |
| Shipment with tracking number and label | Krokul → FedEx | Won deal and client company address | The manager confirms shipping |
| Pickup request and confirmation | Krokul ↔ FedEx | Pickup time on the shipment | The warehouse sets a ready time |
| Tracking webhook event | FedEx → Krokul | Shipment status, deal stage on delivery | Each scan of the parcel |
| Exception event | FedEx → Krokul | Task for the account manager | FedEx reports a delay or problem |
| Address validation result | FedEx → Krokul | Client company address | Before the label is created |
Yes. Krokul integrates with FedEx through the FedEx APIs for rates, shipments, pickups, address checks and tracking, and through the Krokul API and webhooks for custom flows.
A FedEx account number and a project on the FedEx Developer Portal with that account linked. The project gives the API key and secret that Krokul uses.
No. Krokul subscribes each tracking number to FedEx tracking webhooks and receives scans as they happen. For accounts without webhooks, Krokul can check open shipments in batches of up to 30 numbers.
Krokul sorts the events of a shipment by their scan time, so a late delivery scan still closes the shipment and an older in-transit event does not reopen it.
Shipping with the FedEx APIs needs a FedEx account number linked to a project on the FedEx Developer Portal. FedEx bills tracking webhooks monthly per subscribed tracking number, and it does not promise that events arrive in the order they happened.
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.
FedEx is a registered trademark of Federal Express Corporation. Krokul is not affiliated with FedEx.