Article

Kaspi and Bitrix24 integration

15 October 202616 min read
Amirzhan Tazhin
Amirzhan Tazhin

Director, Tochka KZ

Kaspi and Bitrix24 integration is the automatic transfer of orders from the Kaspi Store seller's personal account to the Bitrix24 CRM. Each new order becomes a deal with the buyer's contact and order items, and status changes are synchronized between the systems. A manager works in one program instead of two, and orders are neither lost nor entered by hand.

For sellers in Kazakhstan, Kaspi Store is one of the main sales channels, but it has an inconvenience: orders arrive in a separate account, while the customer base, tasks, warehouse and analytics live in another system. As a result, staff retype data by hand, get confused by statuses and lose repeat buyers. Integration solves this problem and turns Kaspi orders into part of a single sales process. Below we explain what exactly is transferred, which methods can be used, how the project runs, how long it takes and where mistakes are most often made.

What Kaspi and Bitrix24 integration gives you

Bitrix24 is a system where it is convenient to manage customers, deals, tasks and reports. Kaspi Store is the source of orders and payment infrastructure. When they are connected, the company gets a single picture: who bought what, when and for how much, what is happening with shipment and who is responsible for it. Below is which data can be passed between the systems.

What data is passed between Kaspi and Bitrix24
What data is passed between Kaspi and Bitrix24
DataDirectionWhat it gives you
New ordersKaspi → Bitrix24An order appears in the CRM as a deal with no manual entry
Customer contactsKaspi → Bitrix24A customer card with phone number and order history
Order itemsKaspi → Bitrix24Order contents, quantity and amount inside the deal
Order statusesBoth waysThe manager sees the order stage, and changing the stage in the CRM can update the status in Kaspi
Stock and pricesBitrix24 or 1C → KaspiAn up-to-date price list without manually uploading files
Delivery and pickupKaspi → Bitrix24Delivery method and date in the deal, tasks for the warehouse or courier

The exact set of data depends on the Kaspi API capabilities for your store and the chosen integration method.

The main effect is time savings and fewer errors. A manager doesn't have to open the Kaspi account, copy the phone number and address, and then create a deal all over again. The head sees all orders in one report, and the company gets each customer's purchase history and can work on repeat sales.

Who it is relevant for

  • Sellers with several dozen orders a day, where managers spend time on manual entry.
  • Companies with several warehouses, where it's important to see stock and distribute orders.
  • Businesses that sell both on Kaspi and on their own website and want to collect orders in one funnel.
  • Companies that keep accounts in 1C and want orders to get there without re-entry.
  • Managers who need sales and manager workload reports without pivot spreadsheets.

If there are few orders and one employee easily handles them by hand, an integration may be excessive. As a rule, payback is noticeable with several dozen orders a day, several managers or several warehouses: that is where manual work starts to produce errors.

Integration methods: comparison

Kaspi can be connected to Bitrix24 in different ways. The choice depends on how standard your process is, whether a link with 1C is needed and what budget you are willing to allocate. The table shows the main options and their features.

Methods of integrating Kaspi with Bitrix24 and their comparison
Methods of integrating Kaspi with Bitrix24 and their comparison
MethodHow it worksLaunch timeProsLimitations
Ready-made connector from the Bitrix24 app catalogInstalled as an app and configured following the instructions1–3 daysQuick launch, no development neededLimited flexibility, dependence on the app developer, paid subscription
Custom integration via the Kaspi API and the Bitrix24 REST APIA developer writes the exchange for your processes2–4 weeksAny logic, full control over the dataDevelopment cost and maintenance when APIs change
Via 1C as an intermediate linkOrders go to 1C, and from there to Bitrix24 through an already configured exchange3–6 weeksUnified accounting of goods, stock and documentsLonger and more expensive, 1C needs to be adapted
An intermediary integration serviceData transfer scenarios are assembled in a builderabout a weekNo programmer needed, quick changesService limitations, a monthly fee, complex cases can't be covered
Manual file export and uploadOrders are exported from the account and imported into the CRMimmediatelyNothing to configureErrors, delays and a burden on staff

Timelines are approximate. Check the availability and terms of ready apps in the Bitrix24 catalog at the time of choosing.

If the process is standard and you only need to pass orders, it makes sense to start with a ready app: it is faster and cheaper. If you have non-standard statuses, several warehouses or an exchange with 1C, a ready solution is usually not enough, and it's better to design a custom integration right away.

Need to connect Kaspi Store with Bitrix24?

Tell us how many orders you receive and how you currently process them. We will check which data is available in your Kaspi account, choose a suitable integration method, and name the timeline and cost. The initial consultation is free.

Discuss the integration

How data from Kaspi gets into Bitrix24

For orders to be convenient to work with, you need to decide in advance which CRM objects the Kaspi data turns into. The following mapping scheme is usually used.

