1C Support for Customizations and Exchanges
We take over what breaks most often: exchanges with your website, Kaspi and bank, customizations after the next release, and small fixes that pile up for months. You pay a fixed subscription and see where the time went.
- Exchange monitoring: we learn about a failure before your sales manager does
- Customizations checked on a copy of the database before every update
- A task queue with estimates: what we do this month and what comes later
- A monthly report: what was done and how long it took
1C support in Kazakhstan costs from 80,000 to 250,000 tenge per month. The subscription covers exchange monitoring, checking customizations after updates and an agreed volume of fixes.
What 1C support is and who needs it
Not selling licenses and not clicking an update button.
For us, 1C support begins where the standard database has already been customized for the company. There are extensions, external data processors, a website exchange, a Kaspi export, bank statement imports. All of it works until a new release comes out, the marketplace API changes, or the employee who remembered how it all works leaves.
A 1C maintenance subscription is needed by companies where a stopped exchange directly stops sales: the online store cannot see stock, Kaspi orders do not reach accounting, managers work with yesterday's prices. If the database is standard and runs on its own, a subscription often does not pay off, and we say so honestly.
We do not sell licenses, ITS subscriptions or platform installation: that is the franchise partner's area. Ours is code, exchanges and everything written on top of the standard configuration.
A typical situation that brings clients to us: a wholesale company with several thousand items, a website and a Kaspi store. The exchanges were written by a previous contractor, something stops exporting once a month, and every time it is fixed urgently, expensively and without understanding the cause. The job of support is to move this from firefighting to planned work.
What a 1C maintenance subscription includes
The scope is fixed in the contract so there are no disputes later.
- Exchange monitoring. We check on a schedule that the exchange with the website, Kaspi, the bank and Bitrix24 actually ran and did not hang on an error. On failure, the alert comes to us, not to your customer.
- Customization maintenance. Before a configuration update we run extensions and data processors on a copy of the database and fix anything that conflicts with the new release.
- Small fixes. A new field, a field on a print form, a column in a report, a change to a fill rule. The monthly hours are agreed in advance.
- Consultations. How to record a non-standard operation, why a report shows something unexpected, where an import went wrong.
- Task queue. Larger customizations do not get lost: each has an estimate, and you decide what to do this month.
1C support plans
The price depends on the number of exchanges and customizations, not on the number of users.
| Plan | What is included | Price |
|---|---|---|
| Basic | Monitoring of one or two exchanges, customization checks before updates, up to 4 hours of fixes | 80,000 ₸/month |
| Standard | Several exchanges (website, Kaspi, bank), extensions, up to 10 hours of fixes, staff consultations | from 150,000 ₸/month |
| Extended | A complex set of exchanges with queues, scheduled jobs, priority response, up to 20 hours of fixes | up to 250,000 ₸/month |
The subscription is month to month, with no annual commitment. The first month is a trial: if the format does not suit you, we part ways with no penalties, and the source code, customization register and audit results stay with you. Payment by invoice to a legal entity, with an act of completed work every month listing the tasks.
Work beyond the plan is estimated as separate tasks. A large customization, such as a new document or an exchange with another marketplace, goes under a 1C customization estimate from 350,000 ₸; the subscription does not replace it.
How support starts
First we look at the database, then we sign the subscription.
- Audit, 3-5 days. We review the configuration, whether it is still on vendor support, which extensions and external data processors are connected, which exchanges run and how they are configured.
- Risk map. We describe what will break at the next update, which exchanges do not log errors, where source code is missing.
- Choosing a plan. Based on the audit we propose a plan. Sometimes the honest conclusion is that one-off work without a subscription is enough.
- Monitoring setup. We connect exchange checks and failure alerts.
- Working through the queue. We keep a task list and send a report every month.
The monthly report is simple: which tasks were done, how long each took, which exchange failures occurred and how they were resolved, what is in the queue and what it will cost. Unused hours in the basic plan do not quietly vanish: we suggest in advance how to use them, for example cleaning up catalogs or speeding up a slow report.
All source code of the extensions and data processors we write or modify stays with you. If you decide to move to another contractor or hire a specialist, we hand over a description of the customizations and exchanges so they do not start from scratch.
Why exchanges break and how we catch it
Most failures happen quietly.
A 1C exchange with a website or marketplace rarely fails with a loud error. More often it keeps running but stops sending part of the data: new products without an SKU, prices of a different type, stock from one warehouse. Staff notice a week later, when returns and complaints arrive.
So we check not just that the exchange ran but its result: how many items were sent, whether the count matches last time, whether there are products in 1C that disappeared from the website. A discrepancy above the threshold reaches us as an alert.
Another frequent cause is the data in 1C itself. A new product was created without a barcode, a counterparty's BIN changed, a price was set in a different price type. The exchange faithfully exports what is there, yet it gets the blame. So along with exchange monitoring we also check the completeness of the data that goes into it.
A separate cause of failures is changes on the marketplace side. Kaspi and other marketplaces change API formats and limits, and an exchange that worked for a year stops going through. More on marketplace connections on the 1C Kaspi integration page.
Updates and customizations: the main risk zone
We check every configuration update before it reaches the live database.
If customizations were made by editing the standard configuration, every update turns into manual comparing and merging. If they are extensions, the update goes through normally, but an extension may fail to attach when the new release changed an object it relies on.
We install the new release on a copy, check that extensions attach and run the key scenarios: document posting, print forms, exchanges. Only then do we update the live database at an agreed time. Why we do it this way is explained in why 1C updates break customizations (in Russian).
We also watch platform updates. Moving to a new version of the 8.3 platform sometimes changes how old code behaves: deprecated methods, different form rules, new security restrictions for HTTP requests. Such issues do not show up immediately, so after an update we watch the event log for new errors for a week.
Your franchise partner can perform the platform and configuration update itself. We make sure customizations and exchanges survive it without stopping work.
How we differ from a franchise partner and a freelancer
Three common support models and their weak spots.
| Who | Strength | Weak spot |
|---|---|---|
| 1C franchise partner | Licenses, ITS, standard consultations | Customizations and website exchanges are often not their specialty, consultation line queues |
| Freelancer | Cheap and fast at the start | One person: a vacation or illness stops everything, usually no documentation |
| A-LUX | Code, exchanges with website, Kaspi, bank, apps, monitoring | We do not sell licenses or keep books |
We build websites and 1C integrations ourselves, so we see the exchange from both sides and never pass the blame with "it is a website problem" or "it is a 1C problem".
Scheduled jobs and data checks
Part of the support work can be handed to 1C itself.
Many checks staff do by hand can be run by 1C on a schedule. A scheduled job compares the number of products on the website and in accounting every hour, looks for documents with empty required fields at night, and in the morning sends a list of counterparties without a BIN or with duplicates. Staff get a ready list of problems instead of hunting for them.
As part of support we set up such jobs for your database and make sure they do not stop. A typical quiet problem: a scheduled job stopped running after the database moved to another server, and nobody noticed for a month. Monitoring catches such cases too.
If there are many checks, the results are more convenient in Telegram for the person in charge than inside 1C: an item running low, an exchange that failed, a large sale. How this works is described on the AI and automation for 1C page.
Documentation and knowledge transfer
So the database does not depend on one person.
The most common risk we see in audits: nobody in the company knows what exactly was customized or how the exchanges work. The person who did it has left, there is no source code, the extension is attached but nobody knows what is in it. Any change in such a database turns into an excavation.
Under support we keep a simple register: which extensions and external data processors are connected, what each one does, which exchanges run, on what schedule, where to look when something fails. The register is kept on your side and updated after every task.
If you have your own 1C specialist, we work alongside them: we take the complex tasks and exchanges, and they handle day-to-day user questions. That way the company does not pay for what the employee can already do and does not keep someone on staff for rare complex tasks. The two models are compared in our article on hiring a 1C developer in-house or outsourcing (in Russian).
Who this is for
Companies where 1C is tied to sales.
Most of the companies we support are trading businesses with an online store and Kaspi sales, wholesalers with mobile orders from sales reps, manufacturers with customized cost accounting and service companies whose 1C exchanges data with a CRM.
We work with standard configurations for Kazakhstan: Accounting, Trade Management, UNF, Retail, Integrated Automation, and with industry solutions after a review. The configuration affects the scope of work less than the number and quality of customizations in it.
They all have one thing in common: the database contains code written for them and exchanges without which work stops. If that sounds like you, start with an audit: in 3-5 days it becomes clear where the risks are and which plan you need. If you need a one-off task rather than a subscription, see the 1C developer page.
FAQ about 1C support
Plans, updates and how we work.
How much does 1C support cost?
From 80,000 to 250,000 ₸ per month depending on the number of exchanges, customizations and the volume of fixes. We propose a specific plan after the database audit. The number of users barely affects the price: what matters is how many exchanges and customizations you have and how critical they are to sales.
How is support different from ITS?
ITS gives access to updates and standard consultations. Our support covers your code and exchanges: we make sure customizations survive updates and exchanges work every day. They do not replace each other: ITS is needed for legitimate updates, support is needed so updates do not break your code.
Do you update the configuration?
We update a copy, check the customizations, then install on the live database. If your franchise partner handles updates, we agree the schedule with them: they install the release, we check customizations and exchanges on a copy in advance and fix conflicts.
What if the monthly hours run out?
We warn you in advance. Urgent work is done beyond the plan at an agreed estimate, the rest moves to next month's queue. If the overage repeats three months in a row, we suggest moving to the next plan rather than paying for overtime.
Will you take on a database others have customized?
Yes, after an audit. If there is no source code or customizations were made by editing the standard configuration, we explain the risks and the cost of fixing it. Sometimes it pays to move old edits into extensions once rather than suffer at every update.
How quickly do you respond to an exchange failure?
Within a business day, with priority on the extended plan. Failures that stop sales are handled first. Response time and escalation are written into the contract, so there is no ambiguity about what counts as urgent.
Do you work remotely?
Yes, across Kazakhstan. Database access is through a secure connection, work happens on a copy, and only agreed changes go into the live database. Office visits are rarely needed, mostly for staff training or hardware setup.
Can we skip the subscription and order one-off tasks?
Yes. A subscription pays off when there are several critical exchanges. For occasional tasks one-off work by estimate is cheaper. You can switch between subscription and one-off tasks in any month, with no penalties.
More 1C services
Related tasks that usually go together.
1C developer
One-off tasks and task packages with an estimate before work starts.
1C customization
Configuration extensions that keep vendor support.
1C integration
Exchange with your website, app and external systems.
1C Kaspi integration
Products, stock and orders between accounting and the marketplace.
1C bank integration
Automatic import of Kazakhstan bank statements.
Send a request
Describe the task: we reply within one business day and quote before any work starts.