Release Notes

Added new methods for campaigns with custom bid, previously, Auction:

• Custom bid campaigns information
• Changing placements in campaigns with custom bid
• Changing bids in campaigns with custom bid
• Changing the list of product cards in campaigns with custom bid

Starting from September 9, it will be impossible to get campaigns with custom bid and change their bids using the Campaigns information and Changing bids methods.

Added list of complaint reasons submitted through the seller portal in the response of the method for getting list of reasons for complaints about feedbacks and product issues:

• 11 — Review is not related to the product
• 12 — Review was left by competitors
• 13 — Spam advertisement in the text
• 14 — Spam advertisement in photo or video
• 15 — Inappropriate content in photo or video
• 16 — Inappropriate language
• 17 — Photo or video is not related to the product
• 18 — Review with political context
• 19 — Other
• 20 — Threats insults

The lists of complaint reasons on the seller portal and in the API are different. It is not possible to submit a complaint via the API using a reason from the seller portal.

If a complaint is submitted via the seller portal (for example, 13 — Spam in the text), the reason specified on the portal (13 — Spam in the text) will be displayed in the responses of the methods for getting the feedback by ID, feedbacks list and the list of archived feedbacks.

If a complaint is submitted via the API (for example, with reason 3 — Spam), the reason passed via the API will be displayed in the responses of the same methods, while the corresponding reason from the seller portal list (13 — Spam in the text) will be displayed on the seller portal.

Starting September 1, IMEI is required for products costing 20,000 rubles or more for assembly orders of DBW, DBS, and In-Store Pickup models.

If the IMEI is not specified:

• DBW and DBS assembly orders cannot be processed to delivery
• for In-Store Pickup assembly orders, it will be impossible to notify that the assembly order is ready for pickup

Now in the sandbox In-Store Pickup assembly orders automatically receive the same orderCode, if you create multiple assembly orders with a single request. The generated orderCode is passed in the response of the method of getting new assembly orders.

Now when forming a supply for delivery to a pickup point, it is enough to specify the number of boxes when adding them to the supply. It is no longer necessary to add a list of assembly orders to the box.

Starting August 18, will be disabled:

• the methods for adding and deleting assembly orders from boxes
• list of assembly orders in the method for getting the list of boxes. The orders array will be removed from the method response

Added new fields to the response of the Box tariffs method:

• boxDeliveryCoefExpr — coefficient Logistics, %. The logistics cost is multiplied by it. Already included in the tariffs
• boxDeliveryMarketplaceBase — FBS logistics of the first liter, ₽
• boxDeliveryMarketplaceCoefExpr — coefficient FBS, %. The FBS logistics cost is multiplied by it. Already included in the tariffs
• boxDeliveryMarketplaceLiter — FBS logistics of every next liter, ₽  
• boxStorageCoefExpr — coefficient Storage, %. The storage cost is multiplied by it. Already included in the tariffs
• geoName — country, for Russian Federation — federal district  

The field boxDeliveryAndStorageExpr will be removed on August 19.

Divided rate limits for Marketplace methods according to sales models:

• FBS assembly orders, supplies and passes
• DBS assembly orders
• In-Store Pickup assembly orders

Separated the limits for getting and deleting metadata for FBS, DBS, and In-Store Pickup from the limits for methods for adding metadata.

Allocated separate rate limits for methods:

• Seller Warehouses 
• Inventory

Changes in the FBW Supplies section:

• Added the transit directions method for forming supplies
• Added the supplies info methods for getting:
  • Supplies list
  • Supply details
  • Supply products
  • Supply package

To the response of the method Chat List added new object goodCard with information about the product card, for which the buyer started the chat:

• date — order date
• needRefund — has refund been requested
• nmID — WB article
• price — actual price with all discounts applied. Charged to the buyer
• priceCurrency — currency
• rid — unique order ID
• size — product size
• statusID — product status

In the sandbox added new fields with the final product price that the customer paid to the information about DBS and In-Store Pickup assembly orders:

• finalPrice — the price in the currency of sale including all discounts, multiplied by 100

• convertedFinalPrice — the price in the currency of seller’s country including all discounts, multiplied by 100

Also added new fields to the information about In-Store Pickup assembly orders in the sandbox:

• convertedPrice — the price in the currency of seller’s country including all discounts, except the WB Wallet discount, multiplied by 100

• convertedCurrencyCode — the currency code of the seller's country

The prices are provided for informational purposes.

New fields are added to the responses of the methods:

• Get new orders list (DBS)
• Get information on completed orders (DBS)
• Get new assembly orders list (In-Store Pickup)
• Retrieve information on completed assembly orders (In-Store Pickup)

1. Added the officeID field — ID of the WB warehouse associated with the seller's warehouse — to the methods:
   • Get new orders
   • Get orders
2. Added the destinationOfficeId field — ID of the destination office for the supply — to the methods:
   • Get a supplies list
   • Get supply details

Starting from September 1, in the method for adding assembly orders to a supply, an error 409 will be returned if the officeID of the assembly order does not match the destinationOfficeID of the supply.

The destinationOfficeId field will only be present in new supplies. If the supply has a cargoType field, changes will not affect it.