What we connect to
We do not say “any ERP”: that is a promise nobody can check. Here is the concrete list of what the platform works with today, and in what shape it takes data in.
accounting system
Two routes: direct OData access, or a scheduled file export. The second works even where 1C sits in a closed network with no outside access.
our own product
Our own till: sale, refund, discount, shift and end of day. The receipt lands in the system immediately, so shelf stock and computed stock are the same number. Deployed where there is no till, or where it changes together with the accounting system.
POS and inventory
If a till is already in place and there is no reason to change it, we read sales, stock and the product catalogue from it — by API or file export.
POS and inventory
REST API: sales, balances, the product catalogue and historical stock reports.
file exchange
Supplier price lists, catalogues and balances. The format is documented, and the system shows what it failed to read instead of silently dropping a row.
order delivery
The channel an order travels to the supplier through, and the supplier's reply travels back on. To the supplier it is an ordinary chat.
outbound access
Read-only access to your own tenant's data under a separate key — for your BI or a contractor.
A connection starts read-only. We write nothing back into your accounting system until the figures reconcile and you explicitly allow it.
How we connect
Missing units, uncategorised items, days without movements, duplicated receipts. That is the first screen after connecting — before any analytics.
Speed depends on your 1C configuration and on what the export actually contains. We name a date after we have seen the data.
Show us one critical process. We will show how it runs here.
We look at your cycle: how an order is assembled today, who decides, where time leaks and what the system takes over.