Dropshipping Price Sync: Automate Markup & Updates

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
Dropshipping Price Sync: Automate Markup & Updates
Medium
~2-3 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
    929
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    948

Dropshipping faces a problem: purchase prices change, and manually updating retail prices leads to errors and lost margin. According to our data, manual updates for a store with 500 products take 8 hours per week and result in 5–10% incorrect positions — direct revenue loss. Automating price synchronization solves this: we implemented solutions for 50+ online stores, cutting update time by 10x and eliminating errors entirely. As noted on Wikipedia, dropshipping requires automation to scale. Supplier prices change on a schedule (new price list weekly) or in real time (exchange-traded goods, currency dependency, dynamic pricing). Without automation, the store loses margin when purchase prices rise or loses to competitors when they drop. Our experience helps avoid these problems: over the years we have refined a reliable synchronization scheme that updates prices 10x faster than manual entry and completely eliminates human errors.

Why Automatic Synchronization Matters

Manually updating thousands of products is a path to errors and lost profit. Imagine: the supplier drops the purchase price by 30% and you don't know — competitors are already selling cheaper and you lose sales. Or conversely, a sharp 40% increase eats your margin if you don't raise retail in time. Automation ensures that the retail price always reflects the current purchase price with the desired markup. As a result, margin is preserved and customers see correct prices. We handle integration with any type of supplier.

Price Sources: Approach Comparison

Source Update Frequency Complexity Reliability
REST API Real time Medium High
FTP/CSV price list 1x per day Low High
Webhook from supplier Instant Medium High
Website scraping Scheduled High Low (requires maintenance)

Types of Markup Rules

Rule Type Application Example
Percentage Universal fixed percentage 25% on all products
Fixed amount Add a constant +50 ₽ to purchase price
Stepped table For different price brackets up to 1000: 40%, 1000–5000: 25%, above: 15%

Typical Errors with Manual Synchronization

Even experienced managers make mistakes:

  • Input errors: swapped digits, extra zeros, wrong currency.
  • Missed updates: forgot to update a popular product's price — sales stall.
  • Inconsistency: different employees apply different markup on the same product.
  • No history: impossible to track when and why a price changed.

Automation eliminates these errors, and all change history is stored in a dedicated table — you always know who updated the price and when.

How We Implement Synchronization

Work stages: analyze current state → design architecture → implement in Laravel (PHP 8.3+) → test on real data → deploy with monitoring. We do everything turnkey.

  1. Analysis — study price sources and margin requirements.
  2. Design — choose architecture and markup rules.
  3. Implementation — write code, integrate with supplier.
  4. Testing — run on historical data, check anomaly protection.
  5. Launch — deploy and set up monitoring.

Storing Price History

Schema::create('dropship_price_log', function (Blueprint $table) {
    $table->id();
    $table->foreignId('dropship_product_id')->constrained();
    $table->decimal('prev_supplier_price', 10, 2);
    $table->decimal('new_supplier_price', 10, 2);
    $table->decimal('prev_retail_price', 10, 2)->nullable();
    $table->decimal('new_retail_price', 10, 2)->nullable();
    $table->decimal('margin_percent', 5, 2)->nullable();
    $table->string('source')->default('sync');
    $table->timestamp('recorded_at');

    $table->index(['dropship_product_id', 'recorded_at']);
});

Retail Price Calculator

The retail price is calculated from the purchase price using margin rules. Rules can be global, at the supplier level, category level, or specific product.

class PriceCalculator
{
    public function calculate(DropshipProduct $dp): float
    {
        $supplierPrice = $dp->supplier_price;
        $marginRule    = $this->resolveMarginRule($dp);

        return match($marginRule->type) {
            'percent' => round($supplierPrice * (1 + $marginRule->value / 100), 2),
            'fixed'   => round($supplierPrice + $marginRule->value, 2),
            'markup_table' => $this->applyMarkupTable($supplierPrice, $marginRule->table),
        };
    }

    private function resolveMarginRule(DropshipProduct $dp): MarginRule
    {
        // Priority: product > category > supplier > global settings
        return $dp->margin_rule
            ?? $dp->product?->category?->margin_rule
            ?? $dp->supplier->margin_rule
            ?? MarginRule::getDefault();
    }

    /**
     * Stepped markup: expensive items — lower %
     * [up to 1000 → +40%, 1000–5000 → +25%, 5000+ → +15%]
     */
    private function applyMarkupTable(float $price, array $table): float
    {
        foreach ($table as $tier) {
            if ($price <= $tier['max_price']) {
                return round($price * (1 + $tier['percent'] / 100), 2);
            }
        }

        // Last tier without max limit
        $last = end($table);
        return round($price * (1 + $last['percent'] / 100), 2);
    }
}

Price Synchronization Job

