Setting Up a Ready-Made Online Store from 1C-Bitrix Marketplace
The 1C-Bitrix Marketplace contains hundreds of ready-made solutions for online stores. Installing a template takes fifteen minutes. But bringing it to working condition without module conflicts and performance degradation is a task requiring understanding of the platform's internal workings.
How to Choose a Solution and Not Regret It
Every solution on 1C-Bitrix Marketplace has a card with rating, installation count, and last update date. Focus on three parameters:
- Last update date — if solution hasn't been updated in 6+ months, the developer likely abandoned it. This is critical because Bitrix core updates regularly, and old code starts conflicting.
-
Edition compatibility — a solution for "Business" won't install on "Startup". Check the "Required edition" field in card. If you have "Small Business" but solution requires extended
salemodule — cart functionality will work partially. - Install count vs rating — 10,000 installs with 3.2 rating is worse than 800 installs with 4.8 rating. Massive solutions often overloaded with universal code.
Before purchasing, deploy a demo version. Most partners offer 30-day trial periods. Check catalog load speed with 500+ products — this is where architecture problems show.
Installation and Basic Configuration
Installation is done through admin panel: Marketplace → Solution Catalog → Install. System downloads archive, unpacks to /bitrix/templates/ and /local/templates/, registers components.
After installation:
- Activate template in Settings → Site Templates for needed site
- Go through solution setup wizard (if available) — it will set basic parameters: logo, colors, contacts, catalog structure
- Check what modules solution installed additionally — often pulls in composite modules, CDN, push notification modules
Pay attention to template path. Solutions can install to /bitrix/templates/ or /local/templates/. Second option is preferable — it won't be overwritten on core update.
Template Customization
Ready-made solution never fits 100%. Customization affects three levels:
Styles — template_styles.css. Located in template root. This is where colors, fonts, spacing change. Don't edit directly — create custom.css file and connect via header.php, so solution update doesn't wipe changes.
Component logic — result_modifier.php. Each component (catalog.section, sale.basket.basket) has template in /templates/.default/. File result_modifier.php allows modifying $arResult array before output in template.php. This is standard mechanism — use it instead of editing component.php.
Output structure — template.php. If you need to remark up a block, copy component template to site template (/local/templates/your_template/components/bitrix/catalog.section/.default/) and edit the copy. Original stays untouched.
Pitfalls
Module conflicts. Ready-made solution can install its own cart or filter module conflicting with standard catalog.smart.filter. Symptoms — white screen when accessing catalog or errors in bitrix/modules/. Check logs in /bitrix/logs/ and disable conflicting module via CLI:
php bitrix/modules/main/cli/bootstrap.php module:disable vendor.module
Performance. Many marketplace solutions pull 15-20 CSS and JS files unminified. Enable combining and compression in main module settings: Settings → Module Settings → Main Module → CSS/JS Optimization. For composite cache — activate "Composite Site" technology in Settings → Composite Site.
Updates. When updating solution through Marketplace, template files are overwritten. Everything you edited in original files — disappears. Rule: customize only via component template copies and separate CSS files. Before updating, backup via bitrix/backup.php or hosting tools.
License restrictions. Some solutions include encrypted files (Bitrix Framework Encoded). They can't be edited. If logic is hardcoded in such file — you're limited to parameters exposed in settings.
What to Check After Launch
Check site via built-in Performance Monitor tool (Settings → Performance → Performance Panel). Score below 30 with 500 products — reason to reconsider solution or optimize server environment. Make sure opcache is enabled and opcache.revalidate_freq set to 60 for production.
Ready-made solution from marketplace is foundation, not final product. Customization volume depends on business logic complexity, but basic action set — moving styles to separate file, copying component templates, and checking performance — is mandatory in every project.