Negative stock: when to block an issue and how to correct it

What does “prevent negative stock” mean?

It might mean never taking physical quantity below zero, never selling reserved goods or never consuming a blocked lot. These are different rules. Specify which balance is checked and when: order creation, reservation, picking or issue confirmation. Explain whether an exception can be authorized, who approves it and which review stays open. A warning anyone can dismiss is not equivalent to a hard control.

Microsoft distinguishes physical negative inventory from financial negative inventory and warns that the former can affect costing. Its documentation describes a setting that prevents certain issues when insufficient stock exists. Verify the actual configuration rather than applying those rules to every program. Negative inventory reference.

Why does having pieces not mean you can issue them?

Evaluate matching dimensions at the source and destination. Ten pieces at another branch do not solve an issue from A-01. A new order should not borrow stock reserved for another customer or awaiting inspection. Ask the message to explain on-hand, reserved, blocked and available quantities. For those categories, see inventory between warehouses; here we test the point where an issue is allowed.

Worked example: two requests compete for four pieces

Run N01 and N02 from two sessions showing the same initial availability. The final check must allow only one issue while four pieces are available. Session order does not matter; the resulting balance does. R04 must then correspond to goods actually received and their document, rather than an invented receipt to unblock N02. Retain both responses, their identities and the history explaining the final ten-piece balance.

How do you correct an existing negative balance?

Investigate the sequence first: unrecorded receipt, incorrect unit, duplicate issue, wrong location or estimated consumption. Check physical goods against delivery documents, movements and times. If goods arrived, record or correct that receipt with evidence. If an issue was duplicated, reverse the identified duplicate. A count adjustment needs a reason and approval; directly setting stock to zero simply hides the difference. Retain the supporting document and the person responsible for the correction.

Odoo 19 lists products with movement history even below zero and retains adjustment and reversal movements. This supports investigation but does not prove that an installation blocks negatives. Adjustment documentation. If closed periods or valuation are involved, coordinate the correction with the person responsible for those records before changing earlier dates.

What should normal, exception and retry cases show?

• Normal: an issue within availability is confirmed and retains product, dimensions, user and reference.
• Exception: an insufficient issue remains pending or is rejected according to policy, without silently deducting a portion or releasing someone else’s reservation.
• Concurrency: repeat the two-session scenario, including imports or an integration if those can also issue stock.
• Retry: after a lost response, query the original identity. Repeating an accepted issue must not deduct again; changing its content must require review.

How can a real discrepancy become a test?

The issue control and correction worksheet records expected and observed behavior without modifying inventory. Pick an item with a recent negative balance and reconstruct three surrounding movements. The general guide and cycle counting help validate physical quantity. Put these rules in the scope of your inventory management system, including the exceptions your operation actually needs.