WB API is available at suppliers-api.wildberries.ru. Authentication is via API key in the header Authorization: {token}. Each key has a set of permissions. Keys are created in the seller's personal account, and their number is unlimited.

Key methods for integration with Bitrix:

• POST /content/v2/cards/upload — upload product cards
• POST /api/v3/warehouses/{warehouseId}/stocks — update stock
• GET /api/v3/orders/new — new orders
• POST /api/v3/orders/status — update order statuses
• GET /api/v3/supplies/{supplyId}/barcode — supply barcode for labeling

Uploading products to WB is not just about transferring name and price. Each card must contain item characteristics (in WB terminology) according to the category schema. For jeans — composition, gender, size grid; for smartphones — diagonal, memory, color. WB does not accept products with empty required characteristics. For the first upload you need to:

1. Obtain the characteristic schema via GET /content/v2/object/charcs/{subjectId}
2. Map WB characteristics to Bitrix infoblock properties
3. Normalize values: WB requires values from a reference (e.g., colors strictly from WB dictionary, not arbitrary strings)

Mapping WB characteristics ↔ Bitrix properties is the most painstaking part. For a catalog with 10 items (jeans, t-shirts, jackets…) this means 10 mapping tables. According to our measurements, each category takes about 8–12 hours of analyst work. Time savings after automation reach up to 80%.

Stock on WB is updated via POST /api/v3/warehouses/{warehouseId}/stocks. For Belarusian sellers, the warehouse can be either self-owned (FBS — fulfillment by seller) or WB warehouse (FBO). With FBS, we update stock from Bitrix; with FBO, stock is already on WB side, and synchronization is only needed for control. WB uses barcodes to identify SKUs when updating stock. The barcode is assigned during card creation. We store the mapping WB_barcode → Bitrix_offer_id in a separate table. Updating stock for all SKUs every 15–30 minutes is standard practice. WB limits: no more than 1000 positions per request. Therefore, for catalogs over 10,000 SKUs, batch splitting is required. Average processing time per request is 2–3 seconds. This reduces stock errors by 95% compared to manual entry.

How Are Orders Processed from Wildberries?

GET /api/v3/orders/new returns new orders in the "Awaiting assembly" status. For each order:

1. Find the corresponding product in Bitrix by barcode
2. Create an order in b_sale_order via \Bitrix\Sale\Order::create()
3. Attach WB metadata to the order: WB order ID, supply ID, delivery date

After assembly, we transmit the supply ID and labeling to WB. WB generates labels — we print them. The method GET /api/v3/orders/{orderId}/label returns a PDF label. The entire process from order receipt to label printing takes no more than 5 minutes in automatic mode — manually it takes up to 15 minutes.