class SyncSupplierPricesJob implements ShouldQueue
{
    public $tries = 3;
    public $backoff = [60, 300, 900];

    public function handle(
        SupplierConnectorFactory $factory,
        PriceCalculator $calculator,
    ): void {
        $connector  = $factory->make($this->supplier);
        $priceList  = $connector->getPriceList(); // array [sku => price]
        $updatedCount = 0;

        foreach ($priceList as $sku => $newSupplierPrice) {
            $dp = DropshipProduct::where([
                'supplier_id'  => $this->supplier->id,
                'supplier_sku' => $sku,
            ])->first();

            if (!$dp) continue;

            // Skip if price hasn't changed
            if (abs($dp->supplier_price - $newSupplierPrice) < 0.01) continue;

            $prevSupplierPrice = $dp->supplier_price;
            $prevRetailPrice   = $dp->product?->price;

            $dp->update(['supplier_price' => $newSupplierPrice]);

            // Recalculate retail price if not manually locked
            $newRetailPrice = null;
            if ($dp->product && !$dp->product->price_locked) {
                $newRetailPrice = $calculator->calculate($dp);
                $dp->product->update(['price' => $newRetailPrice]);
            }

            DropshipPriceLog::create([
                'dropship_product_id' => $dp->id,
                'prev_supplier_price' => $prevSupplierPrice,
                'new_supplier_price'  => $newSupplierPrice,
                'prev_retail_price'   => $prevRetailPrice,
                'new_retail_price'    => $newRetailPrice,
                'source'              => 'sync',
                'recorded_at'         => now(),
            ]);

            $updatedCount++;
        }

        Log::info('Price sync completed', [
            'supplier' => $this->supplier->slug,
            'updated'  => $updatedCount,
        ]);
    }
}

How to Prevent Sudden Price Spikes

Sometimes the supplier's price list contains erroneous prices (zero, very high value, typo). Without protection, the store would display an incorrect retail price. We implement anomaly checking: if the purchase price change exceeds a configured threshold (e.g., 50%), the product is flagged for manual verification. For example, the price was 1000 ₽, the supplier sends 1500 (50% change) — at a 50% threshold this is allowed. But if the change is 100% (to 2000 ₽), the product goes to manual review. The manager sees suspicious items in a dedicated admin section and can confirm or reject the update.

class PriceSanityChecker
{
    private const MAX_CHANGE_PERCENT = 50; // do not update if change > 50%

    public function isSafe(float $prevPrice, float $newPrice): bool
    {
        if ($newPrice <= 0) return false;

        if ($prevPrice <= 0) return true; // first price — accept any positive

        $changePercent = abs($newPrice - $prevPrice) / $prevPrice * 100;

        if ($changePercent > self::MAX_CHANGE_PERCENT) {
            // Log for manual review
            Log::warning('Suspicious price change detected', [
                'prev'    => $prevPrice,
                'new'     => $newPrice,
                'change%' => round($changePercent, 1),
            ]);
            return false;
        }

        return true;
    }
}

Products with suspicious price changes are placed into a manual review queue — the manager sees them in a separate admin section. This prevents setting an incorrect retail price. As a result, sharp spikes do not pass automatically; they require human confirmation.

Currency and Exchange Rate Conversion

If the supplier prices in USD or EUR and the store operates in RUB:

class CurrencyPriceConverter
{
    public function convert(float $price, string $fromCurrency, string $toCurrency): float
    {
        if ($fromCurrency === $toCurrency) return $price;

        $rate = Cache::remember(
            "exchange_rate_{$fromCurrency}_{$toCurrency}",
            3600, // cache for 1 hour
            fn() => $this->fetchRate($fromCurrency, $toCurrency)
        );

        return round($price * $rate, 2);
    }

    private function fetchRate(string $from, string $to): float
    {
        // Central Bank of Russia: cbr.ru/scripts/XML_daily.asp
        // Or openexchangerates.org, fixer.io
        $response = Http::get('https://api.exchangerate-api.com/v4/latest/' . $from);
        return $response->json("rates.{$to}");
    }
}

What's Included

  • Integration with any price source (API, CSV, webhooks)
  • Configuration of markup rules (percentage, fixed, stepped)
  • Implementation of anomaly spike protection
  • Storage and visualization of change history
  • Currency conversion with caching
  • Operations documentation and team training
  • Post-launch support

Contact us for a consultation on your project. We'll help automate pricing and protect your margin.

Estimated Timelines

Price synchronization with one supplier + margin calculator — from a few working days. Stepped markup, currency conversion, spike protection — add up to two more days. Final cost is calculated individually — leave a request and we'll discuss your project. Our engineers guarantee reliable operation of the solution. Get a consultation and project assessment — we'll help automate pricing and protect your margin.

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.