An ERPNext stock discrepancy often becomes visible when a storefront says an item is available but warehouse staff cannot pick it. The temptation is to enter a new stock count immediately. That may hide the symptom while leaving the underlying transaction error intact. The safer approach is to establish which stock figure each team is comparing and trace the documents that produced the difference.
On-hand stock and available-to-sell stock are different
Imagine a warehouse physically holds fifteen units but six units are already reserved for confirmed orders. The number available to offer may be nine rather than fifteen, depending on the business reservation policy. ERPNext Actual Qty and Reserved Qty describe different aspects of that position.
Not every warehouse can fulfil every storefront. Stock in a remote branch, quarantine location or in-transit warehouse may be physically present yet unavailable for a particular customer order. The stock figure published to a marketplace therefore needs an explicit warehouse and allocation rule.
Start with the Stock Ledger before adjusting balances
Check the Item, Warehouse, posting date and time. Review Stock Ledger transactions around the first reported difference. Receipts, Delivery Notes, Stock Entries, Stock Reconciliations, returns and cancellations can all explain quantity changes. Backdated entries may also affect calculations made for a past moment.
Do not assume that the latest row explains a historical discrepancy. Identify the last point when totals matched, then inspect the transaction sequence in the relevant warehouse and time range.
Check warehouse, batch and serial details
A warehouse transfer can make an aggregate total look correct while the picking location is short. For batch-controlled goods, staff may hold stock in one batch while the required batch is unavailable or restricted. Serial-controlled items require matching serial records for the specific physical units.
Quality inspection and expiry policies can also restrict stock. Confirm how FEFO or FIFO selection should work before changing the allocation rule to force a transaction through.
When to use Stock Reconciliation
Use Stock Reconciliation after counting the actual quantity and investigating the cause of the difference. Record the count date, warehouse, item and supporting evidence, and require appropriate authorisation for material adjustments.
Reconciliation is not a substitute for fixing duplicate receipts, delayed order events or incorrect warehouse mapping. Otherwise, a later integration retry may post the missing transaction and create another difference.
Avoid stock errors in multichannel integration
Choose which system owns physical stock and which system calculates available-to-sell quantities. Shopee, Lazada, TikTok Shop and Shopify each have their own listing identifiers and event rules. A stable SKU mapping and idempotent event handling prevent repeated updates from incorrectly changing internal quantities.
Do not blindly push zero to a storefront in response to a temporary API failure or mapping issue. Keep the agreed operational policy, an error queue and a recovery procedure so staff know when an exception must be reviewed.
A practical investigation checklist
Confirm the SKU and Variant mapping; compare the affected warehouse and posting time; inspect reservations and pending deliveries; review batch or serial restrictions; then trace the earliest relevant Stock Ledger difference. Record findings before deciding on a correction.
Use ERPNext Inventory and Warehouse Management for a broader design guide, or system integration services when the discrepancy originates between platforms.
