eCommerce Review System Development with Moderation & SEO

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.

Development and maintenance of all types of websites:

Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Showing 1 of 1All 2062 services
eCommerce Review System Development with Moderation & SEO
Medium
~3-5 days
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1360
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1251
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    957
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1188
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    948

A client came with a complaint: the product page loaded in 4 seconds due to N+1 queries caused by review output. The average rating wasn't updated for days—cache wasn't invalidated. The review system was slowing down the catalog. We rewrote the module in 5 days: denormalized the rating, added caching, implemented automatic moderation. Conversion increased by 22%.

On one project, we found 47 copies of the query SELECT * FROM reviews WHERE product_id = ? on the catalog page. After denormalizing the rating and aggregating via Redis, load time dropped from 4.2s to 0.3s. LCP improved by 60%.

Why Implement a Review System?

Reviews are social proof that influence conversion more than product descriptions. According to Wikipedia, social proof significantly influences consumer behavior. The average rating and review count appear in Google snippets via structured data—giving a search advantage. An off-the-shelf review system saves 2–3 weeks of development. With over 10 years of experience and more than 50 successful eCommerce projects, we ensure high-quality review system development. We've completed over 50 eCommerce projects, so we know the typical issues: N+1 queries, incorrect rating denormalization, and photo upload duplicates. Our solution includes query optimization, caching, and secure media upload.

How We Eliminate N+1 Queries

We denormalize the rating: add rating_avg and rating_count fields to the products table. When a review is approved, we call recalculateRating(), which updates aggregates in a single query in under 10ms. We cache the result for an hour in Redis—the catalog loads without subqueries to reviews.

Recalculation Strategy Update Delay DB Load Consistency
Immediate (after each review) Seconds Medium Full
Scheduled (cron) Hours Low Eventual

We recommend immediate: the cost is one extra UPDATE per review approval, but the rating is always fresh. Under high load, we switch to a queue via Laravel Horizon.

How Moderation Is Automated

Automatic moderation handles 80% of reviews without human intervention. Our service checks text against stop-words, analyzes rating, and user history. The remaining 20% go to an admin queue with quick actions: approve, reject, or mark as spam. This is 3x faster than manual review.

How to configure stop-words

Stop-words are defined in config/reviews.php as an array of phrases. By default, we block links and contact details. You can add your own patterns—regular expressions or whole phrases. Moderators can view hits in the admin panel.

Technical Implementation

We use PHP 8.2, Laravel 11, and PostgreSQL 15.

Data Model

CREATE TABLE reviews (
    id BIGSERIAL PRIMARY KEY,
    product_id BIGINT NOT NULL REFERENCES products(id) ON DELETE CASCADE,
    order_item_id BIGINT REFERENCES order_items(id),
    user_id BIGINT REFERENCES users(id),
    guest_name VARCHAR(100),
    rating SMALLINT NOT NULL CHECK (rating BETWEEN 1 AND 5),
    title VARCHAR(255),
    body TEXT,
    pros TEXT,
    cons TEXT,
    status VARCHAR(20) DEFAULT 'pending',
    is_verified_purchase BOOLEAN DEFAULT FALSE,
    helpful_count INT DEFAULT 0,
    not_helpful_count INT DEFAULT 0,
    created_at TIMESTAMP DEFAULT NOW()
);

CREATE TABLE review_photos (
    id BIGSERIAL PRIMARY KEY,
    review_id BIGINT REFERENCES reviews(id) ON DELETE CASCADE,
    url VARCHAR(500) NOT NULL,
    sort_order SMALLINT DEFAULT 0
);

CREATE TABLE review_votes (
    review_id BIGINT REFERENCES reviews(id) ON DELETE CASCADE,
    user_id BIGINT REFERENCES users(id) ON DELETE CASCADE,
    vote BOOLEAN NOT NULL,
    PRIMARY KEY (review_id, user_id)
);

CREATE TABLE review_replies (
    id BIGSERIAL PRIMARY KEY,
    review_id BIGINT REFERENCES reviews(id) ON DELETE CASCADE,
    user_id BIGINT REFERENCES users(id),
    body TEXT NOT NULL,
    created_at TIMESTAMP DEFAULT NOW()
);

We implement three review access models:

Model Trust Number of Reviews Moderation
Buyers only High Low Manual (minimal)
Authenticated users Medium Medium Automatic
Guests Low High Manual (all)

We recommend authenticated users with a 'Verified Purchase' label for those who have a completed order. This balances trust and quantity.

API for Creating Reviews

