CRM, ERP and marketplace integration

What you get

• A service that moves orders, stock, prices and customers between your systems on a schedule or by webhook.
• Mapping of SKUs, articles and customer records, with duplicates merged by a business key such as phone or tax number.
• Retries with backoff and a dead-letter queue: a failed exchange is visible and can be replayed.
• A reconciliation report that shows where two systems disagree.

How I build it

I start from the business process: which system owns which field, what counts as the same customer, and what must never happen twice.

Every write carries an idempotency key and is stored in PostgreSQL before the target system sees it. If the ERP times out and the request is sent again, the order is created once. Tests run against a real database, and you get a README and a handover call.

The blog shows how this works in practice: connecting Kaspi.kz with 1C, what a 1C and Bitrix24 integration costs and how to protect an exchange from duplicates.

When you need a 1C, CRM or marketplace integration

• Kaspi.kz or another marketplace has to see your real stock.
• Managers retype orders from one system into another.
• 1C, a CRM and a website each keep their own customer list.
• An existing exchange works but nobody can say what it lost last week.