Product Photo Retouching & Processing for 1C-Bitrix Catalogs

Your product photo taken in a gray warehouse with lamp glare and dust on the packaging? The buyer won't linger — they're already scrolling. In online stores built on 1C-Bitrix, image quality directly impacts sales: according to statistics, products with professional photos show 30% higher conversion. Yet many catalogs suffer from inconsistency — different backgrounds, color shifts, non-standard sizes. Our team brings images up to commercial standards: defect-free, accurate color reproduction, and in the right formats for Bitrix.

We have been working with Bitrix catalogs for over 7 years. During this time, we have processed more than 100,000 images for 50+ satisfied clients. We know every detail: from selecting the color profile to configuring preview caching. Product card conversion depends more on the photo than on the text. We fix typical issues: incorrect white balance, background clutter, packaging defects, distorted colors. The result is images that drive sales. Savings of up to 30% when ordering a package of 500+ photos compared to per-image processing. Basic processing starts at $1 per image, with volume discounts available.

How to Process Photos for a Bitrix Catalog

Basic processing — applied to every photo:

• Exposure, contrast, saturation correction.
• Color shift elimination (correct white balance).
• Cropping and straightening horizontally and vertically.
• Sharpening and sensor noise reduction.
• Conversion to sRGB, export to JPEG with 80–85% quality.

Commercial retouching — in-depth work:

• Background removal (cutout) — replacement with white, transparent, or neutral.
• Removal of scratches, stains, surface defects.
• Shadow and reflection balancing.
• Correction of specific details (label color, metallic highlights).
• Adding realistic drop shadow under the product.

Three levels of cutout complexity:

The final file is saved as PNG with transparency for use on any background and as JPEG with a white background for the main catalog.

Why Color Correction Matters

The color on screen and the real product often differ. A shift of 3–5° in hue is noticeable to the buyer and causes returns, especially in the fashion segment. With our professional color correction, return rates can be reduced by up to 50%. Our standard workflow:

1. Use a Color Checker during shooting.
2. Profile the monitor with a colorimeter before processing.
3. Save in sRGB — the only profile correctly displayed in browsers without additional settings.

For fabrics and clothing, the shade must match the real material under daylight (D65). We achieve precise matching, reducing return rates.

Preparing Image Sets for Bitrix

For each product, we prepare a set of files compatible with Bitrix import:

product_1.jpg            – main photo (DETAIL_PICTURE)
product_1_s.jpg          – list preview (PREVIEW_PICTURE) — square 600×600
product_2.jpg            – different angle (gallery)
product_3.jpg            – details and texture
product_4.jpg            – context photo (lifestyle)
product_main_bg.png      – transparent background for promo banners

Square preview format is standard for listings: the card grid looks tidy. Size 600×600 or 800×800 is sufficient for retina displays and does not overload the page.

Batch Processing: Automating Routine

Part of the operations is automated to speed up processing of large batches and reduce cost. Automated batch processing is 5 times faster than manual, handling up to 500 photos per day per retoucher. We use Photoshop actions or Python scripts (Pillow). Retouching automation speeds up processing of large batches.

Example script for batch resizing and conversion:

from PIL import Image, ImageOps
import os

INPUT  = './raw'
OUTPUT = './ready'
TARGET = (2000, 2000)

