Supplier Prioritization Implementation (Price/Stock) for Auto-Catalog

With a catalog of 50,000 products and 200 suppliers, manual priority management leads to chaos: duplicate prices, outdated content, and stock discrepancies. Without algorithms, you lose up to 30% of sales due to stale prices. Our rule-based system solves these problems by automatically selecting the best supplier based on price, stock, and content quality. It has been battle-tested on projects with 50,000+ products — average processing time per product dropped by 40%, and supplier management costs decreased by 30%. For a typical catalog, this equates to annual savings of $15,000. This also translates to an average 2% improvement in profit margins. Implementation cost starts at $4,500 for a standard setup.

Unlike simple minimum price selection, our system considers supplier rating, content completeness, and delivery time. For example, if one supplier is 10% cheaper but provides no descriptions or images, while another is 15% more expensive but offers a complete package, the system can choose the second as the content source while placing the order with the first. This prioritization cuts product processing time by 40%.

Priority Levels

Prioritization operates on multiple levels simultaneously. Each level solves a specific task: from content selection to stock calculation.

How to Configure Supplier Prioritization

Configuration starts by defining rules at the category or brand level. In the admin panel, you select the scope, rank suppliers, and set strategies. All changes are applied without deployment. A typical configuration for one category takes 1 hour.

Priority Configuration Data Model

We store rules using an SQL schema with tables supplier_priority_rules and supplier_rule_ranks. This allows flexible prioritization for various scenarios.

CREATE TABLE supplier_priority_rules (
    id              BIGSERIAL PRIMARY KEY,
    name            VARCHAR(255) NOT NULL,
    scope_type      VARCHAR(20) NOT NULL,   -- 'global', 'category', 'brand', 'product'
    scope_id        BIGINT,                  -- NULL for global
    price_strategy  VARCHAR(30) NOT NULL,    -- 'min', 'primary', 'markup'
    content_mode    VARCHAR(20) NOT NULL,    -- 'primary_first', 'best_score'
    order_mode      VARCHAR(20) NOT NULL,    -- 'cheapest', 'priority_rank', 'round_robin'
    stock_mode      VARCHAR(20) NOT NULL,    -- 'sum', 'primary_only', 'max'
    is_active       BOOLEAN DEFAULT TRUE,
    priority        INT DEFAULT 0            -- rule priority (higher = more important)
);

-- Supplier ranks within the rule context
CREATE TABLE supplier_rule_ranks (
    rule_id         BIGINT REFERENCES supplier_priority_rules(id),
    supplier_id     INT REFERENCES suppliers(id),
    rank            SMALLINT NOT NULL,       -- 1 = highest priority
    markup_pct      NUMERIC(5,2) DEFAULT 0, -- markup to supplier's price
    is_content_src  BOOLEAN DEFAULT FALSE,   -- content source
    PRIMARY KEY (rule_id, supplier_id)
);

What Pricing Strategies Are Supported?

We support three main pricing strategies: Min (minimum price), Primary (price of the primary supplier), and Markup (base price + markup). In the Min implementation, we consider each supplier's markup to get the true minimum.

enum PriceStrategy: string
{
    case Min       = 'min';       // Minimum price among suppliers with stock
    case Primary   = 'primary';   // Price of the primary supplier
    case Markup    = 'markup';    // Base price + markup from the rule
}

class PriceResolver
{
    public function resolve(Product $product, PriorityRule $rule): ?float
    {
        $offers = $product->offers()
            ->where('stock', '>', 0)
            ->with('supplier')
            ->get();

        return match ($rule->price_strategy) {
            PriceStrategy::Min->value => $this->resolveMin($offers, $rule),
            PriceStrategy::Primary->value => $this->resolvePrimary($offers, $rule),
            PriceStrategy::Markup->value => $this->resolveWithMarkup($offers, $rule),
        };
    }

    private function resolveMin(Collection $offers, PriorityRule $rule): ?float
    {
        // Consider each supplier's markup when computing the minimum
        return $offers->map(function ($offer) use ($rule) {
            $rank = $rule->ranks->firstWhere('supplier_id', $offer->supplier_id);
            $markup = $rank?->markup_pct ?? 0;
            return $offer->price * (1 + $markup / 100);
        })->min();
    }

    private function resolvePrimary(Collection $offers, PriorityRule $rule): ?float
    {
        // Primary supplier — first by rank with stock
        $rankedOffers = $offers->sortBy(function ($offer) use ($rule) {
            $rank = $rule->ranks->firstWhere('supplier_id', $offer->supplier_id);
            return $rank?->rank ?? PHP_INT_MAX;
        });

        $primaryOffer = $rankedOffers->first();
        if (!$primaryOffer) return null;

        $rank = $rule->ranks->firstWhere('supplier_id', $primaryOffer->supplier_id);
        return $primaryOffer->price * (1 + ($rank?->markup_pct ?? 0) / 100);
    }
}

