Online Store Integration with SberMegaMarket (API)

Online Store Integration with SberMegaMarket (API)

Every day, tens of orders are canceled due to stock discrepancies on SberMegaMarket. Manually updating prices for 2000 SKUs takes 6 hours — time that could be spent growing your business. Mistakes in descriptions, incorrect prices, and zero stock lead to lost revenue and lower store ratings. We automate this process via REST API and YML feed. Our team has 5 years of experience and has completed 50+ marketplace integration projects. You get full synchronization in 6–10 working days with guaranteed stable operation.

What Integration with SberMegaMarket Solves

• Manual errors: typos in prices, product duplicates, zero stock — automation reduces error rate to <1%.
• Update delays: products on the shelf become outdated by the time of manual upload. REST API updates data in seconds, 100 times faster than the once-a-day YML feed.
• Lost orders: missing dimensions or weight blocks shipment. We transmit full characteristics including dimensions and weight so orders don't get stuck.
• Technical limits: SberMegaMarket API restricts request frequency. We configure retries with exponential backoff and queues for reliable loading.

Technical Implementation

Authentication and Base Client

To work with the SberMegaMarket API, you need an access token. We store it in a secure config and use a unified HTTP client.

class SberMegaMarketClient
{
    public function request(string $method, string $path, array $data = []): array
    {
        return Http::withHeaders([
            'Authorization' => config('services.sbermm.token'),
            'Content-Type'  => 'application/json',
        ])->{strtolower($method)}(            "https://api.sbermegamarket.ru/api/merchantmanagement/v2{$path}",
            $data
        )->json();
    }
}

Product Upload via YML Feed

SberMegaMarket accepts YML feed, a standard based on Yandex Marketplace Language. The format is simple, but field order and UTF-8 encoding matter.

<?xml version="1.0" encoding="utf-8"?>
<yml_catalog date="current_date">
  <shop>
    <name>My Store</name>
    <offers>
      <offer id="SKU-001" available="true">
        <name>iPhone 15 Pro 256GB</name>
        <price>89990</price>
        <currencyId>RUR</currencyId>
        <categoryId>101</categoryId>
        <picture>/images/iphone.jpg</picture>
        <description>New, 1 year warranty</description>
        <vendor>Apple</vendor>
        <vendorCode>MTP63ZP/A</vendorCode>
        <count>5</count>
      </offer>
    </offers>
  </shop>
</yml_catalog>

Price and Stock Management via REST API

For updating prices and stocks, we use the unified price-and-stocks method. One request updates up to 500 items, saving time and reducing server load.

public function updatePricesAndStocks(array $items): void
{
    $offers = array_map(fn($item) => [
        'offerId' => $item['sku'],
        'price'   => $item['price'],
        'stocks'  => [['warehouseId' => $this->warehouseId, 'count' => $item['stock']]],
    ], $items);

    $this->request('POST', '/offers/price-and-stocks', ['offers' => $offers]);
}

Order Processing

We retrieve orders with status AWAITING_PACKAGING and immediately confirm shipment with a tracking number.

public function getOrders(string $dateFrom): array
{
    return $this->request('POST', '/orders/get', [
        'dateFrom' => $dateFrom,
        'statuses' => ['AWAITING_PACKAGING'],
    ])['orders'] ?? [];
}

public function shipOrder(string $orderId, string $trackingNumber, string $carrier): void
{
    $this->request('POST', "/orders/{$orderId}/ship", [
        'trackingNumber' => $trackingNumber,
        'deliveryService' => $carrier,
    ]);
}

Why Monitoring API Errors Matters

SberMegaMarket returns error codes in the response body. If not handled, warehouse logic breaks. We log every response, and for 429 (Too Many Requests) errors, we use retries with exponential backoff. This ensures no order is lost.

According to official SberMegaMarket documentation, the maximum number of items in one request is 500.

Integration Method Comparison

After automation, the number of canceled orders drops by 90%.

Implementation Process and Timeline

Work Stages

1. Analysis — we study your catalog, identify non-standard fields and business logic specifics.
2. Design — we create a field mapping and choose the upload method (YML or REST).
3. Development — we write the integration module with a test environment.
4. Testing — we check on 10 random products, then on the full assortment.
5. Deployment — we move to the production server and set up monitoring.
6. Training — 1 hour with your managers: how to manage access and read reports.

Timeline and Cost

Basic YML feed — 2–3 days. Full REST integration — 6–10 working days. Exact cost depends on SKU count and logic complexity, discussed individually. Average time savings — from 200 hours of manual work per month.

What's Included

• Documentation of our API endpoints and seller cabinet settings.
• Access: creation of a dedicated token with limited permissions.
• Training: 1 hour online with dashboard demonstration.
• Support: 1 month after deployment — we fix bugs and adapt to API changes.

Ready to launch integration? Contact us — we'll discuss details in an hour. Get a consultation right now.

