Building an event website on 1C-Bitrix means constructing a transactional system: registration, ticket sales, QR-code generation, personal account, integration with CRM and payment gateways. A mistake at the start—like storing speakers, schedule, and tickets in a single infoblock—leads to painful data migration six months later when a second event is launched. We solve these problems using proven architecture from over 40 event projects.
What minimal infoblocks do you need?
An event site requires at least four infoblocks. You could get by with three by gluing the schedule to events, but as soon as you run multi-day conferences with parallel tracks, that approach breaks.
Events infoblock (type events) — the main entity. Properties: DATE_START, DATE_END (type 'Date/Time', must be indexed on b_iblock_element_property), VENUE (link to a Highload-block of venues), CAPACITY (checked in OnSaleOrderBeforeSaved), STATUS (list of states), STREAM_URL (accessible after payment), SCHEMA_ORG (computed field for JSON-LD).
Speakers infoblock — separate, with multiple binding to events. Contains photo, bio, company, position, and social links.
Schedule infoblock — each element is a time slot linked to an event and speaker, with type (talk, workshop, break).
Tickets infoblock — products of the e‑commerce catalog. Each ticket type is a separate element with properties EVENT_ID, TICKET_TYPE, AVAILABLE_SEATS, VALID_UNTIL.
Why not Highload-blocks? For speakers and schedule the data volume is small, and infoblocks provide ready-made components and a visual editor. Highload is justified for venues (500+ records) and check-in logs.
How to organize ticket sales on Bitrix?
This is the central and hardest part. A ticket is a product in the catalog, but with non-standard logic: linked to a date, personalized, quantity-limited.
Product = element of the 'Tickets' infoblock connected to the e‑commerce catalog. Each ticket type for each event is a separate product. A 500-person conference with three ticket types means three products, each with its own warehouse stock.
Warehouse accounting automatically decreases stock when an item is added to the cart. When stock reaches zero, the 'Buy' button is replaced with 'Sold out' — checked via CCatalogProduct::GetByID() in the template.
The order process includes a custom step with participant fields, payment via YooKassa, Stripe, or PayPal, and the OnSalePaymentEntitySaved event that generates a QR code and sends an email. Promo codes are implemented through catalog.discount with a promo-code condition.
The handler OnSaleOrderBeforeSaved rejects the order if there are no seats. Additional reservation: decreasing QUANTITY on adding to cart with a 30-minute release via an agent. 1С-Битрикс agents in this case free the reservation. This prevents double sales under high load.
Personal account and notifications
For free events — a custom component that writes to a Highload-block and creates a lead in CRM via REST API. For paid ones — automatic registration upon payment.
Member personal account based on sale.personal.section with a custom template: list of events, order history, download PDF ticket with QR, access to stream (link appears 30 minutes before start), participant certificate.
Countdown timer — JS using setInterval with server time. Stream component with access check: authentication, paid ticket, time. On mismatch — redirect to purchase.
Email notifications via the 'subscribe' module: registration confirmation, ticket after payment (with PDF), 24-hour reminder (agent), schedule change (handler OnAfterIBlockElementUpdate).
SEO and calendar
Schema.org Event — in result_modifier.php we generate JSON-LD markup with fields name, startDate, location, offers, performer. The availability field dynamically switches between InStock and SoldOut.
Event calendar: custom component + FullCalendar.js — interactive, cached, loads 3 times faster than the standard one with 50 events. For simple lists the standard iblock.element.list suffices.
What stages does event website development include?
The process is divided into seven stages: planning (1–2 weeks), design (1–2), backend (2–4), frontend (2–3), integrations (1–2), testing (1–2), launch (3–5 days). Approximate timelines depend on scale:
| Project scale |
Approximate timeline |
| Single event, registration without payment |
3–5 weeks |
| Event with ticket sales and QR |
6–9 weeks |
| Multi-event platform with personal account |
8–12 weeks |
What's included in the work
| Phase |
Outcome |
| Requirements analysis |
Technical specification, prototype |
| Architecture design |
Infoblock scheme, HL-blocks, agents |
| Component development |
Backend logic, templates, API |
| Integrations |
Payment systems, CRM, 1C, CDEK |
| QR generation |
endroid/qr-code library |
| Check-in |
Entry via QR, verification |
| Testing |
Load test (simulating 500 purchases) |
| Documentation and training |
Admin guide |
| Warranty support |
1 month after launch |
Automating ticket sales pays off after just two events by reducing manual work. Get a consultation on your event site architecture — our engineers will select the optimal infoblock structure and integrations. Contact us to discuss your project.
How to properly design infoblocks?
When developing a 1C-Bitrix website, we see dozens of projects where poor infoblock structure slows down the site. Typical scenario: the client asks for a "product catalog." The developer creates one infoblock catalog, puts 15 properties in it. Six months later – 40 properties, 8 of which are used only for one category. The filter lags, the b_iblock_element_property table grows to millions of rows, CIBlockElement::GetList runs for 3 seconds. Consequences – conversion drop, loss of customers, additional optimization costs. In one project after catalog refactoring, page generation time dropped from 4.2 to 0.8 seconds, and annual support costs were reduced by over $10,000 through eliminated redundant queries and agents.
Our approach: design infoblocks before writing a single line of code. Separate infoblocks for entities (products, categories, brands), dictionary properties via highload blocks, trade offers for SKUs. This builds performance for years. If you want a preliminary audit of your infoblock schema, contact us for a free review of common mistakes and recommendations.
Why 1C-Bitrix outperforms most CMS for business
The choice of CMS is dictated by business needs, not preferences. Native 1C exchange via catalog.import.1c provides two-way synchronization of products, prices, balances, and orders through CommerceML without third-party modules — five times faster than developing custom exchange on OpenCart or WordPress, saving hundreds of thousands of rubles. Proactive security module includes WAF, file integrity control, SQL injection protection, and two-factor authentication; it's certified for FSTEK requirements. Modular architecture lets you enable only needed modules — iblock, catalog, sale, search — reducing DB queries per hit. Regular patches close vulnerabilities faster than open-source projects (average CVE fix time two weeks). Official documentation is maintained on the vendor's site.
What highload blocks are and how they speed up the catalog
Highload blocks are an alternative to extended infoblock properties when the list of values can grow to thousands of entries. Typical example: manufacturers, countries, colors. If stored as list properties in an infoblock, each filter triggers a full scan of b_iblock_property_enum table. With HL-blocks, selection uses indexes – filter response time drops from 1–2 seconds to 50 ms. We use HLB component and custom queries via Bitrix\Highloadblock\DataManager. This is critical for catalogs with 100,000+ items.
From our practice: an online store with 500,000 items. Standard filter by brand took 4 seconds. The server couldn't handle 50 concurrent requests – pages crashed. We moved the brand directory to an HL-block, added tagged caching for 15 minutes, and set up an agent to clear cache on change. After optimization, filter time was 120 ms, average LCP was 1.8 seconds. The project runs stable without failures.
What integrations are critical for 1C-Bitrix stores
Each e‑commerce project requires reliable connections with payments, fiscalization, logistics, and CRM. We integrate YooKassa, CloudPayments, Tinkoff, Apple Pay, Google Pay for payments; ATOL and OrangeData for 54-FZ compliance via sale.cashbox; CDEK, Boxberry, PEC, Russian Post, Yandex.Delivery for logistics; Bitrix24, amoCRM, Roistat, Calltouch, Mindbox for analytics and CRM. All integrations are configured with proper error handling and fallback logic.
What's included in 1C-Bitrix website development
Each project includes a full set of documentation and artifacts to prevent knowledge loss after handover.
- Technical specification – user stories, infoblock diagrams, integration schemas.
- Source code in Git – with commit history, release tags, branching rules.
- Administrative documentation – description of custom components, deployment instructions, list of agents and events.
- Staff training – up to a 3-hour webinar: admin panel, order management, price settings. Recorded for later review.
- Access to staging during development – test before production deployment.
- Warranty support – bug fixes for 30 days after launch. Post-warranty support packages with SLA (response 2 hours, resolution 8 hours).
Our process and technologies
| Project type |
Timeline |
Complexity |
Key features |
| Corporate website |
from 1 month |
Medium |
Catalog, news, forms, CRM integration |
| Online store |
from 2 months |
High |
54-FZ, marketplaces, 1C exchange, SKU |
| B2B portal |
from 3 months |
Very high |
Personal prices, document flow, Bizproc |
| Landing page |
from 2 weeks |
Low |
LCP < 2s, composite cache, static |
| Multisite structure |
from 1.5 months |
High |
Separate content, shared catalog, hreflang |
Tech stack: mobile-first markup, tested on physical devices (iPhone, iPad, Android). Use BrowserStack for Safari on iOS. Performance goals: LCP < 2.5 s, FID < 100 ms, CLS < 0.1. Enable composite site (composite module), CDN, tagged caching, WebP/AVIF, lazy loading. SEO: Schema.org via JSON-LD, auto-generation of sitemap.xml via seo module, canonical and hreflang for multilingual versions. robots.txt blocks /bitrix/ from indexing. CI/CD: Git, auto-deploy via GitLab CI, staging. DB migrations: sprint.migration module with versioning.
Process:
-
Analytics – study competitors, gather requirements, create prototypes in Figma. Output: technical specification with user stories.
-
Design – UI/UX with design system. Components are reusable.
-
Development – write components with custom templates in
local/templates/. Business logic in local/modules/.
-
Testing – functional, cross-browser, load testing (up to 1000 requests). Critical bugs fixed before launch.
-
Launch – deploy to production, monitoring via UptimeRobot, alerts in Telegram. Fixes for first 48 hours.
Multilingual support and redesign
Full localization via language files lang/ and SITE_ID mechanism. hreflang for each version. Regional versions with different prices and content – IP detection (main.geo) or manual selection. Multidomain – unified management of multiple domains.
Redesign without losing rankings: performance audit (PageSpeed, WebPageTest), SEO (Screaming Frog). New template in local/templates/ with preserved URL structure. 301 redirects only if URL changes significantly. Kernel update, migration to D7 ORM, infoblock restructuring, migration via sprint.migration with Git.
Guarantee and support
We have been working with 1C-Bitrix for 12+ years, completed 500+ projects. Certified developers on staff. Fixed price in contract – no surprises. Warranty period covers code errors. After warranty, subscription packages with SLA (response time 2 hours, resolution 8 hours). 24/7 availability monitoring, alerts in Telegram. Get a consultation and preliminary estimate: contact us via the form on the website or chat – we'll respond within an hour. Order turnkey development – we'll design infoblocks, integrate 1C, and speed up the catalog. If you already have a site on another CMS, order a performance audit and migration to Bitrix.
