Custom New Items Block Development for 1C-Bitrix

The "New Items" block is not just a widget; it requires a balance between data freshness and loading speed. In practice, we often see items not being removed from the "new" label on time, or the block taking 5 seconds to load on catalogs with tens of thousands of items. Our team of certified Bitrix developers with 8+ years of experience and 200+ successful projects offers a proven solution: automatic new item management, tagged cache, and responsive layout. A custom component is 1.5–2 times faster than the standard one when selecting more than 500 items — confirmed by measurements on real projects. We specialize in high-load catalogs up to 500,000 items and 10,000 visitors per day. Below are implementation details that help avoid typical errors and ensure stable results with a 6-month warranty.

Development of the new items block includes several stages: requirements analysis, selection logic design, component implementation, cache configuration, and 1C integration. Each stage has its pitfalls, which we detail below. The result is a fully automated solution that requires no manual intervention and works stably even under peak loads.

How the new item logic works

There are several approaches, depending on how the project manages the assortment.

By date added. The most common option. An item is considered new if the difference between DATE_CREATE of the information block element and the current date does not exceed a set threshold (usually 30–60 days). The query is built via CIBlockElement::GetList or \Bitrix\Iblock\Elements\ElementTable with a filter:

'>=DATE_CREATE' => date('d.m.Y', strtotime('-30 days'))

By a special property. The manager manually marks items with a "New" flag using a Checkbox or list property. Flexible, but requires discipline from the content team. For automatic flag removal after N days, an agent is added that iterates through b_iblock_element_property and resets the value.

By a tagged attribute. If the project has editorial control over the assortment, a separate information block section or smart filter group is used. The logic is simpler and management is more transparent.

Why tagged cache is mandatory for the new items block

Without cache, each request to the block is a database query. The new items block often appears on the homepage, in the catalog, and on the product card, resulting in three identical queries per hit. Tagged cache solves this: it invalidates only when specific items change, not the entire page. Configuration:

• Component cache with a time-to-live of 3600 seconds
• Tagged cache via \Bitrix\Main\Data\TaggedCache
• Composite cache for unauthenticated users

For sites with price groups, the cache key includes the user's GROUP_ID, creating separate cache layers for each group. Database load reduction reaches 30%.

Integration with 1C exchange: pitfalls

If new items are managed by date added or a flag exported from 1C, it's important to check the mapping. In CommerceML, the creation date can be overwritten during each full exchange, "resetting" all items and making them new. Solution: block overwriting of DATE_CREATE in the OnBeforeIBlockElementUpdate event handler or configure the exchange in "do not overwrite date" mode.

How to speed up new items display?

The new items block is often implemented as a horizontal carousel with lazy-load. We load 12–24 items and display 4–6 depending on viewport. For slider initialization, we use Swiper.js or a custom implementation. Important: the product card markup must be identical to that used in the catalog — a shared item.php template. This reuses styles and avoids duplicate markup. The "Add to Cart" button works via an AJAX request to BXBuy.AddProductToBasket or REST API (for headless scenarios).

What's included in the new items block development?

• Custom component in /local/ with tagged cache and price group support
• Agent for automatic new flag removal (optional)
• Responsive carousel with lazy-load and touch events
• Documentation for setup and maintenance
• Training for content managers on using the block
• 6-month warranty on uninterrupted operation

Timeline and warranty

All work comes with a 6-month warranty. Contact us for a consultation and cost estimate for your project. We guarantee stable operation of the new items block and support at all stages.

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.