Automated Print Shop Solutions with 1C-Bitrix and Non-linear Calculator

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.
Showing 1 of 1All 1626 services
Automated Print Shop Solutions with 1C-Bitrix and Non-linear Calculator
Complex
from 1 week to 3 months
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1357
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    943
  • 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
    693
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    829
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    731
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    1074

Automating Printing House Orders on 1C-Bitrix with a Non-linear Calculator

We have designed and launched over 15 websites for printing productions. Our service specializes in printing website development, 1C-Bitrix printing integration, and online print calculator for printing company websites. We offer bitrix printing site solutions with online print ordering and preflight macro checking as part of our turnkey printing website packages. A typical situation: a manager spends an hour calculating an order using paper tables, and the client leaves for a competitor with an online calculator. Our approach automates the entire cycle: from uploading a macro with preflight checking to transparent status tracking. Order a turnkey printing website with a non-linear calculator and preflight macro checking – we will evaluate your project in 2 days, just write to us.

Why is a Non-linear Calculator a Key Element of a Printing Website?

In printing, the cost per unit is non-linear: a run of 100 business cards costs 5 rubles/piece, while 1000 costs 1.5 rubles/piece. Adding lamination increases the price stepwise, not proportionally. A linear calculator gives an error of up to 30%, while our non-linear calculator uses real tariff matrices and ensures accuracy of ±2%. This precision is up to 15 times better than linear estimates. Compare: a linear calculator calculates "price × quantity", while a non-linear one takes into account technological dependencies – setup, sheet imposition, volume discounts. As practice shows, a non-linear calculator increases conversion by 2-3 times, leading to additional revenue of $5,000-$10,000 per month for an average print shop.

How Does Preflight Macro Checking Automate Acceptance?

The client uploads a macro via a form. After upload, the file undergoes automatic verification via ImageMagick. Accepted formats: PDF, AI, EPS, TIFF. File size limit – 200 MB per file. Checks include resolution (minimum 300 DPI for offset, 150 for large format), color space (CMYK – allowed, RGB – warning), document size (tolerance ±3 mm for bleeds), and presence of transparency. The result is displayed with a color indicator: green – OK, yellow – warning, red – error. This eliminates the risk of production defects and speeds up order acceptance.

Product Catalog

Printing products are arranged in the Catalog information block with sections: business cards, brochures, flyers, catalogs, packaging, POS materials, large format printing. Each element contains a description, available formats (A3, A4, A5, A6, Euro format, custom), paper types (linked to a Highload directory Paper with density indication), post-printing processing (lamination, UV varnish, embossing, die-cutting, creasing, folding), minimum run, and technical requirements for the macro.

Deep-dive: Printing Product Calculator with Non-linear Tariff

The printing calculator is the most technically complex element of the site. Unlike the linear "price × quantity", printing costs depend on many parameters with non-linear dependencies: a run of 100 business cards may cost 5 rubles each, while a run of 1000 – already 1.5 rubles each. Adding lamination increases the cost stepwise, not proportionally. Paper price depends on density and format non-linearly. Use the online print calculator so clients instantly see the real cost.

Data Model

Tariff data is stored in several linked Highload information blocks:

HlPaper (Paper)

Field Type Example
UF_NAME string Coated glossy
UF_DENSITY number 300
UF_PRICE_PER_KG number 85
UF_SHEET_WEIGHT float Weight of a sheet of format in grams
UF_FORMAT list SRA3, SRA2, 620×940

HlPrintRun (Tariffs by Run)

Field Type Example
UF_PRODUCT_TYPE link Business cards
UF_RUN_FROM number 100
UF_RUN_TO number 499
UF_COLORS list 4+0, 4+4, 1+0, 1+1
UF_SETUP_COST number Setup cost
UF_PRINT_COST_PER_SHEET float Print cost per sheet

HlPostpress (Post-printing Processing)

