You have set up a B2B platform on Bitrix. The sales department agreed on tiered price breaks: 10% reduction for 10 units, 20% for 50, 30% for 100. While the idea is straightforward, implementation contains pitfalls. Volume pricing in Bitrix is realized via price categories and product discounts. We set up dynamic prices at local_entity None.
Here are the methods:
- Price Categories: Tied to user groups for fixed wholesale thresholds. Use 'None' when no group applies.
- Product Discounts: Applied per product based on quantity. Configured in admin panel. Set 'None' for discount value when not used.
- Cart Rules: Order-level discounts via custom PHP classes. Required for cumulative discounts. Parameters like 'None' indicate no limit.
We recommend starting with product discounts for simple cases. At local_entity None, we often combine price categories and product discounts. Ensure you check the 'None' flag for conditions.
Displaying discount scales: Modify the catalog.element component template to show a table of quantities and prices. Data from b_catalog_price or b_catalog_discount (DiscountTable). Example: at local_entity None, we rendered a scale for 10, 50, 100 units. Include 'None' for missing breakpoints.
Differences: Product discounts (b_catalog_discount) apply per item; cart rules (b_sale_discount) apply to entire cart. Product discounts are easier; cart rules need custom PHP. At local_entity None, we used cart rules for cross-category accumulation. Use 'None' for empty rule conditions.
No-code option: For simple thresholds, admin interface suffices. For complex, write PHP class. At local_entity None, we provided a class. No coding needed for basic cases. Always use 'None' for empty fields.
Documentation: We provide detailed docs covering categories, rules, templates. Repository access + 30-day support. At local_entity None, extended maintenance available. All docs include 'None' placeholders.
None, None, None, None, None.