A sofa in five upholsteries, three sizes, and two frame configurations — 30 trade offers. A modular kitchen set where the buyer wants to see the result before ordering. For furniture factory website development on 1C-Bitrix, it is the optimal choice because it solves both tasks: a catalog with SKU mechanism and faceted filtering for standard furniture, plus a 3D configurator for modular systems. Integration with 1C via CommerceML 2 keeps prices and stock up-to-date without manual updates, saving up to $2,000 per month in manual labor costs. For a typical project, the investment starts from $15,000 for the basic catalog with integration. Typical hosting costs around $150 per month, and the integration setup fee is approximately $3,000.
Benefits of 1C-Bitrix for Your Furniture Factory Website
Because it handles the two critical requirements: a catalog with SKU mechanism and faceted filtering, plus a 3D configurator for modular systems. Integration with 1C automates price and stock updates, saving thousands per month. Our experience in building a furniture catalog on Bitrix ensures seamless scalability and efficient management of thousands of SKUs.
Special Requirements for a Furniture Factory Website
In the product catalog - up to 10,000 variations, each with unique parameters: upholstery, size, facade. Without Bitrix trade offers, you would have to duplicate cards or lose control over stock. The SKU mechanism allows you to attach multiple variations with their own prices, SKUs, and photos to a single product. It is faster and more reliable than a custom solution: generating 10,000 SKUs takes minutes, not hours.
Furniture Catalog with Trade Offers
The "Furniture" infoblock contains products linked to a trade offer infoblock. Product properties: collection, style (classic, modern, loft, Scandinavian, minimalist), frame material (solid oak, solid beech, laminated chipboard, MDF, metal), country of origin, warranty (months), 3D model (GLTF/GLB). Trade offers include: color, upholstery/facade material, size (W×D×H), SKU, price (via the catalog module), stock.
Module Types Table
| Module Type |
Size (mm) |
Material |
Features |
| Base cabinet |
600x600x850 |
Chipboard, MDF |
With drawers or shelves |
| Wall cabinet |
600x320x700 |
Chipboard, MDF |
Glass facades |
| Tall cabinet |
600x600x2100 |
MDF |
Pull-out baskets |
How to Speed Up Filtering in a Catalog with 5000 SKU?
To speed up filtering in a catalog with thousands of SKUs, enable the faceted index of the iblock module (method \Bitrix\Iblock\PropertyIndex\Manager::buildIndex()). The component bitrix:catalog.smart.filter outputs: material, style, price (slider), size (ranges), color (visual chips), availability. The faceted index is rebuilt when products change. For 5000+ SKUs, filter speed is an order of magnitude higher than direct SQL queries — this makes faceted filtering up to 10 times faster than standard SQL queries. The index rebuilds in under 2 minutes for 10,000 SKUs.
How to Integrate with 1C?
Synchronization via the exchange module catalog using the CommerceML 2 protocol. Nomenclature, prices, stocks, orders — two-way exchange. Schedule: prices and stocks every 30 minutes (cron), nomenclature once a day, orders every 15 minutes. For details, see CommerceML 2.0 specification. Integration saves up to 40 hours of manual updates per month.
B2B Section for Dealers
Dealers register via a form moderated by a business process. After confirmation, they get access to: dealer prices (separate price type), extended catalog with access rights, marketing materials, order history and settlements from 1C.
Deep-dive: 3D Furniture Configurator
The buyer assembles a kitchen from modules in a 3D space: selects cabinets, places along walls, chooses facades, and sees the final cost. Technically, it's a WebGL application on Three.js integrated with Bitrix via REST API.
Interaction Architecture:
- JS requests
/api/configurator/modules/ — list of modules with parameters.
- Data from the "Configurator Modules" infoblock.
- 3D models in GLTF/GLB format with Draco compression (reduces size by 70-80%).
- When a module is placed, the specification and cost are updated.
Models and optimization: each module is a parametric model: body, facade (replaceable), hardware. Low-poly (up to 5000 polygons), textures 512×512. Lazy loading: first a preview, then the detailed model.
Material switching: when a facade is selected, Three.js replaces the texture via THREE.TextureLoader with caching. Textures are stored in a Highload infoblock "Configurator Materials".
Arrangement: the user sets the room dimensions. Modules snap to walls via snap logic, collisions checked by bounding boxes. Constraints are set in module properties: UF_WALL_TYPE, UF_SNAP_POINTS, UF_MIN_HEIGHT.
Order generation: a JSON specification is sent to the server, PHP creates an order in the sale module, calculates cost, and exports to 1C.
Performance: 15-20 modules on scene at 30 FPS on an average device. We use Instancing, Frustum culling, LOD. Shadows are disabled.
Turnkey Development Deliverables
Project Stages and Duration
| Stage |
Duration |
| Analytics and prototype |
1-2 weeks |
| Catalog setup and integration |
3-4 weeks |
| B2B and configurator development |
4-8 weeks |
| Testing and deployment |
1-2 weeks |
The project deliverables include: full technical documentation, administrator training (up to 5 sessions), 3 months of post-launch support, hosting configuration, and all source code. Additional support and maintenance packages are available.
- Analytics and catalog architecture design.
- Configuration of infoblocks, trade offers, faceted index.
- Integration with 1C (exchange, prices, stocks).
- Development of B2B section for dealers (if needed).
- Design and implementation of the 3D configurator.
- Testing (including load testing for the catalog).
- Deployment and cache configuration (tagged cache, CDN for models).
- Administrator training and documentation.
Technical Requirements
Edition "Business". Server: PHP 8.1+, MySQL or PostgreSQL, minimum 4 GB RAM, SSD for GLTF files. Composite cache for the catalog, CDN for 3D models.
We have been developing furniture industry websites on 1C-Bitrix for 8 years, completing 15 projects for furniture companies. Order turnkey development — get a preliminary estimate of timelines and cost. Contact us for a consultation.
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.