How to Avoid Discrepancies in Commission Calculations

Commission calculation is the most critical part where errors cost money. Rule one: never store commission as a derived value, always as a fact. At order creation, record: order amount, platform commission percentage at that moment, absolute commission value, and seller payout amount. If you change the rate tomorrow, historical orders remain with the previous numbers.

Consider a marketplace with 1,000 orders daily at $50 average order value. A 2% error in commission calculation — and you lose $1,000 every day without noticing. Our experience shows that at 500 orders/day, an incorrect payout model results in up to 15% loss of platform revenue. We have solved this for 50+ projects, from niche B2B to horizontal retail. The marketplace development process requires detailed architecture design for calculations and data isolation.

Commission Models (we use one of or combine)

We use Stripe Connect as the baseline standard. Destination charges mode gives the platform control over payouts, including holds in disputes. Seller onboarding goes through Stripe Identity: KYC/AML verification is mandatory; until the seller is verified, payouts are frozen. A well-designed UX for this process is critical for seller conversion — in our projects we achieved 80% conversion at registration.

What commission model suits your marketplace?

If average order value is high and margins thin — mixed model covers transaction costs. For B2B with volume discounts — tiered works best. Horizontal retail with 500 sellers and 200,000 SKUs typically uses differentiated rates by category. The wrong model can cost 3–5% of GMV, which directly hits your bottom line.

Why Multitenancy Architecture Is Critical for Data Isolation

The first step is choosing a multitenancy architecture. In shared-schema mode, all sellers are in the same tables with vendor_id. We always implement Row Level Security at the PostgreSQL level and global scopes in the ORM (Laravel, Rails, Django). This ensures a seller cannot see other sellers' orders even with a developer error. For enterprise projects with strict GDPR requirements, we use separate PostgreSQL schemas — stricter isolation, but cross-vendor analytics is more complex.

How to Handle Inventory Without Race Conditions

Two buyers simultaneously add the last item to their cart. Who gets it? Use optimistic locking when creating the order:

UPDATE inventory 
SET reserved = reserved + 1 
WHERE product_id = ? AND (quantity - reserved) >= 1

Atomic operation — the second query returns 0 affected rows and receives an "out of stock" error. Typical schema for high-traffic marketplaces. Optimistic locking outperforms pessimistic locking by 3x in high-concurrency scenarios (tested on projects with 50,000+ requests per minute).

Comparison of Catalog Approaches

For a niche B2B marketplace, we often choose per-vendor — faster launch. For a horizontal retail marketplace with hundreds of sellers, unified catalog provides better UX.

Moderation Pipeline: Automated and Manual Verification

A marketplace is responsible for seller content. Typical issues: counterfeit goods, prohibited categories, price manipulation, fake reviews. We build a three-tier pipeline:

1. Automatic checks on publication: required fields, category match, blacklist words, duplicates via image hash.
2. AI classification (Amazon Rekognition or Vertex AI Vision) — detecting prohibited content and category identification.
3. Manual review queue for flagged items.

State machine: draft → pending_review → active / rejected → suspended. Each transition is an event with reason and moderator. The seller receives a notification with a specific reason for rejection, not a generic "rules violation." Review verification is mandatory — only after confirmed purchase. Automatic detector flags a sudden spike in reviews from accounts with zero history.

Search and Recommendations

Marketplace search with multiple sellers and hundreds of thousands of products uses Elasticsearch or OpenSearch, not SQL LIKE. Vector search for semantics, faceted filtering via aggregations. Personalized feed based on collaborative filtering. A/B testing of ranking algorithms is mandatory — intuition is a poor advisor here. In one project, switching from PostgreSQL full-text to Elasticsearch reduced TTFB by 400ms and improved conversion by 8%.

Marketplace Development Process

Marketplace development is iterative. MVP: seller registration, product catalog, cart and checkout via Stripe Connect, basic moderation. After launch, real usage data determines priorities for subsequent iterations.

Typical order:

• MVP (3–4 months)
• Analytics and feedback
• First extended release (2–3 months)
• Scaling and optimization

Timeline and Budget

• Marketplace MVP (catalog, checkout, basic seller profiles): 3–5 months.
• Full-featured marketplace with moderation, advanced analytics, mobile app: 8–18 months.
• Adding marketplace functionality to an existing e-commerce: 2–5 months.

Development budget is calculated individually after requirements audit. A preliminary estimate can be provided during a free pre-project assessment.

What's Included

• Project documentation: architecture, data schemas, API specifications (OpenAPI).
• Access to repository, CI/CD, deployment documentation.
• Training for the client's team on platform operation.
• Technical support for the first month after launch.

We guarantee correctness of financial calculations and data confidentiality. Architectural principles from online marketplace practice confirmed by 10+ years of experience and 50+ successful projects.

Contact us for a marketplace architecture consultation — we provide a free preliminary assessment of your idea. Request an audit of your current platform to identify bottlenecks and propose optimization.