Regional Warehouse & Delivery Implementation for E-commerce

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
Regional Warehouse & Delivery Implementation for E-commerce
Complex
~5 days
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1361
  • 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
    1189
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    931
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    948

Regional Warehouse & Delivery Implementation for E-commerce

Imagine an online store with 5 warehouses across Russia. Without proper order distribution, a delivery to Novosibirsk might ship from Moscow even though the item is available in Krasnoyarsk. The customer pays more and waits longer. The result is increased returns and lower conversion rates. Our system automatically finds the nearest warehouse, reserves stock there, and calculates delivery from the actual dispatch city. On average, this reduces delivery time by 40% for regional customers and cuts operational costs by 25% through route optimization. The solution is built on Laravel 11 and React 18, using Repository and BFF patterns.

Problems We Solve

  • Reservation errors. The system always selects the warehouse closest to the customer and reserves stock there. The customer receives the order faster and cheaper.
  • Incorrect delivery calculation. Delivery is calculated from the actual warehouse, not the central one. This reduces costs for regional buyers by an average of 15–20%.
  • Scattered stock data. The product card shows total stock across all warehouses as well as city-level details—the customer sees exactly where the item is available.

Unlike a simple "in stock/out of stock" indicator, we display exact quantities per warehouse and offer pickup from the nearest location. This reduces return rates by 15–20%.

How to Select a Warehouse for the Customer?

The core algorithm is implemented in the WarehouseSelector class on Laravel. It receives the product ID, required quantity, and destination city, then performs two steps:

  1. Finds warehouses where available >= quantity, sorted by priority (configurable in admin panel).
  2. If geocoding of the city succeeds, sorts by distance to the customer using the Haversine formula. If not, selects the first by priority.
class WarehouseSelector
{
    public function selectForDelivery(
        int    $productId,
        int    $quantity,
        string $destinationCity,
    ): ?WarehouseSelectionResult {
        // Warehouses with sufficient stock
        $available = WarehouseStock::where('product_id', $productId)
            ->where('available', '>=', $quantity)
            ->with('warehouse')
            ->orderByDesc('warehouse.priority')
            ->get();

        if ($available->isEmpty()) {
            // Try split—take from multiple warehouses
            return $this->splitWarehouseSelection($productId, $quantity);
        }

        // Sort by proximity to customer
        $coords = $this->geocoder->getCoords($destinationCity);

        if ($coords) {
            $sorted = $available->sortBy(function ($stock) use ($coords) {
                return $this->haversineDistance(
                    $coords['lat'], $coords['lng'],
                    $stock->warehouse->lat, $stock->warehouse->lng,
                );
            });

            return new WarehouseSelectionResult(
                warehouse:   $sorted->first()->warehouse,
                isSplit:     false,
            );
        }

        // Geocoding failed—take by priority
        return new WarehouseSelectionResult(
            warehouse: $available->first()->warehouse,
            isSplit:   false,
        );
    }

    private function haversineDistance(float $lat1, float $lng1, float $lat2, float $lng2): float
    {
        $R   = 6371; // km
        $dLat = deg2rad($lat2 - $lat1);
        $dLng = deg2rad($lng2 - $lng1);

        $a = sin($dLat / 2) ** 2
           + cos(deg2rad($lat1)) * cos(deg2rad($lat2)) * sin($dLng / 2) ** 2;

        return $R * 2 * atan2(sqrt($a), sqrt(1 - $a));
    }
}

Why Is Stock Reservation Important at Order Time?

Without reservation, a race condition can occur: two customers may simultaneously place an order for the last unit. Our StockReservationService uses lockForUpdate locks within a transaction to avoid double reservation. The reservation lasts 30 minutes, after which it is automatically canceled.

class StockReservationService
{
    public function reserve(Order $order): ReservationResult
    {
        $reservations = [];

        DB::transaction(function () use ($order, &$reservations) {
            foreach ($order->items as $item) {
                // Find warehouse with required quantity
                $stock = WarehouseStock::where('product_id', $item->product_id)
                    ->where('available', '>=', $item->quantity)
                    ->where('warehouse_id', $item->preferred_warehouse_id
                        ?? $this->getNearestWarehouse($order->delivery_city, $item->product_id)->id
                    )
                    ->lockForUpdate()
                    ->first();

                if (!$stock) {
                    throw new InsufficientStockException(
                        "Insufficient stock at warehouse: SKU {$item->product->sku}"
                    );
                }

                // Increment reserved
                $stock->increment('reserved', $item->quantity);

                $reservations[] = StockReservation::create([
                    'order_id'     => $order->id,
                    'order_item_id' => $item->id,
                    'warehouse_id' => $stock->warehouse_id,
                    'product_id'   => $item->product_id,
                    'quantity'     => $item->quantity,
                    'expires_at'   => now()->addMinutes(30),
                ]);
            }
        });

        return new ReservationResult(reservations: $reservations);
    }

