Setting up scheduled exchange in 1C and 1C-Bitrix

Configuring Scheduled Exchange Between 1C and 1C-Bitrix

Manual exchange initiation is a common cause of data discrepancies: the manager forgot to run it, ran it at the wrong time, or missed an error. Automatic scheduled exchange resolves these issues, but requires correct configuration in both systems.

Configuring the Schedule in 1C

In the Trade Management 10/11 configuration, the exchange is triggered by a scheduled job:

Administration → Scheduled and Background Jobs → Exchange with Website

Job parameters:

• Schedule: every N minutes, hourly, daily at a specified time
• User: the account under which the job runs (must have access to the website exchange)
• Retry on error: enable with a 5–10 minute delay

For stock and price uploads — an aggressive schedule (every 15–30 minutes). For a full catalog export — once nightly, at 2–4 AM.

Configuring Cron on the Site Side (if 1C initiates the exchange)

If the architecture requires the site to periodically request updates from 1C (REST API), use a Bitrix agent for scheduling:

Settings → Tools → Agents → Add Agent:

\MyProject\OneC\ExchangeAgent::run();

Interval: 900 seconds (15 minutes) for prices and stocks. The agent must run via real cron (/bitrix/modules/main/tools/cron_events.php), not via page hits — otherwise the exchange will not run overnight.

Execution Monitoring

Without monitoring, a configured schedule is useless — the exchange can break silently. Minimum monitoring:

• Log of the last exchange with a timestamp in a dedicated table
• Alert if no successful exchange has occurred for more than X hours
• Email/Telegram notification on errors

// Record the exchange result
\Bitrix\Main\Application::getConnection()->query(
    "INSERT INTO b_exchange_log (CREATED_AT, STATUS, DETAILS)
     VALUES (NOW(), '" . ($success ? 'OK' : 'ERROR') . "', '" . $details . "')"
);

Splitting Schedules by Data Type

Setup Timeline

Configuring automatic scheduled exchange with monitoring — 4–8 hours.