Introduction
A marketplace template for 1C-Bitrix rarely fits the business logic out of the box. Often you need not just cosmetic tweaks but deep customization: add blocks for store specifics, remove unnecessary sections, configure catalog filters, connect custom components. All this must be done without losing changes when vendor updates arrive. In such cases, we copy the template to /local/templates/ and work with the copy — this guarantees change preservation. Experienced developers with 10+ years in Bitrix projects handle template customization of any scope on time. Request a template audit — we'll evaluate the work in 1 day. Budget savings with this approach reach up to 40% compared to building from scratch.
How to Safely Customize a Template Without Losing Updates
The first and main step is to place the template in /local/templates/. If the template was purchased and resides in /bitrix/templates/, copy it entirely. The template structure is standard:
header.php — page header footer.php — page footer styles.css — main styles script.js — template scripts components/ — component templates images/ — template images page_templates/ — page templates Files in /local/templates/ are not overwritten by updates. Layout customizations are done in component templates — copy them from /bitrix/components/ to /local/templates/TEMPLATE_NAME/components/ and edit template.php. This allows changing HTML without touching the kernel. As noted in official 1C-Bitrix documentation, copying the template to /local/ is the safety standard.
Why Copying to /local/templates/ Is the Safety Standard
Because vendor updates only work with /bitrix/templates/. If you edit files directly there, every update will wipe your changes. Working with a copy gives you full control: your edits remain untouched, and updates can be selectively applied. In practice, this saves up to 40% on maintenance time. Average budget savings reach up to 40% compared to building a template from scratch.
Typical Customization Tasks
| Customization Type | What We Do | Timeline |
|---|---|---|
| Visual tweaks | Colors, fonts, logo, banners | 4–16 hours |
| Adding new blocks | Layout sections, integration with infoblocks | 1–3 days |
| Component templates | Copying, adapting to template style | 3–10 days |
| Deep rework | Redesign key pages, rewrite CSS | 2–4 weeks |
Case Study: Template Customization for an Online Store with 10,000 Products
One client — an online store with a catalog of 10,000 items — faced a typical problem: the purchased marketplace template did not support custom attribute filters, and product pages loaded in over 5 seconds. The vendor template was copied to /local/templates/. We rewrote the catalog component templates, implemented tagged caching, and optimized SQL queries to infoblocks. Additionally, we configured exchange with 1C via CommerceML for automatic stock updates. As a result, catalog page load time dropped to 1.2 seconds, and filters worked without page reload via Ajax. The project took 4 weeks, including testing.
Typical Mistakes When Customizing a Template and How to Avoid Them
One common mistake is editing files directly in /bitrix/templates/. Each vendor update will overwrite these changes. The solution is to always work with a copy in /local/templates/. Another mistake is overriding component templates without preserving the original logic. Copy files to /local/templates/your_template/components/ and modify only what is needed. A third mistake is ignoring caching: when adding new blocks, remember to flush the tagged cache so changes appear.
More about copying the template
Copy via admin panel: "Settings" → "Product Settings" → "Sites" → select the template and click "Copy". Via FTP: copy the folder from /bitrix/templates/ to /local/templates/. Ensure that the .settings.php file references the template from /local/.
What's Included in the Work
| Stage | Result |
|---|---|
| Template audit | Customization plan with scope estimate |
| Copy to /local/ | Safe environment for edits |
| Modify component templates | Adapted interface |
| Configure caching | Faster page loads |
| Testing | Responsiveness, cross-browser compatibility, performance |
| Handover documentation and access | Maintenance instructions |
| Update recommendations | How to safely apply vendor patches |
Work Process: From Analysis to Deployment
- Template audit — check compatibility, outdated practices, scope of work.
- Design — choose strategy: partial tweaks or page rework.
- Implementation — layout, integration with infoblocks, caching setup, tagged cache.
- Testing — responsiveness, cross-browser, load speed.
- Deployment — push to production, handover access and documentation.
What's Next?
Customization of a marketplace template is on average 3 times faster and 40% cheaper than designing from scratch. We work with any template — from simple landing pages to catalogs with 10,000 products. Our track record: over 80 successful projects. Get a consultation from an engineer: contact us to evaluate your template.