    public function cancelExpiredReservations(): int
    {
        $expired = StockReservation::where('status', 'reserved')
            ->where('expires_at', '<', now())
            ->get();

        foreach ($expired as $reservation) {
            DB::transaction(function () use ($reservation) {
                WarehouseStock::where([
                    'product_id'  => $reservation->product_id,
                    'warehouse_id' => $reservation->warehouse_id,
                ])->decrement('reserved', $reservation->quantity);

                $reservation->update(['status' => 'cancelled']);
            });
        }

        return $expired->count();
    }
}

How Is Delivery Calculated with Warehouse Awareness?

RegionalDeliveryCalculator groups cart items by selected warehouse and requests delivery cost from the carrier calculator for each group. If items ship from multiple warehouses, costs are summed, and the customer is shown a single option—the minimum price for each method.

class RegionalDeliveryCalculator
{
    public function calculate(
        array  $cartItems,
        string $destination,
    ): DeliveryResult {
        // Group items by warehouse
        $warehouseGroups = $this->groupByWarehouse($cartItems, $destination);

        $allOptions = collect();

        foreach ($warehouseGroups as $warehouseId => $items) {
            $warehouse = Warehouse::find($warehouseId);

            // Calculate delivery from specific warehouse
            $request = new DeliveryRequest(
                fromCity:    $warehouse->city,
                fromLat:     $warehouse->lat,
                fromLng:     $warehouse->lng,
                destination: $destination,
                items:       $items,
            );

            $options = $this->carrierCalculator->calculate($request);

            // If multiple warehouses, sum the costs
            if (count($warehouseGroups) > 1) {
                $allOptions = $allOptions->merge(
                    $options->map(fn($o) => $o->withWarehouseNote($warehouse->city))
                );
            } else {
                $allOptions = $allOptions->merge($options);
            }
        }

        // Deduplicate by delivery method—select the best option
        return new DeliveryResult(
            options: $allOptions->groupBy('method')
                ->map(fn($g) => $g->sortBy('price')->first())
                ->values(),
        );
    }

    private function groupByWarehouse(array $cartItems, string $destination): array
    {
        $groups = [];

        foreach ($cartItems as $item) {
            $warehouse = $this->selector->selectForDelivery(
                $item->product_id,
                $item->quantity,
                $destination,
            );

            $warehouseId = $warehouse?->warehouse->id ?? $this->defaultWarehouse->id;
            $groups[$warehouseId][] = $item;
        }

        return $groups;
    }
}

Displaying Warehouse Stock on the Product Card

The React frontend component queries stock by city via API and shows a collapsible list. If no stock is available at any warehouse, it displays "Out of stock".

// Stock by city component
const StockByCity: React.FC<{ productId: number }> = ({ productId }) => {
  const { data } = useQuery(['stock', productId], () => fetchStockByCity(productId));

  if (!data?.length) return <span className="text-red-500">Out of stock</span>;

  return (
    <details className="text-sm">
      <summary className="cursor-pointer text-green-600 font-medium">
        In stock — {data.length} city/cities
      </summary>
      <ul className="mt-1 space-y-1 pl-3">
        {data.map(s => (
          <li key={s.warehouse} className="text-gray-600">
            {s.city} — {s.qty} pcs.
          </li>
        ))}
      </ul>
    </details>
  );
};

Implementation Process

Implementation follows 5 stages:

Stage Duration
Analysis of current architecture and data collection 1-2 days
Data schema and API design 1 day
Backend class implementation (WarehouseSelector, RegionalDeliveryCalculator, StockReservationService) 2-3 days
UI component integration (product card, cart) 1-2 days
Testing, deployment, and manager training 1-2 days

Total estimated time: 6 to 7 business days, excluding inter-warehouse transfers. Exact timeline is determined after an audit of your current architecture.

What Is Included in the Result

  • Documentation of data schema and API.
  • Working backend classes (WarehouseSelector, RegionalDeliveryCalculator, StockReservationService).
  • UI components for product card and cart.
  • Administrator guide for managing warehouses and priorities.
  • Manager training on reservation and transfers.
  • 30 days of post-deployment support.

Comparison with Centralized Warehouse

Feature Single Warehouse Regional Warehouses (Our Solution)
Delivery speed High only in warehouse city Minimal for each region
Delivery cost Fixed from central location Adaptive, often 15-20% lower
Stock display on site Only total Per warehouse with details
Reservation error risk Low Practically eliminated

Order implementation—get a preliminary estimate in 1 day. Our team has 8+ years of e-commerce development experience and has delivered over 50 projects with multi-warehouse logistics. Certified Laravel and React engineers use proven patterns like Repository and BFF to ensure fault tolerance and ease of maintenance. Get a free engineer consultation.

What else should you know?The system correctly handles inter-warehouse transfers—when stock moves between warehouses, quantities are recalculated in real time. We use a background job queue (Laravel Horizon) with movement event processing.

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.