Аккаунт в General iT
Войдите или создайте аккаунт для управления услугами в личном кабинете.
Страны не найдены. Попробуйте другое название или код.
MODULE FOR 1C-BITRIX
TOP MAN DIGITAL
The Ozon Delivery for Business module integrates online store order logistics directly into the Bitrix administrative panel. During checkout, the customer selects an Ozon pickup point or courier service. The system automatically requests delivery costs and timeframes from the service.
The Ozon Delivery for Business module integrates online store order logistics directly into the Bitrix administrative panel. During checkout, the customer selects an Ozon pickup point or courier service. The system automatically requests delivery costs and timeframes from the service. A manager creates the shipment, retrieves the shipping label, and tracks the parcel status without switching to external resources. Listing products on the Ozon marketplace is not required. Integration is performed via the Delivery API and handles only the store's order delivery, without synchronizing the product catalog, prices, or stock levels.
The Ozon Delivery for Business module integrates into 1C-Bitrix and supports three key workflows. At checkout, customers see delivery options: a pickup point or courier, along with calculated costs and estimated delivery times. Managers handle the entire shipping process within the system, including order confirmation, label printing, and status tracking without switching to external resources. Store owners can configure custom pricing rules, account for packaging costs, and reconcile calculated amounts with actual deductions.
The module implements two delivery methods. The first is the Ozon Pickup Point. Customers search for a nearby location by address and select it from a list. If Yandex Maps are connected, selection is available directly on the interactive map. The second method is courier delivery. Customers enter their delivery address using autocomplete suggestions from DaData or Yandex Geocoder to ensure accuracy and speed.
Delivery costs and timeframes are calculated automatically via the Ozon service during order checkout. There is no need to manually update the tariff table in store settings. The system requires the recipient's phone number and the selected pickup point or delivery address to perform the calculation. Until these fields are filled, the module displays a placeholder message instead of a price.
Configuring delivery price for the buyer
Use the Ozon calculation as a base and define your store's conditions:
whether to include insurance in the buyer's total cost;
applying percentage or fixed markups;
setting a minimum delivery fee;
configuring price rounding rules;
defining the order total threshold for free delivery, specified separately for pickup points and courier services.
Individual rules can be configured for each pickup method instead of using general settings. For example, free delivery to a pickup point can be set for orders above one amount, while courier delivery can be free for orders above a different amount.
The calculation breakdown is preserved in the shipment document, allowing managers to see the exact price structure formed for the buyer.
Processing shipments in 1C-Bitrix
Manage delivery directly from orders or shipments via the Transport Request section:
create shipments in Ozon;
confirm them for shipment;
receive printable labels;
cancel shipments if the current status in Ozon allows it;
receive real-time delivery status updates.
Configure which Ozon statuses allow delivery, automatically mark shipments as completed, and update order statuses. By default, the module does not change order statuses on behalf of the manager.
Automatic shipment creation is disabled by default. It can be enabled only after verifying the workflow. Note that creating a shipment in Ozon may incur delivery costs.
Consider packaging dimensions, not just products
Packaging size directly affects delivery cost calculations. The module supports three methods for determining package dimensions:
Box catalog. Specify your box dimensions, and the module will automatically select the appropriate option.
Calculation by product volume. Use a coefficient that accounts for the necessary space required for packaging.
Fixed box. This method is suitable for orders that are always shipped in identical packaging.
The 'Products without weight and dimensions' report identifies catalog items missing mass and size data. The system applies default values for such items, so the catalog should be verified before starting shipments.
Reconcile calculations with actual deductions
The preliminary cost calculated via the API may differ from the final deduction amount in Ozon. The module does not hide this discrepancy.
Upload a CSV file from the financial report in the Ozon account to the 'Packaging Calibration' section. The system will match actual deductions with the preliminary calculation, helping to evaluate whether the selected packaging parameters correspond to real shipments.
Returns and diagnostics
Returns list: view return data, update information from Ozon, and obtain barcodes for pickup.
Pickup points: a local directory with search and filter functions, plus background data synchronization.
Connection: verification of authorization and available delivery methods in the service card.
Exchange log: recording of API responses and errors for problem analysis.
Ozon unavailability: configuration of timeouts and system behavior during calculation failures.
Selecting a pickup point does not require a map: the list with search functionality works without a Yandex Maps key.
To connect, an online store on the 1C-Bitrix platform with the 'Online Store' module installed is required.
To configure the module, you need data from the Ozon Business Delivery account: Client ID, the Delivery API application secret key, and the delivery method number. You also need the phone number of the recipient registered in Ozon. For courier delivery, a DaData or Yandex Geocoder key is required, and for selecting pickup points on a map, a Yandex Maps key is needed.
In the standard order checkout template sale.order.ajax, the widget is connected automatically. For non-standard checkout designs, the module provides components whose installation may require developer assistance. Background tasks in the Bitrix system must run to update reference books and statuses. Receiving shipment statuses is enabled in the online store automation settings.
It is important to note that the module does not export the product catalog to the marketplace and does not replace the integration with the Ozon seller account. Delivery costs appear only during order checkout after entering data for calculation, not in the standard shopping cart. The Ozon calculation is preliminary; actual charges are verified via the financial report in the account.
One shipment in Bitrix corresponds to one Ozon package. Delivery availability, as well as restrictions on goods, dimensions, and directions, are determined by Ozon. The module license does not include payment for delivery services or third-party services.
Test the module on your store. Click the Try button, connect the Ozon account, and verify the full workflow: selecting a pickup point or courier, calculating delivery costs, saving order data, and managing the shipment. If you are unsure whether the module fits your checkout template, contact technical support. Provide the site address, template name, and the checkout component in use. This will allow you to determine in advance if customization is required.
General iT can install “Ozon Delivery for Business: Pickup Points, Courier, and Shipments in Bitrix”, configure its settings and verify its operation in the existing project.
UPDATE HISTORY
- Fixed loading of delivery classes, restrictions, and tracking when using the common site and portal core.
- Fixed processing of international phone numbers, including +995, when calculating and creating shipments.
- Separated messages for missing phone numbers and incorrect number formats.
- Fixed phone number validation in the wizard's control calculation.
- Added masking of international phone numbers in the exchange log.
- Fixed filtering of the exchange log by method, response code, period, and tracking.
- Fixed the list of additional filter conditions for the log.
- The load history of the pickup point (PVZ) directory no longer disables hiding delivery in populated areas without suitable PVZs.
- The hiding is preserved during re-synchronization for the same connection.
- The hint for the delivery hiding setting has been clarified.
- Fixed the matching of names for towns, villages, and settlements when checking pickup point availability.
- Fixed the map center determination for settlements with a parent city, including Dunay in the Primorsky Krai.
- Pickup point search by multiple words works independently of their order and commas.
- Simplified the setup wizard to three steps; fixed saving of active services and field formatting in Safari.
- Fixed map centering for villages and hiding pickup points based on the directory of previous versions.
- For an unregistered recipient number, the estimated price and delivery time are saved; a warning is shown to the buyer and the manager.
- Before creating a shipment, the recipient's actual number is verified again; the store's phone number is not used for sending.
- Added an estimated delivery time during order checkout.
- Refined map centering for villages and settlements.
- Added a setting to hide pickup point delivery when no suitable points are available in the selected locality.
- Selecting a point in the list zooms it on the map; the selected marker is preserved when the map is refreshed.
- Fixed messages about the absence of courier delivery in the wizard's control calculation.
- When editing an address, the previous tariff is hidden until the house is confirmed; clarifications for the courier are preserved.
- Premature recalculations and the application of outdated address suggestion responses have been excluded.
- The map center is determined taking into account the region and district of the selected location.
- Added the ability to choose the position of the Pickup Point button: under the delivery option or under the service description.
- During a clean installation, the position under the description and the pop-up window are enabled by default; existing settings are preserved.
- Fixed the hiding of the Ozon widget when switching to another delivery service.
- Enabled the wizard to pick up existing settings and to create new services from version 1.1.3.
- The wizard automatically detects the single existing service and its settings.
- When multiple services exist, an explicit selection is provided; the selected service and step are saved.
- The saved configuration is separate from the connection test result; active delivery does not require re-enabling.
- New services and wizard profiles receive the Ozon logo and a short description.
- Added loading and selection of delivery methods from the Ozon office.
- Wizard settings are saved by clicking the "Next" button.
- The store's mandatory phone number has been added for preliminary calculation and to designate required fields.
- The map can be loaded without a Yandex Maps key; in case of an error, the list remains.
- Automatic preloading of pickup points and wizard completion from version 1.1.1 have been enabled.
- Automatic preloading of pickup point addresses has been added during installation and update.
- The full initial set has been re-included in the update to restore incomplete loads.
- Wizard messages have been moved to the corresponding actions.
- Explicit completion of the setup with confirmation of enabling the delivery service has been added.
- Handling of incorrect coordinates in the previous map handler has been fixed.
- Added a step-by-step wizard for connecting and configuring delivery.
- Added an initial directory of pickup points with availability verification via the store API.
- Accelerated directory loading: chunks, pause, and resume without losing progress.
- Added readiness checks and trial calculation without creating an order.
- Included fixes for recalculation after phone number change from version 1.0.16; fixed label retrieval diagnostics.
- Added recalculation of delivery after changing the recipient's phone number.
- Fixed loss of recalculation during AJAX redraw of the pickup point or address field.
- Excluded duplicate requests when only the phone number format is changed.
- The map displays all suitable pickup points in the visible area: when zooming out, points are grouped.
- The pickup point card replaces the list; returning preserves the search, scroll, and map area.
- Fixed the size and alignment of the window close button.
- Order and cart loading via the Bitrix edition class registry is enabled from version 1.0.14.
Orders and the cart are loaded via the class registry of the installed Bitrix edition. Changes affect shipping requests, tracking, email variables, and pickup point filtering. Existing settings and data are not migrated. Regression testing of a standard online store has been performed; the Online Store + CRM edition requires separate testing on its own stand. The requirement for PHP 8.0 and above remains.
A detailed pickup point working schedule has been added to the selection card: schedule by date and day of the week, breaks, and weekends. The current day is highlighted, and additional dates expand separately. If no fresh dates are available, the standard weekly schedule is displayed. The update also includes pickup point selection in a popup window, map binding to the order city, and smooth recalculation of the checkout from version 1.0.12. Compact mode remains the default.
Pickup point selection has been added in a popup window: the mode is switched in the module settings. The map and list take into account the city selected during checkout. The selection is confirmed by a separate button; the pickup point address fills the delivery address field. Order recalculation occurs with the window open, without repetitions due to missing price and without scroll jumps. The cumulative update includes delivery dates, email variables, and fixes for tracking in previous versions.
- The address of the selected pickup point is immediately written to the Delivery Address field during checkout.
- The address is verified against the pickup point directory before saving the order.
- Changes from versions 1.0.9 and 1.0.10 are included.
The "Problematic" tag no longer appears due to the module's own status update for Ozon. 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. This specific tag is removed only for Ozon shipments: other order tags remain in place, and the problem 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 have remained 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 mail 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 receipt 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 Ozon delivery service data, those services are removed; services with existing orders are disabled.
- When the module is deleted, its restrictions are removed from the store's delivery services: the shipment card in the admin panel no longer crashes with an error.
- The deletion completion page shows which services were deleted, which were disabled, and why.
Working with the paid build from the Marketplace. The installer and uninstaller no longer connect the module itself, but register its classes directly: in the paid build, connecting the module 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 pickup point directory no longer loses points. Previously, traversing the directory would stop at the first network hiccup, and a point that was not included in one traversal would immediately be disabled - a check on the live cabinet showed that 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 absent 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 'Pickup Points' page during mass disabling. The traversal has become 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 learned about this only after clicking 'Place Order': the order was not saved, and an error 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 continues to work. Server-side validation remains in place: it protects templates where the order buttons are named differently.
Delivery calculation when Ozon responds slowly or not at all. 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 Bitrix then displayed a zero delivery cost for the failed calculation—the buyer saw "free" where a price should have been. For sites with a setting below 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 moment, and as a second option, the price can be shown according to your own rules—markup and the store's minimum cost. Ozon's refusal is not overridden by this setting: a refusal is a response, and it is displayed as is.
Labels for price fields in the delivery service card. The markup and other price fields in the delivery method card work only when the "Set your own price rules instead of general ones" switch is enabled—this is now stated directly in the labels, rather than being discovered through trial and error. The "Price for buyer" tab header in the module settings names this switch.
Pickup point map: the selected pickup point hides the map and displays the "Select another pickup point" button, so the form no longer jolts after selection. The map opens to the city selected during checkout and, if the buyer permits, moves to their location. New setting "Phone for preliminary calculation": until the buyer enters their phone number, the cost is calculated using the store's number, and after entry it is recalculated.
USER EXPERIENCE
How does this solution work in a real project? Share your experience and help others choose.
There are no reviews of this solution on git.ru yet. Tell us what worked well and what could be improved.
Verified purchaseAdd a key if you wish. A verified review gets a badge, priority placement and more rating weight.
Open to every clientJust sign in to your account. A key is optional; all reviews are moderated.
YOUR PROJECT INFRASTRUCTURE
FROM THE SAME DEVELOPER
TOP MAN DIGITAL
Top Man Digital: Reviews module automates the transfer of reviews from external aggregator sites to your website. Simply insert a link to the organization's profile once: the system identifies the source, fetches reviews, avatars, and photos, then stores them in the 'Reviews' information block. The module then periodically checks for new reviews, requiring only your approval for publication.
The smart filter of an online store generates many pages for real parameter combinations: color, size, brand, price, and others. Without specific SEO settings, such pages often inherit identical title, description, and H1 tags from the section. The module transforms filter pages into managed SEO landing pages.
The module reduces page weight and accelerates content loading. It generates lightweight image copies, optimizes CSS and JavaScript files, and configures lazy loading for videos, maps, and third-party widgets. This reduces the data volume transferred to visitors while preserving the original site files.
MORE FOR YOUR WEBSITE
The Sotbit Smart Filter SEO module is designed to increase online store traffic. The tool operates by generating numerous unique pages for smart filters.
SDEK integration module for 1C-Bitrix. SDEK is one of Russia's largest logistics companies, providing courier delivery and operating a network of pickup points. The module connects the online store with the SDEK personal account, offering the following capabilities: Providing customers with delivery options: courier, pickup point, or postmat.
The module is designed for the «1C-Bitrix: Site Management» platform and enables importing infoblock elements, including products, from Excel files. It also supports data loading into Highload blocks.
BEFORE YOU ORDER