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