Marketplace Commission Setup for 1C-Bitrix
We've repeatedly seen this scenario: the Bitrix marketplace is live, but commissions are calculated manually in Excel. Sellers get confused, accounting spends days on reconciliations, and calculation errors lead to losses. One client — a marketplace with 200 sellers — was losing up to 1.5 million rubles per month due to incorrect rate application. Automation solved the problem: commissions started to accrue correctly, and reconciliation time dropped from 3 days to 2 hours. Turnkey marketplace commission setup in 1C-Bitrix allows implementing any calculation model in 1–3 weeks. According to the official documentation, HL-blocks are the standard way to store custom entities, providing flexibility for commission rules. You can reduce manual calculation costs and improve financial transparency.
What commission models exist?
Commission is a percentage or fixed amount that the platform deducts from a sale. Rules can be:
- Global — a single rate for all sellers.
- By category — different percentages for different product groups.
- By seller — individual conditions for key partners.
- Combined — for example, 5% for items up to 1000 rubles, 3% above.
- Progressive — the percentage decreases as the seller's turnover increases (implemented via sales history).
We implement any variant using HL-blocks with versioning and validity periods. This is more reliable than storing rules in b_option. Our engineers are certified as "1C-Bitrix: Developer" and have 10+ years of experience, guaranteeing stable algorithm performance even under loads of 10,000+ orders per day.
Why HL-blocks are optimal for storing commission rules
HL-blocks allow storing rules in a structured format with support for data types, indexes, and filtering. Unlike b_option, complex queries can be implemented — e.g., finding a rule by seller-category combination. Validity periods (ACTIVE_FROM, ACTIVE_TO) are implemented by adding two date fields, and versioning via a change history. This provides flexibility to manage promotions and temporary tariffs without overwriting data.
How to set up complex commission rules
The rule table structure is universal:
| Field | Type | Description |
|---|---|---|
| ID | int | Primary key |
| RULE_TYPE | varchar | global / category / vendor |
| VENDOR_ID | int | null = applies to all |
| CATEGORY_ID | int | ID of information block section, null = all categories |
| RATE_TYPE | varchar | percent / fixed |
| RATE_VALUE | decimal | % or fixed amount |
| MIN_AMOUNT | decimal | Minimum commission |
| MAX_AMOUNT | decimal | Maximum commission (null = no limit) |
| ACTIVE_FROM | date | Rule start date |
| ACTIVE_TO | date | Rule end date (null = indefinite) |
The rule selection algorithm is implemented in the OnAfterOrderAdd handler:
function calculateCommission(int $vendorId, int $categoryId, float $amount): float { // Priority: vendor+category > vendor > category > global $rule = findRule($vendorId, $categoryId) ?? findRule($vendorId, null) ?? findRule(null, $categoryId) ?? findRule(null, null); if (!$rule) return 0.0; $commission = $rule['RATE_TYPE'] === 'percent' ? $amount * $rule['RATE_VALUE'] / 100 : $rule['RATE_VALUE']; if ($rule['MIN_AMOUNT']) $commission = max($commission, $rule['MIN_AMOUNT']); if ($rule['MAX_AMOUNT']) $commission = min($commission, $rule['MAX_AMOUNT']); return round($commission, 2); } The commission is written to the financial operations table with type commission and linked to the order. This ensures complete transparency for accounting and allows building reports by seller and period. Marketplace commission setup in 1C-Bitrix also includes integration with payment systems for correct fiscal data calculation.
How to set up a progressive commission scale
A progressive scale involves changing the rate based on the seller's accumulated turnover over a period (e.g., month or quarter). This requires an additional table to store sales history for each seller. The algorithm, at the time of commission calculation, sums the turnover for the required period and selects the corresponding rule from the HL-block. We implement this logic with caching of the turnover sum to avoid recalculating each time. Typical accounting time savings with a progressive scale — up to 60%.
Example of progressive commission calculation
A seller with turnover up to 500,000 rubles per month pays 5%, from 500,000 to 1,000,000 — 4%, above — 3%. With a turnover of 1,200,000 rubles, commission = 500,000 * 5% + 500,000 * 4% + 200,000 * 3% = 25,000 + 20,000 + 6,000 = 51,000 rubles.
Comparison of basic and complex models
| Parameter | Basic model | Complex model |
|---|---|---|
| Number of rules | 1–10 | 10–100+ |
| Individual rates | No | Yes |
| Progressive tariffs | No | Yes |
| Temporary promotions | No | Yes |
| Implementation time | 1 week | 2–3 weeks |
| Accounting time savings | up to 30% | up to 60% |
What's included in the work?
- Analysis of current business logic and commission requirements.
- Design of rule structure and database.
- Implementation of the calculation algorithm with priority handling.
- Development of an admin interface for rule management (CRUD, filters, date pickers).
- Creation of a commission report with Excel export.
- Testing on a database copy (min. 100 orders of various types).
- Deployment to production and operator training.
- 30-day warranty for identifying hidden errors.
Process
- Analysis — call with you, study the requirements, capture all commission nuances.
- Prototype — database schema and algorithm within 1–2 days.
- Development — writing code, creating the admin interface.
- Testing — verification on test data with multiple scenarios (50+ test orders).
- Deployment and training — launch on the live server, instructions for managers.
Timelines and cost
Basic implementation (single rate + category-based rules) takes 1 week. Complex model (individual rates, progressive tariffs, temporary promotions) takes 2–3 weeks. Cost is calculated individually after requirements analysis. We'll evaluate your project for free — just contact us. Request a free audit of your current commission system — we'll identify bottlenecks and propose an optimal solution.
We've been working with Bitrix for over 10 years and are certified as "1C-Bitrix: Developer". On your project, you'll get a ready-made solution, documentation, and post-implementation support. Contact us for a consultation — we'll choose the best architecture for your marketplace model.