• Integrations

Site integration with 1C or BAS

Integration of the site with 1C is not a "synchronize" button, but an agreement about the fields: what comes from the database, what remains behind the site and by what value the system recognizes the same product the second time. We start with the real download file, because the description in words and the content of the database almost always differ. Next, the scheme of matching fields, prices and balances according to the schedule, if necessary, orders back to the database, a log with visible errors. There is no cost on the page: first, the analysis of the file, then the estimate by stages.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
Where do we start?
from the download file, not from the description in words
Price
after a free audit
Guarantee
30
days after project sign-off
Where do we start?
from the download file, not from the description in words
What is the exchange based on?
stable product key: article number, code or base identifier
Measured scale of the directory
55,321
product pages and 3,868 categories — 59,189 addresses
Speed ​​on this volume
first response 840.5 ms at 454.5 KB HTML, measurement 07/31/2026
Term of works
10-30
working days from the approval of the exchange scheme
Before the estimate
free export analysis, 3-5 working days
Process steps

Transparent stages with approval at every step

Total duration:10–30 days

  1. Export breakdown and field scheme

    2-4 working days

    We take your file, count the items, see which fields are actually filled, and which are only announced. The output is a correspondence table: database field — site field — who owns it. This is the document that is then returned to in every dispute.

  2. Key and reconciliation of the directory

    1-3 working days

    We record how the product is identified, and check the directory with the site's catalog, if it is already full. Here it usually turns out that some of the items do not have an article number, and some are listed twice. We give you the list of discrepancies - you will have to close it from the accounting side.

  3. Unilateral exchange for copies

    3-8 working days

    We deploy a copy of the site and launch products, prices, balances, categories and characteristics on it. A copy is needed precisely because the first run always reveals something unexpected in the scheme - and it is better that this something does not happen on the live directory.

  4. Dry run and reconciliation of numbers

    1-3 working days

    The exchange is started on the combat in a mode where it counts the changes and writes them to the log, but does not record anything. You see in advance: so many items will be updated, so many will be created, so many will disappear. If the number "created" is suspiciously large, it means that the wrong key was chosen - and we will know about it before recording, not after.

  5. Order back to base

    2-8 working days

    The second stream, if you need it: the order with the buyer, warehouse and delivery is entered into the database as a document. We go all the way - from the basket to the document in the accounting - and separately agree on what to do with the buyer who is not yet in the database.

  6. Combat launch, magazine, transmission

    1-4 working days

    We turn on the recording, keep the exchange under supervision for a week and compare the number of items on the site and in the database. Next comes documentation, instructions for your accounting specialist, and the beginning of the warranty period.

Technologies & integrations

What we build on and what it connects to

Stack

  • CommerceML is a native 1C and BAS download format. Limitations: in the customized configuration, the composition of the fields is often changed
  • XML and CSV of arbitrary structure. Limitations: editing the export on the accounting side breaks the analysis, so we fix the format
  • REST API — when you need near-real speed. Restrictions: the load on the base grows, it is agreed separately
  • A queue of background tasks instead of a scheduler. Restrictions: the queue must be monitored, otherwise it stands quietly
  • OpenCart 3 and 4. Limitations: filling tens of thousands of items through the admin takes time out, so we go in batches
  • Next.js and PostgreSQL — when the exchange lives inside the application
  • Exchange journal. Limitations: Shows that the exchange worked, not that the data is correct
  • A copy of the site for test launch. Limitations: The copy is aging and requires updating

Integrations

  • 1C: Enterprise
  • BAS
  • export of the nomenclature
  • synchronization of prices and balances
  • transfer of orders to the database
  • KeyCRM
  • Nova Poshta — declaration number in the order
What's included

Complete list of work and what you get as a result

  • We draw up a diagram of the correspondence of the fields — nomenclature, characteristics, units of measurement, categories — and then the dispute "where should we go" is resolved by a document, not by memory
  • We fix a stable product key: reloading updates the card instead of creating another one next to it
  • We divide the fields into "main database" and "main site" - descriptions, photos and SEO fields are not affected by the exchange even when they are empty in the file
  • We set the export of goods, prices and balances on the schedule you set: every night or every hour
  • We write a rule for each change - new position, removed from sale, changed price, zero balance - so that none of them are processed silently
  • We list the units of measurement and packaging: the coefficient is in the scheme, not in the head of the manager
  • We connect the return of orders to the database when it is really needed: the buyer, the warehouse of the order and the delivery arrive in one document
  • We keep an exchange log: how many items were processed, how many were missed and why - you will learn about the stop from the log, not from the buyer
  • We run the exchange first on copies, then in dry mode on combat: it counts changes and writes to the log without recording anything
  • We pass the instructions separately to your accounting specialist; warranty period — 30 calendar days after acceptance
When this service isn't right

What's not included — so there are no surprises at delivery

  • Improvements in the accounting system itself are the area of ​​your 1C or BAS specialist
  • Bringing order in the nomenclature of the base: duplicates, empty fields, incorrect units of measurement
  • Licenses for the accounting system and its updates
  • Accounting issues: VAT accounting, documents, reconciliations
  • Integration with other accounting systems — we count separately
