A coworking space can lose up to 30% of its revenue if bookings are handled through phone calls and spreadsheets. We've seen this on dozens of projects: an empty desk at 2 PM is lost profit. Our experience shows that automating bookings on 1C-Bitrix frees up to 20% of admin time and increases occupancy. The cost of such development pays off within 3–6 months. We offer a turnkey coworking website: from a space catalog to access control integration and 54-FZ fiscalization. Assess your project — contact us for a free consultation.
A coworking website must sell time: display spaces, let users pick an available slot, accept payment, and issue a QR code for entry — all without admin intervention. On 1C-Bitrix, this is achieved using the sale module, Highload blocks for bookings, and access control integration. For fiscalization, we connect AtolOnline or CloudPayments with 54-FZ support.
Why 1C-Bitrix for a Coworking Website?
The platform provides flexibility for complex tariff structures: hourly rental, daily passes, monthly unlimited. Infoblocks v2.0 and Highload blocks allow storing spaces, bookings, and registrations. Built-in business processes automate checking expired subscriptions via agents (CAgent). We also leverage integration with 1C:Trade Management via CommerceML to synchronize products and orders.
How to Automate Bookings Without Conflicts?
Booking is the core of a coworking site. Standard Bitrix modules are designed for product e-commerce, but here you need to sell time slots with visual occupancy. We use custom development on top of the sale module.
Highload Block for Bookings
The central entity is a Highload block called "Bookings" (BookingTable):
| Field |
Type |
Purpose |
| UF_SPACE_ID |
Binding |
Space from infoblock |
| UF_USER_ID |
Number |
Who booked |
| UF_DATE |
Date |
Booking date |
| UF_TIME_FROM |
String |
Start time (HH:MM) |
| UF_TIME_TO |
String |
End time (HH:MM) |
| UF_ORDER_ID |
Number |
Order ID from sale module |
| UF_STATUS |
List |
Awaiting payment / Paid / Cancelled / Completed |
| UF_QR_TOKEN |
String |
Unique token for QR code |
| UF_CHECKIN |
Date/time |
Actual entry time via access control |
| UF_CHECKOUT |
Date/time |
Actual exit time |
Indexes: composite index on UF_SPACE_ID + UF_DATE + UF_STATUS for fast occupancy queries.
Preventing Double Bookings
When two users try to book the same slot simultaneously, we use optimistic locking: before creating the record, the controller checks for overlaps and uses a DB transaction. If the slot is already taken, an error is returned, and the frontend updates the calendar.
Slots with status "Awaiting payment" are automatically cancelled after 15 minutes by an agent. This prevents popular meeting rooms from being blocked by unpaid reservations.
Space Catalog and Tariffs
An infoblock "Spaces" with sections by type: Hot desk, Fixed desk, Meeting room, Private office, Event hall. Properties: capacity, area, equipment, floor, photos, 3D tour (Matterport), minimum booking time.
The tariff structure is implemented through SKUs of the sale module. For example, the product "Hot desk" has offers: 1 hour, 1 day, 10 days/month, Unlimited/month. Subscriptions are processed as recurring payments with automatic expiration checks via an agent.
Access Control Integration
After payment, the system generates a unique UF_QR_TOKEN (UUID v4) and sends a QR code via email and in the personal account. When scanning the QR on the access control reader, the endpoint /api/skud/verify/ validates the token, status "Paid", and a ±15-minute time window. The protocol depends on the model: for ZKTeco or Sigur — REST API; for Bolid Orion — via an intermediate server.
Tenant Personal Account
Tabs: My bookings, Subscription, Visit history (check-in/check-out from access control), Favorites. For "Unlimited" subscriptions, the QR code is tied to the user for the entire period.
What's Included in Turnkey Development
- Project design: prototypes, Highload ER diagram, booking scenarios
- Design: mockups for catalog, calendar, personal account (mobile responsive)
- Development: infoblocks,
sale products, booking system, access control integration
- Fiscalization: connect online cash register (ATOL, CloudPayments) with data transfer to OFD
- Testing: load testing, booking conflict checks, access control scenarios
- Documentation: technical and user
- Training: admin instruction on managing catalog and bookings
Implementation Timeline
| Stage |
Content |
Timeline |
| Analysis |
Space catalog, tariff matrix, access control requirements |
5–7 days |
| Design |
Prototypes, ER diagram, booking scenarios |
7–10 days |
| Design |
Mockups (catalog, calendar, personal account), mobile responsive |
10–12 days |
| Catalog and tariffs |
Infoblocks, sale products, SKUs |
7–10 days |
| Booking system |
Highload, calendar, payment, conflict prevention |
14–18 days |
| Access control integration |
API endpoint, QR generation, testing with hardware |
7–10 days |
| Personal account and community |
Personal account, residents, events |
7–10 days |
| Testing and launch |
Load testing, access control commissioning |
5–7 days |
Total timeline: 9–12 weeks. Access control integration depends on the equipment model: if the system supports REST API out of the box, we finish within 7 days. If an intermediate server is needed, up to 10 days. The hardware must be installed before the integration stage begins.
Order a turnkey coworking website — we will audit your current processes and propose the optimal solution.
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.
