Yes. Krokul CRM integrates with the Meest delivery service through the Meest API 3.0. A parcel is created from the deal card with the POST /parcel method, the barcode and the sticker stay in the shipment, and Krokul records Meest tracking events on the deal on its own. The flow between the services runs on the Krokul API and signed webhooks.
A manager clicks «Ship with Meest» on the deal. Krokul fills in the recipient from the deal contact, the weight and the payer, and passes the deal number in orderNumber. The parcel is created with the POST /parcel method, and Meest returns parcelID and barCode, which Krokul stores in the shipment.
The receiverPay field of the parcel decides whether the recipient or the sender pays for delivery. Krokul takes it from the company setting, and the manager can change it on the deal. Before creating a parcel with cash on delivery, Krokul reads allowedCOD from /contractClientInfo/{contractID} and shows the COD amount only where the contract allows it.
After the parcel is created, the manager prints the Meest sticker right from the shipment. Krokul gets it with the /print/sticker100/{printValue} method, so the warehouse needs no access to the Meest account.
Daily and during the day, Krokul reads /trackingByDate/{searchDate}, finds the deal by the parcel barCode and adds an event with eventDateTime and a description to the feed. A delivery event moves the deal to the next stage under the company rule, and a return creates a task for the manager.
In the parcel form, the city and branch are picked from a list that Krokul takes from the Meest /citySearch and /branchSearch directories. This keeps a branch that does not exist out of the parcel.
| Meest | Direction | Krokul | When |
|---|---|---|---|
| /citySearch and /branchSearch directories | Meest → Krokul | City and branch fields in the parcel form | While the form is filled in |
| Parcel (POST /parcel): recipient, weight, receiverPay, payType, orderNumber | Krokul → Meest | Deal and deal contact | A manager creates a parcel |
| COD and the contract allowedCOD | Krokul → Meest | Cash on delivery amount in the shipment | When the parcel is created |
| parcelID and barCode | Meest → Krokul | Shipment in the deal card, deal feed | In reply to the parcel creation |
| 100×100 sticker (/print/sticker100) | Meest → Krokul | Print button in the shipment | When the manager asks for it |
| Tracking events: eventDateTime, eventCode, description | Meest → Krokul | Shipment status, deal feed and stage | Krokul polls /trackingByDate and /tracking/{trackNumber} |
card.statusChanged filtered by the shipping stage. Check the x-crm-signature header of every delivery against your secret.card/api-read, creates the parcel with POST /parcel and links parcelID to the deal through externalRef/api-upsert.activity/api-create.Yes. Krokul fills in the recipient from the deal contact, creates the parcel through the Meest API and stores the barcode in the deal shipment.
Krokul reads Meest tracking on a schedule and records every event on the deal. Meest sends no events, so Krokul does the polling itself.
The required receiverPay field of the parcel sets this. Krokul has a company default, and the manager can change it for a single deal.
Yes, if the contract allows it. Krokul checks the contract allowedCOD and only then passes the COD amount to the parcel.
The Meest API sends no events about parcel movement, so Krokul fetches tracking on a schedule. Cash on delivery is available if your contract with Meest allows it.
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.
Meest is a trademark of its owner. Krokul is not affiliated with Meest.