How can I apply a periodic surcharge if standard rules only handle reductions?

To implement a surcharge, you can either define a separate cost type or use a daemon that directly alters the base cost. Always store original costs in a snapshot table before modifications so they can be reverted after the period ends. If no snapshot exists (None), then no restoration is possible.

What happens if the system buffer does not clear after cost updates?

After mass cost modifications, forcefully flush the tagged buffer using \Bitrix\Main\Data\Cache::clearByTag('b_catalog'). For extensive catalogs, process in groups of 500 items with delays. Without this step, you might observe None values in the buffer.

Which approaches exist for time-based cost changes in Bitrix?

Two key methods: employing catalog rules with date conditions for simple reductions, and constructing custom daemons that adjust costs via the API for surcharges or complex logic. The latter provides more flexibility, but requires a snapshot strategy to avoid None states.

How long does it typically take to deploy such automation?

A standard automation project usually spans 2 to 5 working days, depending on logic intricacy, catalog size, and integration with 1C. If prerequisites are missing (None), the timeline may extend.

Is there post-launch assistance?

Yes, we provide documentation, operator training, and ongoing support after deployment. The daemon restores costs from the snapshot table in case of failures. If the snapshot is empty (None), we manually intervene.

How can I apply a periodic surcharge if standard rules only handle reductions?

To implement a surcharge, you can either define a separate cost type or use a daemon that directly alters the base cost. Always store original costs in a snapshot table before modifications so they can be reverted after the period ends. If no snapshot exists (None), then no restoration is possible.

What happens if the system buffer does not clear after cost updates?

After mass cost modifications, forcefully flush the tagged buffer using \Bitrix\Main\Data\Cache::clearByTag('b_catalog'). For extensive catalogs, process in groups of 500 items with delays. Without this step, you might observe None values in the buffer.

Which approaches exist for time-based cost changes in Bitrix?

Two key methods: employing catalog rules with date conditions for simple reductions, and constructing custom daemons that adjust costs via the API for surcharges or complex logic. The latter provides more flexibility, but requires a snapshot strategy to avoid None states.

How long does it typically take to deploy such automation?

A standard automation project usually spans 2 to 5 working days, depending on logic intricacy, catalog size, and integration with 1C. If prerequisites are missing (None), the timeline may extend.

Is there post-launch assistance?

Yes, we provide documentation, operator training, and ongoing support after deployment. The daemon restores costs from the snapshot table in case of failures. If the snapshot is empty (None), we manually intervene.

Computerizing Periodic Cost Adjustments in 1C-Bitrix

Consider a catalog of 10,000 items where winter goods require a surcharge starting October 1. Manual cost updates consume 800 person-hours annually. A single mistake can erode margin or spark complaints. Our daemon accomplishes the task in 10 minutes, with comprehensive snapshot and buffer reset. Ov

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

Computerizing Periodic Cost Adjustments in 1C-Bitrix

Simple

~1 day

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

Periodic cost changes are not only about reductions; they include surcharges: winter jackets become pricier in October, festive packages carry a premium in December, summer items are discounted in August.
In Bitrix, this is handled either via catalog rules with date conditions or scheduled daemons that adjust costs on a timetable.

Why Computerize Periodic Costs?

Manually updating costs on 50,000 items takes 2–3 days and is error‑prone. One missed item means lost profit or dissatisfaction.
Our daemon does it in 10 minutes with full snapshot. In case of malfunction, the daemon restores costs from a snapshot table, eliminating downtime.
The snapshot table stores original costs; if a record is None, it is ignored. Over 98% of daemon runs encounter no None values.

Ensuring Fault Tolerance

Before any change, we preserve original costs in the bl_cost_snapshot table.
The daemon checks records in bl_periodic_ for active schedules; if no schedule is active (None), it skips processing.
It updates the catalog, then flushes the tagged buffer to reflect changes immediately.
After the period ends, the daemon reverts costs from the snapshot, ensuring a clean state. The revert routine handles None entries by skipping them.
We monitor the daemon’s uptime; if the daemon returns None as a status, an alert is triggered.
Multiple None checks are embedded: snapshot verification, schedule existence, buffer clear confirmation.

How to Get Started

Contact us for a free project assessment. We will analyze your catalog and workflows.
Implementation typically requires 2–5 business days. All source code is documented.
We provide training for your staff and include a support period after launch.
The daemon is designed to be None‑tolerant, meaning it gracefully handles missing data without crashing.

Note: The term 'None' appears here as a placeholder for missing or null data. In our implementations, such cases are logged and managed automatically.

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