Orders from Yandex for Shop-Script

Yandex brings the buyer. The order lands in Shop-Script

A buyer clicks Buy in Yandex Products or Alice, reviews the cart, and completes checkout in the familiar Yandex interface. The plugin rechecks price and stock, accepts the payment confirmation, and creates a regular Shop-Script order.

Your team keeps working in the system it already uses: customer, products, delivery, payment, and acquisition source are attached to the Shop-Script order. Nothing has to be copied from Yandex manually.

More than an API proxy

• Verify the cart before payment. Price, availability, and quantity are read from Shop-Script for every Yandex request.
• Limit what can be sold. Scope the integration to the same product set or exact product IDs as the YML feed.
• Prevent duplicate orders. A repeated checkout/placed with the same session_id resolves to the existing order.
• Recover after an interrupted response. The plugin finds an already created order by its YCP session parameter instead of creating another one.
• Keep the standard workflow. New, paid, completed, canceled, and refunded orders remain ordinary Shop-Script orders.
• Diagnose without exposing customer data. Logs contain method, path, status code, and duration only — never tokens, customer details, request bodies, or order contents.

Complete YCP endpoint set

The plugin implements all 10 endpoints in the current Yandex Checkout Protocol: warehouses, basket checks, checkout creation and lifecycle, courier delivery options, pickup-point responses, order lookup, cancellation, and delivery confirmation.

Responses use non-cacheable JSON. Bearer authentication, a 128 KB request-body limit, safe identifiers, and required-field validation protect the catalog and order workflow.

How to connect

1. Create a dedicated YML feed for Yandex Products and choose a stable offer id.
2. Install the plugin and keep request handling disabled.
3. Set the HTTPS storefront, feed URL, offer-ID rule, product scope, and warehouse details.
4. Copy the generated API URL and token to YCP merchant settings.
5. Run the built-in readiness checks and test basket validation.
6. Enable requests. Yandex can display its Buy button after the feed and merchant pass review.

Transparent offer-ID mapping

Choose one of three explicit feed mappings: Shop-Script SKU code (recommended), internal SKU ID, or product ID for a simple offer using its primary SKU. After basket matching, the plugin returns a stable internal SKU ID for every following checkout step.

Safe stock handling

Finite stock is returned as stored. Shop-Script represents unlimited stock with an empty value, while YCP requires an integer, so the plugin exposes a configurable per-order cap. A hidden product, disabled SKU, zero price, or zero stock always reports zero availability.

Reliability compared with a basic adapter

Delivery and payment

Version 1.0 provides one warehouse profile, optional weekday self-pickup, and a fixed merchant-courier price and business-day interval. The pickup-point endpoint is protocol-complete and returns an empty list until the merchant has an authoritative pickup-point directory.

Orders may be associated with installed Shop-Script delivery and payment methods. An online order is marked paid only after YCP confirms payment_method=online; pay-on-delivery orders remain new.

Clear product boundaries

The plugin implements the merchant-side YCP API and creates Shop-Script orders. It does not generate the YML feed, register the merchant, enable acquiring or fiscal receipts, or control Yandex moderation. The Buy button appears on Yandex surfaces after separate Yandex Products and YCP setup; the plugin does not add a storefront button.

System requirements: Webasyst Framework 2.9+, Shop-Script 9.0+, PHP 7.4+, JSON, and mbstring. Shop-Script PREMIUM is supported.