Budget: 22000 UAH Deadline: 7 days
Hello! The task with the specific unloading of spare parts is clear to me. Although I am not a narrow-profile 1C developer, I specialize in automating complex data flows and can offer a more flexible and modern solution through n8n/Make. Instead of rewriting the internal logic of 1C and creating thousands of duplicates within it, I propose to move the processing of the XML feed to an external level of automation. Here’s how I will implement it:
1. In your 1C, the product will remain in a single instance (this is important for accurate accounting of prices and stocks). OEM numbers will be stored in additional attributes.
2. My script will automatically retrieve the unloading from 1C, "unpack" the list of OEM numbers, and create a separate entry in the XML file for Prom.ua for each of them.
3. The result for Prom: Each OEM number will be displayed as a separate product card with a unique ID (for example, ID_product_OEM), which will provide maximum coverage in search. At the same time, the photo, price, and stock will be synchronized with the main card.
Advantages of my approach:
• Speed: Setting up such logic in n8n takes 3–5 days, which is significantly faster than making deep changes to the 1C configuration.
• Flexibility: If you want to add unloading to Rozetka or other marketplaces with different logic, I won’t need to edit the 1C code again — I will simply add a new branch in the script.
• Order in reporting: You will get rid of the problem of duplicates in inventory accounting.
My experience:
• 3+ years in implementing CRM and complex automations.
• Over 30 implemented cases of database synchronization and creating custom XML feeds for marketplaces.
• Building automated accounting and analytics systems for e-commerce projects.
Regarding resources:
• Cost: $400 — $700 (depends on the volume of data and the current structure of unloading from 1C).
• Term: 4–6 working days.
I suggest discussing the technical details in private messages to form a turnkey proposal for you.