Who it's for

Situations where this service delivers results

Scenario 1 of 4

In the database there is a nomenclature with characteristics, and on the website - a flat list

Size, color, length, packaging live in the database as separate values, they arrive on the site by name in one line, and there is nothing to filter by. The exchange distributes them by card attributes. This is where the most frequent pitfall of units of measurement emerges: the base keeps a pack of 12, the site sells by the piece, and without the coefficient in the scheme, the price on the site turns out to be twelve times higher than the real one.

We'll review your situation in a free audit
One stream from the base to the site versus a round trip

How this option differs from the alternative

Bilateral exchangeOur approach
What movesthe same plus orders and counterparties back to the baseproducts, characteristics, prices, balances — from the base to the site
Who should be involved?also an accountant: counterparty, composition, statuses of documentsa specialist accompanying the base
What breaks most oftenadditionally — the order that was changed on the website after transferchanging the composition of the fields in export
How long does it last?plus a separate thread with a run-through and its own testingshorter path: parse, scheme, copy, run
When is enoughdozens of orders per day and reprinting eats up working timethere are few orders and the manager reviews them all the same
Free audit

Free analysis of export from the accounting system

We ask you not to describe the exchange of words, but to send the actual export. In half a day, everything can be seen from the file: how many items, which fields are filled, whether there are characteristics and how the product is identified. Without it, any given amount would be a fiction.

What we measure

  1. How the product is identifiedArticle number, code or internal database identifier. The most important issue of exchange: with an unstable key, each download gives birth to new duplicates of goods on the site.
  2. How many items and how they are structuredThe nomenclature with characteristics, units of measurement, and packaging is laid out differently on the site than a simple flat list, and it takes a different amount of time.
  3. Which fields are actually filledOften there is a price and balance in the database, but no description, photo and category. This is normal - it just determines what the exchange brings, and what will have to be kept on the site.
  4. Direction of exchangeOne-way export of goods and balances or two-way with the return of orders to the base. The second is more complicated and requires coordination with your accountant.
  5. Update frequencyOnce a day, hourly or in near real time. The architecture depends on this: file exchange according to the schedule or task queue.
  6. Who accompanies the base from your sideThe exchange is always two-way organizationally: someone from the accounting side has to agree on the format and be in touch during the launch.

What you get

  • Analysis of the file: how many items, which fields are filled, how the product is identified.
  • Exchange scheme: what comes from where, in which direction and how often.
  • List of risks - places where the exchange can create duplicates or erase data on the site.
  • Assessment of work by stages and a 40-minute conversation with your accounting specialist.

Timeline: 3-5 working days after receiving the download file

Why is it free

Because the difference between the net export and the base in which the same product is introduced three times is different projects. You can see it only in the file, and no one will see it in less than half a day.

What's next

After analysis, we give an estimate by stages. If it is clear from the file that the nomenclature must first be put in order, we will say so directly, in the contract, and the document will remain with you in any case.

Short form: your contact and site URL

Did not find your case?

Describe how it works on your side — we will tell you whether “Site integration with 1C / BAS” fits and what it means in your situation. No brief and no call: one question, one answer.

Contract and paperwork

We work officially

Contract, act and invoice — for every project, not just large ones.

Trusted by6 brands

Trusted by: Kvant Energy, GYPSUN, Naturel Cosmetics, Pancer Protection, LUGI, BeeTech

Terms fixed in writing8 points

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

We sign NDAs on request. After completing the work, we delete our access to your services ourselves.

What affects the price

Why two seemingly identical tasks are priced differently

  • What exactly does your base give?The finished CommerceML download is half the work done before us, because it is formed by the accounting system itself. Arbitrary XML or CSV, which someone once added for a specific task, has to be analyzed field by field and fixed in a document, otherwise the next edit in the database will silently break the exchange.
  • The structure of the nomenclatureA flat list of articles with price and balance is placed on the site almost verbatim. Nomenclature with characteristics, packaging and several units of measurement requires a separate breakdown into attributes and conversion factors — and this is where the project grows most noticeably.
  • State of the identification keyWhen the article is unique and filled everywhere, the comparison is made in a day. Empty articles and duplicates mean that the directory was manually checked before programming - otherwise, the exchange will simply move the duplicates to the catalog and add new ones.
  • Direction and number of flowsProducts, prices and balances per site — one stream. The order back to the base is the second, and it entails the reconciliation of counterparties and statuses with your accountant. Each thread is tested and broken separately.
  • Frequency and volume of exportSeveral thousand items can be completely refilled every night. At tens of thousands, portions are required, transmission of only changed items, and dilution of the exchange with peak hours—in the 55,321-page catalog we measured, heavy prime-time exchange would be felt immediately.
Cases

Tasks and results in numbers — all metrics measured by us

G-Shop (магазин Husqvarna)

online store of an official seller of garden equipment and spare parts

