Attack on the Ozon Logistics Center in Adygeysk: Operational Status and the Compensation Approval BugNote · digest for November 5
Reportage photograph of a nighttime evacuation and emergency services working outside a logistics complex with warning beacons.
Note2 sections≈ 3 min

Attack on the Ozon Logistics Center in Adygeysk: Operational Status and the Compensation Approval Bug

On the night of November 4, 2026, Ozon's regional fulfillment center in Adygeysk (logistics facility "Адыгейск_РФЦ", Republic of Adygea) came under an aerial drone attack. Falling debris sparked a fire on the warehouse complex grounds. The incident hit a key marketplace transport artery in southern Russia and triggered an immediate response from the platform's security services. Earlier, we covered the timeline of incidents at southern cluster logistics facilities in detail. In this situation, it is vital for sellers to keep a cool head, know the operational status of their batches, and avoid fatal mistakes when filing for compensation.

Operational Status of the Adygeysk Warehouse and Flow Rerouting

According to official statements from marketplace management and Head of the Republic of Adygea Murat Kumpilov, safety protocols worked as intended: shift staff were promptly evacuated to safe zones, with no casualties or injuries among warehouse personnel. Arriving EMERCOM crews quickly contained the fire hotspots.

For sellers, however, the incident translated into abrupt operational restrictions:

  1. Products hidden from the storefront. All inventory stored at "Адыгейск_РФЦ" has been temporarily pulled from sale in the customer app. If an SKU is duplicated at other company distribution centers, the product card stays active and orders are automatically routed to backup warehouses. If stock was held only in Adygeysk, the card is switched to "Out of Stock."
  2. FBO receiving halted. Acceptance of new deliveries at the Adygeysk warehouse is completely blocked, and all previously booked slots have been canceled. Trucks with goods already en route are being manually rerouted by marketplace dispatchers to distribution centers in Rostov Oblast and Stavropol Krai.

Bug in the Ozon Dashboard: Why You Must Not Sign Certificates Blindly

Alongside dealing with the aftermath of the incident, sellers ran into strange behavior in the seller dashboard under "Finance" → "Insurance" → "Documents" → "Compensation," where the marketplace processes electronic payout certificates for goods lost at warehouses.

The consent form requires reproducing a control statement verbatim. Yet the algorithm throws a "Text does not match sample" validation error at the slightest discrepancy: the system requires the letter "ё" in the words "подтверждённых" and "расчётом," and also blocks submission if a space is missing after the comma in the line "товаров, наличие." Submission is available exclusively to the account owner with "Manager" ("Управляющий") rights.

But the main issue lies in the legal substance of the document. By confirming the form, the seller agrees that the proposed amount is exhaustive compensation for damages and declares a waiver of any further claims against Ozon and the Insurer (Ingosstrakh). You must never sign consent blindly: before submitting, be sure to download the SKU register and verify purchase prices. If the insurance company undervalued the batch or deducted extra amounts, record your disagreement through support and do not apply your electronic signature until an official recalculation is completed.

Want a deep diveVotes help us choose what to break down in detail. This material has 0 votes.
Sources · 4