Syntha Lab RU

Systems and data: 1C and ERP, PIM and MDM, BI, integrations (e-document exchange, marking, marketplace API), cost of ownership and data quality

The document describes what systems make up the IT landscape of a brand and a retailer, how to choose and implement an accounting system (1C, ERP, cloud services), how to make the product card a single source (PIM and MDM), how to build BI with agreed metrics and how to set up integrations with e-document exchange, marking, tills and platforms. It helps decide what to buy, what not to invest in and how to measure data quality.

Brand, customer, organisation Brand and retail Verified: 2026-11-14

Open interactively →

Why this document

Most “analytics problems” are data problems: the same product is called differently, stock does not match the till, the card has no composition, and marking requires codes. The most expensive implementation mistakes: choosing a system from a presentation without describing processes and data, and paying for customization of what could be configured. The document is read by the IT director, the finance and operations directors and process owners; it is needed to compare options by cost of ownership and to make sure every entity has an owner.

At a glance

What is this document and why is it needed?
The document describes what systems make up the IT landscape of a brand and a retailer, how to choose and implement an accounting system (1C, ERP, cloud services), how to make the product card a single source (PIM and MDM), how to build BI with agreed metrics and how to set up integrations with e-document exchange, marking, tills and platforms. It helps decide what to buy, what not to invest in and how to measure data quality.
Who owns the document and how often is it rebuilt?
The IT director or project head; requirements from the finance and operations directors and process owners; the decision is approved by the owner, architecture and dictionaries are revised once a year.
What mistakes are the most common?
A system is chosen from a presentation without describing processes → customization costs more than the license → first a functional map and a prototype on your data. Brand: keeps product descriptions in different files for platforms → discrepancies and fines → a single card in PIM and a completeness check before publication. Retail: moves dirty dictionaries into a new system → “garbage” migrates with the data → cleaning and common rules before migration.

For whom

Brand
The brand keeps PLM (product, specification, versions), PIM or MDM (product card), ERP (purchasing, production, finance), WMS and exchange with platforms and wholesale clients; the core of its landscape is tied to product and production, and sales come from several channels.
Retail
The retailer keeps POS and tills, stock accounting by store, CRM and the loyalty program, OMS and the site, exchange with suppliers and e-document exchange; the core of the landscape is tied to points of sale and stock, and the product dictionary comes from suppliers and must be brought to a single form.

What it consists of

Map of systems and data

  • Accounting and ERP: bookkeeping, purchasing, stock, production, finance; in Russia the core is often built on 1C (a standard or industry configuration, a cloud version) or on an integrator’s ERP; the main requirement is shared dictionaries and end-to-end accounting.
  • PLM: product, patterns, specification, versions and statuses; the approved version goes from PLM to ERP, not a file.
  • PIM and MDM: PIM stores the description and attributes of a product for the storefront and platforms (name, composition, photos, sizes), MDM watches the common dictionaries (SKU, SKU, price, counterparty) and the “golden record”.
  • WMS, OMS, POS: the warehouse (receiving, put-away, picking), orders of all channels, the till and returns; they must see the same stock and prices.
  • CRM and CDP: customer, loyalty card, consents, purchase history; linked to the till and the site by a customer identifier.
  • BI: a data mart and dashboards; fed from ERP, WMS, OMS, POS and advertising accounts; metrics are defined once and identically for all reports.

Choosing and implementing an accounting system

  • Functional map: processes (purchasing, receiving, stock, re-pricing, returns, commission, export/import, e-document exchange, marking, cost calculation) and requirements for each; items are divided into “must”, “important” and “later”.
  • Options: standard 1C with customization (cheaper and faster start, dependence on customization), a cloud service by subscription (fast, less control of data and processes), an industry ERP with an integrator (deeper, costlier, longer).
  • Cost of ownership (TCO) over three years: licenses, implementation, support, infrastructure, training and hidden customization costs; compare the present value, not only the first payment.
  • Stages: survey and description of processes, a prototype on your data, migration of dictionaries and stock, a pilot in one store or warehouse, training, launch, support; without a pilot an error becomes common.
  • Risks: data migration (dirty dictionaries), excessive customization, dependence on one contractor, schedule slips at the seasonal peak; a launch is not set for the peak of the season.

Data: card, dictionaries, quality, BI

  • The product card: a single set of attributes (name, composition, sizes, color, photos, code, marking, description) and a version; one card feeds the site, platforms and printed materials.
  • Data quality: completeness (are the mandatory fields filled), uniqueness (no duplicates), validity (format and allowed values), timeliness (data not older than the term); a total index with weights by importance.
  • Data owners: every entity (product, price, customer, counterparty) has one owner and rules of change; without an owner a dictionary grows and breaks.
  • BI: a star-schema mart (facts of sales, stock, orders and dimensions product, store, date, customer), common keys and metric definitions, dashboards by role, access rights and an update schedule.

