How inventory sync works
Every place you sell or advertise keeps its own copy of your stock numbers: the website database, a marketplace listing, the till at a physical counter, a product feed in Merchant Center, a catalogue in Meta Ads Manager. Inventory sync is whatever keeps those copies agreeing after each sale, return, delivery and manual count.
Two mechanisms do the work. A scheduled push sends the whole stock file on a timer — simple, but it leaves a window in which the copies disagree. An event-driven update fires the moment a quantity changes, through a webhook or an API call, and narrows that window sharply. Most small shops run a mixture: live updates on their own site, and a slower refresh for feeds that the advertising platforms only recrawl periodically in any case.
The sync is only as good as the identifier it matches on. If the website, the feed and the warehouse spreadsheet each label the same item differently, quantities land against the wrong row. One stable stock keeping unit per variant is what makes the rest of the chain trustworthy.
Why inventory sync matters
Advertising spends money to send someone to a product page. If that page says available and the store room says otherwise, you have paid for the click, taken an order you cannot fill, and bought yourself a refund and an apology. The platforms police it as well: a feed that repeatedly offers items the landing page cannot sell risks disapprovals and account-level warnings, which cost far more than the single lost sale.
It matters more in Nepal than shop owners expect, because so much selling happens across a website, Instagram and Facebook messages and a physical counter at the same time, with the true stock number living in someone’s head or a shared spreadsheet.
Where inventory sync goes wrong
The usual failure is silent. A sync job stops running, nothing alerts anyone, and the numbers drift for weeks until a customer complains. Close behind it is double counting: stock reserved at checkout that is never released when the payment fails, slowly hiding items you actually have.
Bundles and variants break naive setups too. A kit that draws from three separate items, or a shirt in several sizes, needs the sync to understand the relationship rather than treat every listing as its own pile. And a feed refreshed far less often than the site will keep advertising yesterday’s availability whatever the website now says.
What to do about it
Pick one system as the single source of truth — usually the ecommerce platform or the order management system — and make everything else read from it rather than hold opinions of its own. Give each variant a permanent identifier and never reuse one. Then add monitoring: an alert when the sync last ran longer ago than it should, and a periodic comparison between platform stock and a physical count.
Decide in advance what happens at zero. Hiding the item, marking it unavailable, or accepting a backorder are all defensible; leaving it quietly buyable is not. Where feeds drive Shopping campaigns, treat availability as part of Merchant Center feed management rather than an afterthought.
