Top summary
Do not book every count difference as shrinkage. First prove the inventory record, isolate the cause, quantify the verified loss at the policy-approved cost, and retain the evidence that connects the operational event to the accounting adjustment.
- A physical shortage can be theft, damage, mis-pick, unrecorded return, or bad master data.
- Cycle counts are a diagnostic control, not merely a journal-entry trigger.
- Tax methods and inventory valuation require jurisdiction-specific professional review.
Who needs this workflow and what should they decide?
This workflow is for an ecommerce operator who has completed a warehouse or FBA cycle count and sees a difference between available inventory and the accounting/ERP balance. The immediate decision is whether to correct a data error, create an operational incident, or recognize a verified inventory loss in the current period.
Natural questions reviewed on 12 August 2026 included “How should I account for inventory shrinkage?”, “How do I record inventory shrinkage from a cycle count?”, “What is shrinkage and how should I account for it?”, “How should I handle customer returns in the books?”, and “Do FIFO/LIFO change the journal entry format?” from retail accounting guides, plus “What records do I need to support inventory?” and “How is inventory valued?” from IRS material. The final title is independently supported by recurring ecommerce accounting question wording in representative results and the IRS’s inventory recordkeeping guidance. It was selected because existing results often jump to a debit/credit entry without an evidence trail, a channel-location decision tree, or boundaries for tax-method changes.
What does the accounting framework actually require?
Under IAS 2, inventories are measured at the lower of cost and net realisable value, and inventory losses and write-downs are recognized as an expense in the period they occur. The IRS says records should include inventory purchases and supporting documents, and that a taxpayer using inventory generally needs a method that clearly reflects income. Those statements do not tell you that every scanner mismatch is a loss; they make accurate records and consistent measurement the control objective.
| Observed difference | First evidence to inspect | Likely route | Do not do |
|---|---|---|---|
| Units short after count | Count sheet, bin history, transfer log | Recount then investigate loss or transaction error | Write off before recount |
| Cost differs but units agree | Receiving invoice, PO, landed-cost allocation | Cost/master-data correction | Call it theft |
| Returns balance unexplained | Return authorization and disposition | Return, damage, or resale decision | Put all returns back into sellable stock |
| Marketplace stock differs | Channel movement and reimbursement records | Settlement/location reconciliation | Adjust the ledger from one report |
What is the cycle-count diagnostic tree?
- Validate the count. Recount blind, check unit of measure, and isolate damaged or quarantined goods.
- Validate the location. Compare warehouse, in-transit, third-party fulfilment, and returns locations separately.
- Validate transactions. Inspect receipts, transfers, picks, shipments, cancellations, returns, and manual adjustments from the last known good count.
- Classify the remaining difference. Use distinct labels: suspected shrinkage, damage, obsolete inventory, data correction, or timing difference.
- Approve and post. Apply the documented valuation policy, attach evidence, and assign a prevention action.
The useful insight is that “shrinkage rate” is an output after this tree, not an input that makes a variance acceptable. A rising variance in one SKU family may be a packing control issue; across all SKUs, it may instead be unit-of-measure or integration failure.
How do you calculate the adjustment without hiding the cause?
For a verified shortage, calculate verified missing units × approved unit cost. Keep a separate operational field for quantity and cause code; do not hide it inside a net inventory adjustment. The usual entry pattern is debit inventory shrinkage/variance or an appropriate cost-of-sales account, credit inventory. Exact account names, cost flow assumptions, and tax treatment depend on the company’s policy and reporting framework.
Hypothetical example, not a customer result. A cosmetics seller’s blind recount confirms 24 units missing from a 200-unit bin. The approved weighted-average cost is $18 per unit, so the provisional verified-loss value is $432 (24 × $18). The team finds 10 units were recorded as transferred to returns but never physically moved; those are corrected as a location/transaction error. The residual 14 units equal $252 and are supported by recount sheets, movement logs, photos of damage cages, and manager approval. Only that residual is considered for a shrinkage adjustment. This example excludes sales tax, insurance recoveries, marketplace claims, and any tax deduction; do not infer those outcomes from the calculation.
What should be in the count-to-ledger evidence pack?
- Count date, counters, blind recount result, SKU, location, and unit of measure.
- Book quantity before adjustment and the last confirmed count date.
- Movement extract for receipts, transfers, orders, returns, and manual edits.
- Cost basis, approval, journal reference, cause code, and corrective action owner.
- For third parties: their statement, claim/reimbursement status, and the cutoff used.
The IRS’s recordkeeping guidance emphasizes supporting documents such as invoices, receipts, and deposit records; build the pack so an operator or adviser can reperform the conclusion rather than trust a spreadsheet total.
How should inventory shrinkage be reported to operations?
Report it by location, SKU family, cause code, quantity, value, count date, and time since the last reliable count. A single companywide percentage hides whether the risk is a receiving dock, a return cage, a specific marketplace, or a data integration. The finance owner should report the accounting impact; the warehouse owner should report the prevention action and whether it was tested.
Set proportional investigation thresholds. A one-unit variance in a high-volume, low-value SKU may need a trend check, while one missing high-value serial-numbered item needs an incident review. Thresholds should not turn a known loss into an ignored loss; they should determine who investigates, how quickly, and what evidence is required.
Common failure modes after a count
Do not net positive and negative SKU variances before diagnosis; that can conceal both a receiving error and a loss. Do not use retail selling price when your reporting policy requires cost. Do not reuse a prior count’s cause code just because the amount is similar. And do not book a marketplace adjustment until you know whether the external party’s inventory report uses the same cutoff and disposition statuses as your books.
When should an operator stop and seek tax or accounting advice?
Stop before changing an inventory valuation method, estimating tax shrinkage, applying reserves, or making a material prior-period correction. The IRS explains that changes to a method of accounting for inventory shrinkage can require Form 3115 and a detailed description of the proposed method. IAS 2 and local GAAP/IFRS reporting may also require specific impairment and disclosure judgments. This article is a close-control method, not tax advice.
Self-check checklist
- Was the discrepancy independently recounted at the correct location and unit of measure?
- Have transactions since the last reliable count been reviewed before a loss label was used?
- Is the residual valued with the same policy used for inventory reporting?
- Can each posted adjustment be traced to an evidence pack and approver?
- Does the corrective action target the cause, not just the accounting symptom?
Sources and last updated
Last updated: 12 August 2026. Primary sources: IFRS Foundation, IAS 2 Inventories; IRS, Publication 334; IRS, Recordkeeping; IRS, inventory shrinkage method-change guidance. Caigeek can organize SKU/location data, reconciliations, evidence packs, and close checklists; a qualified professional should review policy and tax implications.
FAQ
Is every inventory variance shrinkage?
No. A variance can arise from receiving, transfer, unit-of-measure, return, listing, or count errors. Investigate the record before booking a loss.
What is the basic entry once loss is verified?
The common pattern is debit a shrinkage, inventory-variance, or cost-of-sales account and credit inventory, subject to the business's policy and accounting framework.
Can a US business estimate shrinkage for tax?
That is a method-of-accounting question with requirements. Seek qualified tax advice before changing a method.