Integrations

  • Platforms and the site: orders, stock, prices, statuses, returns; exchange through platform interfaces or an integrator; stock discrepancies are the main cause of fines and cancellations.
  • E-document exchange: UPD, invoices, acts, reconciliations; exchange with counterparties through an operator; check format and signature requirements in the current rules.
  • Marking: codes on goods, introduction into circulation, movement between warehouse and store, sale and return through the till; integration of accounting with the marking system, code discrepancies lead to blocked sales.
  • Monitoring: an exchange log, error alerts, resending, delay control; an integration without monitoring breaks silently.

What the brand does

  • Brand: starts with the product card and specification (PLM) and dictionaries of SKUs and SKUs; chaos here then multiplies in every system.
  • Brand: builds PIM for platforms and the site: a single card, templates by platform requirements, a completeness check before publication.
  • Brand: sets up exchange with wholesale clients (orders, pre-packs, ASN, reconciliation statements) and platforms; watches stock discrepancies across channels.
  • Brand: counts TCO and the payback of implementation as saved hours, fewer fines and faster collection release, not as “modernity”.

What the retailer does

  • Retail: starts with the till, stock accounting by store and a single product dictionary brought from suppliers to one form (names, sizes, colors).
  • Retail: links the till, CRM and the loyalty program by a customer identifier so that CRM coverage and end-to-end analytics work.
  • Retail: sets up e-document exchange and marking at the store level (receiving by codes, returns, stock-taking), trains staff and runs a pilot in one store.
  • Retail: builds BI by stores, categories and suppliers with common metrics (turnover, GMROI, full-price share) and data quality control.

Where the data comes from

Data sourceFields
Description of processes and requirementsfunctional map, process owners, volumes of documents and users
Dictionaries and product cardsSKUs, SKUs, attributes, photos, codes, marking; record counts and completeness
Contractor and vendor proposalslicenses, implementation, support, infrastructure, terms, customization conditions
Exchange and error logsmessage counts, errors, delays, stock discrepancies

How to build it step by step

  1. Step 1: Brand: describe the key processes and entities, appoint an owner of each entity (product, price, customer, counterparty).
  2. Step 2: Retail: build a functional map with the items “must”, “important”, “later” and volumes (documents a month, users).
  3. Step 3: Retail: assess the completeness and quality of current dictionaries (see the figure) and draw up a cleaning plan before migration.
  4. Step 4: Request proposals from 2-3 options and calculate the three-year TCO and the present value (see the example).
  5. Step 5: Brand: put PLM, PIM and exchange with wholesale clients and platforms into the requirements and the order of work.
  6. Step 6: Retail: put the till, stock by store, loyalty and e-document exchange with marking into the requirements and the order of work.
  7. Step 7: Make a prototype on your data and a pilot in one store or warehouse; check the reconciliation of stock and documents.
  8. Step 8: Brand: launch outside the seasonal peak, switch on integration monitoring and a monthly data quality report; revise the architecture once a year.

Formulas

MeasureFormulasNote
Three-year cost of ownershipTCO = Licenses + Implementation + 3 × (Support + Infrastructure)Add training, customization and downtime; the present value discounts annual payments at the cost of capital.
Present valuePV = One-time + Σ Annual ÷ (1 + r)^t, t = 1…3The rate r is set in your model; it shows that a subscription and a one-time purchase are comparable only in present value.
Data completenessCompleteness = Σ filled mandatory fields ÷ (Cards × Mandatory fields)Count by attribute group; the quality index is assembled from completeness, uniqueness, validity and timeliness with weights.

Formulas in notation

Data quality index
Q = Σ w_i · q_i / Σ w_i
q: the score for a dimension (completeness, uniqueness, validity, timeliness) from 0 to 100, w: the weight by business importance.

Worked example

A teaching comparison of three accounting system options: cost over three years, 30 users, a rate of 15%, thousand ₽

OptionOne-timePer yearOver 3 yearsPresent valuePer user a year
Standard 1C with customization4,2001,2007,8006,94086.7
Cloud service by subscription1,2002,0007,2005,76680.0
Industry ERP with an integrator9,5002,40016,70014,980185.6

The numbers are illustrative, contractor and subscription prices are not given: use your proposals. A subscription is cheaper at the start but catches up in price as users and terms grow; an industry ERP pays back when processes are complex and customizing a standard system is costlier.

Figures

