A site and 1C: what to synchronise first

A site exchange with 1C is promised "so everything matches". On the first day it turns out the storefront price, the promo price and the accounting price are three different things, and warehouse stock is not the stock you can sell. Until the source of truth is named, synchronisation multiplies the argument.

A sensible first queue

• The catalog and the base price from accounting, if the store should not live in its own sheet.
• Stock with a rule: what exactly can be shown to a buyer and how often it is updated.
• An order into accounting after payment or after confirmation, not every abandoned cart.
• Images and marketing texts more often stay on the site. Accounting does not need them, and the storefront needs them to be decent.

A two-way exchange of everything in the first release is almost always early. The conflict of "who wrote the price last" is fixed by a rule, not by running more often. A nightly full exchange that takes the site down is worse than a rare and understandable one. A person has to see an exchange error, otherwise the storefront shows yesterday for a day.

Lexora starts with a map: which field has which source, and what travels in the first queue. 1C and the site each keep their own job, instead of an attempt to make them one organism in a week.