Browse all topics
Something looks wrong
A number disagrees with reality — start here.
You recorded a delivery and the stock level did not move
Recording a delivery posts the stock immediately, so a level that has not moved almost always means you are looking at a different location: a delivery lands where the purchase order said it would, not at your default warehouse. Next most likely, the receiving is still Awaiting post and never posted, or you are waiting on costing, which never changes quantity.
A stock count does not match what is on the shelf
A count posts the difference between what you counted and what the app believed when the session opened. It never overwrites. So a mismatch usually means the session belongs to another location, or lines were left blank and stayed at the system figure. Less often the session is stale, or units are in transit and still on the books where they left.
A kit will not build even though the app says it can
Buildable is counted per location, so the usual cause is components sitting somewhere else: the headline figure on a product list is org-wide and can pair a part in one warehouse with a part in another. Next most likely, the kit contains sub-kits nobody has built yet, or component stock is already allocated to orders. An unapproved order blocks it too.
An order is stuck and you cannot tell why
An order counts as stuck when it is still unfulfilled fourteen days after it was placed. The app labels a reason and tests five in a fixed order: Missing SKU, Out of stock, Split shipment, Sync error, then Awaiting Shopify as the catch-all. Read the label first — it tells you whether the fix is yours or your storefront's.
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.
A page will not open, or the app keeps sending you somewhere else
Three different things look identical from the outside. Most often your role has not been granted the permission that page needs, and you land on a no-access screen. Second, two roles are mobile-only by design, so every desktop page bounces them to the mobile app. Third, any phone is sent to the mobile app whatever the role. Only the first is fixed by granting a permission.