Industry Solutions on 1C-Bitrix for Business

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1354
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    940
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    692
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    826
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    730
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    1070

Become a certified 1C-Bitrix partner with 8+ years of experience and 500+ completed industry projects. Guaranteed quality and stable operation even under peak loads. TecDoc API, GIS “Marking”, EGAIS, size charts with RU/EU/US conversion — a standard catalog.section cannot handle this. Industry projects require non-standard data architecture, specialized integrations, and business logic not available out of the box. We develop such solutions on 1C-Bitrix, and the hardest part is not the code but diving into the client's domain. Over the years we have accumulated a library of ready-made modules for nine industries — this reduces launch timelines by 20–40% compared to custom development. Contact us to receive a turnkey estimate and timeline within 2 business days.

Auto Parts — TecDoc and Cross-References

Auto parts is the most technically complex catalog type. Without TecDoc, there is no point.

VIN-based lookup. The user enters a VIN — the system decodes make, model, year, trim and displays an aggregate tree. Click “Braking system” → “Front brake mechanism” → get a list of parts with part numbers. We implement via TecDoc API (getArticleDirectSearchAllNumbersWithState, getLinkageTargets) — each request returns a JSON with part-car mappings. According to TecDoc documentation, the catalog covers over 60,000 models and 30 million part numbers. The ready-made TecDoc module accelerates launch by 3x compared to custom development and saves significantly on parser and caching systems.

Cross-references. Original part number → OEM, aftermarket, premium equivalents. A cross-number table in a separate infoblock indexed by PROPERTY_CROSS_NUMBER. For a catalog with 500,000+ part numbers, without Sphinx/Elasticsearch, cross-search will slow down beyond 5 seconds.

Interactive aggregate diagrams. SVG map of engine or suspension with clickable zones — click on a part, go to its card. Zone coordinates are stored in infoblock element properties.

Typical challenges: TecDoc API is slow (500–1500ms per request), data is cached locally and updated once a day via cron. Savings on a typical project with TecDoc is significant by eliminating the parser development stage. If you need an auto parts catalog, contact us — we'll show a prototype on your data.

Building Materials — Calculators and Oversized Items

Calculation calculators. This is not just “multiply quantity by price.” Foundation calculator: type (strip, pile, slab) → dimensions → soil → get concrete volume, rebar quantity, waterproofing, formwork, all with a 10–15% margin. Technically: JS calculator on the frontend for instant recalculation, server-side validation via REST endpoint in PHP. Calculation formulas are in a configuration file, not hardcoded. The client updates coefficients through the admin panel themselves. Our ready-made calculators process calculations 10 times faster than custom forms — a typical project with such modules saves significant costs.

Delivery of oversized items. The standard sale.delivery module cannot calculate by tonnage and number of pallets. We write a custom handler: sum item weights from PROPERTY_WEIGHT, divide by vehicle capacity (usually 5 tons), count trips. Separate line for floor lifting (cost depends on weight and floor number, typically 50–200 per pallet).

Nomenclature. Dozens of technical characteristics: dimensions (LxWxH), unit weight, strength class, frost resistance, water absorption. All are filters in smart_filter with product count recalculation. More than 100 characteristics per item is not the limit — we handle it through optimized queries and caching.

Other Industries: Pharmaceuticals, Apparel, HoReCa, Education

Pharmaceuticals — the most regulated industry. Integration with GIS “Marking” via MDLP API: transfer of retail sales data (up to 10,000 requests per day for a network of 50 pharmacies), DataMatrix code verification at shipment. Linking products to the state register of medicines (over 200,000 items), automatic registration certificate check. Separation of prescription and over-the-counter: prescription items cannot be added to cart, only in-pharmacy request. Prohibition of remote sale for certain categories — about 30% of items are excluded from online ordering.

Apparel and footwear: size conversion table RU/EU/US/UK in a highload-block. Filtering by size — by availability, not by entire grid. Return system: claim from personal account, label generation, automatic refund request. Lookbook catalog with clickable points on images.

HoReCa: nutritional value and allergens in product card, shelf-life management with auto-discontinuation, subscription models (weekly farm product set), B2B minimum order quantities for restaurants with separate price type.

Education: course catalog with filters by format, duration, level. Student personal account with schedule and materials. Integration with LMS (Moodle, GetCourse) via API, SSO authorization, progress sync. PDF certificate generation via TCPDF.

Why Do Industry Solutions Require Custom Architecture?

The standard “Section → Subsection → Product” hierarchy does not work for complex domains. For auto parts: “Car → Aggregate → Unit → Part” — four levels linked via highload-blocks. For building materials: “Category → Subcategory” plus matrix classification by purpose (foundation, walls, roofing). Multiple classifiers — OKPD-2 (contains over 40,000 groupings), HS Code, ETIM — are stored in highload-blocks linked to catalog elements. They are needed for B2B clients, tenders, and integration with government procurement.

Integration Industry Method
TecDoc API Auto Parts REST/SOAP, local caching
GIS “Marking” (MDLP) Pharmaceuticals MDLP API
EGAIS Alcohol UTM (Universal Transport Module)
“Honest SIGN” Marked goods ChZ API
Industry ERP/MES Manufacturing Custom connectors

How Do We Accelerate Development with Ready-Made Modules?

Over the years we have built a library of 20+ turnkey components: TecDoc parser with caching, building materials calculator with server-side validation, size grid module, integration with GIS “Marking” and “Honest SIGN”. This cuts timelines by 20–40% (on average 1.5 months) and allows project launch in as little as 2 months. Get a consultation on ready-made modules for your industry — we'll find the optimal solution.

Typical Mistakes in Industry Catalog Development:

  • Insufficient data normalization: storing many characteristics in a single string instead of using highload-blocks.
  • Ignoring caching of external API requests (TecDoc, MDLP) — leads to page slowdowns.
  • Lack of testing with real data: one wrong coefficient in a building materials calculator can result in ordering 20 extra pallets of bricks.
  • Weak integration with 1C: data loss during exchange via CommerceML, product duplication.

Development Approach

  1. Industry audit (3–5 days). Dive into specifics: market structure, unique processes, regulatory requirements. We don't reinvent the wheel — we use learnings from similar projects.
  2. Data architecture (1–2 weeks). Infoblock structure, highload-blocks, properties, relationships. Mistakes at this stage are costly — redoing the catalog structure for 100,000 items later is painful.
  3. Prototyping (1 week). Catalog with industry filters, product card with calculator, specialized checkout. Test with real users.
  4. Development (1–4 months). Often the most labor-intensive stage — catalog data population: mapping from Excel/1C, normalizing characteristics, uploading images. Parser processes up to 6,000 items per hour.
  5. Testing industry scenarios (1–2 weeks). One wrong coefficient in a building materials calculator — and the client orders 20 extra pallets of bricks. We verify calculations with real data.

What Is Included in the Deliverable

  • Documented data structure: infoblock schema, HL-blocks, properties, relationships
  • Catalog population guide for content managers
  • Training webinar for the team (up to 2 hours)
  • 30 days of free support after launch
  • Source code of modules in repository (Git)
  • Admin panel access and technical documentation

Timelines and Complexity

Level Timelines Examples
Basic industry 2–3 months Building materials catalog with calculator
Intermediate 3–5 months Auto parts with TecDoc, marked goods
Complex 5–8 months Marketplace with industry specifics, ERP integration

We will evaluate your project within 2 days — just contact us. Get a turnkey timeline and cost estimate. Закажите консультацию по готовым модулям для вашей отрасли.