Integrations: CRM, ERP,
payments, marketplaces

Usually, yes. We can build the exchange through the built-in CommerceML format, HTTP services, or a middleware database. On the first call, we check your version and configuration and tell you exactly what's realistic.

Usually every 5–15 minutes; for critical items, almost real time via webhooks. We tune the frequency so we don't overload your 1C with extra requests.

We always build in logging and alerts: if a sync fails, you and we find out right away — not a week later from customer complaints. No data gets lost either; the queue just finishes processing once things are fixed.

Then we build our own layer: either a wrapper around the database, a scraper for the admin dashboard, or a scheduled file exchange. We pick the option based on reliability, not on how fast it is to build.

A standard 1C-to-website sync takes 3–5 days. Connecting a CRM takes 2–4 days. Marketplaces and shipping carriers are estimated separately since they depend on the platform's own rules. The slowest part usually isn't the development — it's cleaning up your reference data on your end.

No. We build it in a test environment and run it alongside your usual manual process. We only switch over once the numbers in both systems match for several days in a row.

That's exactly why we use a test environment. Plus, every exchange is logged — you can see what went out, what came back, and where any failure happened. If there's an error, you get an alert, and the data queues up instead of getting lost.

That's a normal situation. We start by mapping it out: what's stored where, what comes from where, and what the source of truth is for each field. Often it turns out half the connections aren't even necessary — cleaning up one system is enough.

You do. The source code, access credentials, and documentation are all handed over to you. We don't hold onto any keys that would break the integration if you switched vendors.