CoreviaFlowCOREVIAFLOWDIGITAL PROJECT COMPANY Leave a request
EN UA RU
Warehouse & DeliveryUA

Meest integration & automation

A Meest waybill is created straight from the deal, the sticker prints from the CRM, and the delivery status updates on the card by itself — the manager stops copying addresses into the Meest cabinet.

Meest is a Ukrainian postal and delivery operator: branches, parcel lockers, courier delivery, international shipping. For an online store or a wholesaler it means dozens of parcels a day, and each one is registered in the Meest cabinet by hand: the address is copied from the order, the sticker is printed, the tracking number is pasted back. CoreviaFlow connects Meest to your CRM so that the waybill is created from the deal, the sticker prints in one click, and the delivery status comes back to the card on its own.

What we connect

  • You need a business contract with Meest and a login to its business cabinet — we do not issue them, we connect what you already have. The login is stored on the CRM side, and the connection renews its access key by itself, because Meest issues it for one day.
  • Together we decide which parts you need: creating parcels from the deal, printing stickers and registers, choosing a branch or a parcel locker, calculating the cost and the delivery date, calling a courier, tracking statuses.
  • We set up the programmatic connection to Meest through its official documented interface and match the fields: sender and recipient, delivery type (to the door or to a branch), payment terms, parcel size and weight.
  • The CRM uses the Meest directory of cities, streets and branches, so the manager picks the branch from a list instead of typing it and the parcel does not go astray because of a typo.
  • We test on a few real parcels next to your current process: create, print, hand over, follow the status — and compare with what the Meest cabinet shows.
  • Go-live: statuses are refreshed regularly (Meest gives all changes for the last two hours in one request), and if a parcel is refused or returned, the manager gets a notice on the deal.

Automation scenarios

01

The waybill is created from the deal

Before the manager opens the Meest cabinet, retypes the recipient, the address and the contents from the order, then pastes the parcel number back into the CRM.

After one button on the deal creates the parcel in Meest with the data already on the card, and the parcel number is saved on the deal at once.

02

Stickers and the daily register in one click

Before at the end of the day someone prints stickers one by one from the cabinet and writes up the list of parcels for the courier.

After the CRM prints the stickers for all today's parcels on A4 sheets, forms the register and orders the courier in the same step.

03

The delivery status is on the card and the customer knows about it

Before the customer asks 'where is my parcel?', the manager searches the tracking page and answers by hand.

After the CRM refreshes the status itself — sent, arrived at the branch, delivered, refused — and sends the customer a message through the channel you already use, while the manager sees a refused parcel the same day.

04

The delivery cost is known while talking to the customer

Before the manager guesses the delivery cost and date and later apologises for the difference.

After the CRM asks Meest for the cost and the expected date for this parcel and this branch while the customer is still on the line.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

  • Meest publishes an official API v3.0 with an OpenAPI/Swagger description; authentication is by the contractor's login and password, which return an access token.

    Source: wiki.meest-group.com ↗ checked 2026-09-28
  • A parcel is created with full data: contents, sender, recipient, payment terms and delivery date.

    Source: wiki.meest-group.com ↗ checked 2026-09-28
  • Tracking returns the history of a parcel's operational statuses, and a separate method returns all status changes within a two-hour window for bulk synchronisation.

    Source: wiki.meest-group.com ↗ checked 2026-09-28
  • The API includes a directory of branches and parcel lockers with filters, cost and delivery-date calculation, and printing of 100×100 mm stickers, A4 sheets and registers.

    Source: wiki.meest-group.com ↗ checked 2026-09-28
  • A register of parcels and a courier call request are created in one request.

    Source: wiki.meest-group.com ↗ checked 2026-09-28
  • On its business pages Meest offers a comprehensive API integration with the client's own e-commerce software.

    Source: ua.meest.com ↗ checked 2026-09-28

Limits

The connection works only with a business contract with Meest: requests are made under the contractor's login and password and refer to the contract number, so a personal account is not enough. The access token issued by Meest lives 24 hours from creation and has to be renewed — the connection does this itself, but if the password in the cabinet changes, it must be updated in the CRM too. A register and a courier call can be edited only while the register is not yet dispatched, and deleted only until the courier has left, so late corrections go through the Meest support line. The official documentation is in Ukrainian only, and its interactive page needs JavaScript; the full description is available as a file. Meest limits the intensity of requests from one user, so status refreshes are scheduled rather than continuous. Of ready-made connectors Meest officially publishes only a module for 1C; modules for store or CRM platforms are not confirmed on Meest's official pages, so we connect through the documented interface rather than promising a plug-in.

Screenshots

Meest openAPI 3.0 documentation page
The official Meest openAPI 3.0 documentation for the Meest Poshta system: this is the interface through which the CRM creates parcels, prints stickers and follows statuses. Source: wiki.meest-group.com ↗
Meest openAPI: workflow, access key lifetime and request limits
The workflow section of the Meest openAPI documentation: sign-in, addresses, parcels, printing and tracking, plus the access key lifetime and the request limit the connection has to respect. Source: wiki.meest-group.com ↗

How to start

Three steps from a first message to work on your project.

  1. 01

    Leave a request

    Describe the task in the form — in text or by voice. Budget and timing are optional.

  2. 02

    We review and estimate

    A developer studies the brief, asks about anything unclear and sends an estimate.

  3. 03

    We start

    Once scope and price are agreed, the work begins.

or write to info@coreviaflow.space

Questions

We already have a Meest contract and a cabinet. What else is needed?
Only the login to the business cabinet and the contract number. We store the login on the CRM side and the connection keeps its access fresh by itself; nothing changes in your contract with Meest.
Can we keep working in the Meest cabinet as well?
Yes. A parcel created from the CRM is visible in the cabinet like any other, and the statuses match. The only thing to keep in mind: a parcel created in the cabinet by hand will not know which deal it belongs to unless its number is added to the card.
How often are the statuses refreshed?
On a schedule we agree on. Meest can return all status changes for the last two hours in one request, so the CRM refreshes every parcel in flight without asking about each one separately.
Do you send international parcels through Meest too?
The documented interface has a customs declaration form among its printouts, so international shipments are technically reachable; which directions and conditions apply to you is fixed in your contract with Meest, and we confirm it before promising the flow.

Tell us what needs to be connected

Describe the task in text or a voice message. We look at your setup and reply with a plan.