Syntha Lab RU

Systems landscape and data exchange

PLM, ERP, warehouse, orders, POS, CRM, BI and e-documents: who owns which record, how often exchange is needed and what a stale stock figure and a paper document cost.

both Processes and data

Open interactively →

About the topic

A system landscape is a map of where data lives in the company and how it moves between systems. Typically these are PLM or tech-pack files for development, ERP for purchasing, cost and finance, a warehouse system, an order system, a till, CRM and BI; outside are connected electronic document exchange and a labeling system. Each is good at its own job, and the problems arise at the borders: stock updated in the warehouse but did not reach the site; the price in the till is new and in the card old; a document went on paper because the counterparty has no roaming set up.

Why it matters to a brand or retailer. Sales, returns, reports and taxes depend on whether records in different systems match and how fast they update. The decisions taken here: which system is the master for each reference, how often stock and prices must be exchanged, what to automate first, whether to move from paper to electronic documents and what to do when an exchange fails.

The logic rests on three rules. First: each reference has one system of record. The edit is made there and others receive a copy. If the same field is edited in two places, at some point they diverge and the right value can be found only by hand. Second: a single key. If a SKU has one code in the accounting system and another on the platform, every exchange becomes matching by name, and that breaks at the first typo. Third: an exchange has a schedule and a log. The schedule sets the price of delay: the rarer the exchange, the more orders sell what is already gone. The log shows a failure before customers report it.

Where to start. List the systems and who runs them; for each reference name the system of record; check that the SKU key is the same everywhere; build the schedule for exchanging stock, prices and orders. Then count two things: what stale stock costs and what electronic document exchange saves. These two numbers usually set priorities well because they show roubles, not convenience.

What not to do: buy a system without describing the process and the data owner; exchange data without a single key; fail to test electronic document roaming with the counterparty before the first send; treat stock on a platform as correct without regular reconciliation; keep no exchange log. There is no universal set of systems: a small brand is fine with an ERP and a simple exchange, while a chain of stores and platforms usually needs a separate catalog and warehouse.

Key ideas

Who owns which reference

Example split: PLM owns composition and tech pack, ERP owns cost and purchasing, warehouse owns physical stock, the order system owns the price on the platform, CRM owns the customer profile. If the price is edited both in the ERP and on the site, within a week they diverge. The owner is chosen not by convenience but by where the record is created and verified first.

The price of stock-exchange delay

Illustrative example: 1,200 orders a day, 6% on SKUs with low stock, that is 72 orders; in a day without update 15% of such orders hit an already sold unit. With an exchange every 6 hours (a quarter of a day) that is about 72 × 0.15 × 0.25 = 2.7 conflicts a day, 81 a month and at 450 roubles per conflict 36,450 roubles. With an hourly exchange: 13.5 conflicts and 6,075 roubles. The gain is 30,375 roubles a month; if frequent exchange costs 25,000, it pays back only with a small margin.

Electronic documents versus paper counted in hours and errors

800 documents a month, by hand 25 minutes per document, in electronic exchange 4 minutes. By hand 800 × 25 ÷ 60 ≈ 333 hours, electronic about 53 hours, saving 280 hours; at 450 roubles an hour that is 126,000 roubles a month. The share of documents with errors drops, say, from 6% to 1.5%: 48 versus 12 documents a month, 36 fewer returns and rework. There is further gain in payment and receiving speed.

Reconciling three stocks: ledger, warehouse, platform

We checked 400 lines (a size and color in one place), 280 were exact: line accuracy 70%. By value: surpluses 85 thousand roubles and shortages 310 thousand against book value 4.2 million; sum of absolute values 395 thousand (9.4%), net −225 thousand (−5.4%). The net hides that errors go both ways, so look at both.

An exchange failure must show within hours, not days

If the exchange stopped and nobody noticed for a day, in the example above the conflict risk grows to 72 × 0.15 = 10.8 a day, about 4,860 roubles for every day of silence. An exchange log and an alert for a missed cycle cost less than a few such days.

How to work through it

  1. List all systems, who runs them and which data they hold.
  2. For each reference (product, price, stock, customer, document) name the system of record.
  3. Check the single SKU key in all systems and in exchange with platforms.
  4. Build a schedule for exchanging stock, prices, orders and documents and name the person responsible.
  5. Count the price of exchange delay and decide whether more frequent exchange is needed.
  6. Count the gain of electronic documents against paper and test roaming with key counterparties before the first send.
  7. Introduce an exchange log and alerts for missed cycles and errors.
  8. Once a week reconcile stock between systems and record discrepancies.

Where to start

1) List the systems and who runs them. 2) Name the system of record for each reference book. 3) Check that the SKU key is the same in all systems. 4) Draw up the schedule of exchange of stock, prices and orders. 5) Calculate the price of the exchange delay. 6) Calculate the benefit of e-documents against paper. 7) Reconcile stock between systems once a week. Calculations of the topic in order: “Stock sync latency: the price of stale data”, “E-documents against paper: document time, errors and money”. See also (their primary topic is another one): “Stock record accuracy and the cost of mismatches”.

