We specialize in configuring automated data exchange between 1C:UT 10 and Bitrix sites. UT 10, though still widely used, presents specific challenges: profile settings are buried deeper, support for item characteristics is limited, and scheduled jobs are absent. A typical situation: a product catalog of 50 thousand items, each with 6 colors — characteristics fail to export because UT 10 has no built-in mechanism for variants. We have learned to work around these limitations.
Clients often face problems: orders from the site are not created in 1C, prices are not updated, or exchange runs only when the database is open. Our goal is to make synchronization automatic and error-free. To achieve this, we use external processing, Windows Task Scheduler, and, if necessary, modify the UT 10 configuration.
Automating exchange without manual startup
For automatic exchange from UT 10, an external processing file RunExchange.epf is required, launched via Windows Task Scheduler. Here is an example batch file:
REM File run_exchange.bat "C:\Program Files\1cv8\common\1cestart.exe" ENTERPRISE /S "SERVER\DATABASE" /N "admin" /P "password" /Execute "C:\scripts\RunExchange.epf" The processing performs exchange using the CommerceML protocol and closes the session. The scheduler runs the batch file on a schedule — for example, every hour. This approach is 3–5 times more reliable than manual startup and eliminates human error. Automated exchange is also 5 times more accurate than manual data entry.
What does exchange automation provide?
Automated synchronization saves employee time and eliminates manual entry errors. Where previously a manager had to log into 1C daily, start the export, and wait, now everything happens on a schedule without human involvement. Additionally, it improves data timeliness on the site — prices and stock levels are updated every hour instead of once a day. Based on our estimates, automation reduces exchange errors by 80%.
Location of exchange settings in UT 10
Services → Data exchange → Exchange with site (Bitrix)
If the menu item is missing — the configuration has been modified or the feature is disabled. To enable:
Services → Accounting parameters setup → Additional → Use exchange with site
Differences from UT 11 in exchange setup
| Parameter | UT 10 | UT 11 (and higher) |
|---|---|---|
| Exchange trigger | Only when 1C is open, needs scheduler | Built-in scheduled jobs |
| Characteristics | Limited, often require series | Full support for trade offers |
| REST API | No | Built-in HTTP services |
| Order statuses | New, In Progress, Completed, Canceled | Extended, flexible mapping |
| Exchange format | File-based only | File-based + REST |
Item characteristics. In UT 10, characteristics are poorly implemented. To transfer product variants (color/size), configuration modification or using series instead of characteristics may be necessary. In one project, we encountered a catalog of 50,000 items, each with 6 colors — we had to rework the series mechanism to export all variants.
Orders. In UT 10, orders from the site are created as documents "Customer order" (reference from the sales management subsystem). Order statuses — "New", "In Progress", "Completed", "Canceled". Mapping with Bitrix is straightforward.
Exchange schedule. UT 10 works only in file mode (thick client). Scheduled jobs only run when 1C is open. For automatic exchange without human involvement, a separate 1C session must be set up on the server.
Stages of UT 10 exchange setup
| Stage | Duration | Description |
|---|---|---|
| Analysis | 2–4 hours | Study the UT 10 configuration, catalog structure, requirements |
| Design | 1–2 hours | Determine exchange format, profile, needed modifications |
| Implementation | 4–8 hours | Set up profile, modify 1C, automate via scheduler |
| Testing | 2–4 hours | Check synchronization on a test catalog, fix errors |
| Deployment | 1–2 hours | Deploy to production, hand over documentation |
What's included in the exchange setup service
- Creating an exchange profile: site address, handler URL, authorization
- Modifying UT 10 configuration (if needed for characteristics, series, additional documents)
- Implementing automatic startup via Windows Task Scheduler
- Testing catalog and order synchronization
- Documentation on settings and access to the configured environment
- One hour of remote support after delivery and training session for your team
Cost and savings
Basic catalog and order exchange via UT 10 typically costs $500–$1000, depending on complexity. Automatic startup via scheduler adds $200–$400. If modifications are required, the price is calculated individually. Automation saves up to 20 hours of manual work per month, paying for itself within a few months.
Why consider upgrading to UT 11?
If you are still on UT 10 — whenever possible, we recommend upgrading to UT 11 or higher. Benefits for site exchange: scheduled jobs without manual startup, better support for characteristics and trade offers, HTTP services for REST API. Migrating exchange settings during the upgrade is a separate task — the data structure changes, requiring reconfiguration of mappings.
Timelines and cost
Basic catalog and order exchange via UT 10 takes 1–2 days. With automatic startup via the scheduler — plus 4–8 hours. If modifications are required (characteristics, series, non-standard documents), timelines are calculated individually. The final cost depends on the scope of work and is discussed after auditing your system.
Common issues during setup
- Characteristics not exported: UT 10 lacks built-in trade offers — we use series or modify the configuration.
- Exchange times out: on large catalogs, increase script execution limits.
- Orders created without status: check status mapping and Bitrix user permissions.
Our engineers have 10 years of experience in 1C and Bitrix integrations. We guarantee correct synchronization and post-setup support.
If you need to configure UT 10 exchange with Bitrix, contact us. Get a consultation and project estimate. Get in touch — we will find the optimal solution.