Cost of ownership over three years
Bar chart: Standard 1C with customization 4,200, Cloud service by subscription 1,200, Industry ERP with an integrator 9,50005,00010,00015,00020,000Standard 1C with customizationStandard 1C withcustomizationOne-time: 4,200Annual over 3 years: 3,6007,800Cloud service by subscriptionCloud service bysubscriptionOne-time: 1,200Annual over 3 years: 6,0007,200Industry ERP with an integratorIndustry ERP with anintegratorOne-time: 9,500Annual over 3 years: 7,20016,700thousand ₽
  • One-time
  • Annual over 3 years
Data as a table
MeasureOne-timeAnnual over 3 years
Standard 1C with customization4,2003,600
Cloud service by subscription1,2006,000
Industry ERP with an integrator9,5007,200

Cost of ownership over three years. One-time costs and three-year payments by option: a subscription has no large first payment, for ERP it is the main one.

Card completeness by attribute group
Bar chart: Name and SKU 99.5, Size grid 96, Color 94, Composition and care 82, Photos to standard 75, Customs code (HS) 89020406080100Name and SKUName and SKUFilled: 99.599.5Size gridSize gridFilled: 9696ColorColorFilled: 9494Composition and careComposition and careFilled: 8282Photos to standardPhotos to standardFilled: 7575Customs code (HS)Customs code (HS)Filled: 8989Marking dataMarking dataFilled: 85.585.5Description and keywordsDescription andkeywordsFilled: 6363% of cards
Data as a table
MeasureFilled
Name and SKU99.5
Size grid96
Color94
Composition and care82
Photos to standard75
Customs code (HS)89
Marking data85.5
Description and keywords63

Card completeness by attribute group. The share of filled fields out of 2,000 cards: the weak spots are photos and description, they need closing before publication on platforms.

Data flow between systems. From product to sale and back to analytics: common dictionaries in the center, exchanges around.

  1. PLM: product → MDM and PIM: card
  2. MDM and PIM: card → ERP and 1C: accounts; OMS, site, platforms
  3. ERP and 1C: accounts → WMS: warehouse; BI: reports
  4. WMS: warehouse → BI: reports
  5. OMS, site, platforms → POS and till
  6. POS and till → BI: reports
  7. BI: reports

Specifics by category

Apparel
Apparel: size grid, color, composition and care, season and collection in the dictionary; one style has dozens of SKUs and an error in attributes multiplies.
Footwear
Footwear: the pair, the size system (RU, EU, US), width and last, heel height and material; footwear marking is mandatory, so codes and their movement are critical.
Accessories
Accessories: fewer sizes, more materials and types; item characteristics (belt length, bag size) in attributes, angle photos are mandatory for platforms.
Kids
Kids: age and height, age groups and safety certificates in the card; marking and certification requirements are higher, so completeness of these fields is critical.
Men
Men’s: standardized sizes, collars, lengths, a strict grid; fewer colors, more repeat orders of the base, so the dictionary is more stable and cleaner.
Women
Women’s: more styles, colors, size systems and fit versions; requirements for the card and photos are higher, and an error in the size table causes returns.

Common mistakes

  • A system is chosen from a presentation without describing processes → customization costs more than the license → first a functional map and a prototype on your data.
  • Brand: keeps product descriptions in different files for platforms → discrepancies and fines → a single card in PIM and a completeness check before publication.
  • Retail: moves dirty dictionaries into a new system → “garbage” migrates with the data → cleaning and common rules before migration.
  • Integrations without monitoring → errors are found by customer complaints → an exchange log, alerts and resending.
  • Launching a system at the seasonal peak → sales stop and stock errors → set the launch for a calm period and keep a rollback.

Russian specifics

  • Primary accounting documents and registers are kept under the accounting law; electronic document exchange is allowed provided the format and signature are met; check the requirements of e-document operators and formats in the current rules. Rule: Law 402-FZ of 06.12.2011: Federal Law of 06.12.2011 No. 402-FZ on accounting.
  • Data of Russian citizens is recorded and stored in databases located in Russia (the personal data law); take this into account when choosing cloud services and integrators. Rule: Law 152-FZ of 27.07.2006: Federal Law of 27.07.2006 No. 152-FZ on personal data.
  • Cash register equipment is used under the cash register law: a receipt is generated at the moment of payment and sent to the fiscal data operator; the till system must support marking requirements. Rule: Law 54-FZ of 22.05.2003: Federal Law of 22.05.2003 No. 54-FZ on the use of cash registers.
  • Marking of light-industry goods: codes, registration in the system, introduction into circulation and withdrawal; check the procedure and deadlines in the marking rules and decrees; integrations are done by an operator or an integrator. Rule: Decree 1956 of 31.12.2019: Government Decree of 31.12.2019 No. 1956 (marking rules for light-industry goods) (rule check not completed).

Open interactively →