A delivery module for RetailCRM on RelaxDev: how ADelivo works
ADelivo is a delivery service for online stores. It is now in the RetailCRM Marketplace: a store installs the module with one button, an order from the CRM goes to the dispatcher and the courier, and the courier, status and arrival time come back to the order card. All of it — from the website and database to the route planner and its own road graph — runs on RelaxDev.
Here is what the integration does and which parts of the platform it relies on.
- 🔁 Two-way sync: address, date, time, comment, recipient and courier change both in RetailCRM and in ADelivo, whoever changes them.
- 🏬 Warehouses are bases: a courier's route starts at the order's shipping warehouse; a second warehouse becomes a separate base on its own.
- 🛡 Guaranteed delivery in Moscow: orders that weren't given to the store's own couriers in time are picked up by ADelivo couriers.
- 🚀 5 releases in 45 minutes: on the day this was written, ADelivo shipped five fixes in a row, each built in 4–5 minutes.
ADelivo dispatcher dashboard: the day's orders on a map of Moscow The dispatcher dashboard on a regular day. Courier names and addresses are changed.
What a RetailCRM store gets
The operator stays in RetailCRM and never opens a second interface. In the order they pick the "ADelivo" delivery and a tariff, save — and the order is already with the dispatcher: the address is on the map, the time slot is parsed, the items are visible to the courier.
| In RetailCRM | In ADelivo |
|---|---|
| An order is saved with "ADelivo" delivery | The order is on the dispatcher's map, the slot is parsed, the items are visible to the courier |
| The address, time or items change | The courier gets a push, the manager sees the change on the board |
| A courier is picked in the "ADelivo courier" field | The order goes into that courier's route |
| — | Courier assigned, on the way, delivered: status, courier's phone, arrival time and handover photo — in the "Delivery" block |
| — | The dispatcher fixes the address or reassigns the courier — the same change appears in the RetailCRM order right away |
The address goes from ADelivo to RetailCRM as fields — street, building, block, entrance, floor, flat, metro — not as a line of text. Otherwise RetailCRM politely answers "success" and keeps the old address: it builds the address text from the fields.
The "Delivery" block of a RetailCRM order: courier, phone and arrival time
Pricing. "Own couriers" — 20 ₽ per order: dispatching, AI routes, the courier app, the internal exchange. "Full outsourcing" in Moscow — ADelivo couriers, within the MKAD ring road from 600 ₽ on foot and from 700 ₽ by car. The two can be combined: on regular days the store's couriers deliver, and at peaks whatever they can't handle goes to the external ADelivo exchange. The first 7 days are free, after that an invoice once a month to the company's details. Details are in the module documentation.
Not on RetailCRM yet? Sign up with ADelivo's partner link — the module can be installed right after that.
Where RelaxDev comes in
ADelivo isn't one app but several services. Each is a regular project on RelaxDev with its own build, variables and logs.
RetailCRM ──▶ adelivo.ru (Next.js) ──▶ PostgreSQL + Redis
│
├──▶ routes — day planner (PostgreSQL + Chroma)
└──▶ OSRM — travel time on the road graph| What a delivery service needs | How it's done on RelaxDev |
|---|---|
| Ship fixes several times a day | Build from GitHub after merge — 4–5 minutes to production; preview environments for branches |
| Orders, routes, couriers, payouts | The platform's PostgreSQL, database access from the panel and over MCP |
| Background jobs on several app instances | The platform's Redis: CRM polling, geocoding and the autopilot run once, however many instances are up |
| Plan the day's routes for dozens of couriers | A separate routes project with its own database and a Chroma vector database |
| Travel time between hundreds of points without paying per request | Its own OSRM — a separate project with maps of Moscow and its region and Novosibirsk |
| RetailCRM webhooks to its own domain | The adelivo.ru domain with an automatic certificate |
Its own OSRM instead of paid matrices
To build the day's routes you need travel times between all the points: hundreds of addresses mean tens of thousands of pairs. Paid map APIs charge per request and have daily limits. So next to ADelivo runs its own OSRM, a routing engine on the OpenStreetMap road graph. It's a regular Docker project on RelaxDev with maps of Moscow with its region and Novosibirsk with Berdsk: requests are free and have no daily limit.
OSRM knows nothing about traffic. ADelivo picks the correction for the hour and the day of the week from its own measurements, and when a specific route is calculated, maps with live traffic back it up.
routes: the day planner
Order distribution lives in a separate service. A solver assigns orders to couriers based on the timing of real past deliveries and rules — time slots, trips, walking and driving couriers — and a model checks the plan and explains the choice. The model's version is used only if it follows the rules and is no worse. The dispatcher gets a draft of the day's routes in about a minute and only fixes the disputed spots.
A separate project means a separate build and a separate release: the planner is updated without touching the app the dispatchers are working in at that moment.
The day's routes in ADelivo: points with time slots and the order of stops The day's routes: points with time slots on the map, the order of stops, plan and fact for each point.
MCP: from a question to a fix in production
Most of ADelivo's development goes through RelaxDev MCP: an AI assistant reads the app's logs, queries the database and watches deployments by itself.
An example from the same day. A dispatcher asked why an order was in the list but not on the map. The assistant looked the order up in the database: no coordinates and no error mark either. In the logs it found the cause: two webhooks for the same order arrived at the same moment, and the second one overwrote the point the first had found. Then came the fix, a PR, a merge — and a few minutes later it was in production. A safety net came along with it: if an order still ends up without a point, within half an hour it is sent for geocoding again, and if that doesn't help either, the store gets a notification in Telegram and by email.
Logs, the database and deployments — all in one conversation with the assistant, without switching between consoles.
Numbers
- 📦 700 orders a day with 100 couriers on the line — March 8, at one of the deployments.
- ⏱ 4–5 minutes from merge to production.
- 🚀 5 releases in 45 minutes — November 7.
- 🗺 3 services — the app, the planner and OSRM — live side by side as regular platform projects.
Summary
- ✅ The ADelivo module in the RetailCRM Marketplace: courier, status and arrival time in the order card, edits in both directions.
- ✅ A Moscow store can start with its own couriers and not fear peaks: ADelivo couriers pick up the rest.
- ✅ The whole system — app, database, planner and road graph — runs on RelaxDev.
Connect delivery to RetailCRM — adelivo.ru/integracii/retailcrm. No RetailCRM account — sign up with the partner link. Run your own service the same way — relaxdev.ru.
This is a translation of the original Russian article. Comments are on the Russian page.