Browse all topics
Sync
Storefronts get the new number.
See step 7 in the Overview →How stock reaches your channels
Your storefront does not count stock; it repeats the last number Mossery sent it. Every stock movement queues an update for that product at that location, and a background worker sends it within about a minute. Nothing is sent unless the product and the location are both matched to that store and the connection is switched on.
Group products into a family
A family groups product codes that are versions of one thing, like a notebook in three colours. There is no separate button to create one: saving a new product creates its family automatically. Open the family, rename it and set its option names, then use Create product for new versions or Add product to pull in codes that already exist.
Publish a product to a channel
Publishing creates the listing on a storefront and connects it to the product in Mossery, so stock and price can flow out. Open the product, choose Manage sales channels, switch the channel on, and confirm. New listings arrive as drafts for you to finish. Publishing one product code publishes its whole family as a single listing with one variant per active code.
Mossery says one number and your online store says another
Most disagreements are not errors: a store only sees stock at the locations mapped to it, so retail counters and event stalls are excluded by design. If the number really is wrong, the direction decides the fix. A store showing too few is repaired on its own overnight. A store showing too many is never repaired on its own, and needs a push by hand.
A product shows 0 online, but you have stock
A product shows 0 on your storefront while you still hold stock for one of three reasons: it was never linked to that store, the stock sits at a location that store cannot sell from, or the last update is still sitting in the queue. Check them in that order — the first one accounts for most cases.
Sync errors are piling up and you need to know which ones matter
Sync errors are a log of things an integration could not finish. Nearly all are one of two shapes: something arrived carrying a product code your catalogue does not have, or it arrived from a store location nobody has mapped. Both are grouped by target and counted, so one line can stand for thousands of failures. Fix the mapping once, then re-check to close every matching error together.