Calculations in this topic

  • Stock sync latency: the price of stale data

    From the number of orders, the share of orders on low-stock SKUs and the sync interval calculates how many orders a month sell what is already gone, what it costs and whether more frequent refresh pays back.

    What stale stock on a channel costs and whether more frequent refresh pays back.

  • E-documents against paper: document time, errors and money

    Compares paper and electronic exchange of transfer documents, acts and waybills: hours and roubles a month for handling, errors and delivery and the effect of faster document flow on payment.

    How many hours, errors and money electronic exchange saves against paper.

  • Stock record accuracy and the cost of mismatches

    From a sample count it calculates record accuracy by lines and by value, the net balance of mismatches and estimates the lost revenue from “phantom” stock: an item is on record but not on the shelf.

    How far stock records match reality and what the mismatches cost.

Self-check questions

  • Which system is the master of each reference and how often does the exchange run?
  • Is the SKU key the same in the ledger, warehouse, till, site and platforms?
  • How many orders a month sell what is already gone and would more frequent exchange pay back?
  • How many hours and roubles a month does electronic exchange save against paper?
  • Is electronic-document roaming with key counterparties tested and who is responsible for setup?
  • Does stock match in the ledger, warehouse and platform and how often is it reconciled?
  • What happens to orders and stock when an exchange fails and how soon will you notice?
  • Who may change data in each system and how are changes recorded?

Knowledge check

Multiple-choice questions. The correct answer and the explanation follow each question.

  1. What does the “owning system” of a reference book mean?

    • A. The most expensive system into which all data is loaded
    • B. The one system where a record is kept and corrected; the others receive a copy on a schedule
    • C. The system with the most users
    • D. Any system where the error was noticed first

    Correct answer: B. The one system where a record is kept and corrected; the others receive a copy on a schedule. There is one owner per reference book: the record is kept and corrected there, the other systems receive a copy on a schedule, and two truths do not arise. Price and the number of users do not decide the role; an edit where the error was noticed creates a mismatch until the owner is corrected.

  2. A channel gets 600 orders a day, 10% of them on low-stock SKUs; during a day without a refresh 25% of such orders hit an already sold unit. How many orders a day are sold beyond stock when stock is synced every 6 hours?

    • A. 15
    • B. 60
    • C. 90
    • D. 3.75

    Correct answer: D. 3.75. For a one-day delay: 600 × 0.10 × 0.25 = 15 orders. At a 6-hour interval we multiply by min(1; 6 / 24) = 0.25: 3.75 orders a day. 15 is the conflicts at a one-day delay, 60 is the low-stock orders without the conflict share, and 90 comes from multiplying 15 by the interval instead of dividing it by 24.

  3. A channel: 800 orders a day, 5% on low-stock SKUs, 20% conflicts per day of delay, one oversold order costs RUB 300, a month has 30 days. The sync every 12 hours can be sped up to 3 hours for RUB 20,000 a month. What comes out?

    • A. It pays back: savings of RUB 27,000 against costs of RUB 20,000, net +RUB 7,000 a month
    • B. It does not pay back: savings of RUB 9,000 against costs of RUB 20,000
    • C. It pays back: net +RUB 16,000 a month
    • D. It pays back: net +RUB 52,000 a month

    Correct answer: A. It pays back: savings of RUB 27,000 against costs of RUB 20,000, net +RUB 7,000 a month. At a one-day delay 800 × 0.05 × 0.2 = 8 orders. At 12 hours 8 × 12 / 24 = 4 orders: 4 × 300 × 30 = RUB 36,000 a month; at 3 hours 8 × 3 / 24 = 1 order: RUB 9,000. Savings 36,000 − 9,000 = RUB 27,000, less costs of RUB 20,000 gives +RUB 7,000. “Savings of RUB 9,000” is the remaining loss taken for savings; +RUB 16,000 comes from counting all current losses as savings (36,000 − 20,000); +RUB 52,000 from taking the losses at a one-day delay (72,000) instead of at 12 hours.

  4. There are 500 documents a month. By hand a document takes 30 minutes, in e-documents 6 minutes, an employee hour costs RUB 400. Errors occur in 5% of paper and 1% of electronic documents, fixing takes 30 minutes. Paper delivery is RUB 100 per document, the operator fee is RUB 20 per document. How much do e-documents save a month?

    • A. RUB 134,000
    • B. RUB 80,000
    • C. RUB 124,000
    • D. RUB 155,000

    Correct answer: C. RUB 124,000. By hand per document: 30 / 60 × 400 = RUB 200 of time, 0.05 × 30 / 60 × 400 = RUB 10 of errors, RUB 100 of delivery, RUB 310 in all. In e-documents: 6 / 60 × 400 = RUB 40, 0.01 × 0.5 × 400 = RUB 2, RUB 20 to the operator, RUB 62 in all. Savings (310 − 62) × 500 = RUB 124,000 (about 210 hours). RUB 134,000 comes from forgetting the operator fee, RUB 80,000 from counting only the handling time (200 hours), and RUB 155,000 is the whole cost of paper exchange, not the difference.

  5. A customer order: 200 units at RUB 900. By the dispatch advice 190 units were shipped, but the supplier invoiced 200 units. What should be done and what is the amount of the mismatch?

    • A. Pay the invoice of RUB 180,000 and get RUB 9,000 back later
    • B. Do not pay until the supplier corrects the invoice: the mismatch is RUB 9,000 (10 units × RUB 900)
    • C. Pay RUB 171,000 and not tell the supplier
    • D. Accept the shipment as 200 units: the order matters more than the advice

    Correct answer: B. Do not pay until the supplier corrects the invoice: the mismatch is RUB 9,000 (10 units × RUB 900). The three-way match checks the order, the shipment and the invoice by quantity and price. Here the order and the invoice say 200 units, the shipment 190: the mismatch is 10 × 900 = RUB 9,000, the right amount to pay after correction is 190 × 900 = RUB 171,000. A mismatch is caught before payment: afterwards getting money back costs more; paying less silently creates a contract dispute; 200 units cannot be accepted without the fact of receipt.