Task
Keep a catalog of spare parts for tens of thousands of items on the website with prices and balances maintained by the accounting system, and do not update them manually.
Solution
Store on OpenCart 3 with a catalog up to four levels deep and a site map divided into submaps of 3,000 addresses. The exchange with the accounting system for balances and prices is declared in the project card - that is the scenario for which this page is being written.
Result
Measured on 07/31/2026. 55,321 product pages - the number was actually checked by sub-maps: the first and tenth contain exactly 3,000 addresses each, the nineteenth contains 1,321. Plus 3,868 category addresses, a total of 59,189. First server response 840.5 ms, full download 997.4 ms with 454.5 KB of HTML. The limit, which we call directly: the exchange itself is not checked from the outside. We measured catalog and speed, not the fact of synchronization, and do not mistake one for the other.
What we need from you

We can't start without this — best to prepare in advance

  1. The actual download file from your database is the file itself, not the description in words.
  2. Answer how the product is identified: article number, code or internal identifier.
  3. A list of what is maintained by the database and what is maintained on the site — so that the exchange does not obscure anything.
  4. The required frequency of updating prices and balances: day, hour or event.
  5. A communication channel with a specialist who supports your accounting system.
  6. Agree to deploy a copy of the site to test the exchange prior to combat launch.
If something is missing — let us know, we'll help you gather it or do it as a separate task.
FAQ

Most frequently asked questions — with concrete answers

Where does the integration with the accounting system begin?

From a file, not from a conversation. The description in words almost always differs from what is actually in the base: a person remembers how he planned, and not how it was finally started. Half a day with real export gives an accurate picture - how many items, which fields are filled, whether there are characteristics, how the product is identified. That's why we do the analysis for free and ask for the file itself, not a table with a description of the fields.

Why is the identification key so important?

Because everything else rests on it. When an item is identified by a volatile value—say, a name that the manager periodically edits—each load creates a new card instead of updating the old one. A month later, there are two identical products in the catalog, the balance is spread between them, and the search shows both. Removing such duplicates then does not add anything to the traffic, it just stops scattering it - so it is cheaper to fix the key at the parsing stage.

Will sharing erase our descriptions, photos, and SEO fields?

It will not be erased if it is written in the scheme. The outage looks like this: the description database does not work, the exchange unloads an empty field, the site obediently records the emptiness — and hundreds of cards remain without text. Therefore, at the start, we divide the fields into "leading base" and "leading site": the second exchange never touches, even when they are empty in the download. Separation takes half a day of talking at the circuit stage; recovery of erased descriptions never takes so long.

In the database, the goods are in packages, but we sell individually - is this a problem?

This is a normal situation, but it must be recorded with a number. If the base keeps the nomenclature in packs of 12, and the site sells in pieces, the scheme shows the conversion factor separately for the price and separately for the balance. Without it, the price on the website will be twelve times higher, and the balance will be just as less, and you will notice this already from the complaints. The same applies to weight and volume, if they are included in the shipping calculation.

One-way or two-way exchange - what to take?

Our recommendation: first one thread from the database to the site, and two weeks on live data. During this time, all the discrepancies in the directory will be ironed out, and they will be ironed out cheaply. Connect the order back with the second stage, when the first flow is already stable. In reverse order, you're sorting through the matching errors and the order transfer errors at the same time, and you don't know which one is whose. Plus, the two-way exchange drags the accountant: under which counterparty the new buyer falls and what to do with the order, which was then changed.

How often to update prices and balances?

As much as the business needs, not as much as the equipment can withstand. The slow assortment lives on a daily update at night. Running requires hourly or queued events. The fair limit of the mechanism: there is always a window between two exports in which the last unit can be bought twice - the exchange narrows this window, but does not close it. Each frequency increase loads both the database and the site, so we take the minimum frequency that solves your problem.

After the exchange, will the balances on the site become accurate?

As accurate as they are in the database. The exchange does not correct the account — it quickly and accurately transfers its status to the site. Reassortment, unexecuted write-off, goods that physically left without a document — all this will come to the site along with the rest. Therefore, during the analysis, we ask not only about the file format, but also about the extent to which the residues in the database agree with the composition. When the disagreement is large, it is fairer to deal with it first.

Is it possible to test the exchange risk-free for the combat site?

Yes, and we always do it in two steps. First, a copy of the site: the exchange runs on it, we compare the number of items, prices and balances with the database. Then the dry run is already in full swing - the exchange calculates what would have changed and writes in the journal without writing anything down. It is the dry run that catches an incorrectly chosen key: if the "will be created" report shows a number close to the size of the catalog, it means that the site is going to start all the products again.

What will happen when updating 1C or the site itself?

The exchange will have to be completed - it's "when", not "if". The composition of the download in the database changes, the data structure changes when the platform is updated, and the connection stops converging. Therefore, exchange is an ongoing support cost, and we say this before the contract, not after. Rule of thumb: before any update from either side, the exchange is first run on a copy. The documentation that we transfer is needed for this day, not for the archive.

Send a real upload from your base.

In response, the analysis of the file, the exchange scheme, the list of risks and the evaluation of the works by stages. If it is clear from the file that the nomenclature must first be put in order, you will hear about it in the very first letter.

From measured casesMeasured on 07/31/2026

View cases
  • Reply within 2 hours
  • No commitment
  • We work under a contract

There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.