The shrinkage journal entry: booking count variances from your adjustments log

Short answer: debit a shrinkage or inventory-loss expense, credit inventory — at cost, never at retail — and only book it after your adjustments log proves the number. The entry itself is five minutes of typing. The workflow in front of it is what keeps your books honest, because a shrinkage entry booked from a bad count is just a well-documented error.

What follows is the bookkeeping workflow from counted variance to posted entry, with a worked example. One scope note before anything else: this is educational bookkeeping mechanics, not tax advice — account names and treatments vary by jurisdiction and by how your books are set up, so have your accountant confirm the account mapping. Every entry below is labeled illustrative.

The workflow, from shelf to ledger

Five steps, always in this order:

1. Count. A cycle count or stock take finds a variance — the shelf holds less (or more) than Shopify says.
2. Adjust. Correct the quantity in Shopify using the reason field: Damaged for unsellable stock, Theft or loss for the unexplained, Count for the general counting correction. Every adjustment is recorded with date, quantity, and who made it — that log is your source document (Shopify Help Center, "Adjusting inventory quantities," accessed November 2026).
3. Value at cost. Multiply the variance units by the unit cost from your inventory records — the amount you paid, not the price you sell at. Retail never enters this entry; the inventory asset is carried at cost, so that's all that can leave it.
4. Book the entry. Debit the loss, credit inventory, split by reason if your chart of accounts allows.
5. Tie out. The entry total must equal the adjustments-log total for the period, filtered to the reasons you're booking. Zero difference, every month.

The order matters. Merchants who book first and adjust later end up with a ledger that disagrees with the operational record — and the operational record is the one with dates, staff names, and reasons attached. The fuller behavior of that trail, including system-generated activities versus manual ones, is covered in the inventory adjustments guide.

A worked example, end to end

Northbeam Coffee roasts and ships single-origin beans. November's cycle count of the warehouse turns up variances on two SKUs (all figures illustrative):

• CFB-ETH-1KG (Ethiopia, 1 kg bags): expected 48, counted 42. Unit cost $11.40. The four split-and-stained bags by the loading door are damaged; two are simply gone. Adjustment history: 4 units Damaged, 2 units Theft or loss.
• CFB-BRA-1KG (Brazil, 1 kg bags): expected 60, counted 51. Unit cost $14.10. Nine missing, no pattern, no damage on site. Adjustment history: 9 units Theft or loss.

Value at cost, from the log:

The entries, illustrative:

Entry 1 — damaged stock:

Entry 2 — unexplained shrinkage:

Splitting damage from theft in the chart of accounts costs nothing and tells you something: $22.80 of noise versus $126.90 of pattern is a different follow-up, and the ledger now surfaces it without a spreadsheet archaeology session. Note again what's absent: the $19.50 retail price of a coffee bag appears nowhere in either entry.

Perpetual or periodic: why your entry looks different

The size and visibility of the shrinkage entry depends on how your books track inventory.

Perpetual books (inventory adjusted with every sale — which is how Shopify itself tracks stock, and how most accounting syncs work): your inventory account is already declining with each unit sold, so shrinkage is invisible until you count. The count-based adjustment is the only thing that reveals it, which makes this entry both small and precious — it's the one moment a month where real, physical loss becomes a number.

Periodic books (inventory updated only at period end, COGS computed as beginning inventory plus purchases minus ending inventory): shrinkage is silent inside COGS — the missing bags simply inflate your cost of goods. The shrinkage entry here isn't correcting an asset balance so much as making the loss visible in the right line, so the operating numbers don't lie about margin.

Either way, the source of truth is the same: the counted variance, documented in the adjustments log, valued at cost. If you sync Shopify to accounting software, check where inventory adjustments land before assuming the entry is even needed — the mapping decides whether your monthly routine is booking a journal or verifying one.

Variations you'll actually hit

The count found MORE than the books. Positive variance gets the reverse treatment — debit inventory, credit a shrinkage recovery or income line — but investigate before celebrating: a surplus usually means a receipt or return never posted, and the real fix is upstream. Book the correction after you understand it, not before.

Damaged but still sellable at a discount. Stock that's flawed but not worthless isn't a full loss; it's a write-down to the lower value, with the markdown sale recovering the rest. The write-off versus write-down decision — where each lands and what each proves — is covered in the inventory write-off guide; the entry here is only the full-loss case.

Theft with an insurance claim. If a claim is filed for stolen stock, the recovery is its own entry when it's certain — debit the receivable or cash, credit the loss line — and your documentation trail is what the claim rides on. The records a claim requires live in the records layer, and the monthly export habit below is exactly what feeds it.

A recurring reserve instead of monthly entries. Some merchants accrue a monthly shrinkage estimate so the expense lands evenly. An estimate is fine as a management tool, but it should be reconciled to actual count-based adjustments each quarter — estimates in, actuals truing up — and that policy choice belongs to your accountant, not this template.

The tie-out: making the entry provable

The last step is the one that makes this audit-ready. Filter the adjustments log for the month to the reasons you're booking (Damaged, Theft or loss), sum at cost, and compare to the journal lines:

Export that filtered log and file it next to the entry — the export is the entry's source document, and the monthly archive habit that preserves it beyond the platform's 180-day history window is laid out in the inventory records guide. When book stock and counted stock need a fuller reconciliation than a single entry — timing gaps, in-transit units, unposted receipts — that's the stock reconciliation process.

And keep the framing straight: this article books the loss; it doesn't stop it. If the tie-out keeps finding the same reasons every month, the four-layer prevention stack — where shrinkage actually gets designed out — is the shrinkage prevention guide.

Common questions

Is inventory shrinkage an expense or part of COGS? Both treatments exist in practice. A dedicated shrinkage or inventory-loss expense line keeps the number visible month to month; folding it into COGS is common but hides the loss inside margin. Pick one with your accountant and stay consistent — the choice matters less than not switching between them mid-year.

Do I record shrinkage at cost or retail price? At cost. The inventory asset is carried at the amount you paid, so that's the maximum that can leave it when stock disappears. The retail price never enters the shrinkage entry — a $19.50 bag that cost $11.40 produces an $11.40 loss, no matter what the label says.

What if the count finds more stock than the books show? Reverse the entry: debit inventory, credit a shrinkage recovery line, valued at cost. But investigate first — positive variance usually means a receipt, return, or transfer never posted, and booking the surplus before you understand it papers over the real error. Correct the record after the cause is clear.

How do I record shrinkage without a physical count? Estimates exist — the retail method projects shrinkage from a cost-to-retail ratio — but an estimate is a management figure, not documentation, and should be trued up to actual counts with your accountant's sign-off. The count-based method is the defensible one precisely because the adjustments log documents every unit behind it.

Can my Shopify adjustments log serve as documentation for the entry? Yes — it records the date, quantity, reason, and staff member behind every adjustment, which is exactly what a source document needs. Two caveats: use the reason field every time, and export the log monthly, because product-level history only shows the last 180 days.

Next step

Run the tie-out on last month this week: filter the adjustments log to Damaged and Theft or loss, value it at cost, and see whether it agrees with whatever your books recorded — if they disagree, that gap is the real finding. Then put the monthly tie-out on the calendar, fifteen minutes after month-end close. If the number you just computed is bigger than you expected, the shrinkage prevention stack is where the next hour belongs.