The run screen opens after the source structure step is saved. Here you can run a test export, run the full export, view task progress, and see the export cost in credits with a cost breakdown. Important: the page shows only a preliminary estimate. The final amount is usually different because Eofferix does not charge for images that did not work, products that did not change since the previous exchange, and other actions that did not actually write data to the site. For the full first-run path, start with exporting a catalog to 1C-Bitrix.
What Is On The Run Screen
| Block | Purpose |
|---|---|
| Run | Starts the full exchange with the 1C-Bitrix site. After the click, the button should stop looking available for repeated clicks, and the task should move to queue or preparation. |
| Test export | Sends a limited sample to check the catalog structure before the full run. |
| Test as a full run | Enable it only when the test must use the same rules as the full exchange. A normal test export does not include product or offer deletion and other cleanup unless this option is enabled. |
| Current task | Shows the run state, progress, stop, and continue actions when they are available. |
| Cost | Shows the preliminary credit estimate before launch and helps understand the selected scenario cost. |
Credits
Before launch, Eofferix shows a preliminary estimate. After completion, the final charge should match actual actions: created, updated, or deleted objects and images that were really processed. If a product, offer, or section already matches the prepared data, it is skipped without changes and should not be counted as a full write.
If Eofferix reserved more credits than were needed in the end, the unused part is released after completion. Continuing a stopped task or saving the result again should not charge the same confirmed work a second time.
Test Export
Click Test export to send a small sample first. For 1C-Bitrix, the test sends 5 products. By default, the test does not run deleting rules, so it is suitable for a first check on a live site.
If the source has loading conditions, the test sample follows them too. For example, offers with zero stock will not appear on the site if the source structure says to load only stock above zero.
After The Test
- products appeared in the selected Bitrix catalog;
- offers did not become duplicate products;
- product, offer, and section properties are in the right places;
- images open;
- the report has no unclear errors.
Full Run
Click Run to send the full catalog. Large catalogs are sent in parts so the site is not overloaded. If the site answers slowly, the portion becomes smaller; if it answers normally, the exchange can move faster.
During the full exchange, watch the Current task block. It should show the current phase, progress, how many items were created, updated, skipped without changes, deleted, and whether there are warnings or errors.
Stop And Continue
You can stop a running task. The screen should show that the stop request is being processed: the service finishes the current safe part and saves the continuation point.
After a stop or an error, continue the import from the last confirmed point. Already processed products, offers, and sections should not be created again, and credits should not be charged again for the same work.
Rollback
The result screen shows only a confirmed, currently available rollback point for the same physical 1C-Bitrix destination. Rolling back to it can undo the selected run and later imports to that same destination; data in another destination must not be affected. Check the point time and scope before confirming.
Automatic missing-data cleanup does not delete or unlink properties or dictionary values used by the profile. If they are temporarily absent from a later source, they remain in the catalog; when they appear again, Eofferix reuses the retained mapping when one compatible object can be identified unambiguously. Rules for missing products, offers, sections, and images work separately.
If Protection Stops The Exchange
Sometimes Eofferix stops a run deliberately: for example, cleanup touches more objects than the safety limit allows, no catalog is selected, the site did not confirm the connection, or the source has no needed image file. The message should explain the reason, what exactly stopped, and where to fix the setting.
If the message mentions the deletion limit, first check the source and selected preset. The limit exists to prevent accidental mass deletion. Increase it only after checking that the objects belong to the current source.
Result And Credits
After completion, check actual actions: how many products, offers, and sections were created, updated, skipped without changes, or deleted, and whether there are warnings or errors. These numbers matter for repeat-run speed and credit charging.
| Run result | How it affects credits |
|---|---|
| Created or updated product, offer, section, or property | Counts as completed work. |
| Skipped without changes | Does not count as a full write because the site was not rewritten. |
| Object did not pass a loading condition | Does not count as a written object. Check the source structure if you expected it on the site. |
| Continue after stop | The already confirmed part should not be charged again. |