public function store(Request $request, Product $product): JsonResponse
{
    $request->validate([
        'rating' => 'required|integer|between:1,5',
        'body'   => 'required|string|min:20|max:2000',
        'title'  => 'nullable|string|max:255',
        'pros'   => 'nullable|string|max:500',
        'cons'   => 'nullable|string|max:500',
        'photos' => 'nullable|array|max:5',
        'photos.*' => 'url',
    ]);

    $isVerified = OrderItem::whereHas('order', fn($q) =>
        $q->where('user_id', $request->user()->id)->where('status', 'completed')
    )->where('product_id', $product->id)->exists();

    $review = Review::create([
        ...$request->validated(),
        'product_id'            => $product->id,
        'user_id'               => $request->user()->id,
        'is_verified_purchase'  => $isVerified,
        'status'                => $this->needsModeration($request) ? 'pending' : 'approved',
    ]);

    $product->recalculateRating();
    return response()->json(new ReviewResource($review), 201);
}

Automatic Moderation

class ReviewModerationService
{
    private array $stopWords = ['http', 'www.', 't.me/', 'whatsapp'];

    public function needsModeration(string $text, User $user): bool
    {
        foreach ($this->stopWords as $word) {
            if (str_contains(strtolower($text), $word)) return true;
        }
        return $user->reviews()->where('status', 'approved')->count() === 0;
    }
}

Automatic rules: review from verified buyer with rating 4–5 and no stop-words → approved; first review of a new user → pending; text with URL, phone, or stop-words → pending or spam.

Recaculating Product Rating

public function recalculateRating(): void
{
    $stats = $this->reviews()
        ->where('status', 'approved')
        ->selectRaw('COUNT(*) as count, AVG(rating) as avg, SUM(CASE WHEN rating = 5 THEN 1 ELSE 0 END) as five_star')
        ->first();

    $this->update([
        'rating_avg'   => round($stats->avg, 2),
        'rating_count' => $stats->count,
    ]);

    Cache::forget("product:{$this->id}:rating");
}

The rating is stored denormalized in the products table for fast catalog sorting. After each new review or deletion, recalculateRating is called.

How Reviews Affect SEO

Reviews are exported as JSON-LD for Google. Stars in the snippet appear with at least 1 review. According to our data, this increases CTR by 15–30%. Example markup:

<script type="application/ld+json">
{
    "@context": "https://schema.org",
    "@type": "Product",
    "name": "{{ product.name }}",
    "aggregateRating": {
        "@type": "AggregateRating",
        "ratingValue": "{{ product.rating_avg }}",
        "reviewCount": "{{ product.rating_count }}",
        "bestRating": 5,
        "worstRating": 1
    },
    "review": [
        {% for review in product.topReviews %}
        {
            "@type": "Review",
            "author": {
                "@type": "Person",
                "name": "{{ review.user_name }}"
            },
            "reviewRating": {
                "@type": "Rating",
                "ratingValue": "{{ review.rating }}"
            },
            "reviewBody": "{{ review.body }}",
            "datePublished": "{{ review.created_at }}"
        }
        {% endfor %}
    ]
}
</script>

Sorting and Filtering Reviews

On the product page, reviews are sorted by date, rating, and helpfulness. A clickable star filter in the histogram helps customers find relevant reviews and reduces bounce rate.

Store Replies

Managers can reply to reviews from the admin panel with a 'Store reply' label. This increases trust and encourages more reviews.

What's Included

  • API documentation and endpoint descriptions
  • Administrator training on moderation
  • Source code of the review module (Laravel 11, React 18)
  • Free support for 30 days after delivery
  • 1-year warranty on code
  • 10 years of industry experience in eCommerce

Process

  1. Analysis — study current architecture, load, moderation requirements.
  2. Design — data model, API contracts, caching scheme.
  3. Implementation — backend (Laravel 11, PostgreSQL), frontend (React 18, TypeScript).
  4. Testing — load testing (up to 1000 RPM), moderation verification.
  5. Deployment — Docker containerization, CI/CD setup, monitoring.

Timeline and Cost

Basic implementation takes 4–7 business days. Timeline increases if integration with existing CRM or custom moderation scenarios are needed. Cost is calculated individually and typically starts from $2,500 for a basic implementation. Our ecommerce review system development includes automatic moderation and product rating system integration. The product rating system is enhanced with Schema.org SEO markup. We specialize in ecommerce review system development with SEO-friendly features. Contact us for a consultation — we'll calculate exact timelines for your project. Order development and get a review system that boosts conversion and improves SEO.

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

Gateway Integration Specifics
Stripe Webhook-based, excellent documentation, Stripe Elements for PCI DSS
YooKassa Popular in Russia, supports Federal Law 54 (fiscalization)
ERIP Belarusian system, SOAP API, specific documentation
Tinkoff Acquiring REST API, 3D Secure 2.0, webhook notifications

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

Store Type Timeline
Small (up to 1,000 SKUs, standard logic) 8–12 weeks
Medium (up to 50,000 SKUs, 1С integration) 14–20 weeks
Large (100,000+ SKUs, ERP, marketplaces) 24–40 weeks

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.