Yandex.Market Partner API Integration – Automate Product Management

Imagine: you have 15,000 products, prices change every hour, and a manager spends 4 hours a day manually updating the Yandex.Market cabinet. Manual entry errors affect 5–8% of items. After integrating via Partner API, everything is automated: products upload in 2 minutes, prices sync on a schedule, orders are processed without human intervention. We have implemented over 50 such projects for stores with monthly turnovers ranging from 500,000 to 50 million rubles. With our experienced team, you get a guaranteed smooth integration.

Yandex.Market provides the Partner API—a set of REST methods for managing products, prices, stocks, and orders. The API supports three operational models: FBS (seller stores goods), FBO (goods at Market's warehouse), and DBS (seller handles delivery). In this article, we dive into the technical details: authentication, product upload, price and stock updates, and order processing via webhooks.

Why Automate Yandex.Market Operations?

Manual product management on a marketplace is not only time-consuming but also error-prone. Based on our data, automation via the API reduces catalog update time by 10–15 times. For example, manually uploading 100 products takes 30 minutes; via API it takes 2 minutes. Manual entry errors occur in 5–8% of cases (wrong price, incorrect stock), while automated sync keeps errors below 0.1%. Moreover, the API allows direct order export to your accounting system, eliminating duplicate data entry. This yields savings of up to 100,000 rubles per month for large catalogs.

What Data Is Synced via the API?

The Partner API provides endpoints for key entities:

• Products: create, update, delete; mandatory fields—offerId, name, price, count. Up to 1,000 products per request.
• Prices and Stocks: regular updates (e.g., hourly) via POST /campaigns/{id}/offer-prices/updates and PUT /campaigns/{id}/offers/stocks.
• Orders: fetch new orders, change statuses, cancel. Webhooks notify in real time about changes.

Be mindful of API limits: no more than 5,000 requests per day per campaign. We recommend batch processing.

How We Integrate: Technical Details

Authentication

The Partner API uses OAuth2 tokens. Authorization via Yandex OAuth:

class YandexMarketClient
{
    private string $accessToken;
    private int    $campaignId;
    private int    $businessId;

    public function request(string $method, string $path, array $data = []): array
    {
        return Http::withHeaders([
            'Authorization' => "OAuth oauth_token={$this->accessToken}",
            'Content-Type'  => 'application/json',
        ])->{strtolower($method)}(
            "https://api.partner.market.yandex.ru{$path}",
            $data
        )->json();
    }
}

Product Upload/Update

public function updateOffers(array $products): void
{
    $offers = array_map(fn($product) => [
        'offerId'     => $product['sku'],
        'name'        => $product['name'],
        'category'    => $product['category_name'],
        'pictures'    => $product['images'],
        'vendor'      => $product['brand'],
        'description' => $product['description'],
        'price'       => ['value' => $product['price'], 'currencyId' => 'RUR'],
        'count'       => $product['stock'],
        'barcodes'    => [$product['barcode']],
    ], $products);

    $this->request('PUT',
        "/businesses/{$this->businessId}/offer-mappings",
        ['offerMappings' => array_map(fn($o) => ['offer' => $o], $offers)]
    );
}

Price and Stock Sync

// Update prices
public function updatePrices(array $items): void
{
    $offers = array_map(fn($item) => [
        'id'    => $item['sku'],
        'price' => ['value' => $item['price'], 'currencyId' => 'RUR', 'vat' => 'VAT_20'],
    ], $items);

    $this->request('POST',
        "/campaigns/{$this->campaignId}/offer-prices/updates",
        ['offers' => $offers]
    );
}

// Update FBS stocks
public function updateStocks(array $items, int $warehouseId): void
{
    $skus = array_map(fn($item) => [
        'sku'   => $item['sku'],
        'items' => [['count' => $item['stock'], 'type' => 'FIT']],
    ], $items);

    $this->request('PUT',
        "/campaigns/{$this->campaignId}/offers/stocks",
        ['skus' => $skus, 'warehouseId' => $warehouseId]
    );
}

Order Processing

public function getNewOrders(): array
{
    $resp = $this->request('GET',
        "/campaigns/{$this->campaignId}/orders",
        ['status' => 'PROCESSING', 'substatus' => 'STARTED', 'pageSize' => 50]
    );

    return $resp['orders'] ?? [];
}

public function acceptOrder(int $orderId): void
{
    $this->request('PUT',
        "/campaigns/{$this->campaignId}/orders/{$orderId}/status",
        ['order' => ['status' => 'PROCESSING', 'substatus' => 'READY_TO_SHIP']]
    );
}

Push Notifications for Orders

Yandex.Market supports push notifications via settings in the seller cabinet:

Route::post('/webhooks/yandex-market', function (Request $request) {
    $events = $request->input('data');

    foreach ($events as $event) {
        match($event['type']) {
            'ORDER_STATUS_CHANGED' => ProcessYandexOrderStatus::dispatch($event['orderId']),
            default                => null,
        };
    }

    return response()->json(['status' => 'ok']);
});

Our Integration Process

1. Analysis: We study your current accounting system, product catalog, and business processes.
2. Design: Choose the model (FBS/FBO/DBS) and design the data exchange architecture.
3. Implementation: Write code for product, price, stock, and order sync; configure webhooks.
4. Testing: Validate on Yandex.Market sandbox, then on production.
5. Deploy and Train: Deploy the solution, hold a training webinar for your team, and hand over documentation.

What's Included in the Turnkey Solution

Manual vs Automated: A Comparison

Manual product updates on Yandex.Market (via cabinet) take about 30 minutes per 100 items. Automated integration via API takes 1–3 minutes for the entire catalog. API integration is 15 times faster than manual entry. Manual entry errors occur in 5–8% of cases; automatic sync keeps errors under 0.1%.

Common Integration Pitfalls (and How We Avoid Them)

Based on our experience, frequent issues include:

• Exceeding API limits: Attempting to upload over 1,000 products at once returns a 429 error. Solution: batch into groups of 1,000.
• Incorrect data format: e.g., wrong barcode format or missing required fields. We always validate request structures.
• OAuth token expiration: Tokens expire after one year. We implement automated token refresh.
• API version changes: Yandex may update the API. We monitor the Partner API documentation and adjust accordingly.

Timelines and Next Steps

Integration with Yandex.Market Partner API: 12–16 business days. Contact us for a project assessment—we will propose the optimal solution and precise timeline. Place an order for integration, and your products will always be up-to-date on Yandex.Market.

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.