Website integration with CRM and services

In short

An integration connects your site to the systems the business runs on — a CRM, accounting, payments, delivery, telephony and messengers — so data moves by itself instead of being retyped by hand. We build exchanges in both directions, with signature checks, protection from repeats and a log that shows what was sent and what came back: a failure is visible right away, not a month later. When your product needs to talk to others, we build its own API with documentation. The price is counted in hours and fixed before the start.

1. 01

   One version of the truth

   The site, the CRM and accounting see the same orders, prices and stock — no more “which one is right?”.

2. 02

   No manual copying

   Orders, enquiries and payments go where they belong by themselves — people do the work only people can do.

3. 03

   A faster reaction

   An enquiry from the site reaches the manager in seconds, while the client is still waiting for an answer.

4. 04

   Fewer mistakes

   No typos in phone numbers, no duplicated orders, no forgotten payments.

5. 05

   Visible failures

   Every exchange is logged: if something did not go through, you know right away and see why.

6. 06

   Growth without extra staff

   Ten times more orders does not mean ten times more people copying data.

1. 01

   CRM

   Enquiries and orders become deals with the source of the visit; statuses come back to the site.

2. 02

   Accounting and warehouse

   Products, prices and stock come in; orders and documents go out.

3. 03

   Payments

   Payment, refunds and subscriptions with confirmed notifications from the payment provider.

4. 04

   Delivery

   Cost at checkout, shipments created automatically, tracking numbers to the client.

5. 05

   Telephony

   Calls are tied to the client card, call-back requests from the site go straight to the line.

6. 06

   Messengers and bots

   Notifications to managers and clients, enquiries from chats into the CRM.

7. 07

   Email and mailings

   Subscribers and segments from the site go to the mailing service without exports by hand.

8. 08

   Analytics and ads

   Real sales are sent back to analytics and ad systems — so you can see which channel brings money, not just clicks.

1. One main source for each piece of data

   For every field it is decided in advance where it lives: prices in accounting, deals in the CRM. That way the systems never argue.

2. Signature checks

   Incoming notifications are checked: someone else’s request cannot pass itself off as a payment or an order.

3. Protection from repeats

   A repeated notification is recognised: a payment is not counted twice and an order is not created twice.

4. An exchange log

   You can see what went to the CRM or the payment provider and what came back — and find the cause of a failure in minutes.

5. Retries with a growing delay

   If the other service is down, requests are repeated later instead of being lost.

6. Alerts

   When an exchange keeps failing, the person responsible gets a message instead of finding out from a client.

7. Keys outside the code

   Access keys live in environment variables — they are neither in the code nor in the repository.

1. 01

   Documentation

   The API is described in OpenAPI: another team connects from the documentation, without calls and letters.

2. 02

   Keys and access rights

   Each partner gets its own key with its own rights and can be switched off without affecting the others.

3. 03

   Limits

   Limits on how often the API can be called protect it from overload and brute force.

4. 04

   Versions

   New features come in a new version, and existing clients keep working as before.

5. 05

   Webhooks for partners

   Your product notifies other systems about events itself — with a signature they can verify.

1. A data map

   What goes where, how often, which system is the main one and what happens on a conflict.

2. Access and documentation

   Test accounts and API documentation for each system — from you or from the vendor.

3. Building in a test environment

   The exchange is built and run without touching live orders and real money.

4. Checks on real data

   Edge cases: a cancelled order, a partial refund, a product with no price, a client with two phones.

5. Launch under watch

   The first days after launch the log is watched closely, and anything unexpected is fixed straight away.

6. Documentation for your team

   How the exchange works, where to look when something goes wrong and how to add a new field.

1. “Temporarily” by hand

   Manual copying “until we set up the integration” lasts for years and costs more than the integration itself.

2. No main source

   Both systems can change the same field — and overwrite each other’s changes.

3. An exchange without a log

   When something goes wrong, nobody can tell what was sent and what was lost.

4. Trusting every incoming request

   Without a signature check a fake notification can mark an order as paid.

5. No retries

   The other service was down for five minutes — and every order from those minutes is lost.

6. Nobody knows how it works

   An integration without documentation dies with the developer’s departure.