Stores die when the website stock is a rumor. This track is inventory and order sync: products, prices, availability, and orders moving between the storefront and a warehouse, PIM, OMS, or ERP — without double entry. For CIS clients the ERP is often 1C; for English-speaking teams it is more often Shopify inventory, a WMS, a custom SQL database, or a mid-market ERP. Same engineering: idempotent jobs, structured errors, and logs you can debug at 2 a.m.

I start with a contract: which system owns the SKU, who owns the price, what happens to a paid order if the warehouse rejects it. Then we implement the connector (REST, queues, or official 1C exchange) and a reconciliation report. “We uploaded a CSV once” is not sync.

If the ledger is 1C, this page is the storefront half; the accounting-core work lives on 1C integration (including 1C and website integration). Bitrix shops almost always need this contour. Shopify shops need it when inventory is not native. Custom storefronts need it by definition.

Timeline: a narrow two-way sync (stock + orders) is often 4–8 weeks after credentials and object mapping exist. Cleaning a dirty catalog is extra and should be priced as data work, not “a plugin.”