Common mistakes

  • Mistake: Buying a system without describing the process and data owner

    What it costs: Expensive automation of disorder

    How to avoid: Process, owner and key first.

  • Mistake: Exchanging data without a single SKU key

    What it costs: Matching by names breaks

    How to avoid: Set up a common key and a mapping table.

  • Mistake: Not testing electronic-document roaming before the first send

    What it costs: The document does not arrive and payment is delayed

    How to avoid: Test send and an operator contact.

  • Mistake: Treating platform stock as right without reconciliation

    What it costs: Selling goods that are not there

    How to avoid: Regular reconciliation and safety stock.

  • Mistake: Keeping no exchange log

    What it costs: A failure is learned of from customer complaints

    How to avoid: A log and alerts.

Russia and the EAEU

In Russian practice the standard ERP configurations handle basic exchange of catalog, prices and orders with sites and platforms, while a single master catalog and a warehouse with orders are more often solved by a separate system or integration. Documents between counterparties travel through electronic document operators and roaming between them; signing requires a qualified electronic signature, and when a representative signs a machine-readable power of attorney (MChD) is used; check requirements and the list of operators against current tax service rules (checked 14.11.2026). The universal transfer document (UPD) and the corrective one (UKD) replace the delivery note and VAT invoice, and for labeled goods the document carries codes.

Cash registers work under Federal Law 54-FZ: the receipt goes to the fiscal data operator, and for labeled goods the code enters the receipt. This means the till system is also part of the landscape and must receive current stock and reference data. Personal data of Russian citizens under 152-FZ is recorded and stored in databases in Russia, so the choice of cloud CRM and services must be checked against this requirement. When replacing foreign software, allow time for data migration and parallel running of the old and new systems.

The scheme of owners and keys is universal, while differences lie in national document and cash-register systems. Reference, indicative as of 14.11.2026, check, check: Belarus and Kazakhstan use national electronic VAT invoice portals (ESCHF, ESF), each country has its own formats, obligation and deadlines; cash-register rules and the obligation to use online registers also differ. If you sell through platforms of several countries, one reference must carry several catalogs, currencies and languages, and the exchange must observe national requirements for data storage and labeling. For deliveries between union countries check which documents customs and the tax authority of the destination country accept, and set up roaming with the counterparty in advance.

Categories and audiences

Apparel
Apparel has the biggest reference: model, color, size, and stock must be kept by size. Exchange delay is especially costly on popular sizes: the last size is sold twice. Build the size scale and the SKU key before connecting new platforms.
Footwear
Footwear adds pairs and different size scales, and size returns require tying order, stock and return in one system. Fix the scale (EU, RU, Mondopoint) as a reference, otherwise one pair becomes two SKUs and stock doubles.
Accessories
Accessories have fewer SKUs, so a small brand often needs only a simple ledger-and-site link. But they have a high share of sets and gift items with their own code, and the exchange must pass set composition and write off components.
Kids
For children’s goods certificates and labeling matter, so the PLM or card must store documents and age attributes. Seasonal back-to-school peaks raise load on the exchange, so stock exchange frequency rises toward late summer and before New Year.
Men
In the men’s line the exchange with a marketplace has its own trap: if the system passes stock by size and not by “size x length” cell, trousers look unavailable on the site while the needed length is in the warehouse. And in BI the link to the predecessor model matters: without it the history of carried-over basics breaks when the code changes.
Women
In the women’s line, with frequent promotions a price error on a marketplace is costly: a dress can go at the old price for an hour before the exchange updates. So fix the rule (who changes the price, in which system and at what time) and tie the frequency of price and stock exchange to promotion days, not to an average day.

Questions this topic answers

  • Which system owns each reference book and how often does exchange run?
  • How many orders a month sell what is already gone and will more frequent sync pay back?
  • How many hours and roubles do e-documents save against paper?
  • Does the stock match in the records, the warehouse and the platform and how often is it reconciled?
  • What happens to orders and stock when an exchange fails and how soon will it be noticed?

Key measures and terms

Study first

What next

Next: “Data quality and data owners”, “Order data quality”, “Marking and trading leftovers”.

Documents on this topic

Open interactively →