Mapping of Kaspi data to Bitrix24 objects
Mapping of Kaspi data to Bitrix24 objects
In KaspiIn Bitrix24Comment
OrderDealThe Kaspi order number is saved in a separate field for reconciliation
BuyerContactThe phone number is checked for duplicates to avoid creating extra cards
Order itemsProducts in the dealThe SKU links the item to the CRM or 1C catalog
Order statusDeal stageA separate funnel stage is created for each Kaspi status
Delivery methodCustom field and taskA task for the warehouse or courier is created automatically
Buyer's commentComment in the dealVisible to the manager immediately when the card is opened

Two points are especially important: saving the Kaspi order number in a separate field and linking order items to the catalog. The first lets you quickly reconcile data between systems, the second lets you correctly calculate stock and generate documents.

Stages of Kaspi and Bitrix24 integration

The project usually goes through seven stages. They are the same for a ready app and for custom development; only the scope of work at the third and fourth steps differs.

Order handling process analysis

We find out who accepts orders now, how they get to managers, which statuses are used and where time is lost. This is the basis for designing the funnel.

Access and Kaspi Store preparation

In the seller's personal account we get API access and check which data and operations are available for your store. Conditions may change, so we confirm the current rules.

Setting up the funnel in Bitrix24

We create a deal funnel for Kaspi orders: stages correspond to statuses, and we add fields for the order number, delivery method and warehouse.

Setting up data exchange

We connect a ready app or develop the integration: orders are passed to the CRM, contacts are checked for duplicates, statuses are synchronized.

Scenario testing

We check a new order, a cancellation, a return, a partial shipment, an order with several items and a repeat buyer.

Staff training

We show managers and the warehouse how to work in the new funnel and leave brief instructions.

Launch and control

We switch on the exchange in production mode, for the first days reconcile the number of orders in Kaspi and in the CRM and fix discrepancies.

Project timeline by stages

Approximate timelines for the stages of Kaspi and Bitrix24 integration
Approximate timelines for the stages of Kaspi and Bitrix24 integration
StageWhat we doTimelineResult
Process analysisWe study how orders are currently handled, which statuses and warehouses are used2–4 daysA process description and a data diagram
Kaspi and Bitrix24 preparationWe get API access, configure the funnel, stages and fields in the CRM2–3 daysA ready funnel and access keys
Exchange setupWe connect a connector or develop the integrationfrom 3 days to 3 weeksA working exchange on test data
TestingWe check orders, cancellations, returns, partial shipments3–5 daysA list of verified scenarios
Launch and trainingWe switch on the exchange in production mode and train managers1–2 daysInstructions and a working integration

Timelines are approximate and depend on the integration method and the complexity of the process.

The total timeline is made up of these stages. For a typical project with a ready app, launch takes a few days; for a custom integration, usually two to four weeks; and if an exchange with 1C is needed, the timeline grows.

Usage examples

Below are typical scenarios showing how the integration works in different businesses. These illustrate approaches and are not descriptions of specific clients.

Household appliance store

Orders from Kaspi Store arrive in Bitrix24 as deals. The manager clarifies the details, the warehouse sees a picking task, and stock is updated from the CRM so that nothing out of stock is sold.

Clothing seller with several warehouses

Orders are automatically distributed among warehouses depending on availability. The responsible person sees where the item is and doesn't waste time reconciling spreadsheets between locations.

Wholesale and retail company on 1C

A Kaspi order is created in the CRM, then via the exchange goes into 1C to generate documents. Accounting receives the data without re-entry, and the manager sees the shipment status in the deal.

How much the integration costs

There is no fixed price for integration: it depends on the method chosen and how complex your process is. We name the cost after analysis and fix it in an estimate. The main factors are in the table.

What the cost of Kaspi and Bitrix24 integration depends on
What the cost of Kaspi and Bitrix24 integration depends on
FactorHow it affects the costHow to reduce it
Integration methodA ready connector is cheaper, custom development is more expensiveStart with a ready solution if the process is standard
Number of scenariosEach additional scenario is a separate scope of workLaunch orders first and add stock later
Link with 1CExchange with 1C increases the timeline and labor intensityMake sure the standard exchange already works
Number of stores and warehousesMore points make stock mapping more complexPut the warehouse directory in order in advance
Data qualityDuplicates and different SKUs require cleanupBring the catalog to a uniform state before starting

To assess payback, count how much time staff spend on manual order entry and how many orders are lost or processed with errors. If these costs over a year are comparable to the cost of the project, the integration pays off.

Checklist before starting

  • The store is registered in Kaspi and you have access to the seller's personal account
  • API access has been granted in the account, or another way of receiving orders has been determined
  • Bitrix24 has a deal funnel, or you are ready to create a new one
  • Responsible people are defined: who accepts the order, who picks it, who ships it
  • The product catalog is brought to a uniform state and SKUs match
  • It is decided whether a link with 1C and passing stock to Kaspi is needed

