Top Man Digital: Ozon Delivery for Business

- The address of the selected pickup point is immediately written to the Delivery Address field during order checkout.

- The address is verified against the pickup points directory before the order is saved.

- Changes from versions 1.0.9 and 1.0.10 are included.

The "Problematic" tag no longer appears due to its own Ozon status update.

The core marks a shipment with a transport request upon each save, while the module changes the package status: previously, this caused every Ozon order to turn red, prompting the operator to update the request, which cannot be updated—shipments in Ozon cannot be edited, only cancelled and recreated.

Only this tag is removed, and only for Ozon shipments: other order tags remain in place, and the problematic flag for the shipment and order is cleared only when no remaining tags exist.

The update registers a new tracking event handler: the installer does not run during an update, and without this handler, it would remain dormant.

The module records Ozon delivery dates: the planned date, the arrival time at the pickup point, and the delivery time; they are visible in the shipment card and in the transport request.

For the store code, the class Topman\OzonDelivery\Posting\Info has been added: shipment number, dates, deadline, and package status without contacting Ozon.

Variables #OZON_TRACKING_NUMBER#, #OZON_DELIVERY_DATE#, #OZON_DELIVERY_DAYS#, #OZON_ARRIVED_DATE#, #OZON_DELIVERED_DATE#, #OZON_STATUS#, #OZON_DELIVERY_ADDRESS# have been added to order emails; they are declared in the descriptions of email events.

In email HTML templates, variable values are escaped.

The "Delivery Allowed" and "Shipped" marks and the order status are set when the parcel reaches the required Ozon status or has already passed it.

The tracking update button in the order card applies the same status rules as the automatic check.

The "Module Status" screen and the service card warn if automatic tracking update in the "Online Store" module is disabled.

Checking the pickup point no longer blocks transitions between order checkout steps - other delivery services are visible again.

The client secret is not displayed in the delivery service card; rounding options in the pickup method card are labeled.

The pickup point and courier address from the order form are validated on the server: the address is accepted only from the module's geocoder, and the pickup point only if it accepts parcels by weight, dimensions, and cost.

- When the module is deleted without saving data, Ozon delivery services are deleted; services with existing orders are disabled.

- When the module is deleted, its restrictions are removed from the store's delivery services: the shipping card in the admin panel no longer crashes with an error.

- On the deletion completion page, it shows which services were deleted, which were disabled, and why.

Paid build operation from the Marketplace. The installer and uninstaller no longer connect the module itself, but register its classes directly: in the paid build, module connection fails before the demo license is issued and after the demo period ends. The settings page and module sections distinguish between demo mode and the end of the demo period - instead of a blank page, the buyer sees an explanation, and in demo mode, a reminder. Removing the module after the demo period no longer leaves order properties, and installation and removal steps are not skipped silently: a failure stops the operation with a clear reason. Order properties removed by uninstallation are selected by the module tag, not by the general code - a foreign property with the same code will not be affected.

The Pick-up Point directory no longer loses points. Previously, traversing the directory would stop at the first network hiccup, and a point not caught in one traversal would immediately be disabled - a check on the live cabinet showed that out of eight disabled points, seven continued to accept orders. Now: the traversal repeats the page instead of stopping; a point is disabled only if it is missing from the Ozon list for longer than the term from the 'Agents' tab (default two days); a point whose Ozon card was not provided is considered seen, not missing; a warning appears on the 'Pick-up Points' page during mass disabling. The traversal is faster: the directory has its own short timeout (4 seconds instead of the general ten - the list responds in two-tenths of a second, and a hung request does not revive), and the agent's working time per launch is now a setting, default two minutes instead of thirty seconds. Separately: Ozon rejections in live writing (same_delivery_point_error and others) are now recognized by the error catalog, and the buyer sees a clear phrase instead of the general 'calculation failed'.

An order cannot be placed until a pickup point is selected. Previously, the buyer only learned about this after clicking 'Place Order': the order was not saved, and a message appeared. Now, the click is stopped directly in the form—the widget is highlighted, shows what is missing, and the page scrolls to it. The 'Back' button still works. Server-side validation remains in place: it protects templates where the order buttons are named differently.

Delivery calculation when Ozon responds slowly or does not respond. The timeout for delivery calculation during checkout has been increased from 4 to 8 seconds: four seconds were insufficient during Ozon's slow periods, causing the calculation to fail, and the failed Bitrix calculation displayed a zero delivery cost, leading the buyer to see "free" where a price should be. For sites with a setting of less than five seconds, this update raises the value. The background response timeout has been increased from 5 to 10 seconds. A new setting "If Ozon does not respond" has been added on the "Price for buyer" tab: by default, the buyer sees a message that the cost cannot be calculated at this time, and as a second option, the price can be shown according to your own rules, such as a markup and the store's minimum cost. Ozon's refusal is not overridden by this setting: a refusal is a response and is displayed as is.

Price field labels in the delivery service card. The markup and other price fields in the receipt method card work only when the "Set your own price rules instead of general ones" switch is enabled — this is now written directly in the labels, rather than being discovered through trial and error. The "Price for buyer" tab title in the module settings names this switch.

Pickup point map: the selected point hides the map and shows the "Select another point" button — the form no longer jumps after selection. The map opens on the city selected during checkout and, if the buyer permits, moves to them. New setting "Phone for preliminary calculation": until the buyer enters their number, the cost is calculated using the store number, and after entry it is recalculated.