1C Customization Without Losing Vendor Support
1C:Enterprise customization that matches how your company really works: new fields, buttons, checks, documents and logic. We build it as extensions, so 1C updates install without trouble.
- A configuration extension instead of editing the standard configuration
- An audit before work if someone has customized the database before
- The price of 1C customization in writing before we start
- Testing on a copy of the database and staff training
1C customization starts at 350,000 tenge for a single area, with a timeline of one to two weeks. Comprehensive customization takes from a month, and a database audit three to five days.
When you need 1C customization
A sure sign: spreadsheets kept in parallel with the accounting system.
A standard 1C configuration is written for an average company. Yours is not average: you have your own pricing rules, your own documents, your own sequence of steps. While the differences are small, settings cover them. When settings are not enough, staff start keeping Excel on the side.
The cost of doing nothing is usually higher than it seems. An hour of manual work a day for three employees adds up to hundreds of hours a year, plus copy errors and decisions made on outdated data. A 1C customization that removes such a spreadsheet often pays for itself within a few months.
If a manager fills in a document in 1C and then copies the same data into a separate file, the system is missing something important for your specific work. Those spots are exactly what 1C configuration customization addresses.
A customization can also be protective: it adds no new features but removes errors. Blocking shipment without payment, a mandatory warehouse on an order, a warning when the price is below cost. Such changes are inexpensive and pay back fast.
Another sign: staff know "workarounds". To post a document they tick one box, then untick it, then change the date. Every such ritual shows that 1C logic does not match the real process, and customization can remove it.
The most common requests we get:
- additional fields in products, counterparties and documents;
- your own rules for pricing, discounts and markups;
- checks that prevent posting an incorrect document;
- buttons that fill in a document in one click instead of ten;
- documents for a process the standard configuration lacks;
- automatic creation of related documents.
1C configuration extensions: why we work this way
The key question for anyone customizing 1C: will we still be able to update?
A configuration extension (.cfe file) is a 1C:Enterprise 8.3 platform mechanism that adds functionality as a separate layer on top of the standard configuration. The standard configuration itself does not change and stays on vendor support.
The extension mechanism evolves with the platform, and each version lets you do more with it. So we answer "can this be done with an extension" based on the current platform version, not on decade-old experience.
What this gives you in practice:
- 1C updates install normally, with no manual comparing and merging;
- if a new release conflicts, the extension is disabled, not the whole system;
- the customization can be switched off temporarily to check whether it is the cause of a problem;
- customizations are visible as a separate list instead of being scattered across standard code.
It also matters that the extension sits separately in the configuration list. A new developer who joins a year later sees right away what was customized, instead of comparing the whole configuration with the standard one in search of changes.
For the client this means predictable costs: updates do not turn into a separate project and customizations do not need rewriting every year. That is why customizing 1C with extensions has become the standard for companies planning to work with their database for the long term.
Extensions can add new fields, forms, buttons, checks, event subscriptions and even new documents and catalogs. That covers the vast majority of tasks. More on choosing between an extension and an external data processor in external data processor or configuration extension (in Russian).
When an extension is not enough
It is rare, and you should know about it before work starts.
Some tasks cannot be solved with an extension, or only at excessive complexity. For example, a deep rework of the posting mechanism in an old configuration, or a change to a structure that dozens of standard objects depend on.
Another example: a requirement to change a standard mechanism in a way that forces the extension to intercept dozens of standard procedures. It is technically possible, but every update would require checking all the intercepts, and the benefit of the extension nearly disappears.
In such cases we say so before work starts and explain the consequences: the database leaves vendor support, every update becomes a manual operation and costs money. Sometimes that is justified if the customization delivers a big effect. But the decision should be made consciously, not discovered a year later at the first update.
A 1C configuration extension does not make customization free during updates: after a major release the extension still needs checking. But that is an hour of checking, not several days of manually merging configurations.
A special case is old configurations on platforms before 8.3, where extensions are unavailable or limited. Here customization often becomes a reason to move to a current version, and we help with that, including data transfer: data migration to 1C.
Often there is a third way: simplify the task so an extension can solve it, and get 90% of the result without leaving vendor support.
Audit before customization
Especially if someone has customized the database before.
Before customizing a 1C configuration we look at what has already been done: is the configuration still on vendor support, what changes were made, are there source code and documentation, which release is installed and when it was last updated.
Both the timeline and the price depend on this. A clean standard configuration on vendor support is quick to customize. A database with edits to the standard configuration from three contractors needs care: any change may touch someone else's undocumented code.
The report also covers performance: which operations are slow and why. Slow 1C is often the result of a single poor customization that scans the entire sales history every time a form opens.
After the audit we give a written report: what can move into extensions, what to leave as is, what to rework. Sometimes the conclusion is unpleasant: the accumulated customizations are cheaper to rebuild. We say it directly and price both options. The audit takes 3-5 days, and its cost is credited toward the work if you continue with us.
How customization works
We start not with a specification but by watching how people work.
- Talking to the people who work in 1C. The official procedure and the real process almost always differ. Customizing to the procedure leaves the parallel spreadsheets in place.
- A short solution description. What changes in the employee's work, which fields and buttons appear, what gets checked. Agreed before any code.
- Estimate. The price and timeline of the 1C customization in writing.
- Development in an extension on a copy of the database. Your live 1C is not touched.
- Testing on your data. Staff try it on real documents and we find the inconvenient spots.
- Go-live and training. We install the extension in the live database and show it to staff on their own data.
- Two weeks of fixes. Minor adjustments based on the first days of use are included in the price.
1C customization: price and timelines
We quote after reviewing the database, in writing and before work starts.
| Customization | Timeline | Price |
|---|---|---|
| New fields and checks in a document | 3-7 days | from 150,000 ₸ |
| Print form in your own layout | 3-5 days | from 150,000 ₸ |
| Single area: logic, buttons, documents | 1-2 weeks | from 350,000 ₸ |
| Custom document with its own posting logic | 2-4 weeks | by estimate |
| Comprehensive customization of several areas | from 1 month | by estimate |
| Audit of a database with third-party customizations | 3-5 days | credited toward the work |
Customization can be split into stages and accepted in parts. First the most painful spot, then the rest. That way you see results in a week or two rather than a quarter, and can adjust the plan along the way. Any prepayment is credited toward the first stage.
What affects the price of 1C customization: the configuration, the state of the database and the number of related objects. What barely matters: the number of users. A detailed breakdown is in how much 1C customization costs in Kazakhstan (in Russian).
Examples of typical customizations
The situations we see most often. No company names.
Wholesale company, credit check. Managers shipped to clients with overdue debt because they could not see it while processing the order. Customization: when posting a sale, 1C checks the credit limit and overdue amount and blocks posting without a manager's approval. About one week.
Retail chain, supplier prices. Purchase prices came in Excel and a manager recalculated retail prices by hand. Customization: a data processor imports the supplier price list, recalculates prices using markup rules and creates a price-setting document for review. More on such tasks on the external 1C data processors page.
Distribution, customer bonuses. Volume bonuses were calculated in Excel at quarter end, and disputes with clients dragged on for weeks. Customization: bonus terms in the contract, automatic calculation from shipments, and a report the client sees in their portal. The portal exchange runs through the 1C API.
Manufacturing, made-to-order. Each order has its own parameters that were not stored anywhere. Customization: additional fields on the order, automatic creation of a shop floor task and a specification print form.
Typical customization mistakes we fix
What we find in databases after other contractors.
- Edits directly in the standard configuration. The configuration was taken off vendor support for the sake of one field, and updates were not installed for years.
- Undocumented code. Nobody knows why a data processor exists or what breaks if it is removed.
- Duplicated logic. The same check was written in three places and the versions contradict each other.
- Heavy queries in forms. A document takes ten seconds to open because the whole history is recalculated on opening.
- Exchanges without a log. The exchange fails silently and the error is discovered a week later.
Why old customizations break after updates is explained in why 1C updates break customizations (in Russian).
Configurations we work with
1C:Enterprise 8.3 platform, standard solutions for Kazakhstan.
Trade Management, Small Business Management (UNF), Integrated Automation, ERP, Retail, Accounting for Kazakhstan. We take on industry solutions after a review: what matters is not the configuration's name but the state of its code.
For Kazakhstan configurations we account for local specifics: electronic invoices (ESF), goods shipment notes (SNT), bank formats, Kazakhstan counterparty details. Customizations must not interfere with statutory accounting, so anything touching tax documents is agreed with your accountant.
Bookkeeping and 1C licenses are not our area; that is the work of an accountant and a franchise partner. We are responsible for customization, integrations and automation and often work alongside them. If a customization touches the exchange with your website or Kaspi, we handle that in the same project: 1C integration.
What you get
A customization you can maintain without us.
- A configuration extension tested on your data.
- Extension source code, not just an installed file.
- A description: which objects are affected, how to disable it, what to check after an update.
- Staff training on their own documents.
- Two weeks of fixes based on the first days of use.
If you have a 1C developer on staff, they can continue working with the extension on their own. We do not lock clients in with closed code.
The price of 1C customization is fixed in the contract by stage, so you always know what you are paying for this month.
The extension installs in the live database in a few minutes and can be disabled just as quickly. If something goes wrong after installation, the live database returns to its previous state in one step, without restoring from a backup.
For recurring tasks and checks after updates there is 1C support from 80,000 ₸ per month. If you have many varied tasks, the 1C developer with a task queue format is more convenient.
FAQ about 1C customization
Price, extensions and updates.
How much does 1C customization cost?
Small changes from 150,000 ₸, a single area from 350,000 ₸ in 1-2 weeks. Comprehensive customization takes from a month; we give an estimate after the audit.
What is a 1C configuration extension?
A platform 8.3 mechanism that adds functionality as a separate layer. The standard configuration does not change and updates normally, while the customization works on top.
Will we be able to update 1C after customization?
Yes, if the customization is built as an extension, which is how we do it. We warn about rare exceptions before work starts.
Others have customized our database. Will you take it on?
Yes. We start with a 3-5 day audit, looking at the changes and the source code. The cost of the audit is credited toward the work.
Can old edits to the standard configuration be moved into an extension?
In most cases, yes. After the audit we give a migration plan and return the configuration to vendor support where possible.
How long does customization take?
Small changes 3-7 days, a single area 1-2 weeks, comprehensive customization from a month. The timeline is fixed in the estimate.
Do you work remotely?
Yes, with all of Kazakhstan. Development happens on a copy of the database that we access through a connection you control.
Are fixes after delivery included?
Yes, two weeks of fixes based on the first days of use are included in the price. New requests are estimated separately.
More 1C services
Related tasks that usually go together.
1C developer
Custom 1C development priced per task.
External 1C data processors
Imports and bulk operations without changing the configuration.
1C print forms
Invoices, waybills and labels in your own layout.
1C reports
SKD reports, summary reports, dashboards.
1C support
Checks after updates and fixes on a subscription.
Send a request
Describe the task: we reply within one business day and quote before any work starts.