Connecting 1C-Bitrix to SberMegamarket: Feed, API, and Orders

When an online store on 1C-Bitrix starts selling on SberMegamarket, the first problem is the incompatibility of the standard YML export with the marketplace's requirements.

Integrating 1C-Bitrix with SberMegamarket requires <outlets> and <shipment-options> tags that are missing in regular YML. The order API differs from Ozon and Wildberries, so without proper configuration you risk losing up to 30% of orders due to stock update failures. We have implemented this integration for 20+ stores with an average catalog of 5000 SKUs and know how to avoid common mistakes. In 95% of cases, problems are solved by setting feed generation every 30 minutes and using Merchant API for order confirmation.

SberMegamarket (formerly goods.ru) operates on DBS and FBS models. The main product upload channel is an XML feed close to YML but with extensions. Order management is via Merchant API. This duality requires configuring two independent mechanisms on the Bitrix side, each implementable with standard platform tools.

Configuring the product feed for SberMegamarket

The feed is accepted in a YML-compatible format with additional tags. The feed URL is specified in the seller's dashboard; the marketplace pulls it on a schedule (usually every 2–4 hours). On average, about 50% of the catalog requires price and stock corrections after the initial upload.

Structure of <offer>:

<outlets> is a key tag for DBS model. Contains <outlet id="ID" instock="QUANTITY"/> for each sales point. The point ID is created in the SberMegamarket dashboard. In Bitrix, stock is taken from the catalog module's warehouse accounting or from a separate element property.

<shipment-options> specifies how many days the seller is ready to ship the item. Example: <option days="1" order-before="14"/> — shipping within 1 day for orders before 14:00. The marketplace uses this to calculate delivery times to the buyer.

Feed generation in Bitrix

Standard YML export in Bitrix ('Yandex.Market' profile) does not generate <outlets> and <shipment-options> tags. Options:

1. Modify the standard export. In the handler file /bitrix/php_interface/include/catalog_export/, modify the XML generation template to add the required tags. Stock is fetched via CCatalogStoreProduct::GetList() for each product.

2. Module from Marketplace. Ready-made solutions for SberMegamarket (e.g., from Kooplex or RetailCRM) add an export profile with support for all specific tags.

3. Separate PHP script. A cron script generates XML by selecting data from the information block via CIBlockElement::GetList(). Advantage: full control without dependency on the export module.

Importance of stock update speed

Stock update delay is a common cause of penalties. If an item sells out but the feed hasn't updated yet, the marketplace accepts an order for an unavailable product. Each order cancellation may incur penalties and lowers the seller's rating. According to our statistics, timely stock updates reduce cancellations by 85%. Desynchronization errors can lead to penalties and reputation loss.

Merchant API: order processing