Common integration mistakes

No duplicate protection

One buyer creates several contact cards. A search by phone number is set up before creating a new contact.

Kaspi statuses don't match CRM stages

Managers get confused and orders get stuck. Each order status is assigned its own stage.

No handling of cancellations and returns

The deal stays open although the order is cancelled. Cancellations and returns are planned for in advance.

Stock is updated manually

Items that are out of stock keep being sold. Stock is transferred automatically.

The integration isn't checked after changes

A CRM update or changes on the Kaspi side break the exchange unnoticed. Error notifications and periodic reconciliation are set up.

How to check that the integration works

After launch it is important to measure the result rather than just consider the integration finished. Tracking a few indicators is enough for this.

  • Time from receiving an order to a manager processing it.
  • Share of orders lost or processed late.
  • Number of data errors: wrong items, duplicate contacts, stock discrepancies.
  • Manager workload: how much time goes into manual entry and reconciliation.
  • Share of repeat buyers, visible in customer cards.

Compare these indicators before and after launch. If any of them hasn't improved, the scenario needs refining: most often the cause is inaccurate status mapping or duplicates in the data.

Important to consider

The terms of working with Kaspi Store, the data set and API capabilities may change, so before a project we always confirm the current rules in your seller account and in Kaspi's documentation. Ready apps for Bitrix24 are updated too: their availability, price and features should be checked at the time of choosing. We don't promise what can't be confirmed for your store, and we honestly state limitations before work begins.

Frequently asked questions

Can Kaspi Store be connected to Bitrix24?

Yes. Orders from the Kaspi seller's personal account can be passed automatically to Bitrix24 as deals with contacts and order items. For this, ready apps from the Bitrix24 catalog, a custom integration via the API, or an exchange through 1C are used. It's best to check the availability of a ready solution and its terms at the time of choosing.

What exactly is passed from Kaspi to Bitrix24?

Usually the order number, the buyer and their phone number, order items, the amount, the delivery method and the status are passed. The exact set of data depends on the Kaspi API capabilities for your store and the chosen integration method.

Can I change the order status in Kaspi from Bitrix24?

It depends on the API capabilities and store settings. If the required operations are available, changing the deal stage in the CRM can update the order status in Kaspi. Before the project we check which operations are allowed in your account.

How long does the integration take?

A ready app launches in 1–3 days. A custom integration usually takes 2–4 weeks, with exchange through 1C — 3–6 weeks. Timelines are approximate and are refined after analyzing your process.

How much does Kaspi and Bitrix24 integration cost?

The cost depends on the integration method, the number of scenarios, the link with 1C and the number of warehouses. A ready app is cheaper but has limitations. We name the exact price after analyzing the process and fix it in an estimate.

Is 1C needed for the integration?

No, 1C is not required. If you keep accounts in 1C, it's better to build the integration with the exchange in mind so that stock and documents don't diverge. If you don't have 1C, orders go directly to Bitrix24.

How do I avoid duplicate contacts?

Before creating a new contact, the system searches for the buyer by phone number. If the contact is found, the order is linked to the existing card, and the purchase history is preserved.

What happens to orders if the exchange fails?

With the right setup, errors are logged, the responsible person gets a notification, and the transfer is repeated once the connection is restored. In addition, the number of orders in Kaspi and in the CRM is reconciled.

Can I pass stock from Bitrix24 to Kaspi?

Yes, stock and prices can be updated automatically: a price list is generated from the CRM or 1C and uploaded to the Kaspi account. This reduces the risk of selling an item that is out of stock.

Does the integration suit several stores on Kaspi?

Yes. A separate connection is set up for each store, and orders are collected in one funnel with a source label. Stock takes into account a shared warehouse or separate points.

Is it safe to give access to the Kaspi API?

Access keys are stored in the integration's protected settings and are not shared with third parties. It's recommended to limit permissions to only the needed operations, and when changing contractors the keys are reissued.

Do I need to train managers?

Yes, training usually takes one or two days. Managers get used to the order funnel, and we leave brief instructions and stay in touch after launch.

Kaspi and Bitrix24 integration turns scattered orders into a manageable sales process: less manual work, fewer errors and more data for decisions. Read more on the topic in the articles “CRM for an online store: why it's needed and how to choose”, “Integrating a website with 1C products: what options exist” and “Kaspi Pay and Kaspi QR integration on a website: how to connect”. About CRM implementation — on the page “Bitrix24 implementation”, about exchange with 1C — on the page “1C integration”.

Want Kaspi orders to land in Bitrix24 by themselves? Leave a request — we will discuss the task, timeline and cost.

Free consultation

Tell us about your task — we'll find a solution

We reply within 15 minutes during business hours.

CallWhatsApp