Development
E-commerce Architecture: 1C, ERP, Inventory, Prices and Orders Without Chaos
A 1C integration is not a line item in an estimate; it is part of store architecture. Learn which data belongs in ERP, what stays in the storefront, how to avoid selling unavailable goods and how to test exchange before launch.
In short
A reliable online store begins with one question: which system is the source of truth for product, price, inventory and order. Usually ERP or 1C owns accounting, the storefront owns search and user experience, while an integration layer guarantees repeatable delivery, error logs and safe retries. Before launch, test not only that a product appears but also cancellation, return, partial payment, price change and ERP outage.
Split system ownership before development starts
ERP and 1C are strong at accounting, purchasing, warehouses and financial documents; moving all that logic into the storefront creates two conflicting databases. The storefront must serve catalogue, filters, product pages and cart quickly without making the customer wait on an accounting-system query. Integration transfers changes through a contract: which identifier is stable, who may change price, how a removed product is handled and what happens to an order after payment.
Design exchange as an unreliable network
Exchange sometimes arrives late, twice or not at all. Every operation therefore needs an idempotency key, queue, status, last-success timestamp and a clear error owner. Catalogue and inventory should update separately: batch loading may be fine for catalogue, while critical inventory needs more frequent changes or a reservation during checkout. Once-a-day synchronisation may work for B2B pricing but is risky for fast-moving retail.
| Entity | Typical owner | Pre-launch control |
|---|---|---|
| Product and attributes | ERP / PIM | Stable ID and variant |
| Price and inventory | ERP / warehouse | Exchange lag and reservation |
| Cart and UX | Storefront | Mobile path to payment |
| Order and status | OMS / ERP | Webhook retry and cancellation |
Test the scenarios where stores lose money
Importing 100 products successfully is a weak test. Teams need scenarios where price changes during cart, one item remains in inventory, a payment webhook arrives twice, delivery rejects an order or ERP is unavailable. For each, define interface behaviour and financial outcome: what the buyer sees, what status the manager receives, where a task appears and who decides. This work reduces risk more visibly than choosing a CMS by name.
Measure integration quality after launch
Queue and error monitoring should be accessible beyond developers. The business team needs to see last-exchange age, products missing price or image, orders without status and cancellation share caused by unavailable inventory. These measures connect technical work to revenue and prioritise the next improvement: fix failures affecting money and customers before cosmetic mismatches.
Frequently asked questions
Can 1C be connected to an existing online store?
Yes, but first document current data sources and catalogue quality. A safer migration runs in parallel: first read and reconcile data, then enable limited exchange, and only then move critical operations.
Need a hand with this?
We do this work, not just write about it. Describe the task and we will scope it and send a staged estimate.
Related services
- E-commerce developmentA store is not a shop window, it is an operational tool: catalogue, payments, delivery, stock and orders have to work as one. We build it so your team can run it without a developer.
- Web app and Telegram Mini App developmentFor when a site is no longer enough and you need a product: an account area, a dashboard, an internal tool or a Mini App inside Telegram. We design the architecture, write the backend and frontend, and take it to release.
- IT consulting and product auditThe most expensive mistakes in software happen before the first line of code: a misread problem, a stack chosen out of a contractor’s habit, and a specification that does not exist. Consulting exists to settle all of that before the development meter starts running: what to build, out of what, at what cost and in which order. The result is a document, not an opinion on a call.
Read next
- What to Build Your Site On in 2026: Tilda, WordPress, Bitrix or Next.jsBuilder, CMS or custom code is not a matter of taste but of scenario and planning horizon. We break down three-year cost of ownership, the ceiling of each platform, and what it costs to move if you picked wrong.
- What a Website Actually Costs in 2026: The Estimate, Line by LineA practical breakdown of a web development estimate: what analytics, design, front end, back end and integrations actually cost, which expenses always show up after launch, and where cutting the budget is safe.
- End-to-End Analytics: Connecting Your Website, Ads and CRMStandard analytics shows clicks and leads, not money. A step by step guide to connecting your website, ad accounts and CRM into one system that reports real cost per customer, by channel.