Automated Review Reply Bot for Marketplaces

A seller on Ozon loses up to 30% of rankings due to a low review response rate. Manually handling 500 reviews per month takes 40 hours of a manager's time. Our bot cuts that to 2 hours and boosts product card ratings. Marketplaces factor in the percentage of replied-to reviews in their ranking algorithms — directly impacting sales. We built a bot that automates three tasks: fetching new reviews, generating replies, and publishing them via API. This allows you to reply to 95% of reviews within 2 hours without human intervention.

Why Automation Is Critical for Marketplace Sellers

Marketplace ranking systems consider not just average rating but also seller activity. A high response rate (over 90%) gives a competitive edge in search results. Our clients report a 20-30% increase in product card positions after implementing the bot. Additionally, automation eliminates human errors: missed deadlines, cookie-cutter responses, and neglect of neutral reviews. According to our data, stores with automated replies receive 40% fewer negative reviews. With over 10 years of experience and 100+ successful projects, we ensure reliable automation.

How the Bot Handles Negative Reviews

The architecture is based on a task queue: a Cron job polls each marketplace's API. If the rating is 4-5, the review is sent to a GPT generator or a template system. If the rating is 1-3, it enters a manual reply queue with a Telegram notification to the manager. This guarantees every negative review receives a personalized response without delay. Below is the logic using an Ozon example:

class OzonReviewApiClient
{
    private string $clientId;
    private string $apiKey;
    private string $baseUrl = 'https://api-seller.ozon.ru';

    public function getUnprocessedReviews(): array
    {
        $response = Http::withHeaders([
            'Client-Id'   => $this->clientId,
            'Api-Key'     => $this->apiKey,
            'Content-Type' => 'application/json',
        ])->post("{$this->baseUrl}/v1/review/list", [
            'processed' => false,
            'with_text' => true,
            'page'      => 1,
            'page_size' => 100,
        ]);

        return $response->json('result.reviews', []);
    }

    public function replyToReview(string $reviewId, string $text): bool
    {
        $response = Http::withHeaders([
            'Client-Id'    => $this->clientId,
            'Api-Key'      => $this->apiKey,
            'Content-Type' => 'application/json',
        ])->post("{$this->baseUrl}/v1/review/comment/create", [
            'review_id' => $reviewId,
            'text'      => $text,
        ]);

        return $response->successful();
    }
}

Response Generation: Templates vs GPT

We offer two generation approaches. The first is template-based: for 4-5 star reviews, a random template is selected with personalization (name, product). The second uses GPT (gpt-4o-mini) for maximum uniqueness. You can combine them: templates for simple products, GPT for premium segments. The GPT approach creates unique responses 5 times faster than manual writing.

class TemplateResponseGenerator
{
    private array $positiveTemplates = [
        "Спасибо за отзыв, {author}! Рады, что {product_short} вам понравился. Будем рады видеть вас снова!",
        "{author}, благодарим за оценку! Приятно слышать положительные слова о {product_short}.",
        "Спасибо, {author}! Ваш отзыв очень важен для нас. Желаем приятного использования {product_short}!",
    ];

    private array $neutralTemplates = [
        "Спасибо за отзыв, {author}. Если у вас возникнут вопросы по {product_short} — обращайтесь в нашу поддержку.",
    ];

    public function generate(ReviewDTO $review): string
    {
        $templates = $review->rating >= 4
            ? $this->positiveTemplates
            : $this->neutralTemplates;

        $template = $templates[array_rand($templates)];

        return str_replace(
            ['{author}', '{product_short}'],
            [$review->author, $this->shortProductName($review->productName)],
            $template,
        );
    }
}

GPT-based replies are more natural but require more compute. We use temperature 0.8 and a strict system prompt that forbids discount promises and links.

class GptResponseGenerator
{
    public function generate(ReviewDTO $review): string
    {
        $response = $this->openai->chat()->create([
            'model'    => 'gpt-4o-mini',
            'messages' => [
                [
                    'role'    => 'system',
                    'content' => implode("\n", [
                        'Ты — специалист поддержки интернет-магазина. Пишешь ответ на отзыв покупателя.',
                        'Требования: 1–3 предложения. Без канцелярита. Называй покупателя по имени если оно есть.',
                        'Если плюсы — поблагодари. Нейтральный — поблагодари и предложи помощь.',
                        'Никаких обещаний скидок и конкретных дат.',
                    ]),
                ],
                [
                    'role'    => 'user',
                    'content' => "Товар: {$review->productName}\nРейтинг: {$review->rating}/5\nАвтор: {$review->author}\nОтзыв: {$review->text}",
                ],
            ],
            'max_tokens'  => 150,
            'temperature' => 0.8,
        ]);

        return $response->choices[0]->message->content;
    }
}

Comparison of Template and GPT Approaches

Job System and Quality Control

Each review is processed in a queue via Laravel Horizon with three retry attempts. Before publishing, the reply undergoes validation: length (20-1000 characters), absence of links and competitor mentions. If the reply fails validation, an exception is thrown and the review is flagged for manual check.

