DEMO PROJECT / ORDERS · ANALYTICS · NOTIFICATIONS

RetailCRM orders: analytics and notifications.

I build order analytics and team notification systems, connecting CRMs, summaries and Telegram bots. This RetailCRM example shows order counts and values, sources, trends and notifications for large orders.

My role
CRM connection, analytics screen and bot
What is inside
Order updates, analytics and notifications
Result
An order summary and notifications for large orders.

What needed to be done.

The task was to bring RetailCRM orders into a summary and notify staff about orders above a set value. Acknowledging the notification had to remain separate from changing the order.

  • Connected RetailCRM order retrieval and organised the data in a consistent format.
  • Set up updates by order ID so later imports update existing records.
  • Built the analytics screen and a bot with notification acknowledgement.
  • Investigated order loading errors and missing enquiry sources.

How it works.

  1. Fetch orders from the CRM

    The system retrieves CRM orders and collects the details needed for reporting.

  2. Update the database and analytics

    Orders are updated in a shared database and shown in the analytics view.

  3. Alert and acknowledge

    The bot checks the amount rule and the alert log, then stores the employee's acknowledgement.

The order source needs to be saved.

During integration, I found that enquiry sources were not being saved without configuring extra CRM fields. I investigated the cause and prepared a way to restore the data from an export.

Acknowledgement does not change the order.

Orders and notifications have separate records. Before sending, the system checks whether it has already created that notification.

Implementation and example.

The original dashboard is filled with fictional orders. It shows order count and value, trends and sources. Order value does not mean paid revenue. The UI is in Russian.

A separate example illustrates notification acknowledgement. Its interface was created for the portfolio; it does not send messages or change real orders.

DIAGRAM OF THE IMPLEMENTED SYSTEM

  1. Orders from the CRM

    Orders, statuses, items, totals and custom fields.

  2. Shared order database

    New orders are added and existing ones are updated by order ID.

  3. Analytics and notifications

    Metrics, order card and alert acknowledgement.

Architecture diagram of the project. Live data and connections are not shown.

The result.

The demo brings CRM orders into one summary and flags large orders through Telegram. Notification acknowledgement is recorded separately and does not change the order status.

Technologies and implementation details

Python, RetailCRM REST API, Supabase/PostgreSQL, JavaScript/Chart.js, Vercel and the Telegram Bot API. The integration handles pagination, timeouts and API limits.

Let's discuss your task.

If order reports are assembled by hand or important enquiries get lost, tell me which CRM you use. We can discuss the summary and notifications your team needs.

Discuss a CRM integration ↗︎
PROJECT SCREEN