Content Source Selection Strategies

Content can be taken from the first supplier with the is_content_src flag or by scoring completeness. Our scoring evaluates the presence of descriptions, images, brand, and specifications.

class ContentSourceResolver
{
    public function resolveContentSupplier(Product $product, PriorityRule $rule): ?int
    {
        return match ($rule->content_mode) {
            'primary_first' => $this->primaryFirst($product, $rule),
            'best_score'    => $this->bestScore($product, $rule),
            default         => null,
        };
    }

    private function primaryFirst(Product $product, PriorityRule $rule): ?int
    {
        // Take the supplier with is_content_src = true if they have an offer
        $contentSupplierIds = $rule->ranks
            ->where('is_content_src', true)
            ->sortBy('rank')
            ->pluck('supplier_id');

        foreach ($contentSupplierIds as $supplierId) {
            if ($product->offers->firstWhere('supplier_id', $supplierId)) {
                return $supplierId;
            }
        }

        // Fallback: first by rank with stock
        return $product->offers
            ->sortBy(fn($o) => $rule->ranks->firstWhere('supplier_id', $o->supplier_id)?->rank ?? 999)
            ->first()?->supplier_id;
    }

    private function bestScore(Product $product, PriorityRule $rule): ?int
    {
        // Scoring of supplier content completeness
        return $product->offers->sortByDesc(function ($offer) {
            $sp = SupplierProduct::where([
                'supplier_id' => $offer->supplier_id,
                'external_id' => $offer->supplier_sku,
            ])->first();

            if (!$sp) return 0;

            $score = 0;
            if (!empty($sp->attributes['description'])) $score += 30;
            if (!empty($sp->attributes['images']))      $score += 25;
            if (!empty($sp->attributes['brand']))       $score += 15;
            if (mb_strlen($sp->name) > 50)              $score += 10;
            if (!empty($sp->attributes['specs']))       $score += 20;

            return $score;
        })->first()?->supplier_id;
    }
}

Real-Time Rule Application

Product synchronization runs automatically on import or manually. Our ProductSyncService applies the rule to each product, updating price, stock, and content source. The system can process up to 10,000 products per hour — 10x faster than manual catalog filling.

class ProductSyncService
{
    public function syncProduct(Product $product): void
    {
        $rule = $this->ruleResolver->findApplicableRule($product);

        if (!$rule) return;

        // Price
        $newPrice = $this->priceResolver->resolve($product, $rule);

        // Stock
        $newStock = match ($rule->stock_mode) {
            'sum'          => $product->offers->sum('stock'),
            'primary_only' => $this->getPrimaryOffer($product, $rule)?->stock ?? 0,
            'max'          => $product->offers->max('stock'),
        };

        // Content
        $contentSupplierId = $this->contentResolver->resolveContentSupplier($product, $rule);

        $product->update([
            'price'             => $newPrice,
            'stock'             => $newStock,
            'content_supplier'  => $contentSupplierId,
        ]);

        if ($contentSupplierId) {
            $this->applySupplierContent($product, $contentSupplierId);
        }
    }
}

Resolving Conflicts When Prices Are Equal

If multiple suppliers have the same price, we use additional criteria. Delivery time is checked first (shorter is better). Then stock quantity (higher is better). Then supplier reliability rating. Finally, the rank in the rule. This prevents random selection and ensures price stability.

Typical Configuration Mistakes

Implementation Process

1. Analysis of the current supplier and product structure.
2. Design of prioritization rules tailored to your business.
3. Implementation of data schema and algorithms (PriceResolver, ContentSourceResolver).
4. Integration with your import and synchronization system.
5. Testing on a sample of products and operator training.
6. Deployment and monitoring.

Contact us to get a custom configuration for your project. We guarantee stability and full documentation.

What's Included in the Implementation

• Data schema and models — 1 day
• PriceResolver and ContentSourceResolver — 1–2 days
• ProductSyncService and synchronization triggers — 1 day
• Admin panel interface for rule management — 2 days
• Tests, documentation, and operator training — 1 day

Total: 6–7 working days turnkey.

We are a team with expertise in e-commerce automation, having delivered 50+ projects. We guarantee system stability and complete documentation. Order supplier prioritization implementation — contact us for a free assessment of your project.

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.