Check product visibility, update permissions, location, loss classification, valuation dates and zero valuation settings before applying any shop stock correction.
Key takeaways before updating shop stock
- Start with product visibility before assuming a missing item needs no correction. An absent record does not confirm zero physical stock; it may indicate that the product lacks the history required for that list view.
- Check who holds update rights next. Account owners or team members with item and inventory permissions can update item availability, modifier availability, and stock counts on your point of sale, according to Square. Verify the specific user role before applying any count change.
- Finally, pin the correction to the right storage spot. Location is the specific location in the warehouse where a product is stored, as defined by Odoo. Selecting the correct location prevents misapplying adjustments across different warehouse zones.
| Check Area | Core Rule | Source |
|---|---|---|
| Product Visibility | Products without stock history are hidden from the Physical Inventory page | Odoo |
| User Permissions | Item and inventory permissions control updates to availability and stock counts | Square |
| Location Selection | Odoo defines location as the specific spot in the warehouse where a product is stored | Odoo |
Check missing products and stock update permissions first
Start by verifying whether the item you intend to correct actually appears in your inventory interface. According to Odoo, products that do not have a stock history do not appear on the Physical Inventory page. An absent product does not prove that it lacks physical stock; it may simply lack the historical data required for display. If you need to create a new inventory adjustment from this specific page, the documentation states to click New.
Before applying any changes, confirm that the user account performing the work has the necessary rights. According to Square, account owners or team members with item and inventory permissions can update item availability, modifier availability, and stock counts on your point of sale. Verify that the staff member currently logged in holds these specific permissions before they attempt to modify counts. The platform supports receiving, adjusting, and counting inventory from several supported interfaces. These include the Square Dashboard, the point of sale app on iOS devices, Square Terminal, Square Stand, and Square Register. Ensure the person making the correction is using one of these supported interfaces.
If a product is missing from your view, check its stock history status first rather than assuming an error in the count itself. Confirm the user role matches the permission requirements for updating stock counts. Use the New action on the Physical Inventory page to start the adjustment if the product is visible. If the product remains invisible, investigate why it lacks stock history according to your tool’s rules. Do not assume that absence from the list means the item is out of stock physically; it may just be hidden due to lack of history.
Correct the location and classify the stock loss
Before applying a stock correction, verify that the adjustment targets the correct physical storage area and the appropriate business entity. The system also tracks the company whose database receives these inventory adjustments. Confirming both elements prevents you from recording a count against the wrong facility or legal entity. If your shop operates multiple warehouses or serves different corporate databases, selecting the wrong context can misplace the entire correction.
When using Zoho Inventory, the workflow requires you to choose the warehouse in which the stock adjustment should be reflected. You then select the specific items whose stock you want to adjust within the item details section. This step ensures the quantity change applies to the right products in the right place. Always review the selected warehouse and item list before finalizing the entry.
Classifying the reason for the loss is equally important for accurate reporting. Zoho allows you to choose the account in which you want the adjustment to be reflected. For example, you can track losses due to theft or damage under a separate account so that reports provide clear-cut information. This separation helps distinguish between routine shrinkage and specific incidents like breakage or pilferage. While Zoho documents this account-based approach, other tools may use different classification methods. Square, for instance, supports custom adjustment reasons as a documented option. Do not assume that every tool uses the same method for categorizing losses.
If your shop experiences frequent damage or theft, setting up a dedicated loss account simplifies end-of-period reviews. This practice is an editorial recommendation based on the capability described in the Zoho guide; it is not a requirement of any single platform. Ensure your accounting team agrees on how these accounts map to your bookkeeping before making the first entry. Misclassifying a loss as a standard purchase or sale can distort your profit margins and inventory valuation.
Review valuation dates and zero valuation settings
A posting date that precedes the latest applied valuation date can create a quantity-value mismatch in average cost calculations. In a Microsoft Learn example, the posting date falls before the latest valuation date of applied value entries at 03-01-20. This scenario results in a situation where the quantity on inventory is zero, but the inventory value is negative, according to Microsoft Learn. To avoid such a quantity-value mismatch, the system sets the valuation date to equal the latest valuation date of the applied value entries, specifically 03-01-20, according to Microsoft Learn. After revaluation, the value in the Cost Amount (Actual) field becomes 10.00, meaning the quantity on inventory is zero, and the inventory value is also zero, according to Microsoft Learn. These figures illustrate how date alignment affects recorded values; they are not benchmarks for shop shrink levels or acceptable loss rates.
When reviewing a correction, check whether your tool’s valuation logic aligns posting dates with the most recent applied value entries. If a discrepancy appears between physical count dates and system valuation dates, verify which date the software uses for cost calculation. The example above demonstrates that misaligned dates can produce negative inventory values even when the quantity on inventory reaches zero. Ensure your adjustment workflow accounts for these temporal dependencies before finalizing stock changes.
ERPNext includes an explicit setting called Allow Zero Valuation Rate. This setting describes permission to submit a purchase document with a zero rate, not a recommendation to use zero rates for ordinary shop operations. Check this specific configuration before attempting to process items without assigned costs. Do not assume that enabling this option is advisable for routine inventory updates.
Illustrative example: a 3-unit count gap
Suppose the system shows 13 units of a product but a shelf count finds 10. Before changing the record, check that the item appears on the Physical Inventory page, that the person logged in holds item and inventory permissions, and that the adjustment targets the correct storage location. Only then enter the 3-unit difference, classified under a loss account if the cause is theft or damage.
Inventory correction reference table by publisher
The following table lists the specific documented adjustment features for each publisher. Use this reference when verifying which settings apply to your current stock count before applying a change.
| Publisher | Documented Adjustment Feature | Specific Quote Detail |
|---|---|---|
| Odoo | Missing products before correction | Products that do not have a stock history do not appear on the Physical Inventory page. |
| Square | Permissions before changing stock | Account owners or team members with item and inventory permissions to update item availability, modifier availability, and stock counts on your point of sale. |
| Zoho | Location selection | Choose a warehouse in which the stock adjustment should be reflected. |
| Microsoft Learn | Valuation dates and mismatches | A posting date that comes before the latest valuation date of applied value entries (03-01-20). |
| ERPNext | Zero valuation submission setting | Ticking on 'Allow Zero Valuation Rate' will allow submitting a purchase document even if the Valuation Rate of the Item is 0. |
| Zoho | Loss accounts and reasons | Choose the account in which you want this adjustment to be reflected. |
Review one proposed stock correction and check the applicable tool's product visibility, permissions, location and classification before applying it.
Record which tool checks apply to your correction
Review one proposed stock correction against the specific rules of the inventory software you use. Do not assume that a workflow in one system applies to another, as permissions and visibility settings differ by publisher. Start by identifying whether the item appears in the physical count view or if it lacks stock history. Then verify that the user performing the update has the correct role for the interface they are using. These two checks prevent errors caused by missing data or insufficient access rights before any numbers are changed.
Next, confirm the location context for the adjustment. Ensure the correction is applied to the specific company and storage location intended, rather than the current screen context. In systems like Zoho, this involves selecting the warehouse and items explicitly within the correction workflow. Misidentifying the location can result in adjusting stock for the wrong entity or area. After confirming the location, classify the reason for the loss or gain. Some tools allow tracking theft and damage under separate accounts, while others offer custom adjustment reasons. Choosing the appropriate classification ensures that reports reflect the true nature of the stock change. Your next step: pick one pending correction today and run it through these checks before you save it.
FAQ: mistakes when changing shop stock records
What inventory adjustment mistakes should I check first?
Check product visibility, update permissions, location, loss classification, valuation dates, and zero valuation settings before applying a correction. These six checks cover the specific risks documented in the tools' guidance. Start by verifying whether missing products lack stock history and who has permission to change counts. Then confirm the correct storage location is selected for the adjustment. Finally, review how losses are classified and whether valuation date mismatches or zero rates affect the record.
Does the missing-product warning apply to my Odoo Physical Inventory page?
Yes, products that do not have a stock history do not appear on the Physical Inventory page according to Odoo. This means an absent item does not prove it lacks physical stock. You must verify stock status through other methods if the product is missing from this view. The absence may reflect the tool’s display rule rather than the actual inventory count.
Who can update stock counts in Square?
Account owners or team members with item and inventory permissions can update stock counts on your point of sale as stated by Square. These users also manage item availability and modifier availability. Ensure the person making the correction holds these specific permissions.
How can Zoho separate theft or damage losses in reports?
Choose the account in which you want the adjustment to be reflected to separate these losses according to Zoho. Selecting a distinct account provides clear-cut information in your reports. This allows you to track theft and damage separately from other adjustments. Use this setting to maintain accurate financial categorization for stock discrepancies.
Can ERPNext submit a purchase document with a zero valuation rate?
Yes, ticking 'Allow Zero Valuation Rate' allows submitting a purchase document even if the Valuation Rate of the Item is 0 according to ERPNext. This is a permission to submit, not a recommendation to use a zero rate.