for fname in os.listdir(INPUT):
    if not fname.lower().endswith(('.jpg', '.jpeg', '.png')):
        continue

    img = Image.open(os.path.join(INPUT, fname)).convert('RGB')
    img.thumbnail(TARGET, Image.LANCZOS)

    # Add white background for square preview
    bg = Image.new('RGB', TARGET, (255, 255, 255))
    offset = ((TARGET[0] - img.width) // 2, (TARGET[1] - img.height) // 2)
    bg.paste(img, offset)

    bg.save(os.path.join(OUTPUT, fname.replace('.png', '.jpg')),
            'JPEG', quality=83, optimize=True, progressive=True)

Manual control remains for complex retouching and non-standard objects. Automation does not replace the retoucher's experience but reduces time on routine tasks.

Typical Defects Removed During Retouching

• Folds and creases on clothing (natural ones are left untouched).
• Dust and hairs on glossy surfaces.
• Yellow spots on packaging from glue or transport.
• Uneven paint on metal parts.
• Shadows from studio equipment.
• Burned-out highlights on glass and metal.

What's Included in Photo Processing for the Catalog

After processing, you receive:

• Files with names ready for Bitrix import (DETAIL_PICTURE, PREVIEW_PICTURE, gallery).
• Versions on white and transparent backgrounds (JPEG + PNG).
• Square previews 600×600 pixels.
• Structured folders by product.
• If needed, a guide on uploading images to Bitrix.

All photos pass quality control: color check, sharpness, compliance with standards. We guarantee satisfaction with every batch. Contact us for a consultation — we will estimate timelines and cost.

Process

1. Source analysis and agreement on quality standards.
2. Sample processing of 5–10 photos for style approval.
3. Batch processing of the entire batch with intermediate checks.
4. Final cleanup and conversion.
5. Delivery of ready sets with names ready for Bitrix import.

Estimated Timelines

The cost is calculated individually — depends on complexity and volume. With over 7 years of experience and 100,000+ images processed, our team delivers professional-grade retouching that boosts conversion. Order processing of your photo batch turnkey. Write to us — we will evaluate your project.

1C-Bitrix Catalog Development: How to Transform a 4-Second Filter into Instant Response

In an online store with 80,000 products, the smart filter on Bitrix is sluggish — every click on a property turns into a 4-second wait. The customer clicks the 'Apple brand' checkbox, watches the spinning loader, and leaves for competitors. Conversion drops by 20%. This is a familiar pain. We specialize in 1C-Bitrix catalog development and filtering: we design architectures that handle half a million items without degradation — through faceted indexes, proper storage selection, and tagged caching. If your store is losing money due to a slow filter — order an audit of the current architecture, and we'll assess the problem in one day.

How Do Information Blocks Affect Catalog Performance?

Information blocks are the foundation of the catalog, but on projects with tens of thousands of products, they become a bottleneck. The standard bitrix:catalog.smart.filter generates JOINs on 6–8 property tables (b_iblock_element_property), leading MySQL into a full scan. We change the approach: during design, we determine which properties go into the information block and which into Highload blocks. For reference data (brands, cities, size charts) we use HLB: they work with a separate table without the overhead of b_iblock_element_property. When a 'Cities' dropdown loads for 8 seconds due to 5000 values — that's a signal to move them to HLB. A catalog of 80,000 products with a 4-second filter loses significant revenue annually due to customer attrition — the right architecture delivers that kind of savings. Contact us to estimate the benefit for your project.

What Is the Faceted Index and Why Is It Important?

The core performance lies here. Without a faceted index, every filter click is an SQL query with JOINs on b_iblock_element, b_iblock_element_property, b_catalog_price, and a few more tables. On 100,000 products, such a query takes 2–4 seconds. With a faceted index — 30–80 ms. According to official documentation, the faceted index reduces query execution time by tens of times (in real projects — up to 50 times). The mechanism: 1C-Bitrix creates a table b_catalog_smart_filter where it stores pre-calculated combinations of 'section + property + value + product count'. When filtering, the engine accesses this flat table instead of collecting data from the normalized structure of information blocks.

Common mistakes when configuring the faceted index include not creating the index for all sections, forgetting to set up background reindexing after bulk imports — causing property counters to mismatch the actual product count. Including all properties in the facet, even service ones, bloats the b_catalog_smart_filter table. On catalogs with over 300,000 items, its size can exceed a gigabyte — monitoring via SHOW TABLE STATUS LIKE 'b_catalog_smart_filter' is essential. Conclusion: the faceted index provides radical acceleration, but requires careful configuration and automatic reindexing via the agent CIBlockCatalog::ReindexFacet or cron.

Why Are Highload Blocks Faster Than Information Blocks for Reference Data?

In practice, the best architecture is hybrid. Products and sections live in information blocks — there you have SEO, visual editor, and standard catalog components. Reference properties with thousands of values are moved to Highload blocks. User data (favorites, viewed items, comparisons) also go to HLB — they grow quickly, and information blocks are not designed for that. Want to know which architecture to choose for your catalog? Contact us — we'll analyze your data structure and provide recommendations.

SEO Filters: How to Get SEO-Friendly URLs and Not Get Penalized by Yandex?

The standard filter generates ?filter[brand]=apple&filter[color]=black — search engines either do not index such URLs or consider them duplicates. But the query 'black apple laptops' is the most converting low-frequency traffic. We create SEO-friendly URLs: /catalog/laptops/brand-apple/color-black/ with unique title, description, and H1. Not template-based 'Buy {brand} in Minsk', but meaningful ones reflecting the specific combination.

• Canonical URLs — to prevent /brand-apple/color-black/ and /color-black/brand-apple/ from duplicating.
• Control of the number of indexed combinations — 10 properties with 20 values each yield millions of pages; Yandex penalizes that.
• Automatic sitemap for SEO filter pages.
• Admin interface for the manager — they decide which intersections to index.

Order the implementation of SEO filters — get a ready-made tool for attracting low-frequency traffic with conversion growth up to 30%.

What Methods Provide a Significant Performance Boost?

• Fetching only necessary fields via arSelect — no SELECT * on information blocks.
• Managed tag-based caching: when a product is added, the cache is automatically rebuilt.
• Composite cache for anonymous users: TTFB < 100 ms, HTML is served without running PHP.
• Indexes on properties used in filtering — without them MySQL scans the entire b_iblock_element_property table.
• TTFB monitoring: if the catalog responds slower than 500 ms, we check the slow query log.

What Is Included in Comprehensive Catalog Development on 1C-Bitrix

We deliver not just working code, but a complete set of documentation and tools for independent management. Deliverables include:

• Audit of current catalog and filtering architecture.
• Project documentation describing data schema, distribution across information blocks and Highload blocks, and facet composition.
• Ready smart filter with AJAX mode, grouping, and state persistence.
• Configured faceted index with cron reindexing.
• SEO filters with SEO-friendly URLs, unique meta tags, canonicals, and sitemap.
• Integration of quick view and sorting (AJAX, mobile adaptation).
• Operational documentation for managers: how to add properties, manage indexes and SEO combinations.
• 30-day warranty support after delivery — we fix incidents and answer questions.

How We Develop a Catalog: Step-by-Step Plan

We don't just install components. The process includes:

1. Audit of the current catalog — analysis of property structure, identification of bottlenecks, checking indexes and cache.
2. Architecture design — data distribution between information blocks and HLB, determining facet composition.
3. Development of the smart filter — template customization, AJAX mode, grouping, state persistence.
4. Faceted index configuration — creation, cron reindexing, monitoring.
5. SEO filters — SEO-friendly URLs, meta tags, canonicals, sitemap.
6. Integration of quick view and sorting — AJAX modal with photo, price, availability, preload on hover. On mobile — bottom sheet instead of popup.
7. Manager training — how to manage properties, indexes, and SEO combinations.
8. Warranty support — 30 days after delivery.

Implementation Timeline

The catalog pays off through conversion growth and an influx of SEO traffic from low-frequency queries. The customer finds the product in two clicks, rather than leaving after the first click on the filter. Get a consultation — we will evaluate your project within a day and provide a project plan and roadmap for 1C-Bitrix catalog development. Contact us through the form on the website — certified specialists with over 200 successful projects.