Integrations
Connect 1C, MoySklad, Wildberries, Ozon, Excel and REST API
How it works
Data source assessment
We support 3 primary methods: binary 1CD file reader (reads the database directly), SQL dump extraction for large datasets, and a lightweight EPF module that runs inside 1C:Enterprise. Plus CSV/Excel for quick starts.
Field mapping & validation
Our system maps your 1C fields to our schema automatically. Handles variations in naming (Товар vs Номенклатура), unit conversions, and multi-currency pricing. Validates data integrity before import.
Historical data backfill
For AI models to work properly, we need 6–24 months of sales history. The initial import processes this in bulk — typically 2–4 hours for a million transaction records.
Live sync activation
Once backfilled, the system switches to incremental sync: new transactions every 15 minutes via the EPF module, or daily via scheduled CSV/SQL dumps. Zero manual intervention after setup.
Under the Hood
Parses the proprietary 1C database format at file level. No 1C runtime needed — reads directly from .1CD files.
Works with PostgreSQL, MySQL, and MSSQL exports. Automatic schema detection and table mapping.
Native 1C plugin for real-time bidirectional sync. Installs as a standard 1C extension — no custom development required.
Real-World Example
Real example
A retail chain with 8 locations connected their 1C system in under a day. The first AI recommendations were generated within 48 hours of data upload.