• Online Stores

Integration of an online store with 1C: prices, balances and orders without manual work

The integration of an online store with 1C or BAS begins not with a code, but with a common key: the code of the nomenclature or article, according to which the position on the site clearly corresponds to the position in the accounting. There is no key, no trade-in, and no mod will get around it. Next comes the tech: prices and balances per site on a schedule, order to account, back statuses, crash log and retry instead of silent data loss. The catalogs we measured in this class hold between 1,848 and 55,321 product pages, and the exchange frequency on these volumes varies. There is no value here on purpose - we first look at your actual discharge.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
From what everything is held
common key: item code or article on both sides
Price
after a free audit
Guarantee
30
days after project sign-off
From what everything is held
common key: item code or article on both sides
The upper limit of the catalog was measured
55,321
product pages and 3,868 categories — 59,189 addresses
The first answer in this volume
840.5
ms with an HTML weight of 454.5 KB, measurement 07/31/2026
Measured lower limit
1,848
cards in 138 categories, 1,992 addresses without duplicates
Setting period
10-25
working days from the approval of exchange directions
Before the estimate
free export audit, 3-5 working days
Process steps

Transparent stages with approval at every step

Total duration:10–25 days

  1. Reconciliation of directories and collation key

    2-4 working days

    We take your download and the site catalog, count the items on both sides and find common articles. Here it usually turns out that there is one number of goods on the site, another in the account, and there are fewer common articles than both. We give you the list of discrepancies - you will have to close it from the accounting side.

  2. Field mapping and test circuit

    2-5 working days

    We divide the fields of your file into store fields: key, name, price, balance, category, unit of measurement. We pick up a copy of the base and make the first run on it. The exchange does not enter the live store until the copy is cleared.

  3. Prices and balances on the site according to the schedule

    1-4 working days

    We start the first direction and set it to cron. Here we agree on the rules: what to do with a zero price, a negative balance and a position that has disappeared from export. Silently ignoring such cases is the most expensive possible behavior.

  4. Order to account and statuses back

    3-6 working days

    The second direction: the order with the buyer, warehouse, delivery and comment is recorded, the status is returned to the site. We drive through - from the basket to the document in the accounting and back to the page of the buyer's order.

  5. Log, Alert, Retry

    1-3 working days

    Each run writes to the log: time, number of processed items, error text. The crash sends a message and repeats instead of going away. Separately, we check that two launches do not overlap each other, when the previous one did not have time to complete.

  6. Acceptance, documentation, transfer

    1-3 working days

    A week of exchange works under the supervision of a live store. After that - documentation, instructions separately for the manager and separately for the accounting person, the transfer of accesses and the beginning of the warranty period.

Technologies & integrations

What we build on and what it connects to

Stack

  • OpenCart 4.x is set by default
  • OpenCart 3.x — when the exchange module does not have a build for 4.x; we fix the version before the start
  • XML of the standard exchange format — it is given by the accounting system itself; limitation: the structure is often different in the added configuration
  • CSV — tolerant of skewed data; limitation: does not pass multiple price ranges and price types without column agreement
  • cron - limit: runs overlap, so exchange is blocked for runtime
  • PHP and MySQL — limitations: uploading a large directory through the admin fails due to the timeout, so the processing is done in portions
  • Exchange log with time, number of items and error text
  • Test circuit on a copy of the base - limitation: the copy gets old, it is updated before starting

Integrations

  • 1C
  • BAS
  • exchange of prices and balances
  • export orders
  • returning statuses
  • Nova Poshta
  • LiqPay
  • WayForPay
  • non-cash VAT settlement
  • Google Tag Manager
  • GA4
What's included

Complete list of work and what you get as a result

  • We compare the accounting nomenclature with the site catalog using a common key - after that, each product has an unambiguous correspondence in the accounting, and not a "similar name"
  • Set up price and balance export on a schedule: nightly or hourly, depending on how fast your warehouse moves
  • We connect accounting price types with buyer groups on the site — retail, wholesale and dealers see their price without manual switching by the manager
  • We transfer the order from the site to the account along with the buyer, the composition of the order, the method of delivery and a comment - the manager stops reprinting
  • We return statuses from accounting to the site, if your process requires it: the buyer sees "collected" or "sent" without calling the company
  • We keep a log of the exchange and send a failure message with a retry - you will learn about the stop from the notification, not from the buyer
  • We prescribe rules for extreme cases: the product has disappeared from the account, the price is zero, the balance is negative, the position is in the account and is not on the site
  • We do portioned export and exchange of only changed items - in a large catalog, this is the difference between an exchange in minutes and an exchange that does not have time for the next launch
  • We chase the first exchange on copies of the base, not on a live store: a mapping error costs a rollback of a copy, not calls to customers
  • We write exchange documentation: what, where, when, by what key and what to do when it stopped
  • We pass the work to two people separately: instructions for your manager and instructions for the person who keeps records
  • Terms of work: 50% advance payment, warranty period of 30 calendar days after acceptance
