Connect your website, app, accounting and CRM so that the same information does not have to be entered several times. We define the data exchange around a specific business process.
An online order may need to reach accounting and CRM, while the customer needs the correct status. We identify the source of each field, the direction and frequency of exchange, and the person responsible for exceptions. If a suitable existing connector meets the need, configuring it may be better than custom development.
What we can assess
Our Russian catalogue covers 90 products across ten areas. They are candidates for integration, not a claim that every product has already been used in a completed project. Compatibility depends on the installed version, plan, licences and permitted interfaces.
Accounting and inventory: 1C and MoySklad
CRM and workflows: Bitrix24, amoCRM and retailCRM
Websites and commerce: 1C-Bitrix, WooCommerce and OpenCart
Marketplaces and analytics: Ozon, Wildberries and Yandex Metrica
Messaging and email: Telegram, MAX and UniSender
Telephony and helpdesk: MANGO OFFICE, UIS and Okdesk
Payments and documents: YooKassa, CloudPayments and Diadoc
Delivery and logistics: CDEK, Russian Post and Yandex Delivery
Restaurants and local services: iiko, r_keeper and YCLIENTS
Specialist systems: GetCourse, Medesk and TravelLine
Fuel-station systems we have worked with
The ontech.pro team has practical integration experience with SNK-AZS / Sibneftecard and Servio Pump. For a new project, we still check the actual installation and available interfaces. Prior experience is not a promise that all operations are accessible in every configuration.
Agree the result before development
We document the business scenario, fields, identifiers, error handling and checks. The estimate distinguishes development from external licences, vendor work and infrastructure. We agree logs, failure notifications and support responsibilities before launch.
Test more than the successful request
Checks cover ordinary operations, rejected or missing data, repeated requests and temporary unavailability. We agree which operations may be retried and how duplicates are prevented within the capabilities of the connected systems. A payment or order must not be assumed successful merely because a request was sent.
Before we start
Can we keep our current software?
That is usually the purpose of integration. We first examine the permitted exchange options. If a change of software is necessary, we explain why and discuss alternatives.
What do you need for an estimate?
The system names and versions, one example of the manual operation, the data involved and available documentation. Do not send passwords, access keys or customer databases through the public form.