On this page
- Troubleshooting: Stocktake Module
- Problem: Stock Not Being Deducted
- Problem: Product Was Set to 0 After a Stocktake
- Problem: Stock Level Is Changing While a Stocktake Is In Progress
- Problem: Duku Uploads Are Not Visible in HQ
- Problem: Product Cost Is Wrong
- Problem: Cannot Finalise Invoice
- Problem: Delivery Date Cannot Be Backdated
- Problem: Stock Was Added to the Wrong Location
- Problem: Unknown Barcode on Duku
- Problem: Large Variance After Stocktake
Troubleshooting: Stocktake Module
Having issues with the Stock Module? Find solutions to common problems below.
Problem: Stock Not Being Deducted
Why it happens: One of three things — the location has no Draws From rule, the product has a product-level draw rule pointing to the wrong location, or the product’s stock type is set to Uncounted.
Solution:
- Go to HQ → Site → Locations → Edit Details and confirm the location has a Draws From setting pointing to a stock location. Every location (including stock locations themselves) must have this set.
- Check HQ → Stock → Product Draw Rules to see if the product has a location-specific override that may be overriding the location default.
- Go to HQ → Products → Products, open the product, scroll to the Stock section, and confirm the stock type is set to Counted or Derived — not Uncounted. Uncounted products do not track stock levels or movements at all.
Problem: Product Was Set to 0 After a Stocktake
Why it happens: If a product is included in an in-progress stocktake but no count is entered against it, Paimnt treats it as a count of 0 when the stocktake is finalised.
Solution:
- Before finalising, review all product lines in the stocktake and remove any products you don’t intend to count (they should not have a line in the stocktake at all).
- If the stocktake has already been finalised, use Make Adjustment on the product in HQ → Stock → Stock Locations to restore the correct stock level.
- Going forward, only add products to the stocktake list that you intend to physically count.
Problem: Stock Level Is Changing While a Stocktake Is In Progress
Why it happens: This is expected behaviour. Sales, invoices, and other movements continue to update stock levels in HQ while a stocktake is open. The stocktake does not freeze live operations.
What to know:
- The stocktake captures a snapshot of the stock level at the start time, not at the time you finalise.
- Variance is calculated against that start-time snapshot — sales made during the count do not inflate the variance.
- You do not need to adjust your physical count to account for sales made while counting. Simply count what is physically present and enter that number.
Problem: Duku Uploads Are Not Visible in HQ
Why it happens: The stocktake tab in HQ was open before the Duku upload completed and has not refreshed.
Solution:
- After uploading from the Duku device, close the stocktake tab in HQ.
- Reopen the stocktake from HQ → Stock → Stock Takes.
- The product counts will now reflect the uploaded Duku entries.
This must be done for each staff member who uploaded from a Duku device, and for each location stocktake.
Problem: Product Cost Is Wrong
Why it happens: An invoice was entered with incorrect pricing, or the wrong costing method was used — most commonly New Cost was used instead of Average, which overwrites the existing unit cost across all held stock.
Solution:
- To correct the cost going forward: create a new invoice at the correct price using the Average costing method (the default).
- To immediately overwrite the current cost: go to HQ → Products → Products, open the product, scroll to the Stock section, and click Update Unit Cost next to the affected location.
Costing method reference:
| Method | What it does |
|---|---|
| Average (default) | Weighted average of existing + new stock. Use for almost all invoices. |
| New Cost | Replaces the unit cost with the invoice price and revalues all currently held stock. Use only to fix incorrect costs. |
| Bonus | Ignores this line for costing. Use for promotional or free stock that shouldn’t affect your standard unit cost. |
Problem: Cannot Finalise Invoice
Why it happens: The total entered in the Total Inc Tax field does not match Paimnt’s calculated total.
Solution:
- Check each product line for incorrect quantities or prices.
- If there is a minor discrepancy due to rounding between your supplier’s system and Paimnt, use the Manual Adjustment field (bottom left of the invoice) to enter the difference.
- For discount or surcharge totals not on a product line, use the Discount/Surcharge field rather than adding negative product lines.
- Do not finalise until the entered total matches the calculated total — this check is intentional to prevent finalising an incomplete invoice.
Problem: Delivery Date Cannot Be Backdated
Why it happens: The delivery date on a stock invoice cannot be set to a date before a stocktake that included any of the products on the invoice.
Solution:
- If you need to enter a delivery that occurred before a recent stocktake, the stock level adjustment will need to be handled manually using Make Adjustment on the affected products in HQ → Stock → Stock Locations.
- Where possible, enter invoices promptly so the delivery date does not need to precede a stocktake.
Problem: Stock Was Added to the Wrong Location
Why it happens: The wrong stock location was selected when finalising the invoice, so stock quantities were added to the wrong location.
Solution:
Use a stock transfer to move the quantity to the correct location:
- Go to HQ → Stock → Stock Locations and click Transfer Stock.
- Set From to the incorrect location and To to the correct location.
- Add each affected product and enter the quantity to move.
- Click Move and confirm.
Transfers automatically recalculate the weighted average unit cost in the destination location.
Problem: Unknown Barcode on Duku
Why it happens: The product scanned has no barcode assigned to it in HQ.
Solution:
- On the Duku device, assign a temporary name to the unknown barcode and continue counting. You can still enter a quantity against it.
- Upload the count to HQ as normal.
- In HQ, match the uploaded unknown barcode entry to the correct product so the count is applied correctly.
To prevent this in future, ensure all products have barcodes assigned in HQ → Products → Products before starting a Duku stocktake.
Problem: Large Variance After Stocktake
Why it happens: The variance is calculated from the stock level at the start time of the stocktake, not at the time of finalisation. Sales during the count are expected and do not inflate the variance. A genuinely large variance typically points to a count error, a data entry error, or unrecorded stock movements.
Solution:
- Recount the products with the largest variances.
- Check for data entry errors — wrong decimal places or misread quantities are common.
- Review stock movements in HQ → Stock → Stock Locations for any transfers, wastage, or adjustments recorded around the count period that may not have been accounted for.
Was this page helpful?
Help us keep the docs accurate and useful for your whole team.
