1C ↔ Online Store Two-Way Sync Integration
Employer
Mykola
Project parameters
Type of cooperationOne-time project
SectionWeb development
Prepaymentwithout prepayment
Payment methodsCash, Bank transfer
Acceptance of requestsfrom today, 12:51 until Sep 6, 2026
Project description
Our company runs its entire accounting, inventory and pricing on 1C, while sales happen through our public website and online store. Right now the two systems live separate lives: a manager exports spreadsheets from 1C, edits them by hand and uploads the data to the site, then copies new orders back into 1C the same way. This routine eats hours every day, and worse, it produces mistakes we only discover after a customer has already ordered something that is out of stock or seen a price we no longer offer. We are looking for a developer who can turn this fragile manual process into a dependable, automated bridge between the two systems.
The goal is genuine two-way synchronization on a schedule. Products, stock levels and prices must flow from 1C to the website, while new and updated orders must flow back from the website into 1C, so both sides always agree. The integration has to survive real-world conditions: partial data, temporary outages, and being launched twice in a row. That means idempotent, safe re-runs that never double-post an order or corrupt a record, clear conflict-resolution rules when the same entity changes on both sides, and detailed logging so we can see exactly what was transferred and diagnose any failure without guessing.
We will provide access to our 1C configuration and a test copy of the site. Please describe your approach, the exchange format you propose, and your experience with similar 1C integrations.
Key requirements:
— Two-way sync of products, stock, prices (1C → site) and orders (site → 1C)
— Scheduled runs with configurable frequency and manual trigger
— Idempotent, safe re-runs with no duplicate orders or data corruption
— Explicit conflict-handling rules and per-record logging
— Error alerts and a readable report of each exchange session
— Documentation and handover so our staff can maintain it
The goal is genuine two-way synchronization on a schedule. Products, stock levels and prices must flow from 1C to the website, while new and updated orders must flow back from the website into 1C, so both sides always agree. The integration has to survive real-world conditions: partial data, temporary outages, and being launched twice in a row. That means idempotent, safe re-runs that never double-post an order or corrupt a record, clear conflict-resolution rules when the same entity changes on both sides, and detailed logging so we can see exactly what was transferred and diagnose any failure without guessing.
We will provide access to our 1C configuration and a test copy of the site. Please describe your approach, the exchange format you propose, and your experience with similar 1C integrations.
Key requirements:
— Two-way sync of products, stock, prices (1C → site) and orders (site → 1C)
— Scheduled runs with configurable frequency and manual trigger
— Idempotent, safe re-runs with no duplicate orders or data corruption
— Explicit conflict-handling rules and per-record logging
— Error alerts and a readable report of each exchange session
— Documentation and handover so our staff can maintain it
