How order statuses change

The status change diagram shows the stages that go through DBS-the order, and the logic of transitions between statuses. This will help you correlate the statuses of Yandex. Market and your system, set up integration with Yandex.Market correctly, and avoid transmitting unnecessary statuses and substates.

Designations:

• The diagram shows the order statuses and substates at each stage in the format Status of the Sub-status. For example, PROCESSING STARTED.

  List of substates CANCELLED see the section Substates when canceling an order.

• The arrows show the transitions between the stages, and their color — when this transition occurs:

  • green — The store's status has changed.
  • blue — The market has changed its status.
  • orange — cancellation of an order by one of the parties;
  • red — exceptional cases.

Decoding the scheme

Status, sub-status, and stage description	Who is changing the status	Methods by which the status is changed or information about the order is received in this status
PROCESSING STARTED The store is processing the order.	Yandex. Market	POST v1/businesses/{businessId}/orders POST notification
DELIVERY DELIVERY_SERVICE_RECEIVED The order has been delivered.	Shop	POST v1/businesses/{businessId}/orders POST notification PUT v2/campaigns/{campaignId}/orders/{orderId}/status
DELIVERY USER_RECEIVED The customer received the order. It is transmitted only when working through Yandex. Delivery.	Yandex. Market	POST v1/businesses/{businessId}/orders POST notification
DELIVERY DELIVERY_USER_NOT_RECEIVED The delivery time has expired, and the customer has not received the order. Arbitration begins, as a result of which the order can be canceled or transferred to the status DELIVERED DELIVERY_SERVICE_DELIVERED.	Yandex. Market	POST v1/businesses/{businessId}/orders POST notification
PICKUP PICKUP_SERVICE_RECEIVED The order has been accepted at the PVZ.	Shop	PUT v2/campaigns/{campaignId}/orders/{orderId}/status
DELIVERED DELIVERY_SERVICE_DELIVERED The order has been delivered. It is transmitted automatically when working via Yandex. Delivery. If you are delivering on your own, change the status after the order is delivered.	Yandex. Market Shop	POST v1/businesses/{businessId}/orders POST notification PUT v2/campaigns/{campaignId}/orders/{orderId}/status
DELIVERED DELIVERED_USER_NOT_RECEIVED The delivery time has expired, and the customer has not received the order. Arbitration begins, as a result of which the order can be canceled or remain in the same status.	Yandex. Market	POST v1/businesses/{businessId}/orders POST notification
CANCELLED Substates The order has been cancelled. To cancel an order, pass the sub-status SHOP_FAILED. If the order is in the status DELIVERY or PICKUP and the buyer cancelled it., confirm the cancellation.	Yandex. Market Shop Buyer	POST v1/businesses/{businessId}/orders POST notification PUT v2/campaigns/{campaignId}/orders/{orderId}/status

Substates when canceling an order

The substates that the store can transmit

Depending on the current order status, the store can use the following cancellation sub-statuses:

• In the status PROCESSING:

  • SHOP_FAILED — the store cannot complete the order.
  • USER_CHANGED_MIND — the customer cancelled the order for personal reasons.
  • USER_UNREACHABLE — couldn't contact the buyer.
  • INCORRECT_PERSONAL_DATA — For an order from abroad, the recipient's information is incorrect, and the order will not be checked at customs.

• In the status DELIVERY:

  • SHOP_FAILED — the store cannot complete the order.
  • USER_CHANGED_MIND — the customer cancelled the order for personal reasons.
  • USER_UNREACHABLE — couldn't contact the buyer.

• In the status PICKUP:

  • SHOP_FAILED — the store cannot complete the order.
  • USER_CHANGED_MIND — the customer cancelled the order for personal reasons.
  • USER_UNREACHABLE — couldn't contact the buyer.
  • PICKUP_EXPIRED — the storage period of the order in the PVZ has expired.

The substates that are set by the buyer or the system

• RESERVATION_EXPIRED — The customer did not complete the reserved order within 10 minutes.
• USER_NOT_PAID — the buyer did not pay for the order (for the payment type PREPAID) for 30 minutes.
• USER_CHANGED_MIND — the customer cancelled the order for personal reasons.
• USER_REFUSED_DELIVERY — the buyer was not satisfied with the terms of delivery.
• USER_REFUSED_PRODUCT — the product did not fit the buyer.
• USER_REFUSED_QUALITY — the buyer was not satisfied with the quality of the product.
• USER_IDENTIFICATION_MISMATCH — The buyer's identification document does not match the data in the order.
• REPLACING_ORDER — the buyer decided to replace the product with another one on his own initiative.
• PROCESSING_EXPIRED — the value is no longer used.
• PICKUP_EXPIRED — the storage period of the order in the PVZ has expired.
• TOO_MANY_DELIVERY_DATE_CHANGES — the order has been postponed too many times.

Other values may also be returned. You don't need to process them.

PUT v2/campaigns/{campaignId}/orders/{orderId}/cancellation/accept