When this service isn't right

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

  • Finalizing the configuration of the accounting system is the area of ​​your accounting specialist
  • Bringing order in the accounting nomenclature: duplicates, missing articles, inconsistent units of measurement
  • Licenses and updates of the accounting system
  • Accounting support
  • Hosting, domain, acquiring
Who it's for

Situations where this service delivers results

Scenario 1 of 5

The manager transfers the prices from the account to the site every morning

The supplier raised the price, it was changed in accounting, it is old on the website until the evening - or until Monday. Every order in this window is at the old price, and you pay the difference. Exchange closes the window itself. An honest limit: it will not make your accounting more accurate - if you have not changed the price in accounting, the site will show the old one.

We'll review your situation in a free audit
Automatic exchange versus manually updating the price

How this option differs from the alternative

The manager updates manuallyOur approach
Delay between the price change in the account and on the websitefrom a few hours to a week - depends on the workload of the managerthe schedule you set: hourly or daily
Stockare updated when someone mentions themare drawn from the account along with zeros and negative values
Ordertranscribed by hand, with typographical errorsare registered with the buyer, order warehouse and delivery
Launchingthere is no need to start anything - the work is already paid for by the manager's salarya separate project for 10–25 working days
What breaksnothing breaks: the data just quietly becomes obsoletethe exchange stops and writes to the log - the failure is visible the same day
Data requirementsworks on any data, because man is a beasteach item must have a unique article number
Free audit

Free audit before setting up exchange

The exchange breaks down not on the code, but on the disagreement of the directories: in the accounting there is one nomenclature, on the website another, and there is nothing to connect them. The audit verifies exactly this - before we agree on the work and name the amount.

What we measure

  1. Mapping keyIs there a common field in the account and on the website — the nomenclature code or article number. Without it, exchange is basically impossible, and it's the first thing we look at in your file.
  2. Download formatWhat exactly does your system output: standard exchange format XML, arbitrary XML, CSV or manual upload. Half of the labor intensity of the project depends on this.
  3. Exchange directionsWhat and where should go: prices and balances on the site, orders in the account, statuses back. Each direction is a separate volume of work and separate testing.
  4. State of the nomenclatureHow many items, how many duplicates, how many without an article number. In the catalogs of this class measured by us, there are from 1,848 to 55,321 product pages, and each volume has its own requirements for the frequency of exchange.
  5. Update frequencyHow quickly balances and prices move. Hourly and daily exchanges are different workloads, different decisions and different deadlines.
  6. Who is responsible for accountingIs there a person who will set up the export on your side. Without it, the project will stop, and it is better to know about it before the start, and not in the third week.

What you get

  • Conclusion, whether it is possible to exchange your data and according to which mapping key.
  • A description of exchange directions with an estimate of the volume for each one separately.
  • A list of nomenclature issues that must be closed before the exchange is launched.
  • A conversation for 30–40 minutes on the document, where we show what is critical and what will wait.

Timeline: 3-5 working days - you need to see the actual export, not its description

Why is it free

Because exchange is the task where "we thought it was simple" costs the most. It is cheaper to see the actual export in a few days than to discover in the third week that there are no articles in the account. The document remains with you in any case - even if we do not make the exchange.

What's next

After the audit — the amount and term by stages with dates, contract, invoice, report. If the exchange of your data is not possible, we will say so directly and offer an easier import of the price according to the schedule.

Short form: your contact and site URL

Did not find your case?

