Classifieds Portal Development on 1C-Bitrix
We often encounter a scenario where a client wants to launch a classifieds portal but loses users at the listing submission stage. Our experience shows that designing a classifieds portal on 1C-Bitrix should start with the user scenario, not the database. A person wants to sell a sofa — takes a photo, writes a description, visits the site, and hits a 30-field form. They give up and go to Avito. If the portal loses users at submission, everything else (moderation, search, monetization) is irrelevant. We've seen that 90% of users abandon a form if it has more than 5 required fields. So the first step is to design a 3-step submission form with autosave.
The Form Submission Problem
In a recent project for a real estate classifieds portal, the initial form had 25 fields. After our redesign to a 3-step wizard with 5 fields per step and autosave via localStorage + AJAX every 30 seconds, completion rates jumped from 40% to 85%. This single change doubled active listings within a month.
Content Model Architecture
A classifieds portal is a catalog of user-generated content with categories, each having its own attribute set. A car is described by make, model, year, mileage. An apartment by area, floor, number of rooms. A smartphone by model, condition, storage.
In 1C-Bitrix, this is implemented using infoblocks with user-defined properties. Two approaches exist:
-
Single infoblock — all listings in one, category defined by section. Dynamic properties via frontend logic.
-
Separate infoblocks for each major category (auto, real estate, services). The second approach is preferable: clean property schemas, indexes tuned for filters, no empty fields.
| Feature |
Single infoblock |
Separate infoblocks |
| Property flexibility |
Medium (logic required) |
High (each infoblock its own schema) |
| Filter performance |
Lower with >10 properties |
Higher (indexes on specific fields) |
| Moderation complexity |
Similar |
Similar |
Each listing element contains:
- title, description, price (with currency)
- category + subcategory (sections, up to 4 levels)
- photos (multiple file property, up to 20 images)
- geolocation (city, district — reference or coordinates)
- contacts (hidden until authorization)
- status: draft, pending moderation, active, sold, removed, blocked
- type: private / business
- placement period and expiration date
Why Category Selection Matters
The submission form should be step-by-step: choose category → fill fields → upload photos → preview → publish. Each step minimizes cognitive load. Autosave through localStorage + AJAX every 30 seconds saves progress if the tab is closed.
We implement a custom component based on bitrix:iblock.element.add.form or a fully custom form using REST API. The second option gives full control over UX: inline validation, progress bar, client-side image cropping.
Content Moderation
Without moderation, the portal fills with spam on day one. We implement a multi-level system:
| Check type |
Timing |
Implementation |
| Stop words |
On save |
OnBeforeIBlockElementAdd |
| Duplicate photo |
On upload |
Perceptual hash, compare with database |
| Duplicate text |
On save |
Shingles or MinHash |
| Phone number in text |
On save |
Regex filter |
| Manual moderation |
After submission |
Queue in admin with bulk actions |
| Abuse reports |
After publication |
Counter with auto-hide threshold |
For new users, we enable pre-moderation (first 5 listings); for experienced users, post-moderation. The moderator interface with keyboard shortcuts speeds up processing.
Search Performance
Search is the primary navigation method. A user sets parameters: "apartment, 2 rooms, Minsk, up to $50,000". Faceted filters on standard CIBlockElement::GetList work up to ~10,000 listings. For 100,000+ listings, we use Elasticsearch: it provides autocomplete, typo correction, synonym search ("one-bedroom" → "1-bedroom"). Elasticsearch is 10x faster for filtering on multiple properties.
Geo-filtering is implemented via coordinates and radius on a map. Saved searches with new listing notifications — through Bitrix agents.
Monetization and Personal Account
The personal account includes: my listings, favorites, internal messaging (contacts hidden until deal), notifications, reviews, balance.
Monetization is built on paid services: listing promotion, highlighted listings, VIP placement, increased photo limits. Subscriptions for sellers with unlimited listings and statistics. Payments via the "E-Store" module and payment systems (YooKassa, CloudPayments). Recurring payments for subscriptions — via card tokenization.
1C-Bitrix documentation recommends using infoblocks v2.0 for catalogs with more than 10,000 elements.
Development cost is calculated individually, based on feature scope and expected load.
SEO and Scalability
Generate unique title/description from properties: "{Title} — buy in {City}". Human-friendly URLs: /category/subcategory/id-slug/. Filters — separate landing pages with meta tags. noindex for empty categories. Microdata Product according to Schema.org.
Performance: composite cache, faceted index, CDN for images with resizing, queues via agents or RabbitMQ. At loads above 500 RPS, we add a read replica.
Development Process
- Analysis: requirements gathering, form prototyping, content model definition.
- Design: database architecture, infoblock schema, caching setup.
- Development: custom components, payment integration, search setup.
- Testing: load testing up to 1000 RPS, moderation testing, usability tests for submission form.
- Deployment: production rollout, monitoring setup, data migration.
Example Docker configuration for local development
FROM php:8.1-fpm
RUN docker-php-ext-install mysqli pdo_mysql
What's Included?
- Content model and database architecture
- Step-by-step submission form with autosave
- Moderation system (auto + manual)
- Elasticsearch search with faceted filters
- Personal account and internal messaging
- Monetization (paid services, subscriptions)
- SEO templates, human-friendly URLs, sitemap
- Administration documentation
- Client team training
- 3 months post-launch support
Our team has 10+ years of experience in 1C-Bitrix development and over 50 successful projects. We guarantee stable portal operation and optimization for high loads. Contact us to discuss your project. Request classifieds portal development or get a consultation.
How a corporate portal on Bitrix24 solves the problem of information chaos?
Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.
We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).
What does the portal offer in daily work and why is it better than messengers?
In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.
Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.
Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.
Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.
HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.
Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.
Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.
How does integration with 1C and Active Directory accelerate HR management?
Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.
Types of corporate portals and key integrations
| Type |
Purpose |
Key Feature |
| Intranet |
Internal communications and services |
News, phone directory (sync with AD), meeting room booking, IT requests via BP |
| HR portal |
HR management and development |
Profiles, KPI/OKR on custom HL blocks, training, electronic document flow |
| Knowledge portal |
Documentation and regulations |
Categorization, tags, ratings, subscriptions to updates |
| Extranet |
Work with partners and contractors |
Granular permissions via CGroup and extranet module, access without VPN |
| Holding portal |
Management of multi‑company structure |
Separate workspaces, consolidated reporting, cross‑cutting BPs |
Additional integrations that deliver real value:
- Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
- IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
- Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
- EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.
Security and compliance with Federal Law 152‑FZ
The portal contains personal data, financial reports, strategic plans. We guarantee protection:
- role model via CGroup and section‑level permissions;
- two‑factor authentication (OTP, Yandex.Key, SMS);
- audit of all actions (b_event_log);
- TLS encryption for transmission and disk encryption;
- full compliance with Federal Law No. 152‑FZ "On Personal Data".
How is implementation carried out? Step‑by‑step plan
| Stage |
Duration |
What we do |
| 1. Audit |
2–3 weeks |
Interviews, process analysis, architecture, integration plan |
| 2. Setup and customization |
3–6 weeks |
Structure, roles, BPs, branding (CSS template) |
| 3. Integrations |
2–4 weeks |
1C, AD, email, telephony, EDI |
| 4. Data migration |
1–2 weeks |
Documents, directories, employees from current systems |
| 5. Training and pilot |
1–2 weeks |
Administrators, key users, pilot of 20–30 people |
| 6. Scaling |
2–4 weeks |
Connecting departments, fine‑tuning based on feedback |
- Audit — we record current processes, measure time losses.
- Design — choose portal type, plan integrations.
- Implementation — configure business processes, permissions, interface.
- Test — pilot group tests scenarios, we fix issues.
- Launch — connect all employees, train, hand over documentation.
What you receive after implementation
- Project documentation: architecture, integration scheme, business process diagrams.
- Configured portal with all integrations (1C, AD, telephony, EDI).
- Business process descriptions and instructions for administrators and users.
- 30 days of technical support after launch.
- Access to our knowledge base and migration scripts.
Post‑launch support: how to prevent the portal from becoming obsolete
After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.
Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.
Order a turnkey corporate portal implementation
Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.
