Ozon Delivery Service

Version 2.0.11

The result of manual sending is displayed below the button in the order card without transitioning to a separate page.

Clear error messages for address, phone number, and delivery availability have been added. Internal server errors are not revealed in the interface.

When sending a courier order, the correspondence of the city and region to the address determined by the Geocoder is checked.

The display of the sending status in the order card for the business contour has been fixed.

Version 2.0.10

The determination of the courier address region has been fixed: the federal district is no longer accepted as a krai or oblast when checking the order location.

A setting "Do not check address during order checkout" has been added, which is disabled by default. When enabled, the courier address is checked when sending to Ozon, and the cost for business is calculated in advance based on the selected city.

Version 2.0.9

A check for the Geocoder functionality before displaying courier delivery has been added, which is disabled by default.

When the setting is enabled, if the Geocoder is unavailable, courier delivery is not displayed. The check is performed without caching.

The API address for Yandex Maps geocoding has been updated.

Version 2.0.8

A setting to save the preliminary cost of courier delivery before order placement has been added. This setting is disabled by default.

When the setting is enabled, the courier price is calculated based on the selected city and does not switch to the address in the cart; during order placement, the address is verified as before.

Version 2.0.7

For Ozon Delivery for Business, a preliminary calculation of courier delivery cost has been added even when the buyer's address is not yet filled in.

The calculation uses the coordinates of the first suitable pickup point (Punkt Vyzova) of the selected city and the phone number for preliminary calculation from the settings. The delivery mode in the Ozon request remains as courier.

After the address is entered, a standard precise calculation is performed; the buyer's address and phone number are still required to complete the order.

Version 2.0.6

When the city is changed, the selected pickup point is reset so that delivery is not calculated for the previous location.

The selected pickup point is highlighted on the map, and its marker and pop-up information are displayed more accurately.

The preliminary cost calculation after page refresh has been fixed: the old pickup point is no longer taken from the session without an explicit selection.

The phone input window before selecting a pickup point is now displayed on top of the order completion elements.

Version 2.0.5

A configurable phone number mask has been added to the input window before selecting a pickup point.

Fixed input of numbers starting with 8 or 7 in the pickup point selection window.

In the order address field, the address of the selected pickup point is recorded with the label "Ozon Pickup Point."

In the Ozon Delivery for Business environment, items from the same order can be sent in a single parcel. This setting is enabled by default; when disabled, a separate shipment is created for each item.

Version 2.0.4

The modal window setting for entering a phone number before selecting a pickup point has been restored on sites where update 2.0.2 was not applied completely.

The necessary script, style, and phone validation handlers are reinstalled.

Version 2.0.3

The re-update of Ozon Delivery for Business pickup points has been accelerated: for points with an unchanged address, the saved location is used.

The location search for new and modified pickup points is performed by the database index.

The volume of cached locations in memory during synchronization is limited.

Concurrent updates of pickup points for one site are blocked; manual updates and background agents do not start a second import simultaneously.

Background synchronization of pickup points saves progress and continues processing in parts without restarting completed imports.

Version 2.0.2

For Ozon Delivery for Business, a preliminary calculation of delivery cost to a pickup point (PVZ) by the selected city has been added. The setting is disabled by default; the calculation uses the phone number specified in the settings.

The pickup point (PVZ) preliminarily selected for the calculation is not saved in the order: the buyer must select a valid pickup point on the map.

When the city is changed, the previous pickup point (PVZ) from the calculation context is not used for the new city.

The message during order placement without a selected pickup point (PVZ) has been clarified.

General request limits are used to verify the phone number and calculate the cost preliminarily, so that limits cannot be bypassed via a neighboring handler.

Phone verification limits also apply when verifying delivery in the seller environment; repeated requests to Ozon are counted in the overall limit.

Repeated geocoding of the same address in the cart uses a short-term cache, which reduces the consumption of the Yandex.Maps quota.

Version 2.0.1

Fixed request frequency validation on hosting environments where the file outside the site directory is restricted.

Module logs are saved one level above the site root.

For Ozon Delivery for Business, a fixed cost has been added separately for pickup points and couriers; a value of 0 indicates free delivery.

Cost fields for pickup points and couriers switch based on the calculation type. Previously installed modules without this setting retain the Ozon tariff calculation.

If Ozon refuses delivery for the specified phone number, the buyer receives a clear message instead of a general calculation error.

When a pickup point is selected, its address is inserted into the configured order address property, even if it is mandatory to fill.

A phone number check via Ozon before opening the pickup point map has been added for both delivery channels, disabled by default.

The settings sidebar remains visible while scrolling the page.

The request limit file is included in the installation package; if a server response error occurs, the buyer no longer sees a technical JSON parsing error.

The API log does not save buyer data from order and delivery requests; phone number validation is additionally limited by cart and a total of 300 requests per hour.

When importing pickup points for Business, Bitrix locations are loaded as needed, without reading the entire table into memory.