Creating Banners for 1C-Bitrix: Modules, Infoblocks, Sliders

Creating Banners for 1C-Bitrix: Modules, Infoblocks, Sliders

We often hear from clients: "I need a banner on the homepage." It sounds simple, but in reality it's three separate questions: where the banner is stored (advertising module or infoblock), how it's displayed (static, slider, animation), and who updates it (developer or manager through admin panel). Wrong choice at step one means rework at the first "can we add another slide." Our team of certified Bitrix specialists with 8+ years of experience and 100+ successful projects guarantees a smooth process and avoids these mistakes.

Advertising Module vs. Infoblock

Bitrix has a built-in advertising module—a banner system with targeting, impression statistics, and rotation. For most corporate sites this is overkill, but for e‑commerce stores with promotions and A/B tests it's justified.

Use the advertising module when you need rotation (different banners with different probabilities), CTR statistics and unique impressions, targeting by user groups (GROUPS_BY_USER), or automatic deactivation by date. Banners are stored in the b_banner table. The bitrix:advertising.banner component outputs a banner by the group symbolic code.

An infoblock "Banners" with sections by position (homepage, category, sidebar) is a universal solution. Each element contains an image, title, subtitle, and URL for desktop and mobile versions. A content manager can easily manage elements through the standard interface.

Why Choose an Infoblock for Banners?

If banners are managed by a non‑developer, if you need binding to catalog sections or promotions, or if there are many slides with different links—the infoblock wins. It's more flexible: you can add custom properties for links, deadlines, target groups. The advertising module is overkill for such tasks.

Technical Requirements for Banners

Before creating a banner, fix the requirements in a brief:

GIF for banners is archaic. Animated banners are made with CSS animations (@keyframes) or GSAP. GIF weight is 5–10 times larger for the same visual result. According to a study on web performance, replacing GIF with CSS animations reduces page weight by an average of 60%.

Responsiveness: one image file for all sizes doesn't work. Either two separate images (stored in two infoblock properties: BANNER_DESKTOP and BANNER_MOBILE) or the <picture> tag with srcset:

<picture>
    <source media="(max-width: 768px)" srcset="/upload/mobile-banner.webp">
    <source srcset="/upload/desktop-banner.webp">
    <img src="/upload/desktop-banner.jpg" alt="Bitrix banner for promotion" loading="lazy">
</picture>

How to Choose a Slider Library?

A homepage slider is the most common case. Swiper.js is the most relevant choice: 65 KB gzipped, touch support, lazy load. For comparison, Bootstrap Carousel is over 200 KB, making Swiper.js 3x smaller. Alternatives: Splide (25 KB), Glide.js (minimal). Do not use Bootstrap Carousel (heavy) or Slick (unmaintained since 2016). Connect in Bitrix via Asset:

\Bitrix\Main\Page\Asset::getInstance()->addJs('/local/assets/swiper.min.js');
\Bitrix\Main\Page\Asset::getInstance()->addCss('/local/assets/swiper.min.css');

Or via Webpack/Vite if you have a build setup.

Animated HTML5 Banners

For banners with text animation (title appear, button), CSS animations are preferable to JavaScript:

.banner-title {
    opacity: 0;
    transform: translateY(20px);
    animation: fadeUp 0.6s ease 0.3s forwards;
}
@keyframes fadeUp {
    to { opacity: 1; transform: translateY(0); }
}

GSAP is only needed for complex scenarios: sequential animations, SVG morphing, parallax effects. For a typical promo banner GSAP is overkill.

Managing Banners via Admin Panel

For a manager to change banners without a developer, a clear interface is needed. The standard infoblock interface is not perfect. Improvements:

• Rename fields through infoblock settings: "Preview picture" → "Mobile image", "Detailed picture" → "Desktop image".
• Add hints in property descriptions (size, format, recommendations).
• Implement a preview—a custom subcomponent shows how the banner will look on the site.
• Enable drag‑and‑drop sorting in the element list (sort by SORT field).

A/B Testing of Banners

If banners affect conversion, testing is needed. A simple implementation in Bitrix: two banners in an infoblock, randomly choose one on each request. Write impression and click events to a custom table:

CREATE TABLE b_banner_ab_stat (
    ID SERIAL PRIMARY KEY,
    BANNER_ID INT NOT NULL,
    VARIANT CHAR(1) NOT NULL,
    EVENT_TYPE VARCHAR(10) NOT NULL, -- 'show' or 'click'
    SESSION_ID VARCHAR(40),
    DATE_INSERT TIMESTAMP DEFAULT NOW()
);

Aggregate results with an SQL query calculating CTR per variant. Swiper.js loads 3× faster than Bootstrap Carousel, improving conversion rates.

What's Included

• Design and layout of banners (static and animated).
• Integration with Bitrix (advertising module or infoblock).
• Responsiveness setup (desktop + mobile).
• Admin panel customization (sorting, preview).
• Testing on all devices and browsers.
• Documentation and manager training.

Timeline and Cost

Cost is calculated individually after analyzing your requirements. Request a consultation—contact us for a project estimate.

Typical Mistakes

• Using GIF instead of CSS animations—weight 5–10× larger.
• One image for all resolutions—poor responsiveness.
• Choosing an outdated slider library (Slick, Bootstrap Carousel).
• No preview for manager—long feedback loops.
• Ignoring A/B tests with high traffic.

A banner is the entry point to the sales funnel. It must load fast, display correctly, and be easy to update.

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.