Describe how it works on your side — we will tell you whether “Online store with exchange with 1C or 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

  • Number of directions of exchangePrices and balances on the site — one direction and the shortest term. Plus the order to the account — the second. Plus the return of statuses is the third. Each adds its own testing and its own set of edge cases, and this is where the estimate gets stretched the most.
  • Download formatXML of the standard exchange format is half of the work done before us, because the accounting system itself knows how to give it. Arbitrary XML or an upload that someone once wrote for himself has to be analyzed field by field.
  • State of the nomenclatureThe catalog, where each item has a unique article number, is compiled per day. Duplicates, empty articles, and different units of measurement make reference reconciliation the longest step—and it's done before programming, not after.
  • Volume of the catalog and frequency of exchange1,848 cards can be completely unloaded every night. At 55 thousand, portioned export and transfer of only changed items is required, and this is a different amount of work and other requirements for the server.
  • Complexity of prices and warehousesOne price and one composition is a simple case. Retail, wholesale, and dealer price types, multi-warehouse balances, backorder reserves—each level adds matching rules that must be described and verified.
  • Who is responsible for accountingA full-time 1C specialist significantly shortens the deadline: the issue is resolved in an hour, not a week. Without such a person, pauses appear in the schedule that we have no control over.
Cases

Tasks and results in numbers — all metrics measured by us

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

Task
Maintain a catalog of machinery and spare parts with deep nesting of categories, filters by engine power and type, and up-to-date balances and prices from the accounting system.
Solution
Store on OpenCart 3.x with parts catalog up to four levels deep. In the project card, the exchange with the 1C accounting system for balances and prices is declared - it is not checked from the outside, so we present it as declared, and not as a fact measured by us. Eight payment methods, including cashless with VAT and payment by IBAN, four delivery options.
Result
The measured scale of the catalog as of 07/31/2026: 18 subcards of 3,000 addresses plus 1,321 in the nineteenth — 55,321 product pages, another 3,868 category pages, a total of 59,189 addresses. TTFB 840.5ms, full HTML load 997.4ms at 454.5KB: The slowest first response in our sample, which for 55k items is expected. The sitemap is explicitly declared in robots.txt. Separately fixed PHP 7.3.33 - unsupported as of December 2021.

Viola

wholesale store of underwear with a catalog of more than 13 thousand items

Task
Give the wholesale buyer a selection of sizes and colors within the model and wholesale prices by tier.
Solution
Store on OpenCart, eight payment methods are described both in the text and in the markup via acceptedPaymentMethod. There is no online payment deliberately, and the reason is written directly on the website: so that the buyer does not pay for the product that is not available.
Result
13,428 product pages and 161 categories — 13,590 addresses in the sitemap, of which there is only one duplicate. TTFB 289 ms. The case is valuable from the opposite: the lack of reliable balances cost the store an entire payment channel. Caveats from the same measurement 07/31/2026: The main HTML weighs 751.2 KB — the heaviest document among the 16 sites we measured.

B2B catalog of spare parts for industrial sewing machines

Task
Let the technician find the part by code or equipment model.
Solution
Catalog on OpenCart with a selection of parts by machine model and technical diagrams, cashless payment without VAT and upon receipt of the goods at the carrier's warehouse.
Result
1,848 cards and 138 categories — 1,992 addresses in the sitemap without a single duplicate, TTFB 388.1 ms at 120.2 KB HTML, measured 07/31/2026. The lower limit of the catalogs of this class that we measured: here, full export takes place every night without portioning. Defect found: Universal Analytics still lives in the markup, disabled by Google on July 1, 2023.
What we need from you

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

  1. An example of a real download from your system is a file, not its description.
  2. Mapping key: A nomenclature code or article number that exists on both sides.
  3. The contact person who is responsible for the accounting and can set up the export on your end.
  4. Description of the order process: who processes it, what statuses you have and what the buyer should see.
  5. Access to the site and hosting, including the task scheduler.
  6. Decision on exchange frequency: daily, hourly or per event.
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 exchange begin?

From the mapping key. There must be a field according to which the product on the website clearly corresponds to the position in the account: the nomenclature code or article number. On the store side, it's technically a separate card field, and needs to be locked before launch — then switching the key means reflashing the mappings across the entire catalog. If the articles in the accounting are not filled in everywhere or are duplicated, the exchange will start to confuse the items, and no code will fix this. Therefore, the audit begins with this inspection, and not with the discussion of the schedule.

One-way or two-way exchange - where to start?

