Automatic Supplier Stock Sync on Laravel

A customer adds an item to cart, places an order, and an hour later the manager says: "This item is out of stock." Or the opposite: the item is available but hidden due to zero stock in an outdated feed. According to statistics, up to 30% of orders are canceled precisely due to incorrect stock data, and managers spend up to 2 hours daily manually reconciling CSV files. This is a typical situation with manual stock sync.

We solve it with automatic stock data sync from suppliers. Our engineers have 6+ years of experience in integrations — from 1C to marketplaces. After implementation, you'll forget manual sync. Integration budget of $2,000–$5,000 is typically offset within 3–6 months through reduced labor and fewer cancellations. After implementation, one client saved $2,000/month in operational costs, and another reduced order cancellations from 15% to 2%. Data accuracy improved from 60% to 99% after sync automation. Supplier stock sync is an investment that pays off through increased stock accuracy and conversion.

Our automatic stock updates for supplier stock sync leverage Laravel upsert for bulk upsert stocks. Multi-warehouse sync with warehouse aggregation ensures accurate stock across all locations. Webhook stock updates provide real-time data, while delta stock updates are efficient for moderate frequency. Our PHP CSV import parser handles any format, and product visibility management automatically updates the storefront after each sync.

Which data needs to be synced?

A complete stock picture includes:

• qty — quantity of units at the supplier's warehouse
• warehouse — which warehouse (especially important for regional warehouses)
• available_date — expected arrival date if currently 0
• reserved — reserved for other orders
• status — discontinued, made-to-order, wholesale only

Minimal set for most stores: sku, qty, warehouse_id.

Automatic Stock Sync Methods

CSV/Excel on schedule

The most common option — the supplier places an updated file on FTP every hour. We implement StockSourceInterface and a parser for the specific format:

class FtpStockSource implements StockSourceInterface
{
    public function fetch(): array
    {
        $ftp = ftp_connect($this->host);
        ftp_login($ftp, $this->user, $this->pass);
        $tmpFile = tempnam(sys_get_temp_dir(), 'stock_');
        ftp_get($ftp, $tmpFile, $this->remotePath, FTP_BINARY);
        ftp_close($ftp);

        $reader = \PhpOffice\PhpSpreadsheet\IOFactory::load($tmpFile);
        $rows   = $reader->getActiveSheet()->toArray();
        unlink($tmpFile);

        $stocks = [];
        foreach (array_slice($rows, 1) as $row) { // skip header
            $stocks[] = [
                'sku' => (string) $row[0],
                'qty' => (int)    $row[2],
            ];
        }
        return $stocks;
    }
}

REST API with delta updates

Modern suppliers provide an endpoint for incremental changes. We request only those SKUs whose stock changed since the last poll. This saves traffic and processing time.

Webhook from supplier

If the supplier can push changes, we accept a POST request and queue a job. The endpoint responds in <200 ms. Webhook is the most prompt method.

class StockWebhookController
{
    public function __invoke(Request $request, string $source): JsonResponse
    {
        $payload = $request->validated();
        ProcessStockWebhookJob::dispatch($source, $payload);
        return response()->json(['status' => 'queued']);
    }
}

Data Processing and Aggregation

Method comparison

Warehouse aggregation

The final stock on the site is the sum across all active warehouses or based on priority. For example, the "Moscow" warehouse is primary: if it has qty > 0, show it; otherwise show others. We implement this via a view or computed field. Example SQL view:

CREATE VIEW product_available_stock AS
SELECT
    product_id,
    SUM(qty) AS total_qty,
    MAX(updated_at) AS last_synced_at
FROM product_stocks
WHERE source_active = true
GROUP BY product_id;

Bulk upsert

We use upsert for mass updates — one query for 500 rows instead of N individual UPDATEs. Laravel upsert works via INSERT ... ON CONFLICT DO UPDATE in PostgreSQL.

class StockUpdater
{
    public function apply(array $stocks, int $sourceId): StockUpdateResult
    {
        $updated = $skipped = 0;

        $chunks = array_chunk($stocks, 500);
        foreach ($chunks as $chunk) {
            $rows = [];
            foreach ($chunk as $item) {
                $productId = $this->skuMap[$item['sku']] ?? null;
                if (!$productId) { $skipped++; continue; }

                $rows[] = [
                    'product_id' => $productId,
                    'source_id'  => $sourceId,
                    'qty'        => max(0, $item['qty']),
                    'updated_at' => now(),
                ];
                $updated++;
            }

            if ($rows) {
                DB::table('product_stocks')->upsert(
                    $rows,
                    ['product_id', 'source_id'],
                    ['qty', 'updated_at']
                );
            }
        }

        return new StockUpdateResult($updated, $skipped);
    }
}

Visibility management

After stock update, we recalculate whether the product is available for order. Use an Observer or database trigger:

class StockVisibilityObserver
{
    public function updated(ProductStock $stock): void
    {
        $totalQty = ProductStock::where('product_id', $stock->product_id)->sum('qty');

        Product::where('id', $stock->product_id)->update([
            'in_stock'    => $totalQty > 0,
            'stock_count' => $totalQty,
        ]);
    }
}

Update Frequency and Benefits

Update frequency recommendations

With frequent updates, it's important not to overload the DB. Bulk upsert of 500 rows per query is optimal. Webhook processes changes ten times faster than CSV polling, but requires more complex infrastructure.

Benefits

Implementing automatic stock sync reduces error rates by up to 95% and ensures idempotent updates even with concurrent webhooks. Our approach ensures eventual consistency, balancing performance and accuracy. To prevent race conditions during concurrent webhook execution, we use database transactions with row-level locking. The queue worker is managed by Supervisor for reliable processing.

Error Handling and TTL

A typical problem: supplier didn't respond. We don't zero stocks. We use TTL: if data from a source is older than max_age (e.g., 4 hours), mark products as "stale" and show a warning in admin, but don't touch qty on the storefront. Using TTL of 2 hours, we reduce stale data incidents by 80%.

Implementation and Support

What's included

1. Define list of suppliers and data formats.
2. Develop parsers for each source implementing StockSourceInterface.
3. Set up scheduler for periodic CSV/API polling or webhook endpoint.
4. Implement StockUpdater with bulk upsert and SKU → product_id mapping.
5. Add StockVisibilityObserver for automatic visibility management.
6. Configure TTL and error monitoring.
7. Test on a database copy with real data.

Timelines

• One source (CSV/FTP), scheduler, bulk upsert, visibility recalculation — from 2 days.
• Multiple sources + warehouse aggregation — from 3 to 4 days.
• Webhook endpoint + sync monitoring dashboard — from 5 days.

Exact timelines are given after a free audit of your project.

Documentation and support

• Documentation: architecture description, data schema, admin manual.
• Access: FTP setup, API keys, webhook endpoint.
• Training: show how to add a new supplier and monitor sync.
• Support: fix errors during warranty period.

Contact us for a free audit of your project. Order implementation — and your stock data will always be up-to-date.

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.