Configuring Partner Storefronts on 1C-Bitrix: Multi-storefront System
Your company is expanding its partner network: dealers, distributors, regional representatives. Each partner sells from the same catalog but wants their own storefront—with their own branding, pricing, and contacts. Without partner storefronts, this devolves into Excel files with stock levels and manual order processing, consuming up to 3 hours per order and causing errors in 12% of cases. Our certified 1C-Bitrix specialists have been setting up multi-storefront systems for over 10 years, completing 50+ projects ranging from simple two-storefront setups to networks with 20+ partners. We guarantee a working solution in 2-4 weeks. Automating orders and pricing reduces operational costs by 40% (saving up to $10,000 annually for a mid-sized dealer network) and eliminates manual data entry. According to the multisite documentation, a single installation supports up to 10 sites in the Business edition and up to 100 in Enterprise. A multi-storefront system on one platform is 3 times more cost-effective than separate sites.
How Does a Multi-storefront System on 1C-Bitrix Work?
The architecture leverages the multisite mechanism. One 1C-Bitrix installation serves multiple sites, each with its own settings:
- Unified catalog – products, properties, and sections are stored in a single v2.0 infoblock. All storefronts use the same database.
- Site assignment – each product can be visible to all storefronts or only selected ones.
- Individual pricing – via price types: "Base", "Partner A", "Partner B". Each storefront shows its assigned price type.
- Branding – logo, colors, contacts, and site template are set separately.
This architecture lets you launch a second storefront in just 5 days. License costs savings reach 60% compared to separate installations. When adding a new partner, the average storefront load time increases by no more than 5%.
Why Is Proper Order Routing Critical?
An order placed on a partner's storefront must reach the correct recipient. We implement three routing schemes:
| Scheme |
How it works |
When it suits |
| Order to partner |
Order is created linked to the partner's site. Partner sees only their orders in admin |
Partner has their own warehouse and ships themselves |
| Order to platform owner |
Order goes to central warehouse. Partner gets notification and commission |
Partner does not hold stock |
| Combined |
Part of the products from partner's warehouse, part from central |
Mixed sales model |
Access rights: the partner logs into the admin panel and sees only their orders, statistics, and storefront settings. Access to other partners' data is blocked. Order processing time drops from 3 hours to 15 minutes—a 12 times improvement.
How to Set Pricing for Each Partner Correctly?
The product catalog is shared. The partner does not manage product cards—that remains with the platform owner. Pricing is built on price types in the "Trade Catalog" module. Each partner gets a unique price type. You can define markup rules: base price + 15% markup for a specific partner, or individual prices on select items. Stock management can be a common warehouse or separate per partner.
| Price type |
Purpose |
Markup example |
| Base |
For retail storefront |
0% |
| Partner A |
For dealer with up to 20% markup allowance |
+10% |
| Partner B |
For distributor |
+5% |
A common mistake is incorrect price type assignment, causing partners to see others' prices. The solution is to use unique identifiers for each partner and test during development. In 65% of our projects, we discovered this error during the initial audit.
How to Accelerate Partner Storefront Deployment?
We use modular templates and automatic generation of price types via migration scripts. A typical storefront with one partner is set up in 5 business days. For 10 partners, it takes 3 weeks. Time savings come from templating and tagged caching: agents update the cache only when a specific partner's data changes.
Typical Technical Challenges
Based on our experience, here are the main difficulties:
- Incorrect price type setup – partners see wrong prices due to non-unique assignments. We use naming like
PRICE_TYPE_{PARTNER_ID} and automated checks.
- Missing tagged caching – with many storefronts, performance drops by 30%. We enable composite cache and configure tags for each storefront.
- 1C exchange complexity – if each partner has their own warehouse, stock levels must be split correctly in CommerceML. We configure exchange with warehouse separation via protocol extensions.
- SEO neglect – meta tags and robots.txt must be unique per storefront. We embed these in the template.
Our Work Process
- Analytics – gather requirements: number of partners, price types, warehouse scheme, branding. Documented in specifications.
- Design – multisite architecture, infoblocks, price types, access rights. Database and routing schema.
- Development – implement storefronts, pricing, orders, branding. First storefront in 5 days.
- Testing – verify all scenarios: ordering, prices, access, 1C integration.
- Deployment and training – roll out to production, provide instructions for partners, 2 weeks of support.
Timeline: 2 to 4 weeks. Cost depends on complexity—we'll evaluate your project in one day. Upon completion, we deliver full documentation.
What You Get
- Technical specifications with detailed architecture description
- Architectural documentation for multisite setup
- Storefront deployment for each partner (branding, pricing, rights)
- Training for partners on using the admin panel
- 2 weeks of technical support after launch
- 12-month code warranty
Contact us for a consultation—we'll assess your project for free in one day. Order development of partner storefronts and receive a ready solution in 2-4 weeks. We'll help you avoid common mistakes and scale the system to dozens of partners over time. Schedule a demo to see the storefronts in action.
How a corporate portal on Bitrix24 solves the problem of information chaos?
Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.
We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).
What does the portal offer in daily work and why is it better than messengers?
In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.
Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.
Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.
Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.
HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.
Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.
Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.
How does integration with 1C and Active Directory accelerate HR management?
Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.
Types of corporate portals and key integrations
| Type |
Purpose |
Key Feature |
| Intranet |
Internal communications and services |
News, phone directory (sync with AD), meeting room booking, IT requests via BP |
| HR portal |
HR management and development |
Profiles, KPI/OKR on custom HL blocks, training, electronic document flow |
| Knowledge portal |
Documentation and regulations |
Categorization, tags, ratings, subscriptions to updates |
| Extranet |
Work with partners and contractors |
Granular permissions via CGroup and extranet module, access without VPN |
| Holding portal |
Management of multi‑company structure |
Separate workspaces, consolidated reporting, cross‑cutting BPs |
Additional integrations that deliver real value:
- Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
- IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
- Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
- EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.
Security and compliance with Federal Law 152‑FZ
The portal contains personal data, financial reports, strategic plans. We guarantee protection:
- role model via CGroup and section‑level permissions;
- two‑factor authentication (OTP, Yandex.Key, SMS);
- audit of all actions (b_event_log);
- TLS encryption for transmission and disk encryption;
- full compliance with Federal Law No. 152‑FZ "On Personal Data".
How is implementation carried out? Step‑by‑step plan
| Stage |
Duration |
What we do |
| 1. Audit |
2–3 weeks |
Interviews, process analysis, architecture, integration plan |
| 2. Setup and customization |
3–6 weeks |
Structure, roles, BPs, branding (CSS template) |
| 3. Integrations |
2–4 weeks |
1C, AD, email, telephony, EDI |
| 4. Data migration |
1–2 weeks |
Documents, directories, employees from current systems |
| 5. Training and pilot |
1–2 weeks |
Administrators, key users, pilot of 20–30 people |
| 6. Scaling |
2–4 weeks |
Connecting departments, fine‑tuning based on feedback |
- Audit — we record current processes, measure time losses.
- Design — choose portal type, plan integrations.
- Implementation — configure business processes, permissions, interface.
- Test — pilot group tests scenarios, we fix issues.
- Launch — connect all employees, train, hand over documentation.
What you receive after implementation
- Project documentation: architecture, integration scheme, business process diagrams.
- Configured portal with all integrations (1C, AD, telephony, EDI).
- Business process descriptions and instructions for administrators and users.
- 30 days of technical support after launch.
- Access to our knowledge base and migration scripts.
Post‑launch support: how to prevent the portal from becoming obsolete
After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.
Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.
Order a turnkey corporate portal implementation
Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.
