Stock on hand and availability
One row per SKU showing what Shopify holds beside what Landara has costed, why the two are different facts, and the two gaps worth acting on.
Updated 22 August 2026
Dashboard → COGS → Availability puts two different records of your stock side by side: what Shopify says you are holding, and what Landara has a cost for.
One row per SKU, expandable to its locations and the cost layers behind them, with a location filter and a SKU search.
Two views of the same row
The Cost / Availability toggle switches what the columns report.
| View | Columns | Source |
|---|---|---|
| Availability | On hand, Committed, Available, Difference | Shopify |
| Cost | Units, Avg cost, RRP, Margin, Value, Layers | Landara's cost layers, plus your Shopify selling price |
Available is derived as on hand minus committed. Landara asks Shopify for exactly those two numbers and calculates the third, rather than reading Shopify's own available field, because that field is only ever written to and can be stale.
Expanding a row shows each location, then every cost layer behind it: when it was received, which document it came from, the reference, units received, units remaining, unit cost and value. That drill-down is the whole point of the page. A number you cannot trace is a number you will not defend to an accountant.
Why the two sides are never reconciled here
These are different facts, and the page deliberately does not add them up or make them agree. Shopify's on-hand is what the store believes it is holding. Landara's position is the units it has a cost for. A SKU can legitimately appear in one and not the other, and the gap is a finding to look at rather than an error to fix on this screen.
That is why the difference column is informational. Turning drift into costed adjustments is a separate, deliberate action on Reconcile vs Shopify, where you can see each variance before anything is written.
The two gaps worth acting on
Above the table, Landara counts two things neither view shows on its own. Both are silent, and both cost you money later rather than now.
| Count | What it means | What to do |
|---|---|---|
| SKUs Shopify holds with no cost layer | They will report as uncosted COGS the moment they sell | Import the supplier invoice, or add a layer on the Cost Layers page |
| Costed positions Shopify does not report | A supplier SKU linked to a code the store does not use, or a SKU renamed in Shopify | Check the SKU alias and the renamed-SKU list on Cost Layers, or the stock has genuinely gone |
The first is the more expensive one. Nothing errors, nothing turns red on the COGS report: the sale simply costs nothing and your margin looks better than it is. See sales that cost nothing.
If you renamed a SKU in Shopify
Renaming a SKU in your Shopify admin splits the product in two as far as costing is concerned. Your cost layers keep the old code and stop depleting, so they sit there as stock that never sells, and sales of the new code find no layers and cost nothing. Both counters above move at once, for the same product.
Landara notices this on its own. Each time it syncs stock it compares Shopify's own internal id for the variant, which does not change when you rename, against the SKU it last saw. Anything that moved is listed on Dashboard → COGS → Cost Layers under "SKUs renamed in Shopify", with the number of cost layers stranded under the old code and a button to move them across.
Landara will not move them for you. Moving layers changes which sales they cost, and once in a while a rename is a SKU being reused for a different product, where merging the costs would be wrong. So it shows you what it found and lets you decide.
Detection runs when stock syncs, and that happens when you ask for it. If you rename SKUs in Shopify, run a stock sync from the Cost Layers page afterwards so Landara sees it.
Nothing is lost by finding this late. Landara works COGS out by replaying your movements rather than storing a figure, so sales that already went through uncosted are costed correctly the moment the layers move.
The second is usually a naming problem rather than a stock problem. Landara keys the ledger on your Shopify SKU and treats a supplier's code as an alias pointing at it, so an alias aimed at a code your store never used files receipts under a SKU nothing will ever sell.
What the feed does not include
Shopify does not report a location holding zero. A product sitting at zero on hand does not appear in the availability feed even if it has open orders against it. The page says so rather than implying the list is complete, but it is worth knowing before you conclude a SKU is missing.
How it relates to the other pages
| Page | Question it answers |
|---|---|
| Availability | How many units do I have, and how many can I sell |
| Valuation | What is my stock worth right now |
| COGS report | What did the stock I sold in this period cost me |
The Cost view's totals and the Valuation page agree to the cent, deliberately. Both sum the same unrounded figures and round once at the end, so two screens can never quote different values for the same inventory.
