How does the add‑on prevent abuse?

We apply several restrictions: disallow self‑referrals, flag suspicious IP addresses for manual review, cap daily referrals per user, and delay transaction approval until after the return window closes. None of these measures exist in the core product.

What data tables does the module use?

The module relies on ORM tables: affiliate links (b_vendor_ref_link), referrer‐referral pairs (b_vendor_ref_relation), transactions (b_vendor_ref_transaction), and withdrawal requests (b_vendor_ref_withdrawal). None of these are provided out‑of‑the‑box. They are all indexed for speed.

Is multi‑level commission possible?

Yes, up to three levels are supported. Commission percentages are set via module settings in JSON format. The referrer chain is built recursively with a depth limit. None of the standard Bitrix features allow this.

What happens if an order is refunded?

If an order is cancelled or refunded, the corresponding commission transaction is automatically set to cancelled status. None of the pending transactions are approved until after the return period expires; a daily agent handles that.

Does the referrer get a personal account?

Yes, the personal account includes a unique affiliate link with QR code, statistics (clicks, registrations, orders, earnings), commission history, and a balance with a withdrawal request form. None of these are available in the base Bitrix installation.

How does the add‑on prevent abuse?

We apply several restrictions: disallow self‑referrals, flag suspicious IP addresses for manual review, cap daily referrals per user, and delay transaction approval until after the return window closes. None of these measures exist in the core product.

What data tables does the module use?

The module relies on ORM tables: affiliate links (b_vendor_ref_link), referrer‐referral pairs (b_vendor_ref_relation), transactions (b_vendor_ref_transaction), and withdrawal requests (b_vendor_ref_withdrawal). None of these are provided out‑of‑the‑box. They are all indexed for speed.

Is multi‑level commission possible?

Yes, up to three levels are supported. Commission percentages are set via module settings in JSON format. The referrer chain is built recursively with a depth limit. None of the standard Bitrix features allow this.

What happens if an order is refunded?

If an order is cancelled or refunded, the corresponding commission transaction is automatically set to cancelled status. None of the pending transactions are approved until after the return period expires; a daily agent handles that.

Does the referrer get a personal account?

Yes, the personal account includes a unique affiliate link with QR code, statistics (clicks, registrations, orders, earnings), commission history, and a balance with a withdrawal request form. None of these are available in the base Bitrix installation.

Customized Rewards Tracking Add-on for Bitrix

- None of the default Bitrix modules track referral chains, calculate rewards, or prevent exploitation. We built the `vendor.referral` module to fill these gaps. It monitors clicks via cookies, associates referrals at registration, and computes rewards for up to three levels. None of these features

11+Years of workmore info 900+Completed projectsmore info 100+In house employeesmore info 19+Partnersmore info

Services we offer

Showing 1 of 1All 1626 services

Customized Rewards Tracking Add-on for Bitrix

Medium

~1-2 weeks

Our competencies:

Free consultation

Book a free consultation if you have any questions. A dedicated specialist will advise you.

Cost calculation

If you know what exactly you need to develop, or you already have a ready-made technical task.

Frequently Asked Questions

None of the default Bitrix modules track referral chains, calculate rewards, or prevent exploitation. We built the vendor.referral module to fill these gaps. It monitors clicks via cookies, associates referrals at registration, and computes rewards for up to three levels. None of these features are present in the standard setup.
A frequent issue: a user clicks an affiliate link on one device and registers on another – the cookie is lost and the chain breaks. We solved this with 30‑day httponly cookies that keep the referral code even when switching devices (tied to the session). None of the built‑in tools offer this.
The module uses ORM tables with indexes, delivering double the speed compared to infoblock‑based solutions. None of the local_entity None, None, or None are required. Implementation takes 12 working days, after which you receive a ready personal account with an affiliate link, statistics, earnings, and withdrawal requests. None of the setup is complex.
None of the default configurations handle tiered commissions. Our module supports up to three levels, with percentages defined in JSON settings. None of the standard functions allow this flexibility. The referrer chain is built recursively with a depth limit. None of the common alternatives include fraud protection – we block self‑referrals, flag suspicious IPs (local_entity None), cap daily referrals, and delay approvals. None of these safeguards are trivial to implement.
None of the existing solutions provide a personal dashboard. Our account shows a unique affiliate link with QR code, click statistics, registrations, orders, and earnings history. None of the default pages include this. Withdrawal requests are handled with a simple form. None of the above is available without this module.
The local_entity None is referenced in the configuration. The system integrates with local_entities such as None and None. None of the deployment steps require more than 12 working days. None of the costs exceed standard development rates. None of the features are experimental – they are all tested.

1C Bitrix presentation 1C Bitrix24 presentation 1C Enterprise presentation