Our recommendation: first one direction, prices and account balances per site. Let him work for two weeks on live data - during this time all the differences of the directories will be out, and they will be out cheaply. Connect the order to the account in the second stage, when the first direction is already stable. Doing so takes longer on paper and is faster in reality: in reverse order, you're sorting through matching errors and order transmission errors at the same time, and it's not clear which is which.

How often to update balances?

As often as how fast they move. For a catalog where items are sold individually and rarely, nightly exchange is sufficient. An hourly one is required for the running range. The fair limit of the mechanism: there is always a window between two exports in which the same last unit can be bought twice - the exchange narrows this window, but does not remove it. Constant synchronization in real time sounds attractive and creates a load that, on a large catalog, noticeably affects the speed of the site.

Will the balances on the site be accurate after the exchange?

As much as they are accurate in accounting. The exchange does not correct the account - it transfers its status to the site quickly and accurately. If in the accounting there is a resort, unrepresented write-offs or goods that have physically gone, but the document has not been issued, the site will show exactly that. Therefore, during the audit, we ask not only about the file format, but also about how many catalog items are actually available. When the discrepancy between accounting and inventory is large, it is fairer to deal with it first and then automate.

What happens when the exchange breaks?

It will break - sooner or later, because something will change in the accounting. The only question is whether you find out about it from the magazine or from the buyer to whom you sold the missing product. Therefore, the work includes a log with the time and number of processed items, a failure message and a retry. Separately, we make sure that the two runs do not overlap: if the night exchange did not finish before the morning one, they will go parallel without blocking and start overwriting the same items. A silent failure is the most expensive scenario of all.

We have 50,000 items — will the exchange pull?

It will extract, but it is necessary to unload in portions and only what has changed, and not the entire catalog every time. The garden equipment and spare parts store we measured, whose card claims an exchange with an accounting system for prices and balances, holds 55,321 product pages and 3,868 categories — 59,189 addresses together. The first response from the server there is 840.5 ms: for such a volume, this is expected, and that is why heavy exchange cannot be set for peak hours. From the outside, the exchange itself is not checked, and this should be said directly, but the scale of the directory shows that the task is working.

How long does setup take?

10–25 working days depending on the number of destinations and the status of the inventory. Usually, it is not programming that takes the longest, but the reconciliation of directories: when it turns out that there is one number of products on the site, another in the account, and there are fewer common articles than both numbers. This work is done once, and it is better to do it before launch. The second stage in terms of duration is the order in the account with backward statuses, because it has to be run through several times.

Who completes the configuration of 1C - you?

No, and this is fundamental. We work with what your system gives to the outside: an upload file or protocol exchange. Everything inside the configuration — new requisites, changing the composition of the export, rules for forming the price — is done by your accounting specialist. The reason is simple: a third-party contractor comes into your configuration with the risk of breaking what works, and the responsibility for accounting remains yours. At the audit, we immediately check whether there is such a person: without him, the project stops at the very first question before export.

What will happen when updating 1C or the store platform?

The exchange will have to be completed - and it's not "if", but "when". The composition of the export in the accounting system changes, the structure of the database changes when the store is updated, and the connection between them ceases to coincide. So trade-in is an ongoing support cost, not a one-time purchase, and we're saying this before the contract, not after. Practical: before any update from any side, the exchange is first run on the copy, and only then on the live store. The documentation we give is needed for this particular day.

Demo

Your catalogue on a phone screen

This is how your store can look on a phone: a collection banner, popular products and a cart one tap away. Tap “Add to cart” and the counter in the header updates, just like in a real store.

  • Collection bannerThe first screen shows what is new, not a logo.
  • Product cardsPhoto, price and a button — no extra page to open.
  • One-tap cartThe counter in the header updates instantly, like in a real store.
Stores in the portfolio
This is a demo interface, not a client's store. Live projects are in the portfolio.
SHOP
New collectionAutumn / WinterExplore
PopularAll products ›
  • Essentials Hoodie1 290 ₴
  • Urban Backpack1 490 ₴
  • Classic Cap690 ₴
  • Basic Tee590 ₴
  • Street Sneakers2 390 ₴
  • Active Shorts890 ₴

Please send an example of a real download from your system.

In response, whether it is possible to exchange your data, by which key, which directions, and how long it will take in stages. If you don't need an exchange right now, let's say it directly and offer a simpler price import.

From measured casesThe measured scale of the catalog as of 07/31/2026: 18 subcards of 3,000 addresses plus 1,321 in the nineteenth

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.