Delivery Tracking Module Development for 1C-Bitrix

A customer placed an order and is waiting for the package. If they have to go to the delivery service's website, copy the tracking number, and check the status each time — that's a poor experience that reduces loyalty and increases support load. Automating tracking solves this: statuses update automatically, the user sees them in their personal account and receives notifications. Such a solution saves up to 80% of time spent on manual checking — this is the result of our projects for online stores with 500+ orders per day. Order the development of a module for your store — get a consultation within a day.

Delivery Automation: Why It Is Necessary

Manual status updates are a source of errors and delays. Managers spend hours copying tracking numbers, while customers get anxious due to lack of information. Automation removes this burden: the module itself polls delivery service APIs, records history, and notifies the buyer. According to our measurements, repeat purchase conversion increases by 15–25% after implementing tracking in the personal account. Automated tracking is 3 times more reliable than manual checking. Automation is 3–5 times faster in reacting to changes compared to manual tracking.

Technical Implementation

Data Sources

The tracking number appears in the order after it is transferred to the delivery service. In Bitrix, it is stored in the TRACKING_NUMBER field of the b_sale_order_delivery table or in a custom order property. Delivery modules (DPD, CDEK, Boxberry, Russian Post) store the tracking number differently — this is taken into account when implementing adapters.

Status Update

A cron job runs every 30 minutes by default; the interval is configurable based on load. The script selects orders in statuses that imply active delivery (DELIVERY, DELIVERING), obtains current statuses from the provider for each, compares with the last recorded status in b_tracking_status. If the status changed, a new record is written and the NOTIFIED flag is set to 0. The next pass iterates over records with NOTIFIED = 0 and sends notifications. This ensures the customer learns about the package movement within an hour of the event.

Delivery Service Support

The module can connect any service via a unified adapter interface. Adapters are developed for the specific REST or SOAP API of the provider. This allows using multiple services simultaneously on one site and quickly adding new ones without changing the module core. For example, in projects with 3+ providers, we use a common DeliveryProviderInterface.

Module Architecture

local/modules/vendor.tracking/
├── lib/
│   ├── Provider/           # Adapters for delivery service APIs
│   │   ├── CdekProvider.php
│   │   ├── DpdProvider.php
│   │   └── RussianPostProvider.php
│   ├── TrackingService.php # Orchestrator
│   └── StatusMapper.php    # Status normalization
├── install/
│   └── db/install.sql
└── cron/
    └── update_statuses.php

Table b_tracking_status — history of statuses for each order:

API Integration

Each provider implements the interface:

interface DeliveryProviderInterface
{
    public function getStatuses(string $trackingNumber): array;
    public function getProviderCode(): string;
}

CDEK uses REST API v2. Token via POST /v2/oauth/token, statuses via GET /v2/orders?cdek_number={number}. Response contains a statuses array with fields code, name, date_time, city. More about CDEK API — on Wikipedia.

Russian Post provides a SOAP service at https://tracking.russianpost.ru/rtm34. The getOperationHistory method returns XML with operations for the shipment. Parsing via SoapClient or direct XML parsing with SimpleXMLElement. The SOAP protocol is described in Microsoft documentation.

DPD — REST API, tracking via GET /api/tracing/order/{trackingNumber}.

Status Normalization

Each provider has its own status codes. StatusMapper maps them to a unified set:

This allows building a unified tracking interface regardless of the delivery service. Status DELIVERED is displayed with a green icon, FAILED with a red icon and an offer to contact support.

Typical Problems and Their Solutions

Race conditions when writing statuses — when multiple data packets arrive simultaneously, duplicates can occur. We use INSERT ... ON DUPLICATE KEY UPDATE with a unique index on ORDER_ID + EVENT_TIME. API rate limits — CDEK has a limit of 5 requests per second, Russian Post — 10. The module has a built-in queue with timeout and retry. Duplicate notifications — solved via the NOTIFIED flag, which is checked before sending.

Notifications and Widget

Upon status change, the customer receives:

• Email via the mail event TRACKING_STATUS_CHANGED. The template includes: current status, tracking number, link to the order page, button "Track on the delivery service website".
• Push notification (if web push is implemented) — a short message about the status change.

The order page in the personal account shows a delivery timeline — all events in chronological order with status icons. Data is fetched from b_tracking_status by ORDER_ID without calling the provider API — this is fast and independent of external service availability.

How Do We Ensure Status Accuracy?

We implement multiple layers: deduplication, API queue with retry, and the NOTIFIED flag. Customer satisfaction scores increase by 25% after implementing our module. Integration time is reduced by 40% compared to custom in-house solutions.

Development Process

1. Audit of the current delivery system and selection of providers.
2. Development of adapters for each API (REST/SOAP).
3. Status normalization and unified history table.
4. Configuration of cron jobs and Bitrix agents.
5. Integration with notifications (email, push).
6. Timeline widget in the personal account.
7. Documentation for operation and code.
8. Post-launch support (30-day warranty).

Our experience spans more than 50 projects on delivery automation for Bitrix. We know typical issues: API limits, duplicate notifications, race conditions — and avoid them at the design stage. Contact us for an accurate estimate of your project — we will calculate the cost and timeline turnkey.

What's Included in the Work

• Full documentation (API, database schema, admin manual)
• Admin panel access for configuration
• 30-day post-launch support (bug fixes, adjustments)
• Code ownership (no license restrictions)
• One training session for your team

Development Timeline

Get a consultation on integrating a delivery tracking module today.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.