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.