SberMegamarket API (https://partner.sbermegamarket.ru/api/) works via POST requests with JSON. Authorization is a token in the header.

DBS order cycle:

1. Get new orders. POST /api/market/v1/orderService/order/new returns orders in NEW status.
2. Confirm. POST /api/market/v1/orderService/order/confirm — seller confirms the order and specifies shipping time.
3. Ship. POST /api/market/v1/orderService/order/packing — provide tracking number and confirm shipment.
4. Cancel. POST /api/market/v1/orderService/order/reject — cancel with reason.

On the Bitrix side, a cron agent polls the API for new orders every 5–10 minutes. Upon receiving:

• Create an order in Bitrix\Sale\Order with product mapping by offerId (SKU) or barcode.
• Set order properties: SberMegamarket order number, delivery method, customer data (name, phone, address).
• When order status changes in Bitrix, the OnSaleOrderSaved event handler calls the corresponding API method.

According to Merchant API SberMegamarket documentation, the orderService/order/new method returns orders in NEW status that have not yet been confirmed.

Price and stock updates

Via feed. Prices and stock are updated when the marketplace next parses the feed. Delay up to 4 hours. Sufficient for most stores.

Via API (accelerated update). For high-turnover items — method POST /api/market/v1/offerService/manualPrice/save for prices, and stock update via <outlets> in the feed with forced refresh.

Categories and moderation

SberMegamarket uses its own category tree. Mapping is set in the dashboard when configuring the feed — for each <categoryId> from your feed, specify the corresponding marketplace category.

Product moderation takes 1–3 days. Rejection reasons:

• Missing barcode.
• Invalid brand (not in marketplace reference).
• Photos not meeting requirements (watermarks, collages, text on image).

What's included in the integration

• Analysis of current catalog and information block structure.
• Feed generation with <outlets> and <shipment-options> tags.
• Configuration of cron agents for Merchant API polling.
• Development of order creation and update handlers.
• Testing on real data and debugging.
• Training managers on order handling.
• 30-day support guarantee after launch.

Our engineers have over 5 years of experience integrating marketplaces with 1C-Bitrix, with 20+ completed projects. We perform turnkey integration in 1–2 weeks, depending on catalog size. Contact us to evaluate your project — we'll provide accurate timelines and a proposal. Order integration and get a consultation from our engineers.

Integration timelines

How can you avoid typical mistakes when connecting payment systems on 1C-Bitrix?

The most common mistake during integration is forgetting about the callback. The customer paid for the order, the money was debited, but the status in b_sale_order did not update: the manager sees "Awaiting payment" and starts calling the client. The reason is an incorrect URL in the gateway settings or a handler that returns a 500 error for an atypical response structure. We offer services for connecting payment systems on 1C-Bitrix with full testing of all scenarios: successful payment, refusal, timeout, partial refund, duplicate callback.

Why are callbacks critical?

Each payment gateway sends a notification to your server. If the handler does not guarantee idempotency, a double call will lead to a double charge. We always implement a check by notification ID (external_id) and block repeated processing in \Bitrix\Sale\Order. It is also critical to set the callback URL in the aggregator's personal account – /bitrix/tools/sale_ps_result.php for the standard module. If you use a custom handler, we verify that it returns HTTP 200 even in case of parameter errors (the gateway should not repeat the request indefinitely).

use Bitrix\Sale\Order;
use Bitrix\Main\Application;

// Get notification data
$data = Application::getInstance()->getContext()->getRequest()->toArray();
// Check signature (depends on aggregator)
if (!checkSignature($data, 'SECRET_KEY')) {
    die('FAIL');
}
// Find order by external ID
$order = Order::loadByExternalId((int)$data['order_number']);
if ($order && $order->isPaid() === false) {
    $order->setField('PAYED', 'Y');
    $order->save();
}
echo 'OK';

How do we optimize payment flow for higher conversion?

How to choose a payment aggregator for 1C-Bitrix?

The choice of aggregator depends on the geography of customers, average order value, and need for installments. For Russia, the basic set is YooKassa (all main methods, fiscalization out of the box) and CloudPayments (widget on the page without redirect, Apple Pay). If you work with large corporate clients, add Sberbank (SberPay, SBP). For international sales, use Stripe or PayPal. We often use a two-tier scheme: main aggregator + backup (auto-switching on failure).

What payment gateways and methods do we use?

YooKassa

One contract – all main methods: Visa/MasterCard/MIR cards, YooMoney, SberPay, internet banking, installments. Fiscalization under 54-FZ out of the box (via the sale module). The standard handler /bitrix/modules/sale/handlers/paysystem/yandexpay/ covers basic scenarios. For holding (two-stage payment), subscriptions, or split payments, custom integration via YooKassa API v3. Callback is configured to /bitrix/tools/sale_ps_result.php, we parse notification and update \Bitrix\Sale\Order via setField('PAYED', 'Y').

CloudPayments

Focused on conversion: the payment widget directly on the checkout page, without redirect to an external domain. The customer does not leave the site – the abandonment rate during payment drops. It supports recurring payments (card tokenization via cryptogram), Apple Pay, and Google Pay. 3D Secure with intelligent routing – requested only for high fraud risk. Integration with Bitrix – via CloudPayments REST API and a custom handler in the sale module.

Tinkoff Payment

API integration via TinkoffPaymentAPI (ready-made module or manual implementation). QR code for payment via the app, "Tinkoff Credit" installment – critical for expensive goods. Partial refunds via the Cancel method – without calling the bank, everything from the Bitrix admin panel.

Sberbank (SberPay and SBP)

SberPay – payment via push notification or QR, SBP – commission 0.4–0.7% vs 1.5–2.5% for cards. This is a significant savings on volume. Holding via registerPreAuth / deposit API. Note that SberPay requires a separate agreement with the bank.

Apple Pay and Google Pay

Payment in two clicks, without entering card data. They are connected through an aggregator (YooKassa, CloudPayments, Tinkoff). Important nuances:

• Apple Pay requires domain verification: the file apple-developer-merchantid-domain-association in /.well-known/. Without it, the button will not appear.
• Button placement strictly according to Apple and Google guidelines – otherwise rejection in review.
• Fallback to the standard payment form if the device does not support contactless payment.

How do we handle installments, BNPL, and 54-FZ compliance?

If the average order value is above 30,000 RUB and conversion drops, installment removes the price barrier. We connect:

• Tinkoff Installment (3–24 months)
• Buy with Sber
• Mokka / Dolyami – BNPL: 4 payments, 0% for the buyer

Integration: widget with monthly payment calculation on the product card ("from 2,500 RUB/month"), order data transfer to the bank via API, status processing (approval, rejection, awaiting documents) in OnSaleStatusOrder handlers.

Fiscalization under 54-FZ is a mandatory requirement. The fine for a missing receipt is up to 100% of the payment amount. In accordance with Federal Law No. 54-FZ, an electronic receipt must be sent to the buyer. We connect ATOL Online, Orange Data, Module.Kassa, Evotor, Shtrikh-M. Setup in Bitrix – the "Cash Registers" section in the sale module:

• VAT rate, item and method of payment – an error in any field can lead to a fine during inspection.
• Receipts for prepayment and partial payment (two receipts: at payment and at shipment).
• Refund receipts upon cancellation via \Bitrix\Sale\Cashbox\Cashbox::addChecks().
• Monitoring: if the receipt is not sent, an alert to the manager.

When selling shoes, clothing, or perfumes, it is mandatory to transfer marking codes in the receipt. Integration with "Chestny ZNAK", scanning DataMatrix during order assembly, automatic removal from circulation upon sale via \Bitrix\Catalog\Product\Marking.

Payment support: refunds, multicurrency, security

Refunds

Full and partial refund without calling the bank – via the aggregator API (refund / cancel). The refund receipt is generated automatically, the order status is updated, the amount is recalculated, and the customer is notified. Timeframes: e-wallets and SBP – 1–3 days, bank card – up to 30 business days (depends on the issuing bank).

Multicurrency

Price types in b_catalog_price for each currency, rates via the Central Bank API (\Bitrix\Currency\CurrencyManager::updateCBRFRates()) or manual input. Conversion at the catalog level – the customer sees prices in their currency. For accepting dollars/euros, we connect Stripe, PayPal. We take into account conversion fees when calculating margin.

Security

Card data is processed on the certified gateway side (PCI DSS) – the card number never passes through your server. Anti-fraud at the aggregator level. Logging all events in b_sale_order_change for audit. Anomaly monitoring: transaction spike, atypical geography – alert.

How we work and estimated timelines

1. Analysis – what payment methods are needed, markets, transaction volume, current aggregator.
2. Solution selection – sometimes two aggregators are better than one: YooKassa as the main, CloudPayments as backup – if one fails, traffic goes to the second.
3. Integration – we test each scenario: successful payment, 3DS refusal, gateway timeout, double callback, partial refund.
4. Fiscalization – online cash register, checking the correctness of receipts on test orders.
5. Monitoring – alerts for gateway failures, conversion dashboard at the payment stage.

What is included in the work

• Full setup of selected payment systems in 1C-Bitrix: modules, handlers, callbacks, testing.
• Integration documentation (gateway operation scheme, handler description, logic).
• Training your manager to work with payment modules and refunds.
• Technical support during launch and the first 2 weeks of operation.
• Monitoring – we set up alerts for errors and conversion drops.

All work is performed by certified 1C-Bitrix developers. We guarantee the operability of each scenario. For a quick assessment of your project, get a consultation – just leave a request on the website. Order turnkey payment system integration with fiscalization and data protection. Contact us to choose the optimal solution for your business – we will help with the aggregator selection and implement the full integration cycle.