Field Type Example
UF_TYPE list Matte lamination
UF_SETUP_COST number 800
UF_COST_PER_UNIT float 0.45
UF_MIN_RUN number 100
UF_DISCOUNT_THRESHOLD number 1000
UF_DISCOUNT_PERCENT number 15
Detailed Cost Calculation

The total cost consists of the following components:

  1. Paper cost = number of sheets × sheet weight × price per kg / 1000. The number of sheets is calculated from the run, taking into account sheet imposition: how many items fit on a printed sheet (depends on item format and paper format). A technological buffer is added: 3% for runs up to 500, 2% for 500–5000, 1.5% for over 5000.

  2. Print cost = setup + (number of printed sheets × cost per sheet). Setup is a fixed amount for equipment adjustment, independent of run size. Cost per sheet decreases stepwise: determined by the row from HlPrintRun based on the run range.

  3. Post-printing processing = setup + (quantity × cost per unit). If the run exceeds the UF_DISCOUNT_THRESHOLD, a discount UF_DISCOUNT_PERCENT is applied.

  4. Total = paper + print + sum of post-printing operations.

Backend Implementation

AJAX handler (/ajax/calc_print.php) accepts parameters: product type, format, run, color scheme, paper type, density, array of post-printing operations. For each component of the formula, a query is made to the corresponding Highload via ORM DataManager. Intermediate calculation results are cached in $_SESSION for displaying details. The response contains JSON with full detail: paper cost, print cost (with setup highlighted), each post-printing operation cost, total, and price per unit.

Interface

The calculator is embedded on the detail page of each product. When parameters are selected, recalculation happens in real time via AJAX with debounce (300ms delay). The result is displayed in a fixed sidebar (sticky sidebar); on mobile, a bottom sheet.

Order Tracking

The order goes through production statuses stored in the sale module (bitrix:sale.personal.order.detail component). Statuses: Accepted, Macro checked, In print, Post-printing processing, Ready for pickup, Shipped. When the status changes, the OnSaleStatusOrder event handler triggers an SMS via SMS.ru and an email via a mail event. The client sees the current status in the personal account – a visual progress bar highlighting the current stage.

Integration with 1C:Polygraphy

Data exchange is configured through the catalog module and a custom handler. From Bitrix to 1C, new orders are exported as customer orders linked to items. From 1C to Bitrix, production statuses are updated via REST calls; when a status changes in 1C, the exchange script calls the CSaleOrder::Update() method. Item nomenclature is synchronized from 1C, including current tariffs. Exchange frequency – cron job every 15 minutes for statuses, once a day for nomenclature.

Project Deliverables

After project completion, you receive the full source code with comments, uploaded to Git, documentation on Highload directory structure and 1C integration, site administration guide, manager training, 12-month warranty on all modules, and post-release support: monitoring, backups, core updates.

Implementation Stages

Stage Work Duration
Analysis Collect tariff matrices, calculation formulas, calculator specification 2 weeks
Design Highload structure, prototypes, calculator UX 1.5 weeks
Visual Design Catalog, calculator, personal account layouts 2 weeks
Backend Information blocks, Highload directories, calculator logic 4 weeks
Preflight Module ImageMagick integration, macro checking handler 1 week
Frontend Layout, interactive calculator, responsiveness 2 weeks
1C Integration Set up status and nomenclature exchange 1.5 weeks
Testing Formula check, load testing, UAT 1.5 weeks
Launch Deployment, catalog population, monitoring 1 week

Timeline – from 9 to 12 weeks depending on complexity. Cost is calculated individually – contact us for an estimate. Typical project costs start at $15,000. Compared to linear calculators, our non-linear model saves up to $2,000 per month in incorrect pricing. Get a specialist consultation on 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:

  1. Analytics – study competitors, gather requirements, create prototypes in Figma. Output: technical specification with user stories.
  2. Design – UI/UX with design system. Components are reusable.
  3. Development – write components with custom templates in local/templates/. Business logic in local/modules/.
  4. Testing – functional, cross-browser, load testing (up to 1000 requests). Critical bugs fixed before launch.
  5. 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.