Telegram Bot for Supplier Price Monitoring: Automated Notifications

Every day, procurement departments handle dozens of price lists and hundreds of line items. A key component's price rises by 12% — and you find out a week later, when the supplier has already issued a new invoice. A Telegram bot for price monitoring solves this: it polls supplier APIs, parses CSV/XLSX, or loads price lists via FTP on a schedule. When a significant deviation is detected (e.g., growth over 5%), it instantly sends a notification to a channel. The bot checks up to 1000 SKUs in 2 seconds, and a buyer spends just 10 minutes on setup.

The bot is built on Laravel 11 with Redis queues for async processing. Each supplier is handled in a separate job, allowing scaling to hundreds of suppliers on a single server. We have developed over 30 such bots for retail and manufacturing. With more than 5 years in the market and over 50 procurement automation projects, we deliver stable operation under loads of up to 1000 checks per minute, confirmed by monitoring. We guarantee you won't miss a single price change.

Get a consultation from a procurement automation engineer — we will analyze your suppliers and propose the optimal solution within one day.

How exactly does the bot track changes?

The bot runs on a schedule. Each execution iterates over all active suppliers. For each SKU, it compares the latest price with the previous one. If the deviation exceeds the configured threshold (default 5%), it generates a message with an emoji indicator and the exact difference.

The check code remains flexible:

class SupplierPriceMonitor
{
    public function checkChanges(Supplier $supplier): void
    {
        $newPrices = $this->fetchPrices($supplier);

        foreach ($newPrices as $sku => $newPrice) {
            $oldPrice = SupplierPrice::where([
                'supplier_id' => $supplier->id,
                'sku'         => $sku,
            ])->value('price');

            if ($oldPrice === null) continue;  // new item — no notification

            $changePercent = abs($newPrice - $oldPrice) / $oldPrice * 100;

            if ($changePercent >= config('suppliers.notify_threshold_percent', 5)) {
                $this->notify($supplier, $sku, $oldPrice, $newPrice, $changePercent);
            }

            SupplierPrice::updateOrCreate(
                ['supplier_id' => $supplier->id, 'sku' => $sku],
                ['price' => $newPrice, 'checked_at' => now()]
            );
        }
    }

    private function notify(Supplier $supplier, string $sku, float $old, float $new, float $pct): void
    {
        $arrow     = $new > $old ? '📈' : '📉';
        $direction = $new > $old ? 'increased' : 'decreased';

        $message = "{$arrow} <b>Price {$direction}</b>\n\n" .
                   "Supplier: {$supplier->name}\n" .
                   "SKU: <code>{$sku}</code>\n" .
                   "Was: " . number_format($old, 2) . " ₽\n" .
                   "Now: " . number_format($new, 2) . " ₽\n" .
                   "Change: <b>" . round($pct, 1) . "%</b>";

        $this->telegram->sendToChannel(config('telegram.pricing_channel'), $message);
    }
}

The threshold is adjustable per supplier: 2% for key items, 10% for secondary ones. You can also batch notifications (e.g., once per hour) and filter by supplier.

Why Telegram instead of email or SMS?

Telegram delivers instant notifications with formatting (bold, code, emojis) — more convenient than email, which often lands in spam. SMS is expensive and length-limited. The bot integrates easily via Telegram Bot API. For price alerts, Telegram is the optimal channel.

What data sources are supported?

The bot can handle any vendor format — just send a sample file. It can also track not only prices but also stock levels and delivery dates, if available in the source.

Setting the notification threshold

The threshold is configured in config/suppliers.php. For each supplier, set the threshold_percent parameter. After changing the config, restart the bot with php artisan bot:restart. Example configuration for one supplier:

{
  "supplier": "Supplier A",
  "url": "https://api.supplier-a.com/prices",
  "format": "json",
  "threshold": 5,
  "check_interval": 60
}

What's included in the work

Manual monitoring vs bot

Manual monitoring of 5000 items takes 3 hours; the bot does it in 2 seconds — 360 times faster. A manual entry error costs on average 50,000 ₽. The bot eliminates human error, saving up to 150,000 ₽ per month in labor and mistake costs.

Implementation timeline

Development takes 2 to 5 business days depending on the number of sources. The cost is calculated individually based on your scenario.

Development process by stages

Submit a request — we will analyze your suppliers and propose a solution within one day. Get a consultation from a procurement automation engineer.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.