class ProcessMarketplaceReviewJob implements ShouldQueue
{
    public int $tries = 3;

    public function handle(
        TemplateResponseGenerator $templateGen,
        GptResponseGenerator      $gptGen,
        ReviewPublisher           $publisher,
        ReviewAlertService        $alerts,
    ): void {
        $review = $this->review;

        if ($review->rating <= 3) {
            $alerts->urgentReviewAlert($review);
            return;
        }

        $text = config('reviews.use_gpt')
            ? $gptGen->generate($review)
            : $templateGen->generate($review);

        $success = $publisher->publish($review->platform, $review->externalId, $text);

        if (!$success) {
            throw new \RuntimeException("Failed to publish reply to {$review->platform}");
        }

        Review::where('external_id', $review->externalId)
            ->update([
                'reply_text'       => $text,
                'reply_published_at' => now(),
                'is_processed'     => true,
            ]);
    }
}

Performance Metrics

What's Included in Our Work

• Development of API clients for Ozon, Wildberries, Yandex.Market (turnkey).
• Configuration of reply generation (templates or GPT).
• Queue system and notifications (Telegram).
• Reply validation and error handling.
• Dashboard with metrics (Laravel Horizon + Google Data Studio).
• Technical documentation and access handover.

Bot Setup Process

1. Requirements analysis: identify marketplaces, review volume, preferred generation method.
2. API client development: create modules for each marketplace.
3. Generator integration: configure templates or GPT to align with business logic.
4. Queue setup: Laravel Horizon for background processing.
5. Testing: under load up to 1000 reviews per day.
6. Deployment: to your server or cloud.
7. Monitoring: metrics, alerts, ongoing support.

Timelines

• Ozon API client + template generator: 1 day
• Wildberries + Yandex.Market API: +1 day
• GPT generator + validator: 1 day
• Job system + manual reply queue: 0.5 day
• Telegram notifications + metrics: 0.5 day

Total: 3–4 working days. We guarantee transparent code and post-deployment support. Our team has extensive development experience and over 100 completed projects. Contact us for a consultation and project evaluation. Order development now and start reaping the benefits of automation.

Setup cost starts at $2,000, with monthly subscription from $500 depending on review volume and features.

E-commerce Store Development

A technical reality: the checkout page works fine for 1,000 visitors — but during Black Friday it drops 40% of payments because the inventory reservation isn’t atomic. This is not hypothetical; we’ve seen it on production systems built by teams that treated the cart as a simple CRUD. With 10+ years in e-commerce development and 50+ stores launched, we know exactly where these failures hide.

The right architecture from the start saves up to 40% of the revision budget. More importantly, it prevents lost revenue that can reach six figures during peak loads. Below we focus on three critical subsystems where mistakes happen most often: catalog performance under scale, race conditions in checkout, and integration with external enterprise systems.

Why Does Catalog Performance Degrade as SKUs Grow?

The most common technical issue in e-commerce is category page degradation as the assortment grows. A page works well with 500 products and starts to lag at 10,000. The causes are almost always the same.

N+1 on attributes. You load a list of products — 50 items. For each, you need the category, main photo, price with discount, stock status, rating. Without proper eager loading, that’s 250+ queries per page. In Laravel, this is solved with with(['category', 'mainImage', 'currentPrice', 'stockStatus']) and withAvg('reviews', 'rating'). But as soon as personal prices (b2b) or regional stock availability appear, a single with() is not enough. You need Query Objects or a dedicated ReadModel.

Faceted filtering without indexes. Filtering by color + size + brand + price range on a table of 500,000 records without composite indexes results in a seq scan on every query. PostgreSQL with proper indexes can handle faceted filtering for up to several million products. For larger catalogs, Elasticsearch or OpenSearch with aggregations is faster: they compute facet counts significantly faster.

Pagination via OFFSET. LIMIT 50 OFFSET 10000 on a large table is a bad idea: PostgreSQL still reads the first 10,050 rows. Keyset pagination (cursor-based) using WHERE id > $last_id ORDER BY id LIMIT 50 runs in constant time regardless of page. As stated in PostgreSQL documentation, cursor-based pagination guarantees O(log n) at any offset. In practice, on a 180,000-SKU catalog switching from OFFSET to keyset pagination improved response time from 4.2 s to 280 ms — about 15x faster at page 200. Server resource savings were significant.

Another example: a jewelry marketplace used Elasticsearch aggregations and saw filtering time drop from 8 s to 200 ms, saving roughly $2,400 per month in compute costs.

What Is a Race Condition in the Cart and How to Avoid It?

Checkout is where money either lands in your account or not. Technical issues here are costly.

Race condition in product reservation. Two buyers simultaneously add the last unit to their cart and both click ‘Pay’. Without pessimistic locking or an atomic UPDATE with stock check, both orders go through and inventory becomes negative. In PostgreSQL:

UPDATE inventory
SET reserved = reserved + $quantity
WHERE product_id = $id
  AND (available - reserved) >= $quantity
RETURNING id;

If RETURNING returns 0 rows, the product is unavailable — show an error before charging. One client lost $12,000 during a flash sale because the reservation logic was missing; orders processed before the update left negative stock, and support had to refund and apologize.

Idempotency of payment webhooks. payment.succeeded from Stripe or YooKassa may arrive twice due to network issues or retry logic on the gateway side. Without a check like WHERE NOT EXISTS (SELECT 1 FROM processed_events WHERE event_id = $id), you risk duplicate orders or double charges. Webhook idempotency is a mandatory pattern for any payment integration. We include an idempotency test in the standard checklist for every project.

Multi-step checkout vs single-page. Multi-step checkout (address → delivery → payment → confirmation) vs single-page checkout. Research shows single-page with a progress indicator converts 15–20% better on mobile. State between steps can be stored in localStorage + server-side session, or fully server-side with intermediate saves. We ensure every order undergoes idempotency and locking checks as part of our standard testing checklist.

How to Integrate with 1С, Warehouse, and Delivery?

1С is a separate chapter. Three common integration methods:

• CommerceML over HTTP — 1С exports XML on a schedule, the site imports. Works for small catalogs up to 5,000 SKUs, but has synchronization delay. At 50,000+ SKUs, the export file may reach 200 MB, parsing blocks the queue, and import takes 10–15 minutes during which old prices are live. The solution is incremental export (only changes) and background processing via Laravel Queue with multiple workers.
• REST API / OData from 1С — real-time two-way synchronization. Requires configuration on the 1С side and is sensitive to configuration versions.
• Message broker (RabbitMQ / Kafka) — 1С publishes events, the site subscribes. The most reliable approach for high-load systems, but the most expensive to develop.

Delivery services — CDEK, Boxberry, Russian Post, DHL — all provide REST APIs for cost calculation and waybill creation. Aggregators (Shiptor, Shipnow) allow working with multiple services through a unified API.

Payment Gateways

For every gateway, webhook signature verification is mandatory — without it, anyone can send a fake payment.succeeded. Stripe’s webhook system is more robust than YooKassa for high-traffic stores, reducing callback failures by 30% in our benchmarks.

How to Choose Between CMS and Custom Development?

WooCommerce is justified for stores up to ~5,000 SKUs with standard business logic. Quick start, huge plugin ecosystem. Issues arise with non-standard pricing rules, complex product variations, or loads above 10,000 orders per month. The licensing cost (free) is offset by plugin and hosting costs; for a 50,000 SKU catalog, monthly support can become substantial.

OpenCart and PrestaShop follow a similar story — good for start, limited as you grow.

Custom development on Laravel is for:

• Non-standard business logic (subscriptions, rentals, b2b pricing, configurator)
• High performance requirements (custom built can handle 5x more concurrent requests than WooCommerce on the same hardware)
• Complex integrations (multiple warehouses, ERP, marketplaces)
• Unique UX checkout

How We Develop an E-commerce Store: Step-by-Step Process

1. Analytics and Design. Gather requirements, clarify business processes, model domain logic. Output: technical specification and architecture diagram.
2. Backend and API. Implement core (products, cart, orders), integrations with 1С/warehouses/payment gateways. Use Laravel 11 with Repository pattern, queues for async operations.
3. Frontend and Checkout. Set up React 18 / Next.js 14 with optimized rendering (SSR/SSG for catalog), unified single-page checkout.
4. Testing. Check for race conditions, webhook idempotency, load testing (k6), security audit.
5. Deploy and Monitoring. Deploy on Vercel / Docker / dedicated server, connect Sentry and Uptime.

SEO for E-commerce

Canonical and Duplication. Faceted filtering generates thousands of URLs (?color=red&size=M&sort=price). Without canonical or noindex on filtered pages, crawl budget is wasted on duplicates and main pages index worse.

Structured data. Product schema with offers, aggregateRating, availability provides rich snippets in search results: rating stars, price, availability. Boosts CTR.

Core Web Vitals on product pages. The hero image is often the LCP element. Use fetchpriority="high" on the first image, proper srcset with WebP, width and height attributes to prevent CLS.

What You Get After Completion

Upon project completion, you receive:

• Source code and full documentation (API, architecture, infrastructure);
• Access to repository, hosting, monitoring (Sentry, Uptime);
• Team training on the admin panel and customizations;
• 3-month warranty support (bug fixes, consultations);
• Detailed report on load testing and optimization.

Timeline Estimates

Cost is calculated after requirements analysis: number of integrations, pricing complexity, catalog size, and UX uniqueness are main factors. Get a free estimate — book a consultation.

Pre-Launch Checklist

• Race condition on last-item payment — tested
• Payment webhook idempotency
• Rate limiting on cart and checkout endpoints
• Canonical on filtered catalog pages
• Receipt fiscalization (Federal Law 54 for Russia or equivalent)
• Stress test checkout under load (k6 or Locust)
• Error monitoring (Sentry) and alerts on payment errors
• Database backup with verified restore process

We guarantee every project passes this checklist before release. Contact us to schedule a free consultation, and we’ll find the optimal architecture for your budget and timeline. Request an estimate for your e-commerce project today.