1C Import Queue for CS-Cart

On every 1C export, CS-Cart may fail to recognize existing products and create duplicates instead of updating them. This happens because 1C sometimes generates new identifiers for the same products. The module automatically matches products by SKU and fixes the problem without manual editing.

You need this module if:

• product duplicates appear after every 1C export
• import creates new products instead of updating existing ones
• some products are silently skipped during import with no explanation
• you want to see all CommerceML errors in one place

What the module does:

• Products update correctly, no duplicates — even when 1C changes their identifiers
• Preview before applying — see all changes before they happen
• One-click rollback — instantly undo all changes if something goes wrong
• Duplicate SKU finder — both in the store database and inside the 1C XML file
• Skipped records — shows which products import skipped and why
• CommerceML error log — all errors from log files in one table, linked to products
• Safe mode — verifies product name match before replacing any identifier

1. Installation & Setup

Install using the standard CS-Cart method:

• Unpack the archive and copy its contents to the site root directory, preserving the folder structure
• Go to Add-ons → Manage Add-ons
• Find "IP5 Fixed UUID" and click "Install"
• Open the module settings by clicking its name

Available settings:

• Check product name — if enabled, the identifier is replaced only when the product name in the XML matches the database. Increases accuracy, reduces the risk of incorrect replacements.
• XML file path — relative path from the site root to the CommerceML XML file. Example: var/files/1/exim/1C/import0_1.xml. The module automatically lists found XML files in the export directory below the path field.

Fig. 0 — Module settings page with configuration parameters and quick access buttons

2. Preview & Apply Replacements

The core feature — safe identifier replacement with a full preview before anything is applied.

• Click "Run now" on the module settings page
• The module reads the XML file and builds a replacement list — for each product: SKU, name, current and new identifier from 1C
• Review the table: rows where the product name in XML does not match the database are highlighted separately
• Click "Apply" to update the records
• A notification shows the number of replacements made. The "Rollback" button becomes active.

Fig. 1 — Preview page: products table with pending replacements

Fig. 2 — Detailed view: SKUs, names and identifier pairs

3. Duplicate SKU Check

Click "Check duplicate SKUs" on the settings page. The page has two sections:

• Duplicates on site — products with the same SKU in the database. Shows product ID, name, external identifier and last update date.
• Duplicates in XML file — SKUs appearing more than once in the 1C export file. This signals a problem on the 1C side: during import it is impossible to determine which record to use.

Fig. 3 — Products with matching SKUs in the database

Fig. 4 — Full log file view

Fig. 5 — Duplicate SKUs inside the 1C XML export file

4. Skipped Import Records

Click "Skipped records" on the settings page — displays up to 150 most recent skipped records sorted by date. For each record the module automatically finds the skip reason in the commerceml.log files.

The table shows:

• UUID — external identifier of the record in CommerceML
• Type — entity type (product, category, etc.)
• Name — name from the mapping file
• Reason — skip reason text extracted from commerceml.log
• Log file — name of the log file where the reason was found
• Date — record timestamp

Fig. 6 — Skipped records table with log reason and link to product

5. CommerceML Error Log

Available via the administrator menu link. The module scans all commerceml.log* files, extracts lines with the [error] tag and groups them by log file starting with the newest. Identical lines are shown only once — duplicates are filtered automatically. If a product is found for the identifier in the error, a direct edit link is shown.

6. Rollback

After applying replacements, the "Rollback (N)" button appears on the settings page. The number in brackets shows how many records were changed.

• The module verifies that old identifiers are not taken by other records. If already taken — the record is skipped and logged
• Each pair is reversed
• A notification shows the number of processed pairs and actually restored records

Important: the Rollback button is only available during the current browser session. After logging out the rollback